EPISODE 01 · 2026-09-05

Can AI build my LLC's invoicing app before lunch?

I'm forming an LLC and refuse to pay $30/month for invoices. So I gave Claude Code one prompt and a timer.

Try the appSource on GitHubThe promptWatch on YouTube

THREE minutes. That's how long it took Claude Code to go from an empty folder to a working invoicing app for my new business. One prompt, no code written by hand, and one bug that would've dated every evening invoice TOMORROW. Here's exactly what happened.

Why an invoicing app?

Some context. I'm forming an LLC this month for my apps, and the first boring thing every business needs is a way to send an invoice. The popular tools charge fifteen to thirty dollars a month, FOREVER, and I might send TWO invoices a month. So instead of subscribing, I gave the job to AI, with a timer running. This is App Before Lunch, and the question every week is the same. Can AI build the thing before lunch?

The prompt, word for word

Here's the prompt, word for word. It's in the description if you want to run it yourself. A single file invoicing app. No build step, no backend, everything saved in the browser. A business profile, clients, auto numbered invoices with line items and tax, statuses for draft, sent, and paid, an outstanding total, and a download PDF button that is really just a clean print stylesheet. Notice what I didn't do. No tech stack, no design system, no follow up questions. One paragraph and a list.

The rules

Three rules for every build on this channel. One prompt, no back and forth. The AI writes the code and the tests. And I only step in to report what I can actually SEE on screen, the way a client would, not a programmer. That last rule is the whole point. If it needs me to read the code, it didn't build the app before lunch.

First run, untouched

Eleven thirteen at NIGHT, I sent the prompt. Yes, night. The name of the channel is aspirational. About a minute later there was one file, index dot html, and this is it running, untouched. Empty state on the left, a prompt to set up the business. I filled in the LLC, added a client, and hit new invoice. It numbered itself I N V zero zero zero one, picked the client, and set the due date two weeks out. Line items add up as you type, the sidebar total updates LIVE, and the focus never jumps out of the field you are typing in, which is the thing most first drafts get wrong. Clean, light, and honestly nicer than I expected from one pass.

14 checks, written and run by the AI

Next, tests. I didn't write them either. Claude Code wrote a browser test that clicks through the whole app like a person would. FOURTEEN checks. Profile saves, client saves, the invoice numbers itself, totals come out to the cent, mark sent moves money into outstanding, mark paid moves it into paid this year, the PDF contains the right names and the paid stamp, duplicate makes a fresh draft, delete works, it all survives a reload, and the layout collapses at phone width. Fourteen out of fourteen on the first run. Which made me SUSPICIOUS.

The bug: it is already tomorrow

So I asked one more question. What happens if I create an invoice in the EVENING? Watch the issued date. It's nine thirty at night on September fourth, New York time, and the app dated my invoice September FIFTH. TOMORROW. Every invoice made after eight p m would've been dated the next day, the due date too, and the tests never caught it because they ran in the afternoon. That's a real bug that a real accountant would notice.

The fix: local date, not UTC

The cause is a CLASSIC. The code asked JavaScript for the date in I S O format, and that function answers in universal time. After eight p m in New York, universal time is already TOMORROW. I told Claude Code exactly what I saw, the invoice is dated tomorrow, nothing else. It found the line, explained the time zone problem, and replaced two lines with three that build the date from the local year, month, and day. Total time, under a minute.

Same time of day, fixed

Same clock, nine thirty at night, new invoice. September fourth. Due date two weeks out, on the correct day. Tests rerun, still FOURTEEN for fourteen.

Statuses, totals, and the PDF

Now the part that makes it an actual business tool. Mark an invoice sent, and it lands in the outstanding number at the top. Mark it paid, and it moves to paid this year. DOWNLOAD PDF hides the whole app and prints just the invoice. My business on the right, bill to on the left, the lines, the totals, my payment instructions at the bottom, and a big green paid stamp once it's paid. In a real browser that opens the print dialog and you save as PDF. No account, no watermark, no UPSELL.

Duplicate, shortcuts, delete

A few extras it added without being asked. Duplicate copies an invoice as a fresh draft with the next number, handy for repeat clients. Command N starts a new invoice, Command P prints the open one, and escape closes any dialog. Delete asks first. It even honored the keyboard friendly line from the prompt, which I half expected it to IGNORE.

Verdict

So, would I actually USE this for the LLC? YES. It does exactly what a thirty dollar subscription does for my two invoices a month. The lesson from this one isn't that AI is magic. It got all the boring parts right on the first try, and it still shipped a bug that its own tests couldn't see, because the tests ran at the wrong time of day. You don't need to read code to catch that. You need to use the thing.

Scorecard

Wall clock: 3 minutes to build, 1 to fix
Cost: $0 beyond my Claude subscription
Missing: export, email, recurring invoices

Scorecard. Prompt sent at eleven thirteen. Working app and passing tests by eleven fourteen. Bug found and fixed by eleven sixteen. THREE minutes of wall clock for the build, one more for the fix. Cost, ZERO dollars beyond the Claude subscription I already pay for. What is missing. There is no export or backup, so the data lives in one browser. No emailing an invoice from the app. No recurring invoices. All three are one more prompt away, and I will add export before I actually use it.

The prompt, word for word

Build me a single-file invoicing web app for my new LLC so I never pay $30/month for invoices. Requirements: - One index.html, no build step, no backend. Everything saves to localStorage. - My business profile: name, address, email, payment instructions. Shown on every invoice. - Clients: name, email, address. Pick one per invoice. - Invoices: auto-numbered (INV-0001...), issue date, due date, line items (description, qty, rate), tax rate %, notes, status (draft / sent / paid). - A list of all invoices with status badges and an "outstanding" total at the top. - "Download PDF" = print stylesheet that hides the UI and prints a clean invoice. - Duplicate an invoice, mark it paid, delete it. - Clean, light UI. Keyboard-friendly. Works on a phone.

Next: can AI build the machine that made this video?

This post is the episode's script. The narration in the video is an AI clone of the host's voice; the apps were generated by Claude Code and are shown as recorded. Tools: Claude Code on a paid Claude subscription, ElevenLabs on a paid plan, Remotion (free for individuals). Not sponsored.