Case study · Solo SaaS

KitTracker: A Solo-Built SaaS, Founder to Production

A web app for event kit managers to check equipment in and out at festivals, tours and live productions — designed, built and launched solo.

Next.jsTypeScriptNeon PostgresPaddle

The situation

Kit managers on festivals, tours and live productions need to know what equipment is where, who has it, and whether it came back — with a real audit trail, not a spreadsheet. KitTracker is a multi-tenant web app built to solve exactly that.

The approach

I designed, built and launched KitTracker alone, end to end: schema design, multi-tenant organisations and auth, Paddle billing, CSV import for onboarding existing kit lists, and real-time availability across a whole event.

First live pilot: Wildkind's 2026 season

KitTracker's first live pilot ran through Wildkind's 2026 season, at my day job — and it held up: kit checked in and out across live events without falling back to a spreadsheet.

Outcome

  • A production SaaS product live at kittracker.app — one person, full stack, from schema to billing.
  • Piloted through Wildkind's 2026 season — proof it holds up in the field.
  • Proof of end-to-end range: the same judgement applied to a client's platform applies just as well to a product built from nothing.
Let's talk

Facing something similar?

If this looks like a problem you're staring down, I'd be glad to talk it through.

Get in touch