Somebody has to say a number first. In security creator deals, both sides usually hope it will be the other one. The brand does not want to anchor high, the creator does not want to anchor low, and a week disappears while everyone waits for an email nobody wants to send.
We are not going to publish a rate card. Any number we invented would be wrong for most of the people reading this, and the security creator market is small enough that a made up benchmark would do real damage. What we can do is describe the inputs that should determine a price, because most bad pricing comes from pricing the wrong thing.
Follower count is the worst available input
Pricing by audience size is imported from consumer influencer marketing, where reach genuinely is the product. In security it is not. The product is a specific person applying their judgment to your tool in public, with their professional reputation attached to the result.
That is why a newsletter read by four thousand detection engineers can be worth more than a post seen by four hundred thousand people who do not buy security software. It is also why two creators with identical follower counts can be worth very different amounts to the same brand. One has spent three years writing about Kubernetes admission control. The other has not. There is no audience metric that captures the difference.
Price the work, not the audience
Technical creator content carries production cost that consumer content does not. Someone reviewing your CNAPP properly is not writing a caption. They are standing up a cluster, breaking something on purpose, capturing what the tool did and did not catch, writing it up, and then defending all of it in the comments for two days.
A defensible price is built from line items, not vibes:
- Hands on time. Environment setup, testing, reproducing anything unexpected, and tearing it down again.
- Writing and editing. Usually the smallest part of a technical piece, which surprises brands.
- Original artefacts. A repo, a script, a diagram, a demo recording. These outlive the campaign and should be priced accordingly.
- Review cycles. Capped at a stated number, because uncapped review is where budgets and goodwill both die.
- Post publication engagement. Answering technical questions in the comments is part of the deliverable, and it is billable time.
Four things that legitimately multiply the number
Once the base work is costed, four factors move the price up, and all four are things a brand is asking for on top of the post itself.
- Depth of hands on work. An opinion piece and a tested teardown are different products with different liability attached.
- Usage rights. An organic post is one price. Paid amplification, use on your website, and a permanent slot in the sales deck are three more.
- Exclusivity. Every competitor the creator cannot work with for six months is revenue they are giving up on your behalf.
- Turnaround. A rush job around a launch date displaces other work, and it is reasonable to charge for that.
Costs creators routinely forget
Practitioners who are new to sponsorship almost always underprice, and the missing costs are consistent. Lab infrastructure and licences for the test environment. The hours spent getting employer approval, which for anyone at a large security vendor can be substantial. The ongoing responsibility of a post that stays live with their name on it long after the invoice clears. And the quiet opportunity cost of the competitor who will now not call.
None of these appear on a media kit. All of them are real.
What a cheap price is actually buying
Brands sometimes treat a low quote as a win. It is usually one of two things. Either the creator has priced for a surface level post and will not be testing anything, in which case you are buying a placement and should not expect it to convince an engineer. Or they are underpricing because they are early and do not know the market yet.
The second case is worth handling carefully. Paying somebody properly the first time is how a one off sponsorship becomes a creator who will still take your call in two years. Squeezing them is how you end up back at the top of the funnel every quarter.
A method for the first deal
If you have no reference points at all, estimate the hours honestly, apply the day rate the creator would charge or be charged for consulting work, then add for usage rights and exclusivity. Round up rather than down, because first estimates in technical work are almost always low.
This often produces a number that feels high for a single post. That reaction is useful information: a single post is a poor unit to buy. The same budget spread across three pieces over a quarter gives the creator room to build an argument and gives the brand something a security buyer can actually follow.
Put the number and the scope in the same message
A price with no scope attached invites negotiation on everything at once. A price sent alongside the deliverables, the review cap, the usage rights, and the exclusivity terms gives both sides something specific to adjust. If the brand needs a lower number, they can drop a right or shorten an exclusivity window rather than asking for the same work for less.
Influous is pre-launch, and one reason we are building it is that this conversation currently happens in private, one awkward email at a time, with no shared vocabulary on either side. If you are a security practitioner who publishes, you can apply as a creator. If you are a brand working out what a technical campaign should cost, write to us at info@influous.io and we will talk it through honestly.