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

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

I’m a validation engineer. I’m not a developer. Before AI, I’d never shipped a production app in my life.

In the last year I’ve shipped:

• A playoff fantasy football site that replaced six years of Google Sheets hell
• A sports stats guessing game
• A calculator that tells you how many kids you could beat in a tug of war
• A satirical investor-relations site for my own abandoned projects
• An emergency pants delivery service (yes, really)

None of that existed before because I couldn’t build it. The skill gap was real. AI didn’t “enhance my productivity.” It took me from zero to one on things I was locked out of.

So when I hear “AI is taking from writers, coders, artists,” I hear it, and I also need to say the other half: for a lot of people, it’s handing them the keys to a door they couldn’t open.

The part where people are right

The fear isn’t stupid. People spent years building skills that a model can now approximate in seconds. That hurts. It’s also fair to be pissed when a model was trained on your work without your permission and is now competing with you. I’m not going to pretend that’s nothing.

The part where I’m pushing back anyway

I’m not using AI to mimic anyone. I’m not asking it to write like a living author or paint like a living artist or clone someone’s voice. I’m using it to build things I already wanted to build but didn’t have the technical chops to execute. That’s not theft. That’s a power tool.

“AI is stealing from artists” gets flattened into “AI is bad,” and those aren’t the same sentence. Plagiarism is bad. Deepfakes are bad. Flooding Etsy with AI knockoffs of a real artist’s work is bad. Using Claude to wire up a scoring engine for my fantasy league is… using a tool.

The ATM story is the one people should actually know

Every tech shift comes with a funeral for jobs that don’t actually die. The cleanest example is ATMs.

When ATMs rolled out in the 1970s and accelerated hard through the ’90s, the assumption was obvious: machine does cash, teller is done. The data says the opposite happened, for a long time.

• In 1985, the U.S. had 60,000 ATMs and 485,000 bank tellers. In 2002, there were 352,000 ATMs and 527,000 bank tellers
• The number of tellers required to operate a branch office in the average urban market fell from 20 to 13 between 1988 and 2004
• Urban bank branches increased by 43% during peak ATM proliferation
• Net result: more total teller jobs, not fewer

And the job itself got better. Tellers became part of what banks call the “customer relationship team.” It’s a different sort of skill. Maybe it’s a higher skill. There is some evidence that their wages have gone up. They are hiring more college graduates as bank tellers. The work got more interesting.

Tellers eventually did decline, but not from ATMs. The huge decline in bank teller employment over the last 15-odd years is mainly a story about iPhones and what they made possible. Different technology, twenty years later.

The point isn’t “don’t worry, nobody ever loses.” The point is the first-order prediction — “machine does task, human is gone” — is almost always wrong. The second-order effects are where the real story lives, and they’re usually weirder than anyone guessed.

Every other example tells the same story

• Portrait painters in the 1840s called photography a refuge for hacks and mechanical frauds. Painting didn’t die. It got weirder and better. Impressionism exists partly because photography freed painters from having to be accurate.
• Calculators were going to make kids bad at math. Kids just do different math now.
• Synthesizers were going to end music. They invented entire genres instead.
• Spell check was going to kill literacy. You’re reading this.
• The internet was going to destroy encyclopedias. It did. I don’t miss them.

Each shift came with real losses. Someone got worse off every time. I’m not pretending the pain didn’t happen. But the pie got bigger, the work got different, and in almost every case we ended up with more of the thing, not less.

My actual position

AI is a tool. It’s the best one I’ve ever used. It lets a guy with no CS degree and no design background make things he used to have to beg or pay other people to make for him. For a lot of people who had ideas but no way to execute, it’s the first real shot they’ve had.

Use it, don’t use it, hate it, whatever. I’m going to keep using it to ship weird stuff and write down what happened.

— CT

Read more at Build and Bail

This is the first Build and Bail project to complete the full cycle. Idea. Build. Ship. Bail.

WhoStat is a daily sports stats guessing game — Wordle but for sports nerds. You get a career stat line with no name attached and three guesses to figure out who the player is. Three puzzles a day: NFL, NBA, MLB. Wrong guesses unlock hints. New puzzles every day. 750 players in the database. The site runs itself.

I already wrote the full build log — how I used regular Claude chat to plan the whole project, turned that into twelve prompts, and fed them to Claude Code one at a time to build the thing in a few hours. You can read that here: WhoStat Build Log

This post is about the other half. The bail.

Why I’m Selling It

Because that’s the whole point.

WhoStat works. It’s a fun game. I play it myself sometimes. But I’m not the person who’s going to add leaderboards, streak tracking, push notifications, and an ad layer. I’m not going to maintain a player database across three sports for the next five years. I know who I am.

