“What’s the ROI of this $15,000 going to be?”
It was 2012. The executive asking ran a regional ed-tech company breaking into the K–12 one-to-one market, and he was about to put fifteen thousand dollars into a radio ad. I’d talked him into considering social media instead. Then he asked the one question that, at the time, almost nobody in marketing could actually answer. Not the good ones. Not the expensive ones. Proving marketing ROI wasn’t a discipline yet. It was a promise everyone made and nobody kept.
I said I’d get him a number. Then I went and figured out how.
Believe it or not, my search for ROI started back in high school. I wasn’t exactly a straight-A student—more like a C student who spent a lot of time daydreaming about the future. I imagined a life where my dog and I started our day on a front porch, coffee mug in hand, running our own bed and breakfast. I even wrote my senior paper on the business I would one day own. Those daydreams, though simple, planted the seeds of an entrepreneurial spirit that would carry me through my adult life.
As I matured in my profession, I learned that every marketer eventually hears some version of “no more budget until you prove ROI.” It lands like a threat because it’s usually pointing to your spend is up, pickup is down, and the person who signs off wants to know why the money isn’t showing up as results. When you’ve never owned a number, that conversation is where marketing careers quietly stall.
Here’s what most people get wrong about that moment. They treat it as a reporting problem and build a prettier dashboard, pull better numbers after the fact. It isn’t a reporting problem. It’s an architecture problem. If you didn’t build the tracking before you spent the money, you’re not proving ROI. You’re guessing with confidence.
If you didn’t build the tracking before you spent the money, you’re not proving ROI. You’re guessing with confidence.
The marketers who can answer the ROI question aren’t better at making the case afterward. They set the business up to answer it before the first dollar goes out.
I didn’t get into that room on a résumé. My kids were taking piano lessons from a friend at a local church, we got to talking, and it turned out he was a Sales Exec at the company. That’s the whole origin — proximity, not polish. It’s the same thing I’d spend the next decade building for clients on purpose.
The owner took a chance on me, and I pitched an experiment instead of an ad. We’d give away a tablet for a student and teacher, plus the connectivity to take one classroom fully one-to-one for free. Over a month I built the landing page, stood up tracking in Google Analytics, and designed a submission form that showed me exactly which search terms led to a completed entry. Then I wrote to those terms, because every one of them was a pain point somebody was typing into a search bar. I joined ed-tech conversations on Twitter under the company’s banner while making the funnel legible from the first click.
The result was twenty leads for the sales team, and nine of them were high-quality prospects interested in infrastructure — the kind of deal that ran into the quarter-million-dollar range. My contract ended before I could watch the full sales cycle close. But I walked out with something more useful than a commission: proof that the question everyone was afraid of had an answer, if you built for it up front.
Since that 2012 experiment, I start every role and every contract the same way. Before I run anything, I build the infrastructure that will answer the ROI question because I know it’s coming, and I’d rather have three answers ready than scramble for one.
That means the tracking goes in before the spend, not after the ask. It means a submission form isn’t just a lead-capture tool, it’s a research instrument that tells you which words your buyer actually uses. It means the content gets written to the pain points the data surfaces, not the ones you assume they have. And it means a dashboard exists on day one that ties every tactic back to what it was supposed to return. So when someone asks “is this working,” the answer is on a screen, not in your gut.
Nearly fifteen years later the tools are better and the dashboards are custom, but the sequence hasn’t changed. Build the way you’ll measure before you spend the money you’ll be asked about.
The uncomfortable truth is that proving ROI early can expose things people didn’t want exposed. When you make the funnel legible, you don’t just get to show what’s working — you also can’t hide what isn’t. A campaign someone loved turns out to drive nothing. A channel the owner is attached to leaks money in plain sight.
That’s the part that takes nerve. Tracking from day one is a commitment to being accountable to the number even when the number isn’t flattering. Plenty of marketers avoid it for exactly that reason. A vague “more brand awareness” never has a bad month. But you can’t build trust with an owner on numbers that only ever look good. You build it by being the person who shows the real ones and then fixes them.
A vague “more brand awareness” never has a bad month. That’s exactly why it’s worthless.
Stop asking “how do I prove the ROI of what I already spent?” Ask “what would I need to have built to answer that question the day it’s asked?”
The first question is a scramble. The second is a system. One turns every budget review into a defense; the other turns it into a status update. The difference between them isn’t talent or budget — it’s whether you did the boring, unglamorous work of wiring up measurement before you needed it.
That $15,000 question felt like a threat in 2012. Now it’s the first thing I want a client to ask me, because I already know the answer will be there when they do. That’s not confidence, it’s the architecture.