Two free business ideas. Every Tuesday. Steal them. Or don’t.
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 emailIdea 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.