Battery location on a solar-only quote. Removal costs when there's nothing to remove. EV charger specs when the customer never mentioned one.
If your quote form shows every field for every job, your team wastes time scrolling past stuff that doesn't apply — and eventually someone fills in a field they shouldn't, and it ends up on the customer's quote.
Static Forms Are the Problem
Most quoting processes use a fixed layout. Every field visible, every time. Your team has to mentally filter what applies and what doesn't.
It's slow — scrolling past 15 irrelevant fields on every quote adds up. It causes errors — when a field is visible but doesn't apply, people handle it inconsistently. And it's brutal for training new staff on a 50-field form.
What Conditional Logic Actually Looks Like
Smart forms reshape themselves as you go. Fields appear and disappear based on what you've already selected.
Real example from solar quoting: you start with the basics — system size, panel brand, inverter. Clean and simple. Select a battery, and five new fields appear: backup type, mounting location, wall bracket requirements, installation labour. Add an EV charger — another set appears. Remove the battery — all those fields vanish, along with any data entered into them.
The form only shows what matters for this specific job.
Cascading Dependencies
The real power is when fields depend on other fields in a chain.
Choose an inverter brand → the form filters to show only compatible battery models. Select single-phase power → three-phase-only products disappear. Pick a battery from a specific manufacturer → brand-specific requirements (wall brackets, control units) appear automatically.
Your team literally cannot quote an incompatible system. The form won't let them. No compatibility chart on the wall. No "let me check with the senior installer." The rules are baked in.
Works Across Every Trade
This isn't a solar thing. Same principle applies anywhere:
- Roofing: Select a profile → correct materials, screws, and flashings appear. Choose "existing roof removal" → demolition labour fields show up.
- Electrical: Switchboard upgrade → circuit count, phase type, board condition. Lighting job → fixture types, dimming, room quantities.
- Cleaning: Commercial windows → building height, access, frequency. End-of-lease → room count, oven, carpet steam.
The form moulds itself to the job, every time.
The Result
Fewer fields means faster quotes. No irrelevant fields means fewer errors. And when incompatible products are filtered out of dropdowns, nobody quotes a system that won't work.
Faster quotes that are right first time. No double-checking. No callbacks to fix mistakes.
Why This Has to Be Built For You
Conditional logic doesn't happen by accident. Someone has to understand your products, pricing, and compatibility rules well enough to encode them into the form.
That's what happens during Quotie onboarding — we build your pricing system with all the conditional fields, product rules, and cascading dependencies. Your team sees a clean, simple form. The system handles thousands of rules behind the scenes.
