SERVICES
Three ways we work.
Most engagements need more than one of these. They are listed separately because they are priced and scoped separately, and because you should be able to buy only the part you actually need.
Product Advisory
Deciding what is worth building, before the expensive part starts.
WHAT IT COVERS
- Product strategy and definition
- Technical due diligence on an existing product or a company you are considering acquiring or investing in
- Architecture and code review
- Build-versus-buy analysis
- Roadmap sequencing
- Cost and risk modelling
WHEN YOU NEED IT
- You have a decision worth more than the cost of getting it right
- You have inherited a codebase and do not know what you are holding
- You are being quoted wildly different numbers by different firms and cannot tell which is realistic
- You suspect the thing you are about to build should not be built
WHAT YOU GET
- A written position with the reasoning exposed so you can disagree with it
- An explicit statement of what we would not build and why
- A recommendation on whether to proceed at all, including the recommendation not to
Design & Engineering
Taking it from blank page to production, and handing you the keys.
WHAT IT COVERS
- Product and interface design
- Front-end engineering
- Back-end and API engineering
- Infrastructure, deployment and monitoring
- Third-party integrations
- Quality assurance
- Release management
WHEN YOU NEED IT
- You know what you are building and need it built properly
- You have a prototype that will not survive real usage
- Your current team is at capacity and the work is on the critical path
- You need a small senior team rather than a large junior one
WHAT YOU GET
- Production software, deployed and running
- The complete source, documentation and credentials transferred to you
- No dependency on us to keep it running
Launch & Growth
Getting it in front of people, and measuring whether it worked.
WHAT IT COVERS
- App store optimisation and submission
- Analytics and event instrumentation
- Technical search engine optimisation
- Answer engine optimisation — making the product legible to AI systems that answer questions rather than return links
- Performance and Core Web Vitals
- Conversion work
- Iteration against real usage data
WHEN YOU NEED IT
- You have shipped and nothing is happening
- You cannot tell which parts of the product people actually use
- You are invisible in search, or visible in search but absent from AI answers
- You are making product decisions from opinion rather than evidence
WHAT YOU GET
- A product that is measured rather than assumed
- Instrumentation you can read yourself
- An honest account of what the numbers say, including when they say the product is not working
HOW WE BUILD
The technical approach, plainly stated.
Typed languages, end to end.
We use TypeScript across the front end and strictly typed languages on the server. The discipline of a type system catches an entire class of bugs before the code runs.
Automated testing on what matters.
Business logic, critical paths, and anything that has failed before. Test coverage is a consequence of writing testable code, not a metric we optimise.
Infrastructure as code.
Environments are defined in version control, not configured by hand. Every environment is reproducible from the repository.
Accessibility and performance as requirements.
WCAG compliance and Core Web Vitals targets are set at the start of a project, not retrofitted at the end.
Documentation for the next team.
We write enough that a team who has never seen the codebase can understand the decisions made and continue the work. That team may be yours.
Every engagement follows the same four-phase process — Position, Define, Build, Prove — so you know exactly what you are approving at each step.
See the four-phase processTell us what you are deciding.
The first conversation costs nothing and usually clarifies more than it commits. Send us the situation — where you are, what you are weighing, what is at stake — and we will tell you plainly whether we are the right people.