The symptom made no sense:

• Printer runs the calibration pattern
• Pattern comes out clean. Right position, right everything.
• Printer says calibration failed.
• Repeat. Repeat. Repeat.

Nothing in the docs. Nothing in the Facebook groups — I searched, I scrolled, I posted. Got the usual “did you power cycle it” energy and one guy telling me to check my firmware version, which was current.

So I described the whole situation to Gemini instead. Symptom, what the pattern looked like, what the machine was doing, what the room looked like. It asked about my ambient lighting.

My garage has bright LED shop lights basically directly over the bed. The calibration step has to read the pattern it just printed, and the lights were washing out what it needed to see. Printing perfectly. Reading nothing.

Turned the overheads off, ran it in dimmer light, calibrated on the first try.

What I’d tell past me:

• If the pattern prints correctly but calibration fails, stop debugging the print. Debug the read.
• Ambient light is part of your setup even though it’s not in any spec sheet or checklist.
• Forums are great at common problems and useless at your problem. Twenty minutes describing the full situation to an AI beat a day of scrolling threads.

Standard disclaimer: this is what fixed it for me in my garage. I’m not claiming to know the internals of the machine.

Couple of works in progress below, and both of them taught me something.

Print one: wood hanger, and a white line I didn’t ask for

Printed onto a wood wall hanger. The design file has a transparent background on purpose — I wanted the grain coming through behind the artwork, and that part worked exactly like I hoped.

What I didn’t expect was a thin white line tracing the edge of the artwork. Runs along the spire and across the horizon. It’s not in my file anywhere.

Took me longer than it should have to work out why. On a UV printer, white is real ink. It gets laid down underneath the color so artwork doesn’t go see-through on dark or textured material. The software reads the transparency in your file to decide where that white layer goes. It wasn’t confused by my clear background — it read it correctly and laid the white slightly wider than the color sitting on top of it. So you get a white halo everywhere the design meets nothing.

The obvious fix is to turn the white layer off, but that’s not actually what I want. Without it, the wood tone comes up through every color and the reds go flat. The whole point of this piece is saturated color against bare grain.

So two things to test instead:

• Choke the white layer. Most UV software can shrink the white slightly relative to the color so it can’t peek out past the edge. Need to find what it’s called here.
• Hard-edged file. If the outer pixels of my PNG are partially transparent instead of fully transparent, the software is probably still reading them as “put ink here.” Might fix the halo without touching a single setting.

Print two: same design, dollar store canvas, different problem

Took the same design, added a sky background this time, printed on a cheap canvas from the dollar store.

The canvas wasn’t tight. It had slack in it. Results were smearing and visible lines running through the print.

Here’s the part I didn’t think about beforehand. The print head rides a set distance above the surface. A loose canvas doesn’t hold a flat plane — it bows and flexes. So the head is very likely making contact with the material and dragging through ink that hasn’t cured. That’s the smearing. The weave texture showing through accounts for the lines.

I got a bad print. I could just as easily have damaged the print head, which is the expensive part of the machine. Not doing that again.

Two things filed under stuff nobody tells you:

• Transparency in your file isn’t neutral. It’s an instruction, and the machine follows it further than you meant.
• Substrate flatness isn’t a quality-of-finish concern, it’s a clearance concern. Cheap material is fine. Loose material is not.

If you’ve already solved either of these on an E1, tell me and save me the trouble.

Read more at Build and Bail

I’m not doing that anymore.

I found a tool called VocalLab.ai on AppSumo, and once I opened the audiobook mode I realized I wasn’t looking at a voice cloning problem. I was looking at a casting problem I could actually afford.

Heads up: the AppSumo link in this post is a referral link. If you buy through it I get a cut. I bought it with my own money before I had any reason to write about it.

What changed

The old plan:

• Record all 9 episodes myself in Audacity
• Clone my voice in ElevenLabs for the counterpart character
• A 43-year-old man doing a 10-year-old’s voice for 2.7 hours

The new plan:

• Every character gets its own voice
• I write, direct, and edit — I don’t perform
• Audacity is now for assembly and timing, not recording

The honest version: I did test recordings. I sound like a 43-year-old man doing a 10-year-old’s voice. Finn Caspian works because that guy can actually do it. I can’t.

How VocalLab’s audiobook mode actually works

