Pennant Blinds: A Product Configurator That Replaced Quote Calls
Pennant Blinds designs, manufactures and installs custom window furnishings across South East Queensland. Before the rebuild, every enquiry started with a repetitive quote call — visitors needed to know 'what does this actually cost?' before they'd book a measure. We built a product configurator that answers that question directly, so the calls that do come through are already qualified.


The Results
Illustrative outcomes reported by the client following the redesign. Figures reflect first-party observations, not independently audited metrics.
The Challenge
- Every enquiry started with the same conversation about product options, fabric and indicative pricing — hours of repetitive quote calls per week.
- The old site had photo galleries but no way to explore blinds by type, room or budget — visitors couldn't self-serve into the right category.
- The measure-and-quote booking form was one-size-fits-all, so it didn't capture the details that matter (window count, product interest, install urgency).
- No structured product data meant the site missed out on Product-rich results and category-level search intent.
The Approach
- Built a product configurator: pick the blind type, choose fabric/opacity, select room and get an indicative price range in real time — no login, no wait.
- Restructured the site around product-type hubs (roller, roman, plantation, honeycomb, outdoor) so each category is its own SEO landing page.
- Split the enquiry flow into two paths: 'Get a measure' for decided buyers, and 'Save my selection' for researchers who want to come back later.
- Added Product schema to every product-type hub so Google can surface indicative pricing directly in search results.
What We Built
Real-time configurator
Blind type + fabric + room returns an indicative price range instantly — no login, no wait, no quote call.
Product-type hubs
Dedicated pages for roller, roman, plantation, honeycomb and outdoor — each a proper SEO landing page.
Two-path enquiry flow
'Get a measure' captures decided buyers; 'Save my selection' captures researchers with an email for later follow-up.
Product schema per hub
Product + Offer JSON-LD so Google can surface indicative pricing and product carousels.
Saved selections
Visitors can email themselves their configuration — bringing them back to a warm session instead of a cold restart.
Fast Core Web Vitals
Configurator runs client-side after a lean initial payload — sub-2.5s LCP on 4G, no layout shift.
"The measure appointments we book now already know what they want and roughly what it costs. The quote calls have basically disappeared."
Key Takeaways
- For custom products, a configurator that shows indicative pricing removes the biggest friction step in the sales cycle.
- Product-type hubs (roller, roman, plantation) rank far better than a single blended 'products' page.
- Give researchers a way to save progress — they come back with intent, not cold curiosity.
- Product schema is under-used in home-services; even indicative pricing in the SERP lifts CTR.
Technologies Used
Frequently Asked Questions
Do product configurators really reduce quote calls?+
Yes — for made-to-measure products, the biggest friction is 'what does this cost?'. A configurator that returns an indicative price range answers that question directly, so the calls that do come through are already qualified and much shorter.
Won't showing pricing scare customers away?+
The opposite in our experience. Custom-product buyers know custom costs more than off-the-shelf — what they can't handle is uncertainty. A price range with clear inclusions filters out mismatched enquiries and warms up the right ones.
Why product-type hubs instead of one products page?+
Because each product type (roller, roman, plantation, honeycomb, outdoor) is its own search category with its own intent. Splitting them into hubs lets each rank on its own head term and long-tail queries, and lets visitors self-serve into the right category quickly.
How long does a configurator build take?+
Pennant Blinds shipped in about twelve days including five product-type hubs and Product schema. Configurator scope drives most of the timeline — pricing logic complexity matters more than page count.
What tech was used?+
React with TypeScript, Tailwind CSS, Supabase for enquiry and saved-selection data, vite-imagetools for AVIF/WebP. Product + LocalBusiness schema across product hubs.
Let's Bring Your Vision to Life
From stunning websites and powerful web apps to e-commerce stores and digital marketing — we're here to help grow your business online.