Project help & AI training

Win the Race with the Last Mile.

Expert help for building with AI. We step in on your project, or we train your team to build their own.

Pick your lane

PROJECT HELP

You're building something. We'll help you ship it.

For founders, operators and small teams with a specific project. You built it with Claude Code, Codex, Cursor or Lovable. Now it has to survive real users, real money and people trying to break it.

We review it, fix what will fail, and step in to build alongside you until it's live.

Where most projects stall

AI gets you to 90% in a weekend. The last 10% is the product.

The first 90% is everything a demo shows: screens, sign-in, a checkout that takes test cards. The last 10% stays invisible until it fails. Where do your secrets live? Who can read whose data? What does a runaway loop cost, and who finds out first?

Most people who build with AI never get through that stretch. Talent isn't the problem. Nobody showed them the course.

We've run it. Now we coach it.

~/weekend-buildSPLITS
claude "build a SaaS that schedules social posts"
SPLITSTEP
0:18Scaffolded the app and database
1:05Sign-in with magic links
2:40Stripe checkout
4:12AI caption writer
6:55Live on a preview URL
90%
LATERFOUND AFTER LAUNCH
Day 3API key readable in the browser bundle
Day 4/api/posts returns every user's drafts
Day 6$2,180 AI bill from one runaway loop
Day 9Bad migration. No backup to restore.
Illustrative build. Every line after 90% is a common, real failure.

Who this is for

You're not a vibe coder. You're a software composer.

A composer doesn't play every instrument. They know how each one should sound, when it comes in, and when something is out of tune.

That's the job now. Claude, Codex and Cursor are your orchestra. You write the score. We train your ear, so what you ship holds up when people actually use it.

Vibe codingSoftware composing
Prompts until it runsKnows why it runs
Ships the demoShips the product
Hopes the keys are safeKnows where every secret lives
Hears about outages from usersHears about them from alerts
Starts over when it breaksRolls back in a minute
Can't explain the architectureCan defend it to a senior engineer

The route

The last mile, marker by marker.

Every engagement covers the same six markers, from mile 25.2 to the finish. Together they separate an app that runs from an app you can stand behind.

  1. MILE25.2

    Secrets

    Is your API key sitting in the browser?

    We trace every key, token and credential from your repo to your bundle to your git history, then move each one where it belongs and set up rotation.

    • Client bundle
    • Git history
    • Env variables
    • Rotation
  2. MILE25.4

    Access

    Signed in isn't the same as allowed.

    We test every route as a stranger, as the wrong user and as an admin, and we try to talk your AI features into misbehaving.

    • Authorization
    • Row-level security
    • Input validation
    • Prompt injection
  3. MILE25.6

    Data

    Could you restore yesterday?

    A backup you've never restored is a guess. We set up backups, run a real restore with you, and make schema changes safe to ship.

    • Backups
    • Restore drill
    • Migrations
    • Personal data
  4. MILE25.8

    Spend

    One runaway loop shouldn't cost you $2,000.

    AI endpoints without limits are an open bar tab. We add rate limits, hard caps, caching and a per-user cost you can actually read.

    • Rate limits
    • Spend caps
    • Caching
    • Cost per user
  5. MILE26.0

    Signals

    Find out before your users post about it.

    Errors that reach your phone, logs you can search, and uptime checks. When it's quiet, you'll know it's actually fine.

    • Error tracking
    • Logs
    • Uptime
    • Alerts
  6. MILE26.2

    Ship

    Deploy on a Friday. Calmly.

    Preview environments, automated checks and one-command rollbacks. Shipping becomes routine, and you get a runbook anyone can follow.

    • CI checks
    • Staging
    • Rollbacks
    • Runbook

Readiness check

What mile are you on?

Ten yes-or-no questions about the app you're building. Be honest. It runs in your browser, and nothing is saved or sent.

Mile 21.2 · See your result ↓

Project help · Virtual

Pick your pace.

One-on-one over video, on your real code. Start with an hour, get a full review, or bring us in to build it with you until it ships. You always work with a senior builder, never a junior handoff.

60 minutes

Pace Call

$295

A senior builder on a call with you and your repo. Architecture, stack choices, an AI workflow that ships, or the bug that ate your week.

  • Screen-share on your real code
  • Recording and written notes
  • 48 hours of follow-up questions
Book a Pace Call

Start here · 5 business days

The Teardown

$1,950

We review your codebase against all six markers, probe it the way an attacker would, and hand you a ranked punch list: what hurts first, how to fix it, and what to ignore.

  • Full code and infrastructure review
  • 90-minute live walkthrough
  • A fix plan written so Claude Code can work through it
  • A re-check after you fix
Book a Teardown

2 to 4 weeks

Bring It Home

from$7,500

