madealone
← writing3 min

Seven products, no team, no funding

What it actually looks like to ship and maintain seven live products alone — the weekly shape, the trade-offs, and the three things I was completely wrong about going in.

soloprocess

There's a flavor of advice that sounds clever in a tweet and falls apart the instant a real customer is on the other end of it. "Just ship one thing" is one of those.

I run seven live products. They share infrastructure, a billing setup, and almost nothing else. People keep asking how that's even possible without a team, so here's the honest version — the parts that survived a year of editing, not the parts that look good on a slide.

7
live products
0
employees
0
dollars raised
~28
focused hours/week

The week, plotted

I block time, but loosely. Rigid calendars die the first time a payment processor has an outage on a Tuesday. The structure that actually held up looks like this:

  • Mondays — support, refunds, billing weirdness; anything with a customer waiting
  • Tue–Thu — one feature per product, chosen the Sunday before
  • Fridays — writing, marketing, talking to people I admire
  • Weekends — experiments that may or may not graduate into live products

Tip

The trick isn't the schedule — it's letting bad weeks be bad without re-architecting the calendar every time something slips. A week is a rounding error. A quarter is the unit that matters.

Three things I was wrong about

I went in with a set of confident assumptions. Reality corrected all of them.

I thought solo meant lonely, small, and simple. It turned out to be social, occasionally large, and never once simple.

I thought solo would mean lonely. It doesn't. People who buy software from an obvious single human treat you with a generosity teams never receive. I get more handwritten thank-yous than I have any right to.

I thought solo would mean small. It doesn't. Two of these products each clear more MRR than my last salaried job paid — combined. Bootstrapping just means the y-axis takes longer to feel real.

I thought solo would mean simple. It very much doesn't. The hard part isn't building. It's choosing what not to do, every single day, against the gravity of seven roadmaps that all want Wednesday.

Watch out

Seven is not a goal to chase. It's the number I happened to land on after killing two others. If you're starting out, the right count is one — then one more, only once the first one runs itself.

The shape of a real Wednesday

Not the highlight reel. The actual loop, repeated more than optimized:

  1. Coffee, then twenty minutes reading the support inbox before answering a single thing
  2. The one feature for the day, written in a single focused block
  3. Lunch on a walk, no phone
  4. Ship it — even if the polish isn't all there
  5. Two hours of deep work on whichever product is furthest behind
  6. One hour of marketing — usually writing, sometimes a thread, occasionally a small ad test

That's the whole output. There is no secret seventh hour where the magic happens.

The advice nobody asked for

If you're thinking about doing this:

Ship the thing. Then ship the next thing. The compound interest of "shipped" is the only currency that pays out when the team is just you.