Product studio
Mobile apps, websites, AI workflow automation, and the systems behind them — designed, built and shipped by one small team that stays on the project after launch.
Week one, a plan. Week two, something you can open.
What that covers
Taking on new projects now
The short version
The hard part was never having the idea. It was the six months after it.
What we build
iOS and Android from one codebase, with native code where it actually matters. We handle store submission, updates and the crash reports nobody wants to read.
The site that has to convert, and the dashboard your team logs into every morning. Same team, same standard, no handover between them.
The repetitive work your team still does by hand — quotes, invoices, onboarding, support triage, weekly reports. We wire it into something that runs on its own and asks a human only when it should.
Accounts, payments, admin panels, integrations, the AI bits. The unglamorous half that decides whether the product survives its first thousand users.
How we work
Four stages, no mystery. You are holding working software in the first two weeks, and every week after that.
A week of hard questions. You leave with a written scope, a price and a date — or an honest reason not to build it at all.
Screens you can tap through before anyone writes production code. Changing your mind is cheap here and expensive later.
A build on your own phone every week. No month of silence followed by a demo that misses the point.
Store review, analytics, crash alerts, then the next version. The first release is a starting line, not a finish.
Why us
No account manager in the middle. The person answering your message is the one writing the code.
Every feature has to earn its place before it earns your money. Half the value of a studio is what it talks you out of.
If a model saves your user a step, it ships. If it exists for the pitch deck, it doesn't.
Your repositories, your accounts, your data, from the first commit. Walk away whenever you like and take everything.
The stack
The second product costs less than the first because nothing gets invented twice.
MOBILE
React Native with native modules where performance demands it, so iOS and Android never drift apart.
WEB
Next.js on edge infrastructure. Quick on a laptop, still quick on a phone with two bars.
AUTOMATION
Event-driven workflows with retries, audit trails and a human in the loop, so a failed step is visible instead of silent.
BACKEND
Typed APIs, managed Postgres, background jobs, and model calls with cost limits and a fallback when they fail.
Pricing
Three ways to work with us. No procurement maze, no quote that takes a fortnight.
On request
fixed fee, one week
We map the idea, the users and the smallest version worth shipping.
On request
per month
A dedicated team shipping a build you can install every week.
On request
per month, after launch
Someone still on call once the product is live.
Questions
With a paid discovery week. We map the idea, the users and the smallest version worth shipping, and you get a written scope with a fixed price and date. If we think it shouldn't be built, we say that instead — and you keep the document.
No. Most projects need an app, a site and something running behind both. We build all three, which is why nothing gets lost between three vendors blaming each other.
You do, from the first commit. Work happens in your repositories and your cloud accounts, documented for whoever picks it up next — including a team that isn't us.
Where it removes work: reading a document instead of asking the user to type it, answering instead of making them search, doing a step instead of adding one. Every AI feature ships with tests and a fallback for the day the model misbehaves.
Anything a person on your team repeats. Pulling data out of invoices and into your accounts system, drafting the first reply to a support ticket, chasing a document nobody sent, turning a week of activity into a report. We map the steps first, automate the boring ones, and leave a human approving whatever carries risk.
Discovery is a fixed fee. Build work is a monthly rate sized to the team you need, cancellable with 30 days notice. You get real numbers on the first call, not after three meetings.
Often. We start with a short audit of the code, the releases and the analytics, then tell you plainly whether it is worth rescuing or worth restarting. Both answers happen.
Because you can end it cheaply. Discovery is a fixed fee and a week of your time, the build runs month to month, and the code sits in your accounts from day one. The risk is a month, not a year.
Contact
A paragraph is enough. The reply comes from whoever would build it, and it comes with questions rather than a brochure.