We step in and build alongside you until it's live: secure, monitored and deployed on infrastructure you own. You keep the code, the docs and the skills.

  • Weekly pairing sessions
  • Fixes shipped alongside you
  • Deployed on Cloudflare or your cloud
  • Runbook and handoff
Talk about your project
TEAM TRAINING

Teach your team to build with AI.

For companies, nonprofits and small businesses. Hands-on training, in person or online, where your people build real tools for their own work with coaches beside them.

They leave with something that works, and the method to build the next one.

Who it's for

Companies

Engineers who ship safely

Engineering and product teams learn to build with AI and pass security review, using the same six markers we use on client projects.

Nonprofits

Tools you couldn't afford to buy

Program and operations staff build their own donor reports, intake forms and volunteer schedules.

Small businesses

Automations that run themselves

Owners and their teams automate the busywork: quotes, scheduling, follow-ups and bookkeeping prep.

Two formats, in person or online

For teams new to building with AI

The Clinic

1 day

One hands-on day. Everyone builds a working tool or automation for their own job, and learns the method to build the next one.

  • Discovery call to pick the right projects
  • Up to 16 people, two coaches
  • Everyone leaves with something that works
  • 30 days of follow-up in a shared channel
Request a Clinic

For engineering and product teams

Training Camp

2 days

Compose, then ship. Day one builds the workflow and architecture habits that hold up. Day two runs the last mile, ending with everyone deploying.

  • Built around your team's real projects
  • Up to 16 people, two coaches
  • Everyone ships to production on day two
  • 30 days of follow-up in a shared channel
Request dates

Both run in person at your office or a venue we arrange, or live online for distributed teams. Pricing depends on team size and format. Bring a laptop and a problem worth solving.

Training Camp, hour by hour

Compose

Day 1
  1. Warm-up

    Everyone demos what they're building in five minutes. We pick targets for the two days.

  2. The composer's workflow

    How we drive Claude Code and Codex on real work: specs, context, and checking the output.

  3. Architecture you can defend

    Data model, sign-in, where code runs, and what each choice costs you later.

  4. Build block

    Heads down on your own project, with coaches at your shoulder.

  5. Show the score

    Each person walks the room through what they built and why.

The last mile

Day 2
  1. Live Teardown

    We tear down one volunteer's app in front of the room, so everyone learns where to look.

  2. Miles 25.2 to 25.6

    Secrets, access and data, fixed in your own repo.

  3. Miles 25.8 to 26.2

    Spend limits, alerts, staging and rollbacks.

  4. Race day

    Everyone ships to production.

  5. Finish line

    Demos, a written punch list for each person, and what to do next.

Coaches

Coached by people who've run it.

We don't teach theory. We teach what broke on us, and how we fixed it.

Brian

Architecture & infrastructure

Took Allison and Neil from first prompt to production on Cloudflare. Coaches the parts that keep a product standing: architecture, security, deploys and cost.

April

AI workflows & velocity

Learned Claude Code in March and has made nearly 7,000 GitHub contributions since. Founders already hire her to show them how to really build with AI.

Join the bench

Senior coaches

Shipped an AI-built product to real users? We're building a bench of coaches who have. Tell us what you've shipped.

Field notes · Video

Building in public.

Screen-recorded builds from our own projects, with the code. First episodes coming soon.

Coming soon
NO. 01

How we built Neil on Cloudflare, from first prompt to production

Coming soon
NO. 02

Where AI-written apps leak API keys, and how to check yours in ten minutes

Coming soon
NO. 03

The Claude Code workflow we use for production work

Coming soon
NO. 04

Case 001: taking a social content studio the last mile

FAQ

Before you book.

Do I need to be a developer?

No. Most people we coach are founders, product people and operators who build with AI. We explain everything in plain language, and you leave understanding your own app better than when you arrived.

Is training only for engineers?

No. The Clinic is built for non-technical teams: operations staff, nonprofit program teams and small business owners. If you can describe your work, you can learn to build tools for it.

Do you come to us?

Yes. Clinics and Training Camps run at your office or a venue we arrange, and both also run live online. Project help is always virtual, so it works from anywhere.

Will you rewrite my app?

Almost never. Rewrites are slow, expensive and rarely needed. We fix what matters, in your codebase, and show you why.

What if my app isn't on Cloudflare?

That's fine. We review apps built with any tool and hosted anywhere. If you're still choosing where to deploy, we'll show you why we build on Cloudflare.

How do you handle my code?

Read-only access wherever possible, an NDA if you want one, and access removed when we're done. We don't paste your code into tools that train on it.

What if the Teardown finds nothing?

Then you get that in writing from a senior engineer, which is worth having when investors or customers ask.

One mile to go.

Tell us what you're building, or who you want trained. We'll reply with the right next step.

Or write to hello@lastmile.coach