TOFU, MOFU, BOFU: What These Tags Mean for Content Writers
If you write content for software companies, you've probably seen a brief with "TOFU," "MOFU," or "BOFU" in the tag and figured you'd work it out as you go. Sometimes that works. Often, it's why editors send drafts back.
These three terms describe where a reader sits in their journey from "I've never heard of this product" to "I'm ready to buy." You'll usually see them as tags on a content brief from an editor or content manager. They're not just labels. Each stage changes what you should teach, how prominently you should mention the product, and what the reader actually needs from the article.
Getting this right is one of the more practical skills you can build as a content writer. Here's how each stage works and what it asks of you.
Top of Funnel (TOFU): Teach the Concept, Skip the Pitch
The TOFU reader has a problem or a question but doesn't yet know what solutions exist, or that your company does. They're searching to understand something, not to buy anything. Their queries are broad and educational: "what is kubernetes," "why do containers crash," "what is observability," "exit code 143 meaning."
Their intent is to learn. They want terms defined and concepts explained.
Your job is to teach the concept thoroughly and mention the product lightly, if at all. The goal is trust. If the reader leaves the article feeling like they learned something useful, your company earns a place on their shortlist for when they eventually need a tool. A heavy product pitch at this stage kills that trust immediately.
The tone should be educational and foundational. Assume the reader might be new to the topic. Cover the basics before going deep.
Example topics:
"What are Windows Error Logs?"
"What is visual regression testing?"
Middle of Funnel (MOFU): Help the Reader Evaluate
The MOFU reader already understands the problem. Now they're researching solutions, comparing tools, and narrowing down their options. They know products exist in this space. They're looking for tradeoffs, not definitions. Their queries reflect that: "Datadog vs Middleware," "best observability tools in 2026," "open source alternatives to Splunk."
Their intent is to evaluate, compare, and shortlist.
Your job is to position your product honestly among alternatives. Explain where it fits, where it doesn't, and why it might be the right choice for certain use cases. A good MOFU piece isn't afraid to acknowledge where a competitor has the edge. That honesty is what makes the comparison credible.
The tone should be analytical and confident, not dismissive of alternatives.
Example topics:
"SigNoz vs Datadog: When to choose each"
"Mem0 vs OpenAI Memory: A benchmark comparison"
"Top 5 test management tools for enterprise teams"
Product mention: Direct but not aggressive. The product appears as one legitimate option being evaluated alongside others, or as the recommended solution with clear reasoning.
Bottom of Funnel (BOFU): Prove the Product Works
The BOFU reader has already narrowed their options. They might have your product on their shortlist. What they need now are proof points: specific use cases, real configurations, implementation steps, and a reason to commit. Their searches are high-intent and specific: "Middleware pricing," "how to set up Middleware for Kubernetes," "Mem0 SDK quickstart."
Their intent is to decide, validate, and implement.
Your job is to remove the last obstacles between the reader and a purchase. Show the product in action. Use real scenarios and real numbers. The article isn't about explaining what the product category is. It's about showing exactly how your product solves a specific problem, with steps.
CTAs should be strong and direct: demo, signup, docs, sales call.
Example topics:
"How to monitor exit codes with Middleware in 5 minutes"
"Step-by-step: Setting up visual testing with SmartUI"
"Migrating from Datadog to SigNoz: A complete guide"
Where MOFU and BOFU Overlap
When you see an article tagged "MOFU-BOFU," the brief is asking you to serve readers who are somewhere between evaluating and deciding. These articles tend to address a specific technical problem while demonstrating your product solving it. They include comparisons or tradeoffs alongside implementation steps or CTAs.
A good example of what this looks like in practice: "How to handle graceful shutdown in Kubernetes with Middleware" is MOFU-BOFU. The reader has a real problem (SIGTERM handling), is looking at solutions, and the article shows your product as the answer with enough detail to actually implement.
How This Changes Your Writing in Practice
For TOFU, your job is to teach the concept. The product is incidental. For MOFU, you're helping the reader evaluate, and the product is one credible option among several. For BOFU, you're proving the product works for their exact case, and the product is the subject. For MOFU-BOFU, you're solving a specific problem using the product, with enough context that someone still evaluating can follow along and enough depth that someone ready to implement has what they need.
Why Funnel Stage Affects Tone, Structure, and SEO
Tone shifts across all three stages. TOFU content is educational and mostly neutral because the reader isn't ready to hear a sales pitch yet. By MOFU, you can be more analytical and direct about your product's strengths. By BOFU, the tone is directive and product-centric because the reader wants specifics, not a primer.
The same shift applies to keywords. TOFU targets broad informational queries where people are still learning. MOFU goes after comparison and evaluation terms. BOFU targets branded and high-intent searches from people who are close to a decision.
CTAs follow the same logic. A TOFU article might end with a newsletter signup or a link to related reading. MOFU might invite the reader to try a free trial or see how the product works. BOFU earns the harder ask: book a demo, talk to sales, start implementing.
Length and depth adjust too. TOFU articles tend to run longer because they're covering a broad topic for readers who may be unfamiliar with the space. BOFU articles are usually tighter and more procedural because the reader already understands the context and just needs the answer.
Three Questions to Ask Before You Start Writing
Ask yourself three questions when you see the tag:
What does this reader already know? (Less for TOFU, more for BOFU)
What are they trying to do? (Learn, compare, or decide/implement)
How prominent should the product be? (Barely, moderately, centrally)
If your draft doesn't match the tag on those three dimensions, that's usually what's behind feedback like "this feels too promotional for a TOFU piece" or "this doesn't push the product enough for BOFU."
If you found this useful, subscribe to my newsletter for more content on technical writing, content strategy, and working with developer tools.
