The right investment depends on the work that needs to be done. We start with the purpose, explore the complexity and shape a written scope before agreeing commercial terms.
A page count alone cannot describe a software project. These are some of the decisions that affect the effort and responsibilities involved.
Experience
Number of distinct journeys, roles, content types and interface states — including accessibility and responsive behavior.
System
Data relationships, integrations, authentication, migration and the constraints of the existing platform.
Delivery
Review responsibilities, dependencies, test coverage, release preparation and the handover the project needs.
Continuity
What happens after release: ownership, maintenance, support boundaries and future development priorities.
BEFORE WORK BEGINS
Put the important decisions in writing.
A useful proposal sets boundaries as well as direction. It makes the work and the decisions around it understandable to everyone involved.
Agree the goals, deliverables and exclusions
Identify access, content and integration dependencies
Define review points and acceptance criteria
Agree fees, payment milestones and change handling
Record ownership, handover and post-release responsibilities
COMMON QUESTIONS
Clarity before commitment.
Can we begin with a smaller scope?
We can discuss a useful first slice and the dependencies it still needs. A focused release should solve a complete problem without hiding the work required for later stages.
How are changes handled?
New requests need a shared decision about priorities, effort and timing. The written agreement should explain how changes are reviewed and approved.
Are ongoing costs included?
Hosting, software licenses, third-party services and ongoing support need to be identified separately in the proposal. Their ownership and payment responsibilities should be clear before work starts.
Can you estimate from an early idea?
An early conversation can establish the questions and assumptions that need resolving. A reliable scope requires enough detail about the journeys, systems and delivery expectations.
A CLEAR NEXT STEP
Let’s define the useful first step.
Bring the ambition, the question or the part that is still unclear. We can start there.
Discuss your projectDiscovery form preview — online delivery is not connected yet.