Seven ways to work with us
Every engagement starts with the scope, the price and the risks written down before anyone commits — from a paid discovery week, or from your own spec if you have one. What follows depends on where your product is.
Web applications
Customer platforms, dashboards, marketplaces and portals. TypeScript end to end, a tested API layer, and a component system your future developers will recognise.
We build on React and Next.js with Postgres behind it. Boring, well-documented choices that any engineer can pick up.
Native mobile apps
Swift and Kotlin where the product needs the platform, React Native where a shared codebase is the better trade. We will tell you which one you need and why.
Store submission, review responses and release management are part of the work, not a separate conversation.
Custom CMS & internal tools
The systems your team uses every day and nobody outside ever sees: admin suites, content editors, operations dashboards, approval flows.
Built so a non-technical colleague can change what needs changing without raising a ticket.
MVP & rapid prototyping
Four to eight weeks from scope to a product real users can use. We cut features aggressively and keep the foundations, which is the opposite of most prototypes.
If the idea works, you keep building on what we shipped. If it doesn't, you found out cheaply.
Ongoing engineering partner
A retained senior team on a monthly basis. Roadmap delivery, architectural decisions, code review, and the heavy features an in-house team of two cannot absorb.
Also where our audit work lives: if you have inherited a codebase and need to know what you actually own, we will assess it and give you a plan.
Product discovery
A standalone engagement, run without any commitment to a build. We look at what you already have, what your team actually does each day, and where the time and money are going. That means user interviews, stakeholder interviews, and quantitative usage data read alongside the qualitative feedback rather than instead of it.
The output separates three things that usually get argued about together: where an off-the-shelf tool is already good enough, where a custom build is genuinely justified, and where an AI integration delivers a measurable efficiency rather than a demo.
Some discoveries end with us recommending you buy software rather than build it. That is a valid result, and cheaper than finding out later.
AI practice review
A review of how your team is actually using AI tools today: which ones, for what, and with what exposure. Most businesses find the answer is broader than they expected, because adoption happens person by person rather than by decision.
We identify where real time savings sit, where data is leaving the business without anyone deciding it should, and what good practice looks like written down for your team rather than in the abstract.
Two weeks, fixed fee, and the output is a document your team can act on straight away.
How engagements are shaped
One week, fixed fee
Scope, architecture outline and a costed build plan. Yours to keep whether or not you continue with us. Skip it if you already have a spec we can price against.
Fixed scope, fixed price
For builds with a clear finish line. Change requests are priced openly as they come up, never absorbed silently.
Monthly capacity
Agreed engineering days per month, rolling with 30 days' notice. Most clients land here after a first build.