The first version did its job: it got you customers. Now there are a lot more of them, and the software built for launch is struggling.

  • Pages that get slower every month
  • Timeouts on your busiest days
  • The query someone warned you about
  • Manual steps that made sense at ten customers
  • An infrastructure bill growing faster than revenue

Before anyone rewrites anything

A rewrite is the obvious answer, and it’s usually the wrong one. Most growth problems come down to a few specific places.

  1. Measure

    I find the real bottlenecks by measuring rather than guessing: a query, a job that runs too often, an architecture call that was right at the time.

  2. Fix in place

    Where possible the fix happens inside what you already have, and I rebuild only the part that has to be rebuilt.

  3. Rank the fixes

    You get the findings in writing, with each fix's cost, so you can decide what's worth paying for.

Where I’ve done this

I’ve seen both ends of this. My own Little Memory grew past a million saved entries on infrastructure that had to grow with it, and I’ve built inside systems at the other extreme of scale, like Twitch’s.

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

Tell me what you're working on

I've got room for a few new projects. Write to me and I'll reply with how I'd approach it. I read every message myself.

hello@nerdtower.com