← Blog · Decision content
Your Strategic Decisions Are Marketing. You Just Never Published Them.
Every company has a shelf of hard calls: what to keep, what to cut, what to refuse to build. The reasoning behind them is the most persuasive material you own, and it is the one thing a competitor cannot write.
The shelf of unpublished decisions
Somewhere in your company there is a decision that took three months, two board conversations, and a near miss with a pivot. Someone argued for it. Someone lost. The product you sell today is the result. And the only public trace of it is a feature on the pricing page. This is the normal state of B2B SaaS marketing. Strategy happens in the room; the blog publishes the output. The output is a feature, a tier, an integration, a thing that is true of the product but says nothing about the thinking that produced it. The decision itself, with its pressure and its trade-offs, is kept private, as if it were a liability rather than an asset. It is the asset. Most of what a blog can publish is available to everyone in the category. Your decisions are not. We write about why a blog needs one core theme it returns to; the decisions behind your product are the richest source of that theme, because they are the places where you chose to be different on purpose.Why a decision beats a differentiator
A differentiator is a claim about the present: we have X, they don’t. It is useful right up until a competitor ships X, and then it is either false or embarrassing. We covered that decay in the governance piece. A decision story is a claim about reasoning: here is the situation we faced, the options we saw, what we chose, and what it cost us. Four things follow from that.- It is unique by construction. A competitor can copy a feature. They cannot copy the meeting where you decided to build it instead of something else, because they were not there and their meeting went differently.
- It ages well. If a competitor later matches the feature, the story still stands. You made the call first, for stated reasons, and the reader can see that. The differentiator article becomes a liability; the decision article becomes a record.
- It puts people in the product. Advanced buyers know that software is made by humans choosing under constraint. A story with an argument in it, with someone who pushed back, reads as true in a way that feature copy never does. That is the connection most B2B content has no mechanism for.
- It pre-answers the sales call. The question “why do you do it this way instead of the obvious way” comes up in nearly every serious evaluation. If the answer is already published, the prospect arrives having read it, and the call starts further along.
A feature tells a buyer what you built. A decision tells them how you think. They are buying the second one.
What we did at Zluri
Zluri sells identity governance. It also carries a full SaaS management product on the same platform, and for years that combination prompted the same question in analyst briefings and sales calls: why keep both? The implication was always that the SaaS management side was a leftover from the company’s origin, something they had not got round to shedding as they went deeper into governance. The honest answer was a decision, and it had been made deliberately, against advice to pick a lane. So we wrote it as one. Why We Kept SaaS Management Alongside Our IGA (When Everyone Told Us to Pick a Lane) opens with the question as it is actually asked, names the assumption behind it, and then argues the case: that every IGA revokes access when someone leaves, but almost none can tell you what that saved; that a platform which only knows how to grant and revoke has no lever for the most common remediation, which is a downgrade; and that the two products make each other better in ways an integration cannot replicate. Every one of those points was already true of the product. What changed was the frame. Written as a feature, “SaaS management included” is a bullet on a comparison grid that a competitor matches by adding a bullet. Written as a decision, it is an argument about how governance should work, with a company standing behind it and a reason it chose not to listen to the people telling it otherwise. The second article, on the total cost of running IGA and SaaS management separately, is the same decision viewed from the buyer’s ledger rather than the founder’s. One decision, two articles, one theme. That is repetition doing its job: the idea gets restated until the market associates it with the company.Neither piece announces anything. No launch, no new feature, no funding. The product was exactly the same the day before publication. The only new thing was that the reasoning was now public.
What a decision story needs
The difference between a decision story and a feature post is not tone. It is which questions the article is willing to answer. The table below sets the two side by side; the short version is that a decision story includes the parts most companies instinctively cut.
Feature post versus decision story: what each one is willing to say
In practice, the article needs five things, and the order matters.
| Question | Feature post | Decision story |
|---|---|---|
| What was the pressure? | Not mentioned | Named: the analyst, the board, the customer, the competitor move |
| What were the alternatives? | Not mentioned | Stated honestly, including the one most of the market chose |
| Who disagreed? | Nobody | Someone, and their argument is given fairly |
| What did it cost? | Nothing | A real trade-off: slower roadmap, a lost deal, a harder pitch |
| What does it reveal about the product? | A capability | A principle the capability follows from |
| Can a competitor publish the same? | Yes, next week | No |
- The question as people actually ask it. Not “our approach to X” but the thing prospects say on calls, including the skepticism in it.
- The context at the time. What the market looked like, what the conventional move was, why it was tempting.
- The options you weighed. Give the rejected option a fair hearing. A decision story where the alternative was obviously stupid is not a decision story.
- The reasoning, in the product’s terms. This is where it becomes product-led: the argument should be made with real workflows, real screens, real edge cases, not abstractions. The Zluri piece works because “downgrade” is a concrete verb the platform has and most others do not.
- The cost, stated plainly. What you gave up. This is the line that makes the rest believable.
Where to find yours
Companies assume they have no stories because they are not looking in the right places. The decisions are rarely filed as decisions. They look like this:- The feature you refused to build despite customers asking, and why the refusal was right.
- The product you kept when advisors said to cut it. Zluri’s case.
- The pricing model you abandoned, and what you learned about your buyer from how it failed.
- The integration you built first when the obvious one was a different vendor.
- The segment you walked away from. Every company that is focused got focused by saying no to someone specific.
- The architecture call that made one thing easy and another thing hard, and which customers that serves.
- The rename, the reposition, the category you chose not to use. Category decisions are the ones competitors are most curious about and least able to guess.
How these go wrong
The failure mode is predictable. A decision story gets routed through the same approval path as a press release, and everything that made it a story is removed: the pressure, the disagreement, the cost. What remains is a feature post with a narrative intro.
“We believe a converged platform delivers superior value to customers Two analysts and one investor told us to drop SaaS management and become a pure IGA vendor. We nearly did. Here is the customer conversation that stopped us.”
The second version is harder to approve and harder to write. It requires someone with enough tenure to know the story and enough standing to tell it straight. That is usually a founder or an early product leader, interviewed by a writer who has spent long enough with the product to know which details carry the argument and which are just colour.
Three other ways it goes wrong: making the rejected option a straw man, so nobody believes the choice was hard; hiding the cost, so the whole piece reads as a victory lap; and writing one and stopping, when the point is to return to the decision from several angles until it becomes the thing the market knows you for.
Key takeaways
- Your decisions are the only content a competitor cannot publish. Features can be matched; the reasoning behind them cannot.
- A decision story ages better than a differentiator. When the feature is matched, the record of having chosen it first, for stated reasons, still stands.
- It needs the parts companies cut: the pressure, the alternatives, the disagreement, and the cost.
- Make the argument in the product’s terms. Real workflows and real verbs, not principles in the abstract.
- One decision supports several articles. Zluri’s became a founder’s case and a buyer’s cost analysis. Repeat it until it is yours.