The right starting point
for the work ahead.
A focused prototype, a complete product or a next chapter. Start with the shape of the problem.
Define and prototype
Useful when the direction needs testing. Agree a focused question, a prototype and a decision-ready summary before committing to a larger build.
- A good fit for
- Founders testing a new product and teams deciding which workflow or customer journey to tackle first.
- Scope to agree
- A discovery workshop, a mapped key journey, a clickable prototype and a decision note covering assumptions, risks and a proposed first release. A prototype is not a production system.
- What to bring
- Your business goal, examples of the current experience, known constraints and one person who can make decisions. Sanitised sample data is enough to start.
Design and build
For a website, system or app with an agreed scope. The proposal identifies deliverables, milestones, assumptions and the responsibilities on both sides.
- A good fit for
- Teams launching a website, commerce experience, business system or app, with an owner available for regular reviews.
- Scope to agree
- Agreed interface designs, implemented features, integration work, testing on target devices, release preparation and documented handover. Source files, access and acceptance checks are listed in the proposal.
- What to bring
- Brand assets, draft content, priority requirements, the target platforms and an approval owner. Share system documentation first; grant scoped access securely when needed, not through this contact form.
Improve what already works
For a specific next release, integration or usability issue. First review the existing product and access, then agree a bounded piece of work.
- A good fit for
- Teams with an existing product facing a specific usability, performance, integration or maintenance problem.
- Scope to agree
- An initial technical review, a prioritised change list, the agreed update, regression checks and release notes. Ongoing support is a separate agreement, not an unlimited retainer.
- What to bring
- The current URL or demo, reproducible issues, available documentation and who owns hosting and code. We confirm access and constraints before quoting implementation.