Your product still has customers. It just stopped moving.

You stay the owner

Nothing about ownership changes. You keep the final say on anything that touches money, pricing, legal, or your brand.

We take over the tech

The backlog that's been sitting, the bugs, the modernization. The same engineering work we do for clients, pointed at your product.

We take over growth

Pricing, onboarding, retention, and acquisition run as one thing, instead of four disconnected projects nobody owns.

We're paid on growth

We agree a baseline on day one and sign it. We're paid on what comes in above that line, not on what was already working.

Fastest money first, slowest last.

1. 01

   Pricing

   Most neglected products are priced years behind the market. It's the fastest revenue in the building and it costs nothing to ship.

2. 02

   The backlog

   The fixes and the features your customers already asked for, actually shipped. Usually the reason they were leaving.

3. 03

   Onboarding

   Stop losing the signups you're already paying to get. The cheapest growth is the customers who almost stayed.

4. 04

   Acquisition

   The slow one, so it goes last. Content, outbound, and channels come after the fast wins are banked.

Growth isn't four projects.

Proof we can build is the easy part. Look closer at each of these and it's a business problem, not a bug: signups lost at the door, revenue leaking through billing, reviews bled out by crashes. That's the instinct we bring to operating.

ArtCopy

Lead developer · Mobile + Web · 2026

A realtime multiplayer drawing game. For a social app, the product working is the growth loop, and it was crashing and desyncing mid-game, quietly bleeding reviews and the reason people came back.

What it was costing them

• It crashed as canvases filled up, the exact failure that tanks a social app's reviews and kills its loop. We re-architected the engine so it holds up under real use.
• Multiplayer desynced mid-game, breaking the one thing people came back for. We rebuilt the queue so shared canvases stay in sync.
• The feed served the same posts twice, dead weight on the surface that drives time in the app. We de-duped it.

React Native · Expo · Next.js · Supabase · Skia · TypeScript

artcopy.app ↗

AceStudy

Reliability engineer · Web · 2025–2026

An AI study app we joined after launch. The build worked; the business was leaking, losing signups at the door and revenue through billing. We fixed the parts that touched money.

What it was costing them

• The app lost every new signup's work the moment they created an account. Money spent acquiring students, gone at the front door. We plugged it.
• Billing misfired across the weekly, monthly and yearly plans, revenue leaking on every tier. We made it charge what it was owed.
• The feature students came for froze under real use. We got the core product stable enough to charge for.

React · TypeScript · Firebase · Gemini · Stripe · D3.js

acestudy.app ↗

We turn down more of these than we take on. If any of the below is you, we'd say so on the first call.

There are no customers left

If the product has genuinely stopped being used, there's nothing to grow. We'd rather tell you that on the first call than take it on.

You want to sell next month

This moves in quarters, not weeks. If you're already in a sale process, we're the wrong call.

You don't want it touched

We operate. That means real changes to the product and the pricing. With your sign-off, but not with your daily involvement.