--- title: "How to turn one product sentence into a 30-title content backlog" description: "One clear product sentence contains everything you need to build a 30-title content backlog - here's a two-hour loop that takes you from claim to ranked writing queue." author: "Roey Granot" category: "Growth Playbooks" date: 2026-09-11T06:01:15.454Z canonical: "https://contentagents.dev/blog/how-to-turn-one-product-sentence-into-a-30-title-content-backlog-790u" --- # How to turn one product sentence into a 30-title content backlog ![Overhead flat-lay of a desk with one torn paper strip at the top and rows of smaller slips fanned out below it.](https://hsppuvezyxmkpzkgfkho.supabase.co/storage/v1/object/public/media/enrichment/024a6468-4c4c-4195-b8c2-21b4170617d4/0438b918-b8ff-4409-9b58-5a17e163925b/cf865430-63ce-4a45-9070-8644ab2eec2a.png) > One clear product sentence contains everything you need to build a 30-title content backlog - here's a two-hour loop that takes you from claim to ranked writing queue. Most founders treat content planning as a research problem. They open a keyword tool, stare at search volumes, and try to reverse-engineer topics from data they don't fully trust. The result is a backlog that looks strategic but has no connection to what they actually sell. There's a shorter path. One honest product sentence - the kind you'd say in a sales call - contains enough material to build a 30-title content backlog. No keyword tool required to start. No content strategist needed. Here's how to run the loop in roughly two hours. ## Step 1: Extract the core claim from your product sentence Start with a sentence you already use. Not your tagline - that's usually too polished to be useful. The sentence you say when someone asks what your product does. Something like: *"Our tool turns messy spreadsheets into clean databases."* Break it into three parts using this template: PROBLEM: [what the user starts with or suffers from] SOLUTION: [what your product does] OUTCOME: [what the user ends up with] Example: PROBLEM: messy spreadsheets SOLUTION: turns them into OUTCOME: clean databases Fill this in for your own product. It takes under two minutes. You're not writing copy - you're isolating the mechanism. Once you have the three parts, write one claim statement in each of these registers: - **Technical:** "Convert unstructured spreadsheet data into a normalized relational database without writing SQL." - **User-benefit:** "Stop cleaning spreadsheets by hand - get a structured database in minutes." - **Business-outcome:** "Teams that migrate from spreadsheets to databases cut reporting time by hours per week." These three phrasings are the same product claim. They're not the same article. Angle matters more than topic. What this step will not do: it won't tell you whether your claim resonates with buyers or maps to real search behavior. That's validation work. Right now you're just naming the thing clearly. ## Step 2: Spin the claim into 10 angle variations An angle is the lens through which you approach the same claim. Use this three-axis framework to generate yours: - **By audience:** founder, ops manager, data analyst, engineer - **By outcome:** speed, cost reduction, accuracy, team collaboration - **By format:** how-to, why-now, comparison, cautionary tale, case study Use this template in a doc or spreadsheet to generate 10 combinations: PRODUCT_CLAIM: [your one-line claim from Step 1] AUDIENCE: [who this is for] OUTCOME_TYPE: [what they care about most] FORMAT: [how-to / why-now / comparison / other] Angle output: [AUDIENCE] who want [OUTCOME_TYPE] - addressed via [FORMAT] Example: PRODUCT_CLAIM: Convert spreadsheets into clean databases without SQL AUDIENCE: Ops managers OUTCOME_TYPE: Accuracy FORMAT: How-to Angle: Ops managers who want cleaner data - addressed via a how-to Run through 10 combinations. You'll notice some repeat the same territory. That's useful information. The decision point: pick 5-7 angles that feel distinct and defensible. Watch for two failure patterns. Too similar - six variations of "how-to for ops managers" gives you a backlog with no range, and you'll exhaust that audience fast. Too scattered - mixing "enterprise data migration" with "solo founder productivity" means no single reader feels like you're speaking to them. A useful test: if you swapped the audience between two angles and the article wouldn't change much, they're too close. Cut one. What this step will not do: it won't tell you which angles will convert or rank. That's validation work. Right now you're generating options, not commitments. ## Step 3: Expand each angle into 3 specific article titles For each of your 7 angles, generate 3 titles using this pattern: **[Angle] + [Format] + [Specificity]**. Specificity is what separates a title a reader clicks from one they skip. Take "speed" as the angle for an ops manager audience: - Low specificity: "How to Work Faster with Better Data" - Medium specificity: "How Ops Teams Cut Reporting Time by Cleaning Up Their Spreadsheets" - High specificity: "Why Your Weekly Ops Report Takes 4 Hours - and How a Database Fixes That" The third title is the one worth writing. It names the problem precisely, implies a cause, and offers resolution. Use this template to generate titles for each angle: ANGLE: [from Step 2] AUDIENCE: [who it's for] FORMAT_TYPE: [how-to / why-now / comparison / other] SPECIFICITY: [low / medium / high] Title attempt 1: [generic version] Title attempt 2: [add a specific role or context] Title attempt 3: [add a specific number, time, or scenario] Keep: [title 3, or whichever is most specific and honest] Seven angles, three titles each, gives you 21. You'll likely generate a few more as you work. Round up to 30 by returning to your strongest angles and running one more pass. The trimming decision: a founder working through this exercise recently ended up with 21 titles where three were nearly identical - all "how-to" pieces for ops managers on the same outcome. Keeping all three would have produced redundant content. Cutting two of them and replacing them with a comparison piece and a cautionary-tale piece improved range without losing the audience. Also watch for titles that feel off-brand - if your product is deeply technical, a listicle-style title like "7 Signs You Need a Database" may not fit how your buyers think. The same instinct applies when evaluating whether [your content stack is aligned with how buyers actually make decisions](/blog/why-your-content-stack-is-quietly-costing-you-deals-gaci) - a mismatch there can undermine even a well-structured backlog. What this step will not do: it won't rank these titles by search volume, intent, or competitive difficulty. That's research, not generation. You're building raw material here. ## Step 4: Validate and prioritize your 30-title backlog Before you write anything, run each title through a short checklist. Four questions: - Does this map to something a real person would search for or ask in a sales call? - Does it fit how your brand actually speaks? - Can you write a credible version of this in 1-2 weeks? - Does it connect clearly to your product - not tangentially, but directly? Then score each title in a simple spreadsheet: TITLE: [article title] SEARCH_INTENT: [1-3: how clearly does this match something people look for?] BRAND_FIT: [1-3: how well does this match your voice and product?] RESOURCE_COST: [1-3: how hard is this to write well? 1 = easy, 3 = hard] PRIORITY_SCORE: [SEARCH_INTENT + BRAND_FIT - RESOURCE_COST] Sort by PRIORITY_SCORE descending. Top 10 become your first wave. The prioritization question every solo founder hits: write the easiest titles first, or the highest-intent ones? The honest answer depends on your situation. If you've published nothing yet, write easy titles first - they build the habit, give you something to share, and generate early feedback. If you have a small existing readership or a specific campaign deadline, go for highest-intent first - those titles have more leverage per article. Both paths are valid. What doesn't work is writing randomly, which is what most people do when they skip this step. Once your backlog is running, tracking which titles actually perform requires moving [beyond raw pageview counts to metrics that reflect real content impact](/blog/beyond-the-pageview-engineering-content-intelligence-with-ga4-gsc-8abd). What this step will not do: it won't tell you which titles will drive traffic or leads. That's post-publication analytics. You're making a planning decision, not a performance prediction. ## The whole loop on one page ![](https://cdn.pixabay.com/photo/2019/08/16/15/12/landscape-4410506_1280.jpg?w=960&q=75) Photo by [Kanenori](https://pixabay.com/photos/landscape-lake-world-2nd-clear-lake-4410506/) on [Pixabay](https://pixabay.com) The four steps in sequence: Product sentence → Step 1 (15 min): Extract core claim - outputs 1 claim in 3 registers → Step 2 (30 min): Spin into 10 angle variations - outputs 5-7 distinct angles → Step 3 (45 min): Expand each angle into 3 titles - outputs 21-30 titles → Step 4 (30 min): Score and prioritize - outputs your first 10-title wave If you find that executing the writing itself becomes the bottleneck, it's worth examining [where human review still adds the most value in an AI-assisted content workflow](/blog/ai-content-workflows-where-human-review-still-matters-jq5d) - the planning loop above pairs naturally with that kind of division of labor. ## FAQ ### How do I build a content backlog if I don't know my target keywords? Start with your product claim, not keywords. Keywords are a validation layer, not a starting point. If you can describe what your product does, who it helps, and what outcome it creates, you have enough to generate 30 content angles. Keyword research helps you prioritize later - it doesn't need to drive ideation. ### How many articles should I publish per month as a solo founder? One well-written article per week is a strong target if you can sustain it. Two per month is realistic if writing competes with sales and product work. The frequency matters less than the consistency - a backlog of 30 titles gives you 6-15 months of content at most solo publishing rates, so you won't run out of ideas mid-stride. ### Can I use an AI tool to run this loop instead of doing it manually? Yes, with one caveat. Steps 2 and 3 - generating angle variations and title drafts - work well with an AI assistant if you give it --- Source: https://contentagents.dev/blog/how-to-turn-one-product-sentence-into-a-30-title-content-backlog-790u