I built it to see if I could build it. I could. Now it’s someone else’s turn.

The Flippa Listing

I listed WhoStat on Flippa under Projects & Concepts — because that’s exactly what it is. A fully built digital asset with no revenue. Pre-monetization. The buyer gets the domain, the codebase, the 750-player database, and a deployment pipeline that costs nothing to run.

The honest pitch: this is a working product with a clear path to making money — ads, premium features, more sports — but zero financial history. You’re buying the build, not the business. Someone who wants a sports daily game without starting from scratch, this is their shortcut.

Check out the listing here: WhoStat on Flippa

The Takeaway

The Build and Bail philosophy isn’t about building things that fail. It’s about building things fast, being honest about whether you’re the right person to keep running them, and making room for the next idea.

WhoStat didn’t fail. I just finished my part.

If it sells, great — someone else gets a head start on something cool. If it doesn’t, the domain’s still mine, the game still works, and the build log still exists as proof that you can go from “I have an idea” to “it’s listed for sale” in less time than most people spend debating their tech stack.

Launch. Validate. Abandon. Repeat.

Play it: whostat.com

Buy it: WhoStat on Flippa

Build log: How I Built WhoStat

Status: For sale. The circle is complete.

Read more at Build and Bail

That feels like it needs an explanation.

When I built BizByCT, the whole joke was presenting dead projects with the gravitas of a Series B pitch deck. Abandoned calculator tools. A pants delivery service for emergencies. Formatted like someone was actively soliciting institutional capital. The absurdity was the point.

But while I was building the site itself, I kept thinking: this is actually a useful workflow and nobody talks about it this way. Zero installs. Zero IDE. Just a browser, a GitHub account, Cloudflare, and Claude Code doing the heavy lifting. I shipped the whole BizByCT site that way. So I wrote it up and buried it in the nav of my fake investor site, which is exactly the kind of decision-making that defines this brand.

What the tutorial actually covers

The short version: how to go from “I have an idea” to “I have a live website with a real domain” without touching a terminal, downloading an editor, or pretending you understand what a Node.js version conflict means.

The stack is three tools: Claude Code (browser-based, connects directly to your GitHub repo), GitHub Pages (free hosting, deploys automatically on push), and Cloudflare (DNS, SSL, free tier handles everything you need). Claude Code writes the code, commits it, and pushes it. GitHub serves it. Cloudflare makes it look like you know what you’re doing with a real domain.

The example I used in the tutorial is a fictional dog walking business called Good Boy Walks. I prompted it, built it live, and published the actual output so you can see exactly what Claude Code produces when you give it a real brief. The site is there. It’s real. No dogs were walked.

Why this matters for the Build and Bail workflow

The whole Build and Bail philosophy is that the build phase should be fast and honest. You’re not trying to build something perfect — you’re trying to find out if something works before you spend six months on it. That means the gap between “I have an idea” and “something exists on the internet” needs to be as small as possible.

This tutorial closes that gap. A few hours, three free (or cheap) tools, and you can have a live, real-domain website without asking a developer friend for a favor or watching a three-part YouTube series on web hosting. That’s the point. The faster you can ship, the faster you find out if the idea has any pulse.

I built the tug of war calculator the same way. The BizByCT site itself, same way. When the build is this fast, bailing isn’t even that painful.

The footnote at the bottom

The tutorial ends with: “This tutorial describes a real workflow. The dog walking business is fictional. No actual dogs were walked during the making of this guide, though several were considered.”

That’s the energy. The workflow is real. The business is fake. The lesson applies to both.

Go check it out at bizbyct.com/tutorial — and if you’ve been sitting on an idea because you don’t know how to build the website part, this is your excuse to run out of reasons not to.

Read more at Build and Bail

It started, as most great ideas do, at work.

Someone asked the group how many 5th graders they thought they could beat in a fight. You know the question. Everyone has a number ready. Nobody’s embarrassed about it. The room got loud.

But then someone changed the scenario: okay, but what about tug of war?

And that’s actually a completely different problem. Hand-to-hand combat against a pack of 10-year-olds is a question of reach, reflexes, and how much you’re willing to commit to the bit. Tug of war is physics. It’s weight, friction, grip strength, and coordinated pulling force distributed across a rope. You’re not fighting the kids — you’re fighting math.

So naturally, I tried to research it.

The Research Phase (I Lasted About 20 Minutes)

I poked around looking for actual data on how much pulling force a 5th grader generates in a tug of war scenario. Turns out there isn’t a ton of peer-reviewed literature on this specific topic, which feels like a glaring gap in the academic community.

