Skip to content

task_plan.md

Latest commit

 

History

History
112 lines (100 loc) · 5.32 KB

task_plan.md

File metadata and controls

112 lines (100 loc) · 5.32 KB

Tinybird Guest Post For Cossistant

Article Objective

Draft an approval-ready guest post for the Tinybird blog that tells a product-first story about how Cossistant uses Tinybird for real-time customer support analytics and live visitor presence, with the live globe as the clearest hook.

Target ICP Angle

  • Developer-first SaaS founders and product engineers who want user-facing analytics without building analytics infrastructure from scratch
  • Tinybird readers who care about real-time product surfaces more than back-office BI
  • Teams who want support to feel native to their product, not bolted on

Search / Editorial Intent

  • Editorial customer story, not a keyword-stuffed SEO post
  • Intent sits between MOFU and BOFU: relatable build story first, curiosity about Cossistant second
  • The post should make Tinybird readers think, "this feels like the kind of support product I would actually want to use or build with"

Primary Keyword And Secondary Keywords

  • Primary keyword: real-time customer support analytics
  • Secondary keywords:
    • live visitor presence
    • customer support analytics
    • support backend API
    • developer-first support
    • open source support widget

Differentiator Angle

  • Cossistant did not just add charts to a support product
  • The distinct story is:
    • live support analytics inside the inbox
    • live visitor presence rendered as a globe plus visitor list
    • API-first flexibility for fully custom support experiences
    • open-source, code-first fit between Cossistant and Tinybird

Article Brief

  • Working title options:
    • How Cossistant built real-time customer support analytics and a live visitor globe with Tinybird
    • How Cossistant made support analytics feel live with Tinybird
    • How Cossistant used Tinybird to power live support analytics and visitor presence
  • Final title:
    • How Cossistant built real-time customer support analytics and a live visitor globe with Tinybird
  • Audience and pain point:
    • Builders who want support data to be visible in-product, in real time, without signing up for a side quest in analytics infrastructure
  • Outline:
    • About Cossistant
    • Problem
    • Why Tinybird
    • Results
    • Analytics inside the inbox
    • Live visitor globe
    • API-first custom support story
    • Closing
  • Link targets if Tinybird allows contextual links:
    • https://cossistant.com
    • https://cossistant.com/docs/support-component
    • https://github.com/cossistantcom/cossistant
  • CTA:
    • Invite readers to look at how Cossistant approaches developer-first support, not a hard sell

Approval Checkpoint

  • No invented technical metrics, costs, or latency numbers
  • Playus can be named publicly
  • 600K DAU is approved user-provided proof
  • Anthony quote must stay marked as draft until approved
  • Screenshot shortlist must be included in the deliverable

Current Phase

Phase 5 complete

Phases

  • Phase 1: Gather and lock source truth
    • Review Tinybird customer story structure
    • Verify Cossistant Tinybird implementation details in repo docs and code
    • Capture approved user-provided proof points
    • Status: complete
  • Phase 2: Shape the story and editorial brief
    • Lock headline, angle, audience, and guardrails
    • Distinguish this story from Tinybird's Plain story
    • Status: complete
  • Phase 3: Draft the guest post
    • Write the main article in plain Markdown at repo root
    • Add editorial notes, screenshot shortlist, CTA, and approval items
    • Status: complete
  • Phase 4: Fact-check and humanize
    • Verify every Cossistant claim against the repo or the user's approved facts
    • Run a final human-style pass to remove slop, filler, and hype
    • Status: complete
  • Phase 5: Handoff
    • Update planning files
    • Summarize what is ready and what still needs Anthony approval
    • Status: complete

Decisions Made

Decision Rationale
Lead with the product, not the founder origin story Tinybird customer stories work best when the visible product outcome is clear fast
Use the live globe as the emotional hook It is the most memorable and visually specific part of the Tinybird-powered experience
Keep the story low-jargon The user explicitly asked for plain language, and the audience is technical enough without needing jargon theater
Use Playus as the concrete example The user approved the name and the 600K DAU reference
Keep results qualitative except for approved proof Avoids invented numbers while preserving credibility
Mention LLMs as useful during integration The user explicitly wants that in the story, and it matches the dev-first angle

Risks And Guardrails

  • Do not imply Tinybird powers all of Cossistant. Keep the scope limited to analytics and live presence.
  • Do not claim externally verified Playus metrics beyond what the user approved.
  • Do not borrow Plain's angle about "sprinkling analytics everywhere" as the center of the post.
  • Do not make ClickHouse complexity the headline. The story is about product surfaces and developer fit.
  • Do not sound like a press release.

Files To Deliver

  • /Users/anthonyriera/code/cossistant-monorepo/task_plan.md
  • /Users/anthonyriera/code/cossistant-monorepo/findings.md
  • /Users/anthonyriera/code/cossistant-monorepo/progress.md
  • /Users/anthonyriera/code/cossistant-monorepo/tinybird-guest-post-cossistant.md