This isn’t the standard text-to-speech box. It’s structured for multi-character work:

• One character block at a time
• 2,000 character limit per block
• Inline sound tags dropped right into the text — [laugh], [breathe], [sigh]
• No steering prompts. The text and the tags are your only direction.

That last one matters. If you’ve used TTS tools where you write a separate “read this sadly, slower, more distant” instruction, that doesn’t exist here. Your only lever is the writing itself. Short sentences read slower. Paragraph breaks create air. Punctuation is direction.

Which means the script stopped being a script and became a set of instructions for a machine.

The two things I got wrong first

The pause problem. There’s a moment where Mike says “No. Way.” It has to land as two beats with a real gap. Generated as one block, it comes out as one flat phrase. The fix is three separate blocks — “No.” then silence I insert manually at about 0.8 seconds, then “Way.” Any dramatic beat in your script is a separate generation. Plan for it.

The bleed problem. Grandpa’s laugh was tagged inline at the end of his line and it smeared into the next thing he said. Standalone laughs get their own block with nothing in it but [laugh]. Generate alone, drop into the timeline manually.

The rewrite I didn’t see coming

The book is third person. “Mike opened one eye.” Standard middle grade.

But the podcast has a framing device — a Counterpart Log that opens and closes each episode in Mike’s voice — and that log was already first person. So I had a narrator saying “there’s a journal on my nightstand” and then, thirty seconds later, “Mike chewed his toast.”

It’s a small thing on the page. In audio it’s a guy talking about himself in the third person for 18 minutes.

I went back and forth with Claude on it. Third person is a legitimate audio drama convention — the narrator as an older Mike looking back. Finn Caspian does exactly that. But the log already set the precedent, and first person closes the gap.

Converted all of Episode 1. Mostly a find-and-replace with verb tense cleanup, not a rewrite. Two things I learned doing it:

• Description blocks stay mixed. “Olivia came stomping in,” not “she came stomping in.” Mike is still observing the scene, and first-person narration does this naturally.
• The end-of-episode teaser got better. “I learn the rules” beats “Mike learns the rules.” More personal, more hook.

Where it stands

• Episode 1 is formatted, converted, and partially generated
• Episodes 2 through 9 are scripted but not yet reformatted for the block structure
• Still recording all 9 before publishing any of them
• Still dropping 3 on launch day, weekly after that

Here’s the opening of Episode 1. Judge it yourself.

The stack, updated

• VocalLab.ai — all character voices (referral link — I get a cut if you buy)
• Claude — market research, adaptation, scripts, the first-person conversion
• Audacity — assembly, timing, manual gaps
• Buzzsprout — hosting and distribution
• Gemini (Lyria 3) — the music sting

Gone from the last version: ElevenLabs, and me.

The part I’m still uneasy about

I’m making a children’s podcast where no child ever hears a human voice.

I don’t have a clean answer for that. The alternative was a book nobody could find on KDP, or nine episodes of me doing a voice I can’t do. Bad audio doesn’t serve kids either. But I’m not going to pretend this is a neutral tradeoff, and I’m not going to hide it in the credits.

Tell me I’m wrong in the comments. I’ll read them.

Recording continues. Unless I bail.

Read more at Build and Bail

I needed a way to test a short-form video idea for my demotivational speaker alter-ego, Desmond Vance, without sitting in front of a camera every time I had a thought.

The plan was simple:

• Train a custom avatar in Gemini that matches Desmond’s look and voice.
• Generate short 10-second clips on demand.
• Drop the MP4s into Canva to add text overlays.
• Slap a badge over the Gemini watermark in the corner.

I wanted a zero-friction pipeline. I wanted to go from an idea in my head to a published TikTok in five minutes flat.

The Toolkit

• Gemini (Custom Avatars): Clones the look and voice from a source calibration video and generates new 10-second clips.
• Canva: Handles the vertical 9:16 layout, text formatting, and graphic overlays.
• TikTok: The destination for publishing and watching the numbers.

Here is how we set up the assembly line:

The Strategy / The Build

• Training the custom avatar
  • I dressed up as Desmond Vance:
    • Cheap wig
    • Reading glasses
    • Ugly tie
    • Dress shirt and suit jacket
  • I ran through Gemini’s avatar creation process.
  • I recorded the setup video directly in the tool, moving my head side to side and reading out the prompt numbers on screen so it could lock down my facial geometry and voice tone.
