The problem

Product truth lived in PDFs and sales WhatsApp threads. The public site could not filter by use-case, and RFQs arrived without site size, location, or timeline.

No structured product taxonomy
RFQ form too short for sales qualification
Weak mobile performance on product pages
Sales spent hours clarifying incomplete leads

The solution

We rebuilt Volks Energie around applications and equipment families, then wired a staged RFQ that captured project context before it hit the sales queue.

Our work

Product owners validated taxonomy weekly while Flexus owned UX, build, and measurement.

Catalogue & ICP workshops

Weeks 1–3 · Strategist + Sales

Mapped residential vs commercial buyers and the fields sales actually needed on first contact.

Product UX & content

Weeks 3–10 · Design + Content

Built application pages, equipment cards, and downloadable spec packs with clear CTAs.

RFQ flow & CMS build

Weeks 8–14 · Dev

Shipped filters, RFQ steps, CRM email routing, and performance fixes for image-heavy pages.

SEO & enablement

Weeks 12–16 · SEO + PM

Preserved ranking titles/metas, added internal links, and trained sales on the new lead SLA.

Team time invested

Cross-functional pod from discovery through RFQ stabilization.

Role	Focus	Hours
Strategist	ICP, RFQ rules	70
UX / UI	Catalogue + RFQ UX	140
Content	Product narratives	90
Developers	Build + integrations	240
SEO / PM	SEO, launch QA	70

Total Flexus effort: ~610 hours across 4 months.

Results

Qualified solar RFQs grew 2.4× versus the prior period. Sales reported fewer clarifying loops because project size and location arrived with the lead.

2.4× qualified RFQs
Higher sales acceptance of web leads
Faster first response on complete tickets
Product pages becoming a weekly pipeline chart

“We stopped chasing empty forms. Flexus made the website do the first qualification pass.”
— Sales manager, Volks Energie

RFQ-Ready Website for a Solar Equipment Brand