Build Paths

Signature paths for shaping the build.

Each path is the editorial spine for a common app idea — framing, examples, tool choices, prompts, what tends to break, what AI usually forgets to ask, launch checks, and decision questions.

First buildA weekend

Your first internal tool

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

Walk this path →

Growing builderA week of focused work

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.

Walk this path →

Growing builder10–15 focused hours

A simple client portal

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

Walk this path →

Growing builderA week of focused work

A team dashboard people actually open

Stop the 'where's the number?' Slack pings — give the team one screen they trust.

Walk this path →

ExperiencedTwo to three focused weeks

Turn a service process into an app

The 12-step process you documented in Notion becomes a guided product — without losing the human judgment that made it work.

Walk this path →

Growing builderAn afternoon of honest thinking

Build vs buy: a real framework

Stop pretending you're choosing on technical merit. Decide with eyes open.

Walk this path →

ExperiencedA focused day, then a week of muscle memory

Graduate from Lovable to Cursor

When the prompt-only loop runs out of room, what comes next — and what to bring with you.

Walk this path →

Growing builderTwo to three focused days

Add auth without painting yourself into a corner

Email, social, SSO — pick the one that fits, and make sure the access rules can grow with you.

Walk this path →

Growing builderA focused half-week

Get ready for real users

The unsexy checklist between 'demo works' and 'I gave the URL to 50 people.'

Walk this path →

Authoring next

These paths are queued. Want one bumped up? Open a request from the share page.