• Generating the clips
  • Once the avatar was ready, Gemini had Desmond’s look and voice saved.
  • I started generating 10-second clips by giving it simple visual actions:
    • Staring blankly at a desk
    • Looking unimpressed in an office
    • Walking through an empty hallway
• Polishing in Canva
  • I downloaded the raw 10-second MP4 and dropped it into a blank 9:16 vertical Canva canvas.
  • I set the video as the background.
  • I created a circular headshot badge and positioned it in the bottom corner right over the Gemini watermark.
  • I added bold, centered text across the top with Desmond’s quotes (“Master the Minimum,” “Lower Your Expectations”).

The Roadblocks

• Viewer distraction from the watermark
  • Big tool watermarks in the corner pull eyes away from the clip. I’m not trying to hide that it’s AI—hence writing a whole post about it—I just don’t want people tuning out or getting disconnected from the joke because a software logo is flashing in the corner.
  • The Fix: I made the circular headshot badge in Canva slightly larger than necessary so it comfortably covers the entire corner, keeping the viewer’s focus on Desmond and the punchline.

The Finished Project

The pipeline works. I went from dressing up once in front of my webcam to pumping out multiple TikTok clips without putting the suit back on.

You can see the final Desmond Vance videos live on TikTok:

The Verdict:

I no longer have to set up lights or hit record for every new clip.

I no longer have to open a real video editor just to add text to a 10-second video.

I no longer want to pull my hair out over video production.

Once the template is saved in Canva, shipping a new clip takes under five minutes.

Read more at Build and Bail

The requirements were simple but specific:

• A front page showing overall leaders, split into Men’s and Women’s brackets.
• Clickable sections for individual events (like “Plank Hold” or “Golf Putting”) showing the rules and the current standings.
• A custom point system where 1st place gets 9 points, 2nd gets 7, down to 10th place.
• A hidden admin dashboard where we can add events, enter people’s scores, and let the app automatically calculate who is winning.

The Toolkit

You don’t need to know how to code to build something like this anymore, but you do need to know what tools to tell the AI to use. Here is the basic setup:

• The Brain: Claude Code (an AI that runs on your computer and writes the files for you).
• The Frontend: Next.js and Tailwind (this just means a modern website that looks clean and works fast).
• The Database: Supabase (a free, easy-to-use place to save all our entrants and scores).
• The Hosting: Cloudflare (to put the site on the internet for free).

The Secret Sauce: How to Actually Manage the AI

If you are trying to get an app out of your head and onto the screen, do not write one giant prompt asking the AI to build the whole thing.

If you ask for the whole house at once, the AI will build something that looks like a house, but when you open the front door, the plumbing is connected to the ceiling fan. By the time you notice, it’s too tangled to fix.

Instead, I used a strict checkpoint system. I gave Claude a master to-do list and forced it to stop after every single step so I could verify it worked.

• Step 1: Build the database tables. (Stop and let me check).
• Step 2: Write the math logic that calculates ties and assigns points. (Stop and let me run a test).
• Step 3: Build the public homepage with dummy data. (Stop and let me look at it).
• Step 4: Build the password screen for the admin area. (Stop and let me try logging in).
• Step 5: Build the forms to enter real scores. (Stop and let me try it).

Because I tested step 2 before step 3 was ever written, I knew the math was bulletproof before the AI started building pages that relied on it. This is the secret to rapid prototyping with AI.

The Snag: Getting it on the Internet

The only real headache we hit was when it was time to put the site live on Cloudflare.

• Claude initially tried to use an outdated deployment method.
• It caused the “backend” of our site (the part that saves the scores and checks the passwords) to crash because it was trying to run on the wrong type of engine.
• The fix: I told Claude to rip out the old method and use the modern Cloudflare adapter (OpenNext).

Once we made that swap, the site immediately worked online exactly how it worked on my computer. Note for builders: Always use the “preview” command to test how your site runs on the internet before actually publishing it.

The Finished Project

The final site is live right now at www.awesomeofficegames.com.

It’s fast, minimal, and does exactly what it needs to do. Because we built it in clean, logical chunks, it was incredibly easy to go back at the end and ask Claude to add a few polish features, like a navigation bar for the admin area and the ability to fix typos in people’s names without breaking the leaderboards.

