Services
What we build
New products, the systems behind established businesses, and the infrastructure that keeps both running. Four services, one team, and a fixed-fee way to find out what your project actually takes.
Product Engineering
From idea to production.
Design and build digital products, SaaS platforms, web applications and mobile experiences from concept through launch.
- You have committed to a launch date and have no engineering team behind it.
- A prototype proved the idea and now has to become a product people pay for.
- The requirements are clear to the founders, but not to anyone building.
Custom Software
Software built around your business.
Build systems around your workflows, processes and requirements instead of forcing your business into generic software.
- A critical process runs on a spreadsheet only one person fully understands.
- Your team re-keys the same data into two or three different systems.
- You pay for software that covers most of the job, and work around the rest.
AI & Automation
Put AI to work.
Build AI-powered features, intelligent workflows, agents and automation that improve products and business operations.
- A prototype impressed everyone, then met real data and has not moved since.
- Your team spends hours a week reading, sorting or copying information between systems.
- You are being asked what your AI strategy is and want a real answer.
Cloud & Infrastructure
Technology that keeps software running.
Design APIs, cloud infrastructure, deployment pipelines, observability and scalable technology platforms.
- Deploying takes a person, an evening and a certain amount of luck.
- The first report of an outage usually comes from a customer.
- Nobody has restored from a backup to confirm the backups work.
Who this is for
Four situations we're built for.
If one of these is yours, we can almost certainly help. If none of them is, tell us anyway — we will say so honestly rather than take the work.
- Founders taking a product to market
- You have a clear problem and paying interest, but no engineering team to turn it into software people can buy.
- Businesses that outgrew their tools
- The operation runs on spreadsheets, email threads and an off-the-shelf system that never quite fit.
- Teams that need engineering capacity
- You have a product and a roadmap, and more on it than your current team can deliver this year.
- Companies with software they can no longer change
- It still runs, but every change is risky, slow and dependent on one person who understands it.
Ways to work together
Start where the risk is lowest.
Most clients start with a discovery sprint, because it turns an unknown into a decision for a known fee. None of these require committing to the next one.
Discovery sprint
Find out what it takes before committing to build it.
A short, paid engagement that turns an idea or a problem into something you can make a decision on. You keep everything we produce, whether or not you build with us.
- Scoped requirements and a defined first release
- Technical approach and architecture
- Delivery plan with phases and a cost range
- The risks worth knowing about before you spend
Best for
New products, or a build big enough that guessing is expensive.
Product build
A defined outcome, delivered end to end.
We design, engineer, test and launch the product. Work is phased so you see something real early and keep seeing it, instead of waiting months for one reveal.
- Product design and engineering
- Working software in your hands every phase
- Deployment, monitoring and handover
- Documentation your team can actually use
Best for
Getting a product, platform or internal system into production.
Embedded team
Senior engineering capacity that stays.
We work as part of your team — your board, your standups, your priorities — with the scope set by the roadmap rather than a fixed statement of work.
- A named team, not rotating contractors
- Your tooling, your process, your repository
- Capacity that flexes as priorities change
- Knowledge that stays documented, not siloed
Best for
Live products with more roadmap than delivery capacity.
Rescue and modernisation
Take on software that has stalled.
We start with an honest assessment of what exists — what is salvageable, what is not, and what it would cost either way. Then we stabilise it and make it changeable again.
- Codebase and infrastructure assessment
- Stabilisation of the most urgent failures
- An incremental path off what cannot be kept
- A system your team can safely change again
Best for
Inherited, stalled or legacy software still carrying the business.
How we work
From problem to production.
The same five phases whether we are building a product, a business system or taking over something that has stalled.
- 01
Discover
Understand the business, users, requirements and problem.
- 02
Design
Define the product experience and technical direction.
- 03
Build
Engineer, test and iterate.
- 04
Launch
Deploy, integrate and get the product into production.
- 05
Evolve
Monitor, maintain and continuously improve.
Not sure which service you need? Most conversations start with the problem, and the service becomes obvious.
Describe your problemQuestions
The questions buyers actually ask.
Pricing, ownership, timelines and what happens when things go wrong. If yours isn't here, ask it directly.
- How do you price work?
- Fixed fee for discovery, phased fixed scope for builds, and a monthly rate for embedded teams. You get a cost range before any build starts, and we would rather tell you a number you do not like than discover it together halfway through.
- We don't have a specification. Is that a problem?
- No — it is the normal starting point. That is what a discovery sprint is for. You need to be clear on the problem and who has it; defining the solution is our job.
- Who owns the code?
- You do. All source code, infrastructure definitions and documentation are yours, in your repositories and your cloud accounts, from the first commit.
- Can you work with our existing team?
- Yes. We work inside your repository, your process and your review standards. Embedded engagements are built for exactly this.
- Can you take over an existing codebase?
- Yes, and often. We start with an assessment so that both sides know what is really there before anyone commits to a plan.
- How quickly can you start?
- A discovery sprint can usually start within a couple of weeks. Build capacity depends on what is already running — we will tell you honestly rather than book work we cannot staff.
- What happens after launch?
- Software is not finished at launch, it is only in production. We deploy it with monitoring and alerting in place, hand it over properly, and stay on for support or continued delivery if that is what you want.
- How do you handle security and data?
- Access control, audit trails, secrets management and encrypted data handling are part of the build, not a later phase. We are happy to work to your compliance requirements and sign an NDA before anything is discussed.
Have something worth building?
Tell us what you're building, what isn't working, or what you want to improve.