Defined need
Use the quote builder when a Tech Bundle closely matches the outcome. Select useful options, submit the starting plan and receive a human scope review.
Clarity before complexity
A visible path from business need to working technology.
The exact activities change with the project, but the important decisions should never disappear inside a technical process.
Two sensible starting points
Choose a Tech Bundle or begin with discovery.
Uncertain or custom need
Begin with discovery when workflows, users, integrations or risks are still unclear. Discovery produces a buildable recommendation instead of an unreliable early promise.
The delivery method
Seven stages with clear decisions.
Fit and context
We begin with the business outcome, affected people, current process and any practical constraints.
Discovery and validation
We clarify requirements, assumptions, information readiness, integrations and the risks that could change the approach.
Recommendation and scope
You receive a proposed solution, inclusions, exclusions, starting estimate and delivery approach for review.
Experience and technical design
We shape the user journey, information structure and technical foundation needed for the agreed release.
Build in reviewable stages
The solution is implemented in manageable increments so progress and important decisions remain visible.
Test and accept
We test the agreed behaviour, work through feedback and confirm readiness against the written scope.
Launch, handover and care
We deploy the solution, hand over the agreed access and documentation, then provide the included support or an optional care plan.
How scope stays understandable
Assumptions and trade-offs remain visible.
Written inclusions and exclusions
The agreed scope states what the project covers and what remains separate.
Reviewable decisions
Material changes are discussed before they affect the delivery plan.
Proportionate quality controls
Testing, access, privacy and operational checks reflect the system’s actual risk and purpose.
Clear ownership after launch
Handover, support boundaries and ongoing costs are identified before the project is complete.
Project FAQs
Questions worth answering early.
Is the bundle-builder total a final quote?
No. It is a starting estimate based on the selected Tech Bundle and options. We review the plan and confirm the final scope and quote in writing.
When is discovery required?
Discovery is usually required when workflows, integrations, data, user roles or technical risks are not clear enough for responsible fixed scoping. Relevant Tech Bundles identify this expectation.
Can we start smaller than the full idea?
Yes. We generally recommend the smallest release that can produce useful evidence or operational value, while recording sensible future options.
How are changes handled?
Small clarifications within the agreed scope are handled during delivery. Material additions or changed assumptions are explained and agreed before they affect cost or timing.
Are third-party fees included?
Only when explicitly stated. Hosting, licences, app-store charges, model usage, paid integrations and transaction fees are commonly charged by their providers.
What support is provided after launch?
Each Tech Bundle lists its included defect-support or handover provisions. Ongoing monitoring, changes and improvements can be arranged through an appropriate care plan.