If you’ve got an idea in your head, the tools are ready. Just remember to steer the ship one checkpoint at a time.

Read more at Build and Bail

Published: June 16, 2026 · Read time: 5 min · Series: Two Free Tuesday

A small note before we start

Normally the format is one real business idea and one absurd one. This week, both are technically real. The first one would clearly print money. The second one would also probably print money — but the premise is dumb, which restores balance. Absurd-first returns next week.

Two ideas. Both come with the planning prompt I’d use to build them. Pick one and ship it.

What is Two Free Tuesday?

Every Tuesday I drop two business ideas I’d hand to someone and say “go build this.” These are ideas I’m specifically not building — because I already have too many projects running, or because the audience for them isn’t my audience.

Each Tuesday post includes:

• The pitch
• Who it’s for
• The stack I’d use
• Weekend-build estimate
• How to monetize it
• Why I’m not building it
• A DIY path and a “have me build it” path
• The exact prompt I’d use in Claude to plan the whole build (free, drop your email in the block after each idea)

Idea 1: RecipeReplace

One-liner: Paste any recipe, get back the same recipe rewritten to work without whatever you don’t have, can’t use, or won’t use.

Who it’s for

• Home cooks with allergies (nut-free, dairy-free, gluten-free households)
• Parents with picky eaters who reject specific ingredients
• People who hate driving to the store mid-recipe to grab one missing thing
• Anyone running a low-stocked pantry who wants to actually use what’s there

How it works

• User pastes a recipe — copy/paste from any blog or cookbook
• User selects or types restrictions: “no eggs,” “no dairy,” “no garlic,” “no nuts”
• AI rewrites the recipe with real substitutions, adjusted measurements, and updated instructions
• Output is the full recipe in the same format — not a list of suggested swaps for the user to apply themselves
• User can save the rewritten recipe to their account for later

Suggested stack

• Next.js 14 (App Router) + Tailwind + TypeScript
• Supabase for auth and saved recipe history
• OpenAI or Anthropic API for the rewrite logic
• Stripe for subscriptions
• Cloudflare Pages for hosting

Build time

One weekend. Most of the effort goes into the AI prompt — getting it to output a real recipe instead of a wishy-washy “you could try X” response.

Monetization

• Free: 3 recipe rewrites per month
• Pro: $4.99/mo unlimited
• Annual: $39/year (save ~35%)

Why I’m not building it

The real path to revenue runs through someone who already has a food audience. A food blogger, meal-prep newsletter, or cooking YouTuber could launch this and have thousands of paying customers in 18 months. I have a tech audience — I’d be marketing this from zero on the wrong platforms.

If you run a recipe blog, a meal prep brand, or a food TikTok, this is your bolt-on product. People already trust your recipes. They’d trust your rewriter.

Ship it yourself or have me ship it

• DIY: Most of the work is the AI prompt. Treat the rewrite as structured output — input is recipe plus restrictions, output is the same recipe in the same format with restrictions handled. Test it on weird stuff. People will paste in chocolate cake recipes and ask you to remove sugar.
• DFY: I’ll build it in a weekend and hand you the keys. Book a call →

Get the planning prompt

RecipeReplace is a one-shot generator with light user persistence — input goes in, customized output comes back. The planning prompt below is tuned for generator-type builds. Paste it into Claude, replace the pitch, run the conversation.

I'm looking to build an website called Recipe Replace. It's a website that allows you to paste a recipe (text/image/pdf) and state what components you're missing. It will provide suggested alternatives based on what you have available. Ask any questions then give me the prompts needed to build the website in Claude Code. I'd prefer to use the following stack but am open to other free options: 
- Next.js 14 (App Router) + TypeScript + Tailwind CSS
- Supabase for user accounts, generation history, and saved outputs
- Stripe for subscriptions (freemium model)
- OpenAI or Anthropic API for the generation logic
- Cloudflare Pages for hosting
- Postmark for transactional email

Idea 2: Fish Enbigener

One-liner: An app that makes the fish in your photo look bigger so you can win the group chat.

Enbigen, verb — to make something significantly larger via the internet.

Who it’s for

