Log a pre-product brand spend as a defensible bet

A pre-product brand invoice can be as consequential as a hiring decision. When it is, it needs a decision record. Niklas Lindgren, Endra's co-founder and CEO, put $150,000 into the company's brand before the product existed, and the company booked $1.5 million in annual recurring revenue in a single month. AJ Loiacono, Judi Health's co-founder and CEO, ran the company with $0 on marketing for two years, then brought in $400 million at a $3.25 billion valuation. Other founders made different calls: Colin Zima, Omni's co-founder, missed all five of his first deals and still raised $250 million. Rafael Broshi, Notch's co-founder, let almost everyone go, kept two engineers, then grew the company 12 times, and raised a $30 million Series A. Ben Rudolph, Peregrine's co-founder, operated from a police department at no cost for one year, then built a $6.8 billion company. The outcomes differ, but the record does the same work: it says what the spend was supposed to prove.

Write the spend as a trust test

A pre-product brand bet names a buyer doubt. Without a written doubt, the spend becomes a taste argument, and the design bill pays for a preference instead of a problem.

Vanta checked a security trust gap around SOC 2, a security compliance standard, by putting a zero-code spreadsheet MVP, or minimum viable product, in front of potential customers before building the full product. Christina Cacioppo, Vanta's co-founder, validated the spreadsheet through her own network, sharing it with friends, former coworkers, and contacts at companies from very small startups to large enterprises. That discipline can apply to a brand spend before the design invoice is paid.

Keep the log in the operating rhythm

The list below is the minimum record. Each line is testable in a quick review, and each line exists to stop a different way the spend can drift.

• Amount: A fixed dollar number with a date, so exposure is visible before work starts.
• Buyer trust gap: A short sentence names the buyer and the doubt, so the brand is aimed at a problem.
• Category claim: A sentence a prospect can repeat, so the spend has a message to test.
• Founder channel: A named founder owns manual outreach to a reachable buyer segment, so the test does not depend on paid media.
• Validation milestone: A dated checkpoint says what must be true before more spend is approved.
• Kill condition: A dated trigger says when the spend stops if the milestone is missed.
• Evidence to review: A folder holds outreach replies, meeting notes, and spend receipts, so the review is a document.

A line that cannot be checked in a quick review is too vague to protect the spend. Put it where the next operating review will find it. The log is one page. It needs to be readable before a board meeting and survive a founder change.

Put the log with the operating notes, the board deck, and the cap table. Assign a named owner, because a shared document with no owner becomes a shared assumption. The owner should be able to say who approved the spend, what changed, and what the next checkpoint is. Review it at the same meeting where you review pipeline, because brand spend is a go-to-market input, not a side project. A spend large enough to need an invoice is large enough to need a decision record.

The trust gap line names the buyer and the doubt in plain language. A security reviewer may worry that compliance work will stall a deal. An operations lead may worry that the tool will require a long rollout. The category claim is a sentence the buyer can repeat to a colleague. A claim that needs a slide to explain is too soft.

The founder channel is manual. A founder can send a short message, book a call, and record the reply. Paid media can scale a claim, but it cannot create proof. The milestone is a buyer action: a logo, a deck, or a website is not one, while a buyer who asks for another call is.

The evidence folder holds the records: replies, call notes, spend receipts, and the decision made. When the next person inherits the company, the folder answers why the money was spent and what happened next.

Make the stop rule concrete

A brand spend without a stop rule becomes a sunk cost. Tie the stop rule to the buyer, not the design. A founder channel that cannot reach the buyer points to a reach problem, not a brand problem. A buyer who cannot repeat the category claim points to a claim that needs sharpening. Design taste invites a redesign; buyer response forces a go/no-go call. A stop rule also protects the team from arguing about taste after the invoice clears.

First Round Capital's PMF Method puts dollar-driven discovery, meaning discovery that asks for money, and founder-led sales at the center of business-to-business work before product-market fit. A pre-product brand bet can follow the same logic: the founder tests the claim with reachable buyers before the company pays for a broader audience. Make the brand spend answerable before the next invoice.

For a solo founder, one failed validation filter is enough to stop pursuing the idea. A solo-founder sequence starts with a one-page site in one day, 50 manual outreach messages over three days, and a channel proof inside one week before a go/no-go call. The idea should reach self-funding inside six months, either at $5,000 MRR (monthly recurring revenue) or through at least $30,000 in LOIs (letters of intent) from pre-selling. Those numbers are the kill condition's shape, not a substitute for buyer response.

Vanta finished its first full customer audit in November 2018. A milestone can be that concrete: a named buyer, a completed process, and a date. The kill condition can be equally concrete: no repeatable buyer response by the checkpoint, and the spend stops.

When the milestone date arrives, open the folder and make the call from the notes.