Priya ran outreach for a small software company, and every month her manager asked the same thing: how much did guest posting cost this time? She would open a spreadsheet, point to a total, and watch the conversation stall. The total was accurate. It simply did not answer anything. One afternoon she changed the question to “what does one live guest post cost us?” and the whole meeting changed. If you work in guest posting, you may have faced the same wall. Here are the questions people ask when they start to think in units, answered the way Priya eventually learned to answer them.<\/p>\n
It means everything spent on a month of guest posting, divided by the number of posts that went live. The word “live” matters. Pitches sent, drafts written and conversations opened do not count as units, because nobody can read them. Only a published piece can be shared, linked and measured, so it is the unit that deserves a cost.<\/p>\n
A monthly total moves for many reasons at once: more posts, fewer posts, a tool subscription, a freelancer’s invoice, a busy week. You cannot tell which reason mattered. A cost per live post filters out the volume effect and shows whether the process itself is getting heavier or lighter. It also gives you something to discuss that does not require a spreadsheet tour.<\/p>\n
Time, mostly. Researching a site, reading its guidelines, writing a pitch, drafting the article, handling edits, chasing a reply and fixing a typo after publication all belong in the unit. Priya’s first honest count surprised her, because the hours spent on pitches that never converted were larger than the hours spent writing the articles themselves. Hidden effort of this kind is the main thing a unit cost reveals.<\/p>\n
If the drafting stage is the heavy part of your unit, the article on speeding up article structure with reusable templates<\/a> is worth reading, because shortening one stage shortens the whole unit.<\/p>\n Then their effort still belongs to the programme. Divide it among the pieces that reached publication. It sounds harsh, but it is the only fair way to see the true cost of a successful placement. It also changes how you behave: when rejected pitches show up in the unit, people start choosing targets more carefully. The guide on pitching within a narrow niche so your article gets accepted<\/a> speaks to exactly that choice.<\/p>\n No, and this is where Priya nearly went wrong. For one quarter she celebrated a falling figure, then noticed the posts were landing on weaker sites and getting less attention. Treat the figure as a question rather than a target: when it shifts, find out why. A higher figure with better placements may be a good trade; a lower one that hides lost quality is not. Reading the number next to a view of post quality keeps you honest, and the notes on judging the worth of a guest article through lasting signals<\/a> help you pick the quality side of that pairing.<\/p>\n Some costs arrive every month regardless of volume: a tool licence, a retainer, a shared inbox. Others rise with each post: a freelancer’s fee for an article, an editor’s hours. Keep them in two lines. Divide the variable line by posts to get the cost of the next post, and treat the fixed line as the price of keeping the programme open. Priya found that her busiest months looked cheapest simply because the fixed line was spread across more posts, which is a perfectly normal effect once you can see it.<\/p>\n Ideally everyone who touches the process. The writer knows why a piece took longer. The outreach person knows why a site needed three follow-ups. The finance contact knows what the invoices actually contain. When these people read the same unit, the conversation moves from blame to explanation. That shared reading is the heart of FinOps, a discipline from the cloud world that Priya came across when a colleague in engineering mentioned it.<\/p>\nWhat if some pitches get rejected?<\/h2>\n
Should I aim for the lowest possible cost per post?<\/h2>\n
How do I separate fixed costs from per-post costs?<\/h2>\n
Who should own this number?<\/h2>\n
Where can I learn more about this way of thinking?<\/h2>\n