• Anglers in group chats trying to win the “best catch of the season” bet
• People whose Instagram fishing post got fewer likes than they hoped
• New fishermen who haven’t caught anything impressive yet
• Bachelor party gag gifts
• Father’s Day novelty content

For context: r/Fishing alone has 2.3 million members. There’s a real “fish brag” subculture across Reddit, Facebook groups, and dedicated fishing forums. This is a real distribution channel for a joke product.

How it works

Three tiers, each more committed to the bit than the last:

• $3 — Basic. Upload your photo. AI detects the fish, scales it up by 30-50%, blends it back into the original image. The fish is bigger. That’s it.
• $9 — Trophy. Same as Basic, plus a fake tournament weigh-in graphic overlaid on the photo. Real-looking weight, species name, the whole presentation.
• $19 — Full Alibi. AI replaces the background entirely. You’re on a different boat. The fish is a different species. The lake is a different lake. The sunset is a different sunset. It’s not your fish anymore. It’s a better fish.

Preview-before-pay flow on all tiers — user sees the result watermarked, pays to remove the watermark and download.

Suggested stack

• Next.js 14 + Tailwind + TypeScript
• Supabase for order tracking
• Stripe for one-time payments
• Replicate or fal.ai for image generation (image-to-image with the fish bounding box scaled)
• OpenAI vision API for the “is this actually a fish” check before processing
• Cloudflare Pages for hosting

Build time

A weekend, plus 2-3 extra hours for the image classifier that confirms the upload is actually a fish before processing. You want this. Trust me.

Monetization

• One-time payments per photo (no subscriptions — you don’t fish every day)
• Tiered pricing as above
• Optional bundle: 5 credits for $12 (encourages saving credits for the next trip)

Why I’m not building it

Fishing as a vertical needs someone who actually fishes. The audience would smell it. A real angler with a Facebook group, a YouTube channel, or a fishing newsletter could launch this and clean up. I don’t fish, and the marketing would be hollow without that credibility.

There’s also a 6-12 month window before AI photo editing in every consumer app makes this redundant. That’s enough time to make real money — but you have to move now.

Ship it yourself or have me ship it

• DIY: The hardest part is consistent AI output. Image-to-image generation is unpredictable. The preview-before-pay flow is non-negotiable — it’s the only way users will trust the product enough to pay.
• DFY: I can build this in a weekend and hand you the keys. Book a call →

Get the planning prompt

Fish Enbigener is a one-shot generator with image-based input and output. Same planning prompt template as RecipeReplace — the generator prompt covers both. Drop your email and I’ll send it over.

I'm looking to build an website called Fish Embigener. It's a website that allows you to upload an image of a fish (either alone or being held by the person who caught it). The user can set a percentage to increase the size of the fish and the website will output the same image with just the fish enlarged. Ask any questions then give me the prompts needed to build the website in Claude Code. I'd prefer to use the following stack but am open to other free options: 
- Next.js 14 (App Router) + TypeScript + Tailwind CSS
- Supabase for order tracking, image storage, and audit logs
- Stripe for one-time payments (no subscriptions)
- Cloudflare Pages for hosting
- Cloudflare R2 or Supabase Storage for user-uploaded and generated images
- Replicate, fal.ai, or OpenAI for image generation (image-to-image, inpainting, or full regeneration depending on the task)
- OpenAI Vision API or similar for input classification (confirming the input image matches what we expect)

Recap

• RecipeReplace: Real business. Boring. Would print money if a food creator built it.
• Fish Enbigener: Joke business. Would also print money. Briefly. For the right person, briefly is enough.

Ship one. Tell me.

FAQ

Are these ideas actually free to use?

Yes. Take them, build them, sell them, keep everything you make. The only ask — tell me if you ship one so I can feature you.

What do I get when I opt in for the planning prompt?

One email. One prompt. Paste it into Claude and it generates the full build plan — stack decisions, scope, edge cases, abuse vectors, and the sequence of Claude Code prompts to actually build it. Same workflow I use for every Build and Bail project.

Why give away ideas (and prompts) that could make money?

Because I can’t build all of them. The pipeline is infinite. Bandwidth is finite. If an idea sits on my list for six months, it’s not getting built — someone else might as well.

Is the Fish Enbigener serious?

Yes. The premise is dumb. The business would work.

What’s the stack you usually recommend?

