Four reasons an audience is worth money
There are four common answers. They pull a content system in different directions.
They're concentrated. Your readers share something a third party wants to reach, like an industry, a job title or a software stack. A newsletter for dental practice managers can sell a sponsorship that a general business blog would struggle to. Advertisers already pay for this. Google Ads lets them target a country, an area within it, or a radius around an address. A small audience made of one kind of person is a targeting option somebody would otherwise have to build.
They control budgets. Your readers are the people who approve the spend. There aren't many of them, and they're expensive to reach. One finance director reading your piece the week before a vendor review can matter more than a month of traffic.
They want something they can't get elsewhere. Original data, a calculator that does real work, a point of view that commits. These readers will trade an email address, a meeting, or money for it. The value sits in the scarcity, so it disappears once the content turns into the same summary everyone else publishes.
A few of them will hire you. For an agency, a consultancy, or any company with a sales team, this is the answer that pays the bills. Most readers will never buy. The system exists for the handful who will, and the question is whether the piece convinced them.
A company can have more than one of these. It almost never has all four in equal measure, and the expensive mistake is building one system that pretends it does.
Before you decide how much to publish, decide which of these four your readers are.
Each answer builds a different system
When the value is concentration, the system's first job is protecting the definition of the audience. Every brief names who the piece is for. The kill list includes anything that widens the readership by making it vaguer. A general explainer that ranks well and pulls in students looks like growth on the dashboard. For this audience it's dilution.
Budget control calls for writing toward decisions. The brief carries the objection a buyer raises in a vendor review and the comparison they're going to run anyway. A handful of questions asked right before a purchase matter more than volume. Mentions work the same way. An AI citation that sends the wrong buyer costs a sales call, so counting it as a win flatters the wrong number.
Scarcity changes where the money goes. The savings from cheap drafting should pay for data, interviews and experiments, because the inputs competitors can't copy are the only part a reader would pay for. Every extra summary makes this kind of program a little less worth reading.
The fourth case, the buyer who hires you, is ours too.
Write down why your readers are worth money. Then check whether your briefs and your kill list agree with it.
Make every article a preview of the paid work
A services company sells judgment applied to a specific problem. Its articles should show that judgment working on a problem the reader recognizes. If someone finishes the piece and knows what to change on their own site, the article has done a small, free version of the job a client pays for.
That gives you a test for any draft: could someone who's never done the work have written it? If so, it won't sell the work. A post called "10 tips for better content" fails. A post that takes a real page apart, names what's broken, and says what we'd fix first passes, because it's the same thing we do on a paid engagement. Our free teardown is the literal version. It's the product with the invoice taken out.
The system has to protect this at the brief. Once a pipeline drafts against a generic brief, no editor can add the missing experience at the end. The brief needs the actual case, the actual numbers, and the decision the reader should leave with. The human edit still matters. It just can't add a point of view the brief never had.
If your articles could have been written by someone who's never done your job, they won't convince anyone to hire you for it.
Count the reader, not the row
Once the goal is buyers, the score changes. Sessions can stay on the dashboard as context. The number that runs the system is the inquiry, meaning a form submitted or a demo booked. Google Analytics already handles this. You mark the form submission as a key event and report on the channels that lead to it.
Then read what came in, because a count can lie too. An intake form on one of the sites we run logged five requests between October 10 and November 9. On a dashboard, that's a month of demand. All five were bots. The answer fields held strings like "Uuukgpzoer," and nobody had looked at them. One of our own planning documents had already counted them as $15,000 a month in interest. Real inbound from that form for the month was zero. We found out when someone finally read the text.
So read each inquiry before you count it. Give every public form the basic spam filtering it should have had on day one. A system that can publish thousands of articles still needs a person to look at the five things that came back.
Score the system on inquiries, and read every one before you count it.
Ask why, at the moment they ask
The most useful question a form can ask is the one most forms leave out: what made you get in touch today?
Ask it at the moment of contact. Right then, people can still tell you what tipped them, whether it was an article or a problem that got worse last week. A survey three weeks later gets a tidier answer, and in our experience a less useful one.
Our own contact form asks what the visitor is after. It doesn't ask why now, and "why now" is the better question. "What you're after" tells you which service they want. "Why now" tells you the trigger, and triggers are what briefs should be built around. Say the same reason turns up four times, something like "our traffic fell when the AI answers started." That's the next cluster of articles, written in the words buyers used.
The answers go back into the research step. The next briefs pick them up, and the next round of articles aims at the reason people buy instead of the keyword with the biggest search volume.
Add one question to your contact form: what made you get in touch today?
Price the article as parts
One article usually does several jobs. A system that books it as a single "post" under-counts all of them.
The same piece can be a page on the blog, an issue sent to subscribers, and a native LinkedIn post. It can be the paragraph a salesperson pastes into a follow-up email, or the page an AI answer cites when a buyer asks a chatbot for options. Our own system drafts the LinkedIn version of each article into a queue that sits next to the blog. Each version has its own audience and needs a bit of its own work.
Bundling them under "one blog post" causes two problems. The piece gets budgeted as if it does one job, so nobody pays for the other versions. And nobody measures the other jobs. The system can't see that the copy in a sales email helped close a deal while the blog page drew a few dozen visits. You only see that with a content flow that keeps tracking the piece after it's published.
Give each version of an article its own budget line and its own number.
The first read is an audition
The buyer who hires you rarely does it after one article. The first piece is an audition for the second. After publishing, the system's job is to make that second read likely, with an internal link that finishes the thought or a signup that promises the next useful thing.
So judge an article by what it does to the relationship. Imagine a piece read by 60 people that brings three back for a second article and sends one to the contact form. Next to a piece read by 6,000 who leave, the small one did more. A pageview report hides that. Inquiries tracked by the path that led to them show it.
Track the path from first read to inquiry. That's where an article's value shows up.
Where this leaves volume
We like volume. We run a dozen content sites on one system, and it's built to publish a lot. Cheap production lets you cover every question a buyer asks before they buy.
What changes is what the volume is for. A system pointed at sessions will find the cheapest sessions available, and those are rarely the people who sign. Point it at a defined reader instead. Score it on inquiries and feed it the reasons buyers give. The same cheap production then moves more of the right people toward a call.
Work out what your readers are worth, and to whom, before you decide how much to publish.
If you'd like a second opinion on what your current content is counting, the teardown is free.
