Somewhere in a repository is most of an app. The developer moved on, the budget paused, or the build stalled a few features short of launch, and now it sits there, paid for and unshipped.

A demo that almost works
Ninety percent done for six months
A repository nobody can build anymore
A feature list with nobody building it
An App Store release that never happened

The first question is what you actually have. I read the code and give you an honest count: what’s usable, what’s missing, and how far launch really is. Sometimes it’s the last twenty percent. Sometimes starting clean is faster than untangling what’s there, and if that’s what I find, I’ll say so before you spend on the wrong plan.

Finishing can include

A written read on what exists
The remaining features, designed and built
The parts people forget: sign-in, billing, error states
App Store or web release, handled
Code and accounts moved into your name
Someone who stays after launch

Taking a started thing the rest of the way is familiar ground for me. mycharity: water began as a founder’s rough prototype; I built it into the platform that raised $500,000 in its first two months.

This is one shape of an existing product, picked up and moved forward. The full walkthrough, from first call to launch, is on the services page.

Also: iOS apps · Web apps · An existing product · Fractional work · All services

Let's build it

I'm taking on new projects. Tell me what you're working on and I'll tell you how I'd build it.

Get in touch

I read every message myself.