Next.js 14 App Router, Tailwind, TypeScript, Supabase, and Cloudflare Pages. Full breakdown on my tools page.

Can I hire you to build one of these?

Yes. Every Tuesday post includes a “have me build it” link.

When does the next Two Free Tuesday drop?

Every Tuesday.

More from Build and Bail

• Two Free Tuesday #001: Invoice Nudge + OOO as a Service
• The tools I use to ship every project
• WhoStat — daily sports stats game listed on Flippa

See you next Tuesday.

Read more at Build and Bail

The trap:

• Polishing an idea in your head feels like progress
• It isn’t
• A bad idea you shipped beats a perfect idea you didn’t

Receipt:

• Emergency Pants is a fake on-demand pants delivery service
• It is, objectively, a worse idea than yours
• It exists. It has a landing page. It’s in my portfolio.
• It taught me more than three “good” ideas I never built

What “not good enough” actually means:

• You haven’t tested it on a real person
• The first version isn’t supposed to be good — it’s supposed to exist
• Bad ideas die fast and cheap. That’s the feature, not the bug.

The move this week:

• Ship the worst version of your idea before Friday
• One page. One promise. One way to contact you.
• Let it be embarrassing. That’s how you find out what it actually needs.

Read more at Build and Bail

Every Tuesday I drop two business ideas I’d hand to someone and say “go build this.” These are ideas I’m specifically not building — because I already have too many projects running, or because I’d lose interest by Wednesday, or because the idea is dumb but might work anyway.

Two reasons the ideas are free:

• Ideas aren’t the bottleneck. Shipping is.
• If you build one, it becomes a case study. Everyone wins.

Each Tuesday post includes:

• The pitch
• Who it’s for
• The stack I’d use (links to my tools page)
• Weekend-build estimate
• How to monetize it
• Why I’m not building it
• A DIY path and a “have me build it” path
• The exact prompt I’d use in Claude to plan the whole build

That last one is free if you want it. Drop your email in the block after each idea and I’ll send it over.

This week: one that could actually print money, and one that probably shouldn’t — but might anyway.

Idea 1: Invoice Nudge

One-liner: A dead-simple tool that follows up on unpaid invoices so you don’t have to.

Who it’s for

Freelancers, consultants, agencies — anyone who’s sent a $2,400 invoice into the void and forgot to chase it for three weeks.

How it works

• You CC your invoice email to a custom address
• It parses the client, amount, and due date
• If unpaid by the due date, it auto-sends follow-ups on day 3, 7, 14, and 30
• Tone escalates — polite, then firm, then “interest charges apply”
• Reply “paid” to any thread to mark it closed

Suggested stack

• Next.js 14 (App Router) + Tailwind + TypeScript
• Supabase for auth and database
• Postmark for inbound email parsing (does 80% of the work)
• Stripe for subscriptions
• Cloudflare Pages for hosting

Build time

One weekend. Two if you’ve never touched inbound email parsing before.

Monetization

• Free: 3 active invoices
• Pro: $9/mo, unlimited
• Agency: $29/mo, multi-seat

Why I’m not building it

I don’t freelance. It’s not my problem, so I’d lose interest by day three. But if you freelance, this is a real business — boring, useful, and people will pay for it.

Ship it yourself or have me ship it

• DIY: Stack above. The only hard part is inbound email — Postmark’s parse endpoint covers most of it.
• DFY: I’ll build it in a weekend and hand you the keys. Book a call →

Get the planning prompt

Every project on this site starts with a 30-minute Claude chat that turns the idea into a sequence of Claude Code prompts. Drop your email and I’ll send you the exact planning prompt I’d use for Invoice Nudge — run it yourself, get your own build plan, ship it.

I'm looking to build an website called Invoice Nudge. It's a recurring SaaS — auth, billing, multiple users, admin panel, inbound email parsing. It should be a dead-simple tool that follows up on unpaid invoices so you don't have to. Ask any questions then give me the prompts needed to build the website in Claude Code. I'd prefer to use the following stack but am open to other free options: 
- Git hub as repository
- Next.js 14 (App Router) + TypeScript + Tailwind CSS
- Supabase for any minimal data storage (orders, generated outputs)
- Cloudflare Pages for hosting

Idea 2: Out of Office as a Service

