For builders

Build the thing.
Then build it again, better.

Whether you've never shipped a thing or you're three apps deep, this is where builders sharpen the second 20% — the part AI tools quietly skip.

First-time builders

Ship the first one without setting it on fire.

You're staring at a blank Lovable / Cursor / Bolt screen wondering what to type. Start with a button, not a system.

Where this lane usually trips

  • Scoping a 'system' when a button would do
  • Skipping access rules — your 'team app' is public to anyone with the link
  • No edit screen, so typos live forever

Start here

Your first internal tool

Build the small app that gets your team unstuck — without becoming an engineer.

First buildA weekendWalk it →

Growing builders

Past 'demo works,' onto real users.

You've shipped a thing. People actually use it. Now multi-user safety, real auth, and the spreadsheet you outgrew start to bite.

Where this lane usually trips

  • Two people overwriting each other silently
  • Bulk imports that swallow bad rows
  • No backup before you cut over

Start here

Replace a spreadsheet that broke under load

Turn the 47-tab spreadsheet everyone's afraid to touch into something that won't melt next quarter.

Growing builderA week of focused workWalk it →

Experienced builders

Tighten the last 20%.

You can read the diff. You know when AI is bluffing. You want sharper patterns, real RLS, and the migration path off the prompt-only loop.

Where this lane usually trips

  • Hidden URL ≠ secure (test as Client B)
  • Magic links that never expire
  • File uploads with no virus / size / type check

Start here

A simple client portal

Give clients one place to log in, see status, and grab the latest file — without you in the loop.

Growing builder10–15 focused hoursWalk it →

Built something useful? Pass it forward.

The next builder is two prompts away from your exact mistake. File the Fix, the Gap, or the Build Story they need.