Prove the direction
One narrow audience, result, route, asset group, workflow, or setup decision. Best when the core question still needs validation.
Configure focused scopeWays To Work Together
Some projects need a direction and plan. Some need a launchable build. Others need a staged system with more review, integration, and operating detail. Start at the smallest level that produces a useful result.
Engagement Shapes
The configurator applies these sizes to all seven packages. A final quote still depends on source material, access, risk, and delivery requirements.
One narrow audience, result, route, asset group, workflow, or setup decision. Best when the core question still needs validation.
Configure focused scopeThe intended starter package with its core deliverables, responsive or platform-ready output, one review cycle, and organized handoff.
Configure standard scopeMore pages, assets, states, source material, roles, integrations, documentation, or training after the core result is clear.
Explain the expanded needSeven Starting Packages
Ranges are planning tools, not checkout prices. Configure the closest package and carry it directly into Project Intake.
What Changes The Range?
The package range assumes a first-version boundary. These are the common reasons a project moves toward an expanded scope or separate stage.
From Range To Quote
Choose the closest package, size, and common additions to expose the likely planning range.
Carry that package into Project Intake with the audience, goal, source material, timing, and current blockers.
Confirm access, unknowns, ownership, risks, revision expectations, and what explicitly waits.
Use the reviewed deliverables, boundaries, schedule, handoff, and payment terms as the project baseline.