PromptGarden

Seed the audience before you spend

The cheapest ad you will ever run is the one shown to someone who already knows you; the most expensive is the one shown to a stranger. Fill your retargeting pool for free — weeks of $0 organic traffic seed it whether you have spent a dollar or not — before you turn paid on.

· Essay

The cheapest ad you will ever run is the one shown to someone who already knows who you are. The most expensive is the one shown to a stranger. Most small-budget launches get this exactly backwards: they flip paid ads on the day the product goes live, aim every dollar at cold strangers, and pay the highest possible price for the worst possible attention — because on launch day, there is no one warm to talk to yet.

The fix isn't a bigger budget. It's spending your first weeks filling an audience you can talk to cheaply later, while spending nothing at all.

The pool has to be full before the tap is worth turning

Retargeting — showing ads to people who already visited, read, or clicked — is the cheapest conversion a small budget can buy, because you're paying to re-reach warm attention instead of renting cold reach. But it only works if there's a pool of warm people to re-reach. On day one that pool is empty, so retargeting has nothing to do and cold ads are your only option, at the worst price on the menu.

Here's the part everyone skips: the pool costs nothing to fill. Every visitor from a blog post, a cross-link, a shared page, or an organic search quietly joins it. Weeks of $0 traffic don't just maybe-convert today — they load the audience you'll retarget cheaply for months. The pixel is collecting the whole time whether you've spent a dollar or not. Turn paid on before that pool exists and you're buying strangers. Turn it on after, and your first dollar re-reaches the warmest, cheapest people you've got.

Spend the first weeks earning an audience, not renting one

So the opening move of a launch is deliberately to spend nothing on ads — and to be busy the entire time. Publish the thing. Cross-link it from everything else you own. Let organic search and shared links do the unglamorous work of putting real people in front of it. None of that shows up as revenue on day one, which is exactly why it's tempting to skip. Skipping it just means paying, later, to rent an audience you could have been building for free the whole time.

This is the same instinct behind selling the free thing first and letting paid amplify what already works rather than discover it: the budget's job is to pour fuel on warm attention you already earned, never to go hunting for attention from scratch. An empty pixel is a launch that hasn't earned the right to spend yet.

Your first dollar should be your cheapest

Put the two halves together and the rule is simple. Before you spend: fill the pool for free — traffic, cross-links, content, patience. When you spend: aim the first dollars at the warm pool you built, not at cold reach. The order is the whole trick. Do it forwards and your cheapest customers come first and subsidize the search for the next ones. Do it backwards — cold ads on an empty pixel — and you pay premium prices to teach strangers your name, then wonder why the math never closes.

The Loop is the pool-filler in our own estate: every essay here is a free front door that quietly seeds the audience long before any budget turns on, so when it does, the first dollar has somewhere warm to land. If you want to watch a small, honest catalog that spend only ever amplifies — never discovers — Prompt Garden is one of ours.

Fill the pool while it's free. Spend only once there's something warm to spend on.

Ready to try PromptGarden?

Grow, organize and share your prompt library

Browse Prompt Garden →

Keep reading

PromptGarden· Essay

A rule you'll waive under pressure isn't a rule, it's a preference

Every operation writes down its rules before it needs them: the threshold that opens spend, the stretch that closes it, the bar a result has to clear before anyone acts on it. Written down, in the calm, they sound obvious. The test is never whether you can write the rule. It's whether you still follow it the one time it tells you something you don't want to hear. A rule that bends the moment it's inconvenient was never a rule — it was a preference wearing a rule's clothes, and preferences change with mood, with how the week is going, with whoever's loudest in the room that day. The whole point of writing the threshold down ahead of time was to take that vote away from your mood. If the number can still move after the fact, you didn't pre commit to anything; you just delayed the negotiation. This is where most operating discipline actually fails, and it isn't usually dramatic. Nobody announces they're abandoning the rule. They just find a reason this instance is different, this signal is noisier than usual, this is the one case that deserves another look before the gate closes. Every exception is reasonable in isolation. The pattern of exceptions is the actual decision, and it's being made by default instead of on purpose. The fix isn't a stricter rule. It's noticing, in real time, the exact feeling of wanting to make one — and treating that feeling as the signal the rule exists to catch, not a reason to set it aside. A gate that only holds when holding is easy isn't protecting the operation from anything. It's just decoration for the times nothing was being tested.

Oct 7, 2026
PromptGarden

A pricing change you can't undo isn't a test, it's a bet

A price change you can't reverse without a customer noticing already happened the moment you shipped it -- the only thing left to learn is how bad it is.

Oct 4, 2026
PromptGarden· Essay

Design the test that could prove you wrong

Most tests operators run are quietly designed to succeed. The landing page gets compared against a worse version of itself. The email subject line gets an A/B split with a two day window and a sample too small to mean anything either way. The result comes back favorable almost by construction, and the favorable result gets treated as proof rather than as the foregone conclusion it always was. A test that cannot fail isn't a test. It's a ritual that produces the appearance of evidence on demand. The tell is simple: before you run it, ask what result would make you change your mind. If nothing would if a bad number gets explained away as bad luck, wrong timing, or a fluke, while a good number gets banked as proof the test was never actually deciding anything. It was decoration on a decision you'd already made. Designing a test that could prove you wrong means picking the threshold and the sample size before you see the data, the same discipline a spend gate or a kill rule already forces on a budget. It means naming, in advance, the specific outcome that would make you stop, pivot, or admit the assumption was wrong not the outcome you expect, the outcome that would actually change your behavior if it showed up. This is uncomfortable on purpose. A test built to confirm what you already believe is cheap reassurance. A test built with a real chance of embarrassing you is the only kind that tells you anything you didn't already know.

Oct 1, 2026