Structured Blog Post Planning Template for Consumer-Focused EEG Sleep Technology Startup

This template provides a formal, repeatable framework for planning and producing blog content aligned with strategic business objectives. It is designed for early-stage startups in the consumer health technology space — specifically EEG-based sleep monitoring — where clarity, credibility, and conversion are paramount.

Each blog post must be grounded in strategy and grounded in available assets. Complete this section in full prior to drafting. If any field cannot be meaningfully populated — especially under “Asset Requirements” — pause and gather resources first.

Adherence to this structure ensures logical flow, readability, and alignment with conversion goals.

→ Must clearly reflect the Core Message. → Should pass the “value test”: reader immediately understands what they will gain. → Avoid clickbait; maintain credibility appropriate to health technology. → Example: “The Limitations of Movement-Based Sleep Tracking — And Why EEG Changes Everything”

→ Open with a relatable observation, data point, or question. → Confirm relevance to the Target Group. → State the article’s purpose and value proposition succinctly. → Example: “If you rely on your wearable to understand your sleep but still wake up fatigued, the issue may not be your habits — it’s your hardware. Movement and heart rate alone cannot reveal what your brain is doing at night. This post explains why — and what to do about it.”

→ Organize content under descriptive H2 and H3 subheadings. → Paragraphs: 1–3 sentences maximum. Prioritize scannability. → Use bullet points for comparisons, benefits, or key takeaways. Bold critical terms or conclusions. → Integrate visuals at strategic intervals to reinforce claims or simplify complexity. → Example H2: “The Science of Sleep Staging: Why Brainwaves Matter More Than Movement” → Example H3: “How Consumer Wearables Estimate Sleep — And Where They Fall Short”

→ Summarize the Core Message in one to two sentences. → Transition smoothly to a single, unambiguous Call-to-Action. → Provide clear instruction and minimal friction (e.g., prominent button, short form). → Example: “Accurate sleep insight begins with brain data — not guesswork. Join our early access list to be among the first to experience clinically validated sleep staging at home. → [Button: Request Early Access]”

Maintain consistent, professional tone suitable for a science-driven consumer health brand.

• Authoritative yet approachable. Convey expertise without condescension.
• Empathetic and respectful. Acknowledge reader challenges without dramatization.
• Calmly confident. Avoid hyperbolic claims (“revolutionary,” “miracle”). Let data and logic persuade.
• Humanized professionalism. Use “we” and “our” to reflect team presence, but avoid slang or forced casualness.

• Person-first language. Never use terms like “insomniacs,” “sufferers,” or “patients” unless clinically appropriate and explicitly quoted. Prefer: “individuals managing sleep difficulties,” “users seeking deeper sleep insights.”
• Inclusive gendering. Default to “they/them” or plural constructions (“users,” “readers”). Avoid “he/she.”
• Technical terms. Define on first use in plain language. Example: “EEG (electroencephalography — the measurement of electrical activity in the brain).”
• Competitor references. Always respectful. Position alternatives as useful within their scope, not deficient.

→ Inappropriate: “Smartwatches provide inaccurate sleep data.”

  → Appropriate: “Smartwatches are effective tools for monitoring daily activity and heart rate variability. For granular analysis of sleep architecture, EEG-based systems offer a fundamentally different — and more precise — dataset.”

• No general education. Do not replicate publicly available information (e.g., Wikipedia summaries of sleep cycles). Content must serve the Core Message or drive the Intended Action.
• Feature → Benefit translation. Never list specifications without explaining user value.

→ Weak: “Our device uses six dry-contact electrodes.”

  → Strong: “Six dry-contact electrodes comfortably conform to your forehead, capturing high-fidelity brainwave data without gels or setup — delivering lab-grade sleep staging in your own bed.”  
* **Visuals as functional assets.** Every image, chart, or graphic must clarify, compare, or build trust. Authenticity (real product, real team) > polish.  
* **Mobile-optimized formatting.** Assume >60% of readers are on mobile. Short paragraphs. Clear hierarchy. Tap-friendly CTAs.

NEW SECTION — Critical for early-stage teams working with prototypes and scientific data.

Before publishing, verify that all required assets from Part 1 have been produced or sourced. This is not optional — credibility in consumer health depends on demonstrable evidence.

• ✅ Data & Plots
  1. Confirm dataset source (e.g., “Subject #12, Night 3, 2024-06-10”)
  2. Ensure plots are labeled clearly (axes, units, conditions)
  3. Annotate key insights directly on visuals (e.g., “REM onset detected at 03:14 via theta burst”)
  4. Include brief methodological note if needed: “Data collected using prototype v2.3 with 4-channel dry EEG, sampled at 250Hz.”

• ✅ Photography & Visuals
  1. Use real prototypes — not renders or mockups.
  2. Show device in context (e.g., on pillow, worn during sleep, with real user — with consent).
  3. Include scale reference if helpful (e.g., device next to common object).
  4. Ensure lighting and composition convey comfort, simplicity, and trust.

• ✅ Permissions & Ethics
  1. All human-subject data/images require documented consent.
  2. Anonymize data if not from team members (remove timestamps, IDs, etc.).
  3. If using third-party data or code, cite source and verify licensing.

• ✅ Reproducibility Note (Optional but Recommended)
  1. For technical audiences: “Raw data and plotting scripts available on request for research collaborators.”
  2. Shows scientific integrity without over-educating consumers.

• ❌ Drafting content without completing Part 1 — especially “Asset Requirements.”
• ❌ Publishing without verifying asset availability or quality.
• ❌ Using placeholder visuals or “we’ll add this later.”
• ❌ Including multiple Calls-to-Action. One goal per post.
• ❌ Long, unbroken text blocks. Online readers scan — design for it.
• ❌ Generic or stock photography. Authentic visuals build credibility.
• ❌ Over-explaining basic concepts. Assume baseline knowledge; focus on differentiation.
• ❌ Ignoring accessibility. All images require descriptive alt text. Headings must be semantic.
• ❌ Publishing without mobile preview. Test layout on small screens.

→ Duplicate this template for each planned blog post within your DokuWiki environment. → Mandate completion of Part 1 — including Asset Requirements — prior to content drafting. → Use Part 2 as the structural outline during writing. → Apply Part 3 as an editorial checklist during revision. → Execute Part 4 rigorously before publishing — no exceptions. → Consult Part 5 prior to final approval.

This is not a content repository. It is a conversion-oriented planning instrument grounded in real prototypes and data. Every published post must advance visibility, authenticity, product showcase, or competitive differentiation — as defined in your original objectives. ```

I want you to refine this response, to provide me a properly usable template in DOKUWIKI MARKDOWN STYLE. Make it generally enough for sleep EEG devices (e.g. a smart alarm, measuring sleep stages, ..). Do not be too specific, but be aware we are within a consumer health sector, and obvious competitors are either other sleep bands or sensor devices like oura, apple watch, etc. We are a small startup first starting with the blog. This serves to introduce us, our topic, our expertice, and our product. I don't care about “big company” things like “updates” about fundings etc. This is not a news site, this is a blog with actual content.

What I really liked about the initial proposal: - example for comparing with a competitor. That is good and should be reintroduced (ie not putting it down, but stating it has a different purpose). - good guidelines for proper language in context, specifically for people suffering from diseases. I.e. not saying “insomniacs” etc.. also gendering etc.

As an additional note, our mission is NOT to educate people, thats what wikipedia etc is for. Our blogs need a specific purpose, as stated in my original question.

Stay formal in tone, this is for an internal wiki guide.