Product development
We join at any stage.
Design to release, a stalled build picked back up, or a live product that needs someone to run it. One team owns the outcome either way — or bring us just the people instead on Hire.
02 · Already in progress
Take over a build.
A previous team stalled, moved on, or left you with a codebase you don't trust. We start with an audit — not a rewrite decision made before we've read the code — and take it from there.
- —A short paid audit first: what's salvageable, what isn't, and an honest read before anything changes in production
- —Keep what works — we don't default to a rewrite just because the code isn't ours
- —Two-week sprints from there, same as a build from zero, staged against software you can open
- —Code, repository and IP are already yours — nothing changes hands, we just start committing to it
03 · Already live
Run what's live.
It shipped, and now it needs someone to keep it up — releases, store review cycles, the bug that only shows up on one Android version. We run our own two products this way, so none of it is theoretical.
- —Rolling retainer, resize with a month's notice — not a fixed scope, because upkeep isn't one
- —Store releases and review cycles handled, including the rejections
- —Someone who knows the codebase when something breaks at an awkward hour
- —Growth work too, if you want it — the same people who ship it can move its numbers