One-liner: A service that writes a believable out-of-office auto-reply and — for an extra fee — generates fake vacation photos to post on LinkedIn.

Who it’s for

People who need a mental health day but work somewhere that requires a paper trail.

How it works

• Pick a destination (Portugal, cabin in Vermont, “visiting family”)
• AI writes the OOO message with a realistic return date
• AI generates 2–3 stock-looking vacation photos
• Optional: drip-schedule a “sending this from the road” LinkedIn post for day three

Suggested stack

• Next.js 14 + Tailwind + TypeScript
• Supabase
• Any image generation API
• Stripe for one-time payments

Build time

A weekend. The landing page is four hours.

Monetization

• $19 per trip
• $49 deluxe with photos
• $99 full alibi with scheduled LinkedIn post

Why I’m not building it

The unit economics are bad unless it goes viral. Building a joke business that needs to go viral to work isn’t a plan — it’s a hope. But if you think you can market it, it would print money for a month. For some people, a month is enough.

Ship it yourself or have me ship it

• DIY: Most of this is a prompt and a form. Landing page in four hours.
• DFY: I’d rather build this for someone who thinks they can sell it. Book a call →

Get the planning prompt

OOO as a Service is a different build — one-shot generator instead of a recurring SaaS — so the planning prompt is tuned for that. Drop your email and I’ll send it over.

I'm looking to build an website that writes a believable out-of-office auto-reply and — for an extra fee — generates fake vacation photos to post on LinkedIn. Ask any questions then give me the prompts needed to build the website in Claude Code. I'd prefer to use the following stack but am open to other free options: 
- Git hub as repository
- Next.js 14 (App Router) + TypeScript + Tailwind CSS
- Supabase for any minimal data storage (orders, generated outputs)
- Cloudflare Pages for hosting

Recap

• Invoice Nudge: Real business. Boring. Would probably work.
• Out of Office as a Service: Joke business. Would also probably work. Briefly.

Ship one. Tell me.

FAQ

Are these ideas actually free to use?

Yes. Take them, build them, sell them, keep everything you make. The only ask — tell me if you ship one so I can feature you.

What do I get when I opt in for the planning prompt?

One email. One prompt. Paste it into Claude and it generates the full build plan — stack decisions, schema, API structure, and the sequence of Claude Code prompts to actually build it. Takes about 30 minutes of back-and-forth. Same process I use for every Build and Bail project.

Why give away ideas (and prompts) that could make money?

Because I can’t build all of them. The pipeline is infinite. Bandwidth is finite. If an idea sits on my list for six months, it’s not getting built — someone else might as well. And if the prompts help you ship faster, that’s the whole point.

What’s the stack you usually recommend?

Next.js 14 App Router, Tailwind, TypeScript, Supabase, and Cloudflare Pages. Full breakdown on my tools page.

Can I hire you to build one of these?

Yes. Every Tuesday post includes a “have me build it” link. Typical engagements: a weekend MVP handoff, a build-and-launch package, or a consulting session where I plan the whole thing with you.

When does the next Two Free Tuesday drop?

Every Tuesday (unless I bail on this series).

More from Build and Bail

• The tools I use to ship every project
• How I built and listed WhoStat on Flippa
• Emergency Pants: the pants delivery service that shouldn’t exist

See you next Tuesday.

Read more at Build and Bail

The truth:

• I’m a Validation Engineer, not a developer
• I’ve shipped a dozen sites without writing a line of code myself
• The skill isn’t coding. It’s describing what you want.

What’s actually behind “I don’t know how to code”:

• You’re not afraid of code
• You’re afraid of looking dumb while learning
• You’re waiting for permission to start

The move this week:

• Pick the smallest version of your idea — one page, one feature, no login
• Open Claude
• Describe what you want in plain English
• Watch what happens

You don’t need to learn to code. You need to learn to describe.

Read more at Build and Bail

So buying a $3,200 UV printer is, on paper, the dumbest thing I could do. You can’t git push your way out of a 44-pound machine sitting on your desk. There’s no abandoning it — only using it or staring at it.

I bought it anyway. Here’s the honest reasoning.

What it is

The eufyMake E1. It prints full color directly onto metal, wood, acrylic, glass, ceramic, leather — basically anything flat. The party trick is texture: it can lay down up to 5mm of raised relief, so prints aren’t just colored, they’re raised. Every review on their site calls it a “game changer,” which is how I know not a single one was written by me.

