Built By Dinner
by Joe Lee · Queensbury, NY
One afternoon · you + me · Claude Code

Your startup idea.
Built by dinner.

You show up at lunch with an idea. You go to bed with a working app at a real URL you can send to a customer. Not localhost. Not "coming soon." Live, on your own GitHub and your own Vercel.

4 hoursLunch to dinner
YoursYour GitHub · your Vercel
Side by sideNot built for you. With you
$1,500To start · 2 hours
How to book

Text me. That's it.

No form. No calendar link. Texts land on my personal phone and I answer them myself, usually the same day.

Scan with your phone camera. It opens a text to me with "I'm in" already typed. Add your idea in one sentence and hit send.
Goes straight to Joe · no bot · no VA
Text Joe: "I'm in"
Opens your Messages app with the text already written. Add your idea in one sentence.
The problem

Knowing how to prompt Claude Code doesn't mean you can ship.

You've watched the tutorials. You've started projects. You've gotten 70 percent there and then hit a wall. Some deployment issue, some auth headache, some bug that ate a whole Saturday.

Meanwhile your startup sits there. Half-built. Mocking you.

You don't have a skills problem.
You have a finish line problem.
The afternoon

What happens between lunch and dinner.

This isn't a course. It isn't coaching. It isn't me building it while you watch. It's you and me on a call, side by side, building and launching your MVP together.

01Hour one

Scope and setup

We scope your MVP ruthlessly. I'll probably tell you to cut 60 percent of your features, and you'll thank me later. GitHub, Vercel, environment, done. We start from my Next.js starter template so the boilerplate is already behind us.

02Hour two

Building

You're prompting Claude Code. I'm guiding. Features are shipping. You'll be shocked how fast this goes when someone who has done it a thousand times is sitting next to you.

03Hour three

Debugging, and learning how I debug

More building. We hit bugs. Good. I show you exactly how I work through them: how I screenshot errors, how I talk to Claude when it's being stupid, when to roll back. This is the part you can't learn from YouTube.

04Hour four

Deploy and launch

Deployment. Testing. Fixing what's broken. You push to production. Your MVP is live. Real URL. Real product. Ready for a real customer to break it.

What you leave with

Not a deck.
A product.

  1. A live MVP on your VercelNot mine. Yours. Your account, your domain when you're ready.
  2. Your code in your GitHubCode you actually understand, because you watched every line land.
  3. My starter templateAuth, user management, and the boring parts handled. Battle-tested on my own products.
  4. The Claude Code workflow I use every dayHow I build, how I debug, how I ship. The real one, not the demo one.
  5. The ability to keep goingAdd features. Fix bugs. Scale it. Without me.
After · included

One year inside Modern Creator Network

This is where most "build with me" offers fall apart. They build your thing, wave goodbye, and you're alone the moment something breaks. Not here. Your seat in the network is your safety net for the next twelve months.

  • Live sessions where you can ask about what we built
  • Direct help when you're stuck on a bug or a new feature
  • My latest Claude Code techniques as the tools change
  • A room full of builders, so you're not doing this alone anymore
Fit

Is this for you?

This is for you if

  • You've been sitting on a startup idea for months
  • You've tried vibe coding and can't seem to finish anything
  • You're done with courses that don't build your thing
  • You'd rather pay to compress six months into one afternoon
  • You want to own the code, the hosting, and the startup. No platform lock-in
  • You want "founder" in your bio and you want it to be true

This is not for you if

  • You don't have an idea yet. Go validate something, then come back
  • You want me to build it while you check email. This is co-building
  • You're shopping for the cheapest option. I'm the fastest one
  • You want to learn but don't actually want to launch anything
The investment

Two ways in. Both end with a URL.

Start with two hours
$1,500

See how it feels. Extend at the same rate if you want to keep going.

  • 2 hours of intensive co-building
  • Option to extend at the same rate, same day
  • One year of Modern Creator Network
  • My Next.js starter template
  • You'll know in two hours whether this is worth it
Hire a dev
$5K to $15K

Two to three months of back-and-forth. You still don't understand your own code.

Keep grinding
6+ months

Still no live MVP. Still stuck at 70 percent.

Built By Dinner
One afternoon

Live MVP, plus the skills to keep building. Plus you get to change your bio to "Founder" and mean it.

Questions

The ones everybody asks.

What if we don't finish?

We'll finish. I've been doing this for twenty years and I know how to scope. The whole point of an MVP is building the version that tells you whether anyone wants it. Features come later.

What if I'm a complete beginner?

If you can follow instructions, you can do this. The AI does the coding. I do the guiding. You do the prompting and the learning, and you leave understanding how it all fits together.

Why two hours to start?

Because you shouldn't have to commit to a whole afternoon with someone you've never worked with. Two hours in, you'll know. Most people extend on the spot. Sessions are booked as a commitment on both sides, so there are no refunds, and I hold up my end by making sure you leave with something real.

Can I send someone from my team instead?

Yes. Same price, same offer. Your team member shows up, learns the skills, and builds the MVP with me. You get the product and a trained team member.

Why text instead of a booking form?

Because I want to hear the idea from you before we pick a time, and because I'd rather you have my number than a calendar link. Text "I'm in" and one sentence about what you want to build. I reply personally.

Ready?

One afternoon.
Your MVP. Live.

Here's the whole process.

  1. 01Text me "I'm in" and your idea in one sentence.
  2. 02I reply personally, usually the same day, with a couple of questions and an afternoon that works.
  3. 03We build. You go to bed with a URL.
Text to book

Straight to my phone.

Got a question first? Same number. Ask.

Scan with your phone camera. The text is pre-written. Add your idea, hit send.
Goes straight to Joe · no bot · no VA
Text Joe: "I'm in"
Opens your Messages app with the text already written.