Open Beta: Two Weeks, One Asset That Carries Everything

chronicle beginner 5 min read

What this means for you

The Chronicle launch is a two-week arc anchored by one asset: a screen recording of the timeline scrub. Without that recording, nothing else ships. The campaign theme is “Documents That Remember.” The single conversion action is a waitlist signup at chronicle.dev/waitlist. The category position is memory, not collaboration. The bet is that people see the scrub once and the interaction sells itself.

The pitch

Week one is launch week. The blog post publishes Tuesday. The X thread, the Threads post, and the Bluesky post seed the same morning. LinkedIn carries the emotional and social layers later in the week. Reddit comes last, with technical depth, after the GitHub repo is public. Week two is amplification through cross-posts, founder-voice cuts, and the first beta-user testimonials.

Who it’s for

The advisor or contributor asking what the plan looks like, and the operator deciding what to ship next when an asset has to be cut.

Proof points

Theme is fixed: “Documents That Remember,” documented in docs/marketing/chronicle-launch-strategy.md
Blog post target length is 1,800 to 2,200 words with two mermaid diagrams as embedded shareable assets
Single conversion goal: waitlist signups at chronicle.dev/waitlist, every channel UTM-tagged for cohort analysis
Critical-path asset, named in the campaign-intelligence doc: the timeline scrub GIF. Quote: “Ship nothing until this asset exists. It is the campaign.”
Channel sequence: X and Threads Tuesday 14:00 GMT, Bluesky same day, LinkedIn later in week one, Reddit r/selfhosted in week two after the repo goes public
Three SEO terms to own at launch: collaborative document editor, real-time document collaboration, document timeline

timeline
  title Chronicle open-beta two-week arc
  Week 1 day 1 : Blog post publishes : X thread + Threads + Bluesky seed
  Week 1 day 3 : LinkedIn emotional post : technical writer angle
  Week 1 day 5 : LinkedIn social post : compliance angle
  Week 2 day 1 : GitHub repo public : Reddit r/selfhosted post
  Week 2 day 3 : Beta testimonial drop : cross-post on X and LinkedIn
  Week 2 day 5 : Founder-voice cut : "what we got wrong in week one"

neighbors on the map

Four Readers, Four Reasons to Care deciding which segment a campaign asset is speaking to
Memory, Not Collaboration: Why Chronicle Is in a Different Category answering 'how is this different from Google Docs?'