Services
Product strategy, interface design, mobile and web engineering, store releases, analytics and long-term maintenance. All of it in-house, all of it sold as a fixed scope with a fixed price band, and none of it dependent on hiring a permanent team first.
What we build
We are a small studio on purpose. That means we say no to a lot of work — no CMS rebuilds, no marketing sites, no ten-person waterfall programmes. What is left is the thing we are genuinely good at: turning a product idea into software that runs in production and charges money.
The whole business in software form: onboarding, accounts, permissions, subscriptions, admin tooling and the dashboards you need to run it.
Native Swift and SwiftUI work with App Store review treated as part of the build, not an afterthought.
Kotlin and Jetpack Compose, built for the device spread that actually shows up in your analytics.
The interface your customers log into every morning: fast, keyboard-friendly and cheap to host.
Retrieval, summarisation and assistants wired into a product that already works — with a cost ceiling and a plan for being wrong.
Somebody has to renew the certificates, watch the error budget and shrink the cloud bill. A retainer buys a named engineer who does.
Everything above can be bought as a fixed-scope project, a two-week sprint, or a monthly retainer. Most clients start with one small paid discovery block so nobody signs a big number blind.
Compare engagement modelsAdd-ons
None of these are compulsory and we will tell you when one is not worth it yet. They exist because the same requests come up on most projects around week six.
Event taxonomy, funnels, activation and churn dashboards, wired so you can answer “is this working?” without asking an engineer. Usually two to four days of work.
Listing copy, keyword research, screenshot design and a structured test plan for both stores. The cheapest growth work available to a new app.
Authentication, authorisation, data retention, third-party processors and what your privacy policy has to say. Done before launch, not after an incident.
Cold start times, list scroll performance, query plans, image pipelines and the cloud bill. We measure first and only optimise what the numbers justify.
A structured week of walkthroughs, recorded sessions and a document written for somebody who has never seen the project. Included free with every retainer exit.
For investors and acquirers: an independent read of a codebase, its risks, its team dependencies and what the next twelve months would realistically cost.
How to buy
Most clients start with the first, move to the second, and end up on the third. You can also stop after any one of them with nothing owed and nothing locked.
How we work
Nothing about this process is proprietary and none of it is a secret sauce. It is simply the sequence that stops projects from dying: decide what to build, prove it cheaply, design the hard screens first, build in short cycles you can watch, then treat the launch as an engineering problem rather than a marketing event.
01
Forty-five minutes, no slides. You describe the outcome you want and who is supposed to pay for it. We ask uncomfortable questions about the users you already have, the budget you actually control, and the date that is non-negotiable. You leave with a straight answer about whether we are the right studio.
02
A paid block of one to two weeks where we turn the idea into something buildable: user flows, a data model, the integrations that will hurt, the features we recommend cutting, and a build plan with a fixed price band. If you walk away afterwards, the document is yours to take to anyone else.
03
Interface design in the real constraints: platform conventions, the smallest phone your analytics show, dark mode, empty states, error states and the accessibility rules that stop a store rejection later. We design the ugly screens first because that is where products die.
04
Code from day one against a real backend, with CI, tests on the paths that hold money, and a build in your hands every second Friday. You get a board you can read, a changelog written in human language, and an engineer you can message directly.
05
Beta through TestFlight and the Play internal track, a QA pass on real devices, privacy manifests and data safety forms filled in properly, store copy and screenshots produced, and the review process handled by us — including the appeal, if it comes to that.
06
Post-launch is where a micro-SaaS is won or lost. We instrument activation and churn, read the numbers with you monthly, ship the small changes that move them, and keep the infrastructure bill proportional to revenue rather than to ambition.
Service questions
Swift and SwiftUI on iOS, Kotlin and Compose on Android, React Native or Flutter when one team has to cover both, Next.js or Laravel on the web, PostgreSQL almost always, and boring managed infrastructure on AWS, Cloudflare or Fly. We pick for maintainability by whoever comes after us, not for what is fashionable this quarter.
We handle it — it is included, not billed as extra. In practice most rejections come from a handful of predictable causes: missing account deletion, unclear subscription terms, incomplete privacy answers, demo credentials that do not work, or a feature that duplicates system functionality. We check all of them before submitting, and we write the appeal if one still lands.
Scoping usually starts within one to two weeks of the first call. Full build slots open at the start of each month and we keep at most two running at a time, which is why the availability note in the header is real and not a scarcity trick.
One decision-maker who can answer questions within a day, roughly two hours a week for a demo and a planning call, and access to anything we cannot create ourselves — brand assets, existing accounts, domain records, third-party API keys. Projects that slip almost always slip on decisions, not on code.
Yes, and it is a large part of what we do. We start with a paid two-week audit: we read the code, run it, map the risky parts, and give you a written verdict on whether to continue it, refactor it or replace it. Sometimes the honest recommendation is “keep the data, rewrite the app”, and we will say so plainly.
Thirty days of fixes are included with every build. After that most clients move to a retainer, but it is genuinely optional — if you have an internal team, we run a handover week, record the walkthroughs, and hand you a document that assumes the reader has never seen the project.
Let’s scope it properly
Send us the shape of your idea and we will come back with a written scope, a realistic timeline, a fixed price band and the risks we would want to kill first. No decks, no discovery invoice, no pressure.