Isaac Hess
Back to Isaac Hess

Consulting

I build the thing I wrote the guide about.

I built CageList on my own — schema, payments, bookings, the lot — and wrote down everything it cost and everything I got wrong. If you are building a marketplace, you can read all of that for free, or you can have the person who already made those mistakes make them on your project instead.

Read the whole guide first

Who this is for

Founders and operators building a two-sided marketplace — bookings, payments between two parties, supply that has to be onboarded and approved. The shape I have already shipped in production with real money moving through it.

Also for anyone who has a working business offline and needs the software version of it. That is what CageList is: batting cages that already existed, made bookable.

What that looks like

  • The foundation, not a demo

    The schema, the money columns, the double-booking constraint, the webhook dedupe, the access rules. The parts that are expensive to retrofit and invisible when they are right.

  • Your accounts, from day one

    You own every provider account and every key. I am a collaborator you can remove. Nothing about your business depends on my login.

  • Handed over properly

    A runbook for rotating any key, the full environment inventory, a real cost sheet, and a note on what is deliberately empty and why.

Tell me what you are building

I take a small number of projects. Tell me what it is and where you are, and I will tell you honestly whether I am the right person for it.