In 1513, Niccolò Machiavelli sat in exile and wrote the most ruthlessly practical guide to power ever committed to paper. He wasn’t interested in how things should work. He was interested in how they do.
Five centuries later, most SaaS companies treat their user documentation as an afterthought: a support cost to minimise, a page to publish and forget. Machiavelli would have wept.
“It is better to be feared than loved, if you cannot be both.”
What Machiavelli understood is that power is engineered, not inherited. Your documentation is the most underused weapon in your arsenal.
Great user documentation is a customer acquisition engine, a competitive moat, and a conversion machine, if you are ruthless enough to use them that way.
Chapter I: Know thy enemy’s weaknesses
“The wise man does at once what the fool does finally.”
The Prince, Chapter 3
Before you write a single word of documentation, open your competitor’s help centre and read it like an adversary. Where does it go silent? What questions are left unanswered? What frustrations are users voicing in Reddit threads, community forums, and Stack Overflow posts?
These are open wounds, and your opportunity.
- Use tools like Ahrefs or SEMrush to find queries that rank for your competitor’s product but return thin or unhelpful answers
- Search “[Competitor Name] + problem / error / how to” and catalogue every unanswered question you find
- Build documentation that directly addresses those gaps by solving the problem better than they do
- Notion captured a generation of Evernote users through migration guides and honest comparison pages rather than advertising. That is the play.
Chapter II: Infiltrate the kingdom aka AI search and chatbot optimisation
“One who deceives will always find those who allow themselves to be deceived.”
Attr. Machiavelli
If you think about how people actually solve problems today, they don’t type “best CRM software” into Google and read ten reviews. They type:
- “Why is HubSpot so slow at loading contacts?”
- “How to export data from Salesforce to CSV without errors?”
- “ChatGPT, what’s a cheaper alternative to Asana?”
They’re searching for answers. They’re one bad experience away from switching.
Then they ask their AI chatbot of choice and they trust the answer. Those AI engines are desperate for reliable, structured, authoritative data.
AI-powered search has changed who surfaces first. When a user types “how do I export data from [Competitor]” into ChatGPT, Perplexity, or Google’s AI Overview, the response they receive is synthesised from the best-structured, most authoritatively written content on the topic.
If your documentation answers that question, your product gets recommended.
Your new playbook
Your job is to be the useful ghost that appears right when they need an escape.
- When a user asks an AI “How do I fix [Competitor X’s common error]?” – who gets cited? If you’ve done your job right, you do. Write “How to do X in [Competitor] and a faster way” articles that are genuinely useful. They don’t need to be adversarial
- Write universal, category-first content that ranks for high-intent informational queries, even when the user isn’t looking for you.
- List every frustration, limitation, or missing feature of your top three competitors. Turn each into a natural-language prompt.
- Use clear hierarchical structure (H2s, H3s, short paragraphs) that LLMs favour when constructing summaries
- Contribute helpfully to Stack Overflow, Reddit, and GitHub Discussions with answers that reference your product naturally and honestly
- Schema markup any FAQs so they surface in AI overview panels
The goal is positioning. If someone is frustrated with a competitor’s workflow and your documentation shows them a better path, you have not manipulated anyone, you have served them.
Chapter III: The art of the migration guide
“Men are so simple and so much inclined to obey immediate needs that a deceiver will never lack victims.”
The Prince, Chapter 18
The most valuable users you can acquire are the discontented. This is because they are already motivated to act. They have already done the hard work of deciding their current tool isn’t working. Your job is to remove every remaining barrier.
A great migration guide does these things:
- Acknowledges the switching cost honestly; don’t pretend it’s nothing
- Maps familiar workflows in the old product to equivalent (or superior) workflows in yours
- Anticipates objections and answers them before the user has to ask
These pages rank for the highest-intent searches imaginable: “switching from X to Y,” “X alternative,” “migrate from X.” Someone searching those terms is one good documentation page away from becoming your customer.
Chapter IV: Fortify your own kingdom
“A prince who relies entirely on fortune is ruined when fortune changes.”
The Prince, Chapter 25
Machiavelli’s sharpest warning: a strategy built entirely on exploiting others’ weakness is fragile. The moment your competitor improves, your advantage evaporates. You must build something genuinely unbeatable.
- Sandbox environments where users can run code examples without leaving the page
- Versioned documents that stay accurate across product updates. Nothing erodes trust faster than stale instructions
- An open, public changelog that signals momentum and demonstrates that someone is paying attention
- Search that actually works: semantic, fast, and forgiving of spelling errors
The documentation moat is self-reinforcing. Better documentation attract more users. More users generate more feedback. Better feedback produces better documentation. Competitors cannot copy this easily. It compounds over years.
Chapter V: Win the loyalty of the people
“It is necessary for a prince to have the people on his side; otherwise he has no security in adversity.”
The Prince, Chapter 9
Machiavelli understood something that modern growth teams often miss: the most durable power comes from genuine loyalty. A community that believes in your product will defend it, advocate for it, and produce content about it that no marketing budget could replicate.
- Build a community forum directly adjacent to your documentation. Let users answer each other’s questions and surface those answers back into the official documentation
- Run a documentation ambassador programme: power users who contribute tutorials, translations, and edge-case guides in exchange for recognition and early access
- Create a public roadmap for documentation itself. Show users what’s coming and invite them to vote on priorities
Chapter VI – Control the narrative
“Everyone sees what you appear to be; few experience what you really are.”
The Prince, Chapter 18
The language you use in your documentation shapes how users think about the problem space. This is framing. Every product does it. The question is whether you do it consciously.
Name things in ways that centre your product’s conceptual model as the natural default. If your approach to a workflow is genuinely superior, give it a name that sticks. Reference industry standards your product meets, and that competitors quietly don’t. Let the facts do the persuading; the structure of your documentation amplifies them.
The ethical line
Some might ask, isn’t this manipulative?
Do not lie. Influence the environment so that the truth your product’s genuine superiority becomes visible at the precise moment a customer needs it:
- Publishing accurate, useful information
- Ensuring frustrated users can find a better way
Conclusion – The ruthless editor
Machiavelli’s final lesson was about will. Most of his advice was simply the courage to act on what everyone already knew but no one was willing to say aloud.
Most companies know their documentation is inadequate. They know competitors’ documentation has gaps. They know AI search is changing everything. They just don’t treat documentation as a strategic function worthy of real resources and real ambition.
Treat your documentation team like a product team. Give them a roadmap, a backlog, metrics, and a mandate. Audit quarterly. Cut ruthlessly what doesn’t serve you. Double down on what does.
The prince who does this, who turns the help centre into a competitive weapon, will find that customers arrive already convinced, already loyal, already sold. Not because of advertising. Because of the documentation.
Inspired by Niccolò Machiavelli, The Prince (1532).
Leave a Reply