Why I broke my own rule

Two of my real businesses already sell physical product. This isn’t a bet on a new idea — it’s a tool upgrade for demand that already exists. That’s the difference. I’m not buying capacity hoping someone shows up. People are already here.

What I’m actually going to make

• Golf ball markers (White Knuckle Golf). Right now I laser-engrave them — one color, etched in. The E1 prints full color and raised texture on the same flat disc. Same product, more reasons to buy it.
• Faux stained glass suncatchers. Print on clear acrylic with white ink behind the color for that lit-from-behind glow, then raise the “leading” lines with texture so it reads like real soldered glass. No kiln, no lead, no decades of practice.

The catch nobody puts on the box

The ink. Run it daily and you’re looking at roughly $50/month just to keep the heads from clogging. That’s a real number that turns “fun machine” into “this needs to earn its keep.” Which is fine — that pressure is the test.

How I’ll know if this was a mistake

Same framework as everything else here: KEEP GOING / PIVOT / SHELVE IT. If the markers move and the suncatchers sell, keep going. If only one product line works, pivot to it. And if 90 days in I’m paying $50/month in ink to print things nobody buys — I’ll tell you that too, because that’s the whole point of this site.

Hardware you can’t bail on. So this one, I have to actually finish.

Read more at Build and Bail

So a FreshRoast SR800 roast logging app wasn’t a guess. It was the digital version of a thing I already sell. I built Drop Log for me first — I’m the most reliable user I have — but with actual evidence the need is real, not a hunch I talked myself into.

Then I made a string of calls that look like shortcuts and weren’t. Here’s the reasoning.

Why I built it in a single browser tab

The “proper” plan I worked out with Claude had me installing Xcode, Android Studio, Node, a build service — the full native dev gauntlet before writing one line. I looked at that and decided I’d rather build than configure.

So I used Gemini AI Studio. One tab. Describe what I want, it writes the code, builds it, I test it. No local environment, no terminal. That tradeoff cost me some things (below), but I stayed in flow instead of losing a night to installers.

Why it’s an Android roast logger and nothing else (for now)

Because I’m an Android user and I’m tired of being an afterthought. Every app ships Apple-first and Android waits months for a worse version. I built the Android roast logger I’ll actually use. iOS happens later, if ever — the reverse of how everyone else does it.

Why there’s no cloud and no account

The original plan had a backend, accounts, a shared recipe database. I cut all of it. Drop Log is a home coffee roasting tracker that lives entirely on your phone, locally. No login, no server.

• it’s for me first, and I don’t need a community to log my own roasts
• offline-and-yours-forever is a feature next to a roaster in a garage with bad signal

You save your own recipes locally and replay them. If recipe sharing ever shows up, it’ll be because I wanted it — not because a roadmap demanded it.

The paper logbook still exists for the people who’d rather keep their phone away from the heat. Same problem, two formats. They’re not competitors.

The part where the AI lies to you

Building an app with AI in one tab is great until you notice the tool is a relentless optimist. Gemini ended nearly every reply with a victory lap — real quotes:

• “The build compiled with immediate success.”
• “The application compiles perfectly.”
• “robust and production-ready.”

At the same time:

• it couldn’t publish for three rounds (“Developer status does not allow app creation”)
• the version number kept colliding with itself — 1 → 2 → 3 → 4 chasing errors
• the bottom nav buttons just didn’t always work. tap, nothing.

“Production-ready” and “frozen buttons” were true in the same breath. That’s the catch: the tool narrates success while the thing is broken, and your only real job is to be the person tapping the buttons. I caught the frozen nav by describing the exact symptom, swapped the heat to a real 1–9 scale, and added a Start Roast button so the timer doesn’t run before the first bean drops. Stuff you only find by using it.

Where it stands

Internal testing now — me, garage, real roasts, finding what breaks. Public testing next. Then Drop Log becomes the SR800 roasting app I wanted but couldn’t find.

Verdict: KEEP GOING. I built the app I wanted, on the platform I use, for a problem people already pay me to solve on paper. The “limitations” are choices. The only thing the AI got wrong was telling me it was done.

More once it’s public.

Read more at Build and Bail