For founders
Early teams run lean. Some of what the company needs next, nobody has time to build: the team, the process, the platform. That’s what you bring me in for. The ending is set on day one, and when I leave, your team runs what I built.
What founders call about
The ops load. Eating the calendar you meant to spend on product.
Support. Tickets grow faster than revenue, and the same handful of questions are most of them.
Implementation. Enterprise deals close, then delivery drags, and the next deal waits on the last one.
The second business. Hiding in the platform you already built, with no one to build it.
The product hire. You need the function before you can afford the hire.
The shapes it takes
Read
The return that hasn’t shown up.
When something is broken and you’re not sure where: a support process, onboarding, a stuck metric. Two weeks from the outside, a fixed fee. Fixes come sized and assigned to your team, and what I find is yours whether you hire me again or not. If a build follows, it starts from the read.
Build
What the plan still needs.
What most founders come for. Name the thing: a customer success function that runs itself, an analytics engine, the first product team. I embed with your team, build it, and leave it running. A fixed fee, scoped together, with room for what we find along the way.
Turn
The number where it should be.
Outcome work, two ways in.
A new line on rails you already own. You built the platform for one business. I find the second business hiding in it and build it into a line that sits under you. I’m paid partly on what it earns: a share, for a set term, then it’s all yours.
A number that has to move. You name it: a revenue line, implementation time, the cost to serve each customer. We agree on the latitude I have, and my pay rides on moving it.
What the work looks like
From my decade as the operator, in the seats this practice is built on.
A support queue that answers itself
In the product and ops seat at an early-stage platform, every user question landed on my team. I built automated support over the platform’s own data: routine answers instantly, judgment calls routed to a human. The team got their week back, and the queue stopped scaling with headcount.
Implementation, from a month to a week
At the same platform, enterprise customers signed, then waited. I mapped every step between signature and go-live, killed the ones that only existed by habit, and turned the rest into a process the team runs without me. Typical implementation went from more than a month to under a week without adding headcount.
A new service line on rails we already owned
As operating lead at a shared mobility startup, I inherited a matching platform built for one business: shared taxis at the region’s transit hubs. I found the second business in it, a van share on a corridor the transit map missed, and launched it with a national operator in weeks.
Shipping a new service line in chaos →The first call
Two questions: what are you trying to make real, and how big is it. Thirty minutes, no pitch. If it’s not a fit, I’ll say so, and point you to someone who can help.
hello@auringon.com or book a 30-minute call →