The partnership
You already know how the other version goes. Someone builds it, sends the last invoice, and six months later nobody can tell you why it broke at 2am. I am the opposite arrangement. I stay in the codebase, I keep the context in my head, and you never re-explain your product to a new person.
Five levels, from keeping the lights on to running your whole technical function. Prices are on this page because you should not need a call to find out what something costs.
Move up for a launch, move back down after. There is no re-onboarding, because I already own the whole thing.
Reactive upkeep: monitoring, security and dependency patching, incident triage. Keeps a product healthy between pushes.
Keep-alive plus a couple of small features or fixes a month. You direct, I execute.
The everyday tier. Steady shipping, about 3 to 4 features a month, plus design, monitoring, incident cover, and I review, clean, and merge your own PRs, up to about 8 a month.
Weekly cadence, about 6 to 8 features a month, plus your PRs reviewed, cleaned, and merged, up to about 16 a month. For a real push, a fundraise sprint or a launch.
Also called cofounder. I run your technical function across your apps and think about where the product goes next: roadmap, revenue, real opinions. A technical cofounder without the equity conversation.
These are a partnership, not a menu of hours. I bring the roadmap and flag what will actually move your revenue, rather than waiting for a ticket.
Most clients start for the building and stay for the peace of mind. If you are not sure which level you are, that is the call.
The person who writes your code is the person you message. There is no account manager in between and no junior picking up the ticket.
After a few months I stop asking what you want built and start telling you what I would build. That is the part you cannot buy by the hour.
You always know what I am working on, what it costs, and when it lands. If something slips, you hear it from me first.
Keeping a product alive and patched is real work. I keep doing it long after the launch excitement is over, which is why my clients are measured in years.
Plainly, so there are no surprises on either side. This is how every month runs, at every level.
Book a callWork lands in small pieces through the week, not in one monthly drop. You see progress arrive instead of waiting for a status update.
A short weekly note on what shipped and what is next, and a monthly summary you can forward to a board or an investor without editing it.
Change level month to month as your needs change. Nothing restarts, because I already hold the context.
Features, fixes, upkeep and review are the retainer. A whole new product, a migration, or a rebuild is its own quote, and I tell you before I start, not after.
If it is Keep-alive, I will say Keep-alive. If you do not need a partner at all yet, I will tell you that too. I would rather have the right clients for ten years than the wrong one for three months.
Not ready for a retainer? A Leak Check is a paid, written read of what you already have.