PromptGarden

Earn the ad budget before you spend it

Ad spend is a multiplier, and a multiplier applied to a number near zero stays near zero. Set a gate, make the product clear it with real organic demand, and let advertising do the one thing it's good at: pour fuel on a fire that's already lit.

· Essay

Earn the ad budget before you spend it

Ad spend feels like the lever you pull to make a product work. It isn't. It's the lever you pull once a product is already working, to make it work faster. Pull it before then and you don't buy growth — you buy an expensive, precise measurement of the fact that nobody wanted the thing yet. On a small budget you can't afford that lesson. So the rule we run by is simple: a product has to earn its ad budget before it gets one.

Spend doesn't create demand — it reveals it

Here's the uncomfortable part. If a page can't convert visitors who arrived on their own, paying to send more of them changes nothing about the conversion; it just runs the same failure at a higher volume and a per-click cost. Advertising is a multiplier, and a multiplier applied to a number near zero stays near zero. The money doesn't manufacture interest that isn't there. It only amplifies whatever the product is already doing — which means the honest question isn't "how much should I spend?" but "is there anything here worth amplifying yet?"

That reframes spending from a growth tactic into a bet you place after you have evidence, not before. And evidence is cheap to gather without ads at all.

Set a gate, and make the product clear it

The way to keep yourself honest is a gate — a plain, pre-committed bar the product must clear before a single dollar of budget unlocks. Ours is concrete: a handful of genuine organic sales, or a real conversion rate on a real amount of traffic that arrived without paid help. Not a vibe, not a hunch, not "it feels close." A number you wrote down before you were emotionally invested in the answer.

The gate does two things. It stops you from pouring a tiny budget into a product that hasn't proven anyone wants it — the single most common way small operators burn cash. And it turns "should I advertise this?" from a mood into a fact you can check. Either the product cleared the bar or it didn't. If it didn't, the budget stays in your pocket and the work goes back into the offer, the page, or the audience — the things that were actually the problem.

Waiting is the frugal move, not the timid one

It's tempting to read patience here as a lack of ambition. It's the opposite. The discipline of not spending is what protects the ability to spend later. A budget you didn't waste on an unproven product is a budget still available for the one that proves itself next week. Frugality isn't spending less on everything — it's refusing to spend on the things that haven't earned it, so you can spend decisively on the things that have.

And when a product does clear the gate, the same logic tells you to stop hesitating. Proven organic demand is exactly the signal that says amplification will pay. That's the moment to concentrate the budget, not sprinkle it — put it behind the one thing working instead of splitting it across five things hoping.

The whole rule in one line

Don't advertise to find out whether people want it. Find out first — cheaply, organically, with a number you set in advance — and let advertising do the one thing it's actually good at: pouring fuel on a fire that's already lit. The budget isn't the starting gun. It's the reward the product earns by working without it.

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