Initial build
Define useful journeys and rules for a first version.
Explore the serviceEstimating guidance
Custom development depends on the decisions an application must make, the data it exchanges and the system it joins.
This page sets out quote factors, not a fixed-price offer or a promised outcome.
Two applications with similar screens can involve very different rules, access needs and integrations.
Teams planning a business app, an internal tool or an extension to existing software.
A new build, extension of a system or takeover requiring diagnosis.
They guide discovery; the exact work belongs in the quote.
Define useful journeys and rules for a first version.
Explore the serviceAdd a capability or connect a tool to existing systems.
Explore the serviceInspect an existing system before choosing fixes or changes.
Explore the serviceThe diagram separates interface, rules, data and dependencies to expose what needs examining before a proposal.
Which cases, exceptions and decisions must be represented?
Which screens and contracts connect people and systems?
Which data, permissions and obligations shape the work?
Which environments, checks and responsibilities are needed?
The diagram is educational; architecture, access and outputs are defined for each project.
Business rules, the existing codebase, data and interfaces drive the work behind the screens.
Quality of code, documentation and existing dependencies.
Number of cases, variations and business decisions.
Access, journeys and boundaries to verify.
APIs, contracts, errors and availability of connected systems.
Sources, quality and transformation of relevant data.
Acceptance scenarios and any handover to agree.
The proposal sets out the agreed functions, exchanges, rights and responsibilities for the project.
| Topic | Work to define | Decision to agree |
|---|---|---|
| Scoping | Work to defineJourneys, rules and assumptions to document. | Decision to agreeApprove priorities. |
| Design | Work to defineArchitecture options and dependencies to examine. | Decision to agreeChoose technical direction. |
| Delivery | Work to defineFunctions and integrations explicitly selected. | Decision to agreeBound access and environments. |
| Verification | Work to definePossible scenarios, evidence and handover terms. | Decision to agreeAgree acceptance criteria. |
This table illustrates scoping questions; only an accepted quote fixes scope, rights and commitments.
Rights, formats and handover terms are agreed in the quote or contract.
Technical decisions and limits, if requested.
Scenarios and observed results within the agreed scope.
Information useful for takeover when included.
Extra requests and external responsibilities need separate estimates.
Rules, data and dependencies need scoping for a useful estimate.
Rights of use, delivery and ownership are stated in the applicable contract.
Yes, after assessing code, access and continuity constraints.
Explain the use cases, known rules and systems involved; we can identify the choices that matter to the estimate.