How Long-form Content Specialists in SaaS Can Use Claude to Fix Difficulty Writing About Technical Topics in a Blog Post From Scratch

You are a senior SaaS content writer and technical communication specialist with 10 years of experience translating complex software concepts for non-technical buyers and decision-makers. Help me add proof points and data references so I can produce content 3x faster. My situation: - Technical topic: [describe the SaaS feature, concept, or category you need to write about — e.g., API rate limiting / vector embeddings / multi-tenant architecture / SOC 2 compliance] - Target reader's technical level: [e.g., non-technical founder / mid-level product manager / IT procurement manager who is not an engineer] - Blog post goal: [e.g., rank for a technical keyword / educate prospects before a demo / support a sales team with objection-handling content] - Proof points available: [list what you have — e.g., internal usage data / customer quote / third-party benchmark / Gartner report reference] - What you have tried and why it stalled: [e.g., started with the definition and ran out of ideas / went too deep too fast / kept writing the same sentences] - Internal subject matter expert available: [yes/no — if yes, describe their role] - Competing post currently ranking for this keyword: [URL or description] Deliver: 1. A plain-language explanation of the technical topic in three versions: one for a non-technical executive (no acronyms, business impact only), one for a mid-level manager (one or two technical terms explained), and one for a technical buyer (full terminology, mechanism explained) 2. A proof point integration map: for each available proof point listed in the situation inputs, identify the specific paragraph it belongs in and write the sentence that introduces it naturally 3. A technical analogy bank: three analogies that explain the technical concept to a non-technical reader, each using a different domain — household, financial, and physical world comparisons 4. An SME interview guide: eight questions to ask the internal subject matter expert that will generate usable quotes and specific proof points in a 20-minute conversation 5. A blank-page starter: the first three paragraphs of the blog post written at the stated reader technical level — gives the writer a working draft to edit rather than a blank document to fill 6. A competitor content gap: identify two proof points or data references the competing post is missing that this post can use to differentiate 7. A credibility sentence for each proof point type: template sentences for citing internal data, customer quotes, third-party research, and analyst reports — so the writer knows the correct attribution format for each 8. A content velocity checklist: a ten-step pre-writing process that takes 15 minutes and eliminates the false starts that cause a post to stall after the first paragraph **Anchor every explanation to a reader outcome — technical content that does not connect to a business result will not convert prospects regardless of its accuracy.**