Shipped in a week. Big deal?
Look, we’ve all seen these ‘build in X days’ flexes. Week 8 of NanoCrafts curriculum: AI invoice generator. Natural language in, pro PDF out. No forms, no fuss—or so the pitch goes. But let’s poke it.
The guy’s coming off Resume AI Tailor. Full-stack beast with Stripe, auth, DB. Patterns locked in. Question: can he rinse, repeat for something fresh? Invoice tool. Small. Useful. Type a sentence, boom—PDF. Smart test. Or just low-hanging fruit?
Can Regex Outsmart Human Mess?
Here’s the hook. Ditch the form. Say: “Invoice Acme for 10 hrs at £100/hr.” App grabs client, hours, rate. Currency from symbols. Fast. Free. No AI lag.
Tier one: pure regex. Covers most slop people type.
Invoice Acme for 10 hrs at £100/hr
Bill TechCorp 5 hours at $75 per hour
Charge Wonka Co 3hrs £120/hr
Send invoice to Globex for 8 hours, rate £50
High confidence. Green badge. User trusts it. Fail? GPT-4o-mini steps in. Structured JSON out. Yellow badge—“AI-assisted.” Same form either way. Edit if needed. Neat UX trick. Tells you without nagging.
But regex? It’s brittle. Throw in typos, slang, emojis—crumbles. “Invoice to BigCo, 12h @ $90 bucks.” Fails hard. AI fallback saves it, sure. Costs tokens. Scales? Pray for regex wins.
And that unique bit nobody mentions: this echoes 90s screen scrapers. Remember pulling data from emails with awk scripts? Same vibe. Quick win then. Dinosaur now. History says: bolt on forms eventually. Or die trying.
Short para. Boom.
Now sprawl: the parser shines for 80% cases — that’s the Pareto punch — yet real invoices? Discounts. Multiple lines. Addresses. VAT tweaks. This one’s single-line, hours@rate only. Cute prototype. Production? Users demand tables, notes, your logo (upload? Ha). Week eight glosses that. Focus on speed, not stickiness.
PDF Hell—React Renderer to the Rescue
PDFs. Everyone’s nightmare. @react-pdf/renderer? Reused from week four. React components describe layout. Server-render to buffer. Stream back. No sweat—if you dodge gotchas.
First: renderToBuffer is named export. Lib examples? Messy. Wrong import? TypeError. Fix it.
Second: Buffer to Uint8Array. Next.js Response loves that. Headers for PDF, attachment filename. Clean download.
Third: next.config.ts serverExternalPackages. Or client bundle barfs.
Route: /api/invoices/[id]/pdf. Fetch from Neon. Clerk auth check. Render. Stream. Link clicks—file drops. No JS dance.
Layout? Header with brand, invoice num. Bill-to block. Line items table (hours, rate, amount). Totals: sub, VAT 20%, grand. Footer terms. Solid. Branded. Pro.
But em-dash aside—VAT hardcoded? UK only? Globals laugh. Currency inference? Fine for big three. Rupees? Pesos? Expand or bust.
One sentence. Next?
Reusing renderer saved hours. Muscle memory. That’s curriculum gold. But new project? Tweak layout. Table math. Date formats. Lost a day debugging buffers. Predictable pain.
What Stuck, What Didn’t—Honest Math
Compounding. The sell. Clerk auth? Identical. Proxy.ts, async auth, route matchers. Copy-paste.
Drizzle ORM, Neon Postgres? Singleton DB. Configs. Push workflow. Zero thought.
PDF? Massive save.
New: NLP parser. Regex + AI. Two days tweaking prompts, edge cases. Worth it.
Stripe? Nah, wait—original cuts off. Assume paywall or limits later. Usage caps? From resume project.
Time sinks: UI polish. Saved invoices list. Ownership checks. Badges. Small stuff adds up.
Total: shipped. Validates stack. But prediction—bold one: these nano-SaaS will flood indie hacker forums. Dozens. Mediocre. AI wrappers on templates. Market? Saturated by month three. Real moat? Integrations. Recurring value. Not one-week hacks.
Skeptical? Yeah. Impressive build. Patterns compound. But calling it ‘SaaS product’? Lite MVP. Users want edits, history, emails. Week nine?
Why This Matters for Solo Devs
Stack: Next.js App Router, Clerk, Drizzle-Neon, react-pdf, OpenAI. Battle-tested. Ships fast.
Hype check: not revolutionary. Regex + LLM? Table stakes 2024. But curriculum angle? Teaches shipping over perfection. Rare win.
Dry humor: if every dev clones this, we’ll drown in AI invoices. Who pays?
Deep dive. Paragraphs vary. One’s tiny.
Auth carried. DB schema: invoices table. Id, userId, client, hours, rate, currency, created. Simple.
Frontend: textarea for natural lang. Parse button. Form fills. Save. List saved. PDF link.
No auth leak? Clerk matcher.
Is NanoCrafts Curriculum Worth It?
Eight weeks. Two SaaS. Patterns stick. Time drops. Resume: weeks of glue. Invoice: polish mostly.
Critique: scope creep risk. ‘Small’ picks only. Real world? Feature vomit.
Insight: parallels 37signals. Basecamp: shipped minimal. Iterated. Here? Solo, no team. Burnout bait.
Users? Assume waitlist or something. Metrics missing.
Punchy close.
**
🧬 Related Insights
- Read more: 27 Questions to Vet LLMs Before They Tank Your Project
- Read more: Anthropic’s Mythos: The Super-AI Locked Away for Elite Security Teams
Frequently Asked Questions**
What is NanoCrafts build curriculum?
Eight-week sprint building AI SaaS. Reuses stack. Ships fast.
How to build an AI invoice generator?
Regex first for client/hours/rate. OpenAI fallback. React PDF server-side. Next.js API.
Does shipping SaaS in one week work?
For MVPs, yes. Scale? Add moat quick.