I found some general grip strength data. Some pediatric exercise physiology stuff. Nothing that translated cleanly into “here’s how many kids it takes to drag a 190-pound adult across a line.”

So I did what any reasonable person does when real research gets tedious: I opened Gemini and just asked it.

And here’s the thing — it actually worked. Gemini pulled together estimates on average grip strength by age, made reasonable assumptions about body weight and center of gravity, and handed me a working formula with actual numbers. Real enough to build something. Real enough to settle arguments.

I could’ve written it in a notes app and moved on with my life.

I did not do that.

From Math Problem to Website in One Conversation

Once Gemini gave me the numbers, I had it write the website.

That’s the whole build. One tool, one conversation. I asked it to code me a single-page calculator where you can plug in your own stats on one side and build a theoretical team of kids on the other side, and it spits out who wins on paper.

No frameworks. No database. No backend. Just a clean HTML page with the math baked in, doing exactly one thing.

The whole build took less time than the original workplace argument that inspired it.

I threw it up at tugofwarcalculator.com.

What the Tool Actually Does

You go to the site, enter your weight and general athletic disposition, and then configure a team of elementary schoolers to pull against you. The calculator estimates the combined pulling force of your theoretical kid-team against your own numbers and tells you how the matchup shakes out.

Is the math perfect? No. Is this medically, physically, or ethically sound advice? Also no. But is it directionally correct enough to end a workplace debate? That was the whole goal, and I think yes.

There’s also something kind of funny about the fact that a real academic paper I found on tug of war physics notes that on most surfaces, the sport essentially comes down to who’s heavier — not who’s stronger — because friction is what actually keeps you from sliding. So your grip strength barely matters. Your weight does. That’s either comforting or devastating depending on where you land on the scale.

What I Actually Learned

AI as a research shortcut is underrated. I wasn’t asking Gemini to make something up — I was asking it to synthesize publicly available data on pediatric exercise physiology into a usable estimate. That’s genuinely useful. That used to require either a science background or a lot of time I don’t have.

Scope is a superpower. The calculator does one thing. It doesn’t track your results over time or let you create an account or share your matchups or any of the other feature creep that turns a two-hour project into a two-month one. One page, one question, one answer.

The best tools are the ones people already want. Nobody asked me to build this. But the second I told people it existed, everyone went to try it. The question “how many kids could you beat in tug of war” is already living rent-free in people’s heads — I just gave it a home.

The Verdict

Built: Yes.

Time: A couple hours, including the original research spiral.

Abandoned: Technically. But it’s still up and it still works, so it’s more of a “parked” situation.

Would I do it again: Definitely.

The calculator lives at tugofwarcalculator.com. Go find out how many kids it takes to drag you across a line. The answer is probably fewer than you’d like.

-CT

Read more at Build and Bail

We’ve all got one. That big idea for an app, a product, a side business. The thing you think about in the shower. The thing you’ve been “almost ready” to start for three years.

Most people spend months — sometimes years — trying to make it perfect before they launch. They plan. They worry. They wait.

Here’s the truth nobody wants to hear: most ideas aren’t going to work. And that’s completely fine.

Welcome to Build and Bail.

The Rule: Build Fast, Quit Faster

Everyone in the business world loves to say “never give up.” I think that’s terrible advice. If you’re riding a horse that can’t run, the smartest thing you can do is get off and find a better horse.

Here’s how I operate:

The Build — I take an idea and launch it. Fast. I use AI, 3D printers, and laser engravers to go from idea to prototype before I can talk myself out of it.

The Bail — Once I’m bored, I’m done. No guilt. No long drawn out post-mortem. I kill it and move to the next thing.

That’s it. That’s the whole system.

What You’ll Actually See Here

This isn’t a get rich quick page. There are plenty of those. This is the messy, unfiltered reality of starting things — what it looks like when someone just keeps launching stuff without overthinking it.

You’ll see the idea — the crazier the better. You’ll see the mess — broken prototypes, wrong assumptions, things that seemed genius at midnight and ridiculous by morning. And you’ll see the decision — exactly why I kept going or why I threw it in the trash.

No sugarcoating. No highlight reel. Just the whole chaotic loop.

Don’t Fall In Love With Your Ideas

Most people get stuck because they love their idea too much. I love the process. The build. The moment something goes from a weird thought to a real thing you can hold or click on.

I’m looking for the one idea that actually works. And I’m completely fine failing a hundred times to find it.

Stick around. Watch me build it.

Then watch me bail.

— CT

Read more at Build and Bail