From wizard brief to scoped estimate
How a structured intake becomes a price and a plan—without inventing fake certainty
Clients rarely lack ideas. They lack a shared artifact that turns ideas into scope. Our service wizard exists to collect that artifact early—so an estimate is a reading of constraints, not a theatrical guess.
Intake that forces decisions
A useful brief names the offer path, must-have outcomes, constraints (timeline, integrations, content readiness), and what is explicitly out of scope. Vague adjectives—“premium,” “modern”—do not price. Decisions do.
The wizard’s job is to make those decisions legible before a kickoff call, not to replace conversation.
Map answers to estimate inputs
We translate structured answers into estimate inputs: surface area, complexity multipliers, care plan hints. The mapping is deterministic enough to discuss; it is not a promise that reality will never surprise anyone.
Brief fields that feed an estimate
- Offer path / package shape
- Must-have outcomes (not mood adjectives)
- Integrations and systems in play
- Content readiness (copy, media, product facts)
- Timeline pressure (relaxed / standard / urgent)
- Explicit out-of-scope items
- Open questions that stay visible on the brief
Price the unknown as a question
Open questions stay visible on the brief. We do not bury risk inside a single round number. Ranges and assumptions travel with the estimate so both sides can challenge them.
If a dependency is unknown (legacy CRM, migration, legal review), the honest move is a discovery slice—not a fake precision total.
From estimate to plan
Once assumptions are accepted, the brief becomes the spine of the delivery plan: milestones tied to outcomes, not to aesthetic mood boards. Changes to scope update the artifact—they do not vanish into chat history.
Final thoughts
A scoped estimate is a conversation with receipts. Structure the intake, map it transparently, keep unknowns named, and let the brief remain the shared source of truth as the work evolves.
Related Articles
How long a website project really takes (and what slows it down)
Realistic timelines by package—and the content, revision, and integration delays that stretch them
How to choose a web agency: 12 questions that expose vague proposals
Ask these before you sign—scope, hosting, SEO ownership, handoff, and maintenance
Ready to build something this considered?