Content that plans, produces and publishes across every format you use.

Turns what your company already produces into content: product releases and your codebase, sales and support calls, research, founder notes and results. Plans the calendar, drafts long and short form in each author's voice, from docs and tutorials to newsletters, case studies and video scripts, and publishes through the tools your team already uses once someone approves.

Build Content for your company How a build works

02 · Content · this morningExample

ReadsMon 07:00
This week's inputs: three merged releases in your repo, four sales calls, the roadmap and last month's analytics.
Reasons07:01
The plan: release notes and a developer tutorial from the new API, a customer story, the newsletter and a demo script.
Remembers07:02
Your style guide, your glossary and what performed: tutorials outread opinion pieces two to one.
Connects07:03
Social gets a cut for each channel. Acquisition gets the customer story for its open deals.
Drafts07:05
Five pieces in progress across docs, blog, newsletter and video, each in the right author's voice.
Checks07:06
Code samples run, every claim sourced, all five staged in your CMS for review.

Landed for you · Plan · this week

Five pieces from one release

API v2 release notes for the docs. A tutorial: your first webhook in ten minutes. A customer story for sales. Newsletter number 14. A 60-second demo script. Each one waits for its approver.

Runs in Notion, Google Docs or your CMS · GitHub or Linear · Gong or Fireflies

What it reads

Your product: releases, changelogs, pull requests and docs, so developer and product content comes from what actually shipped.
Your customers: call transcripts, support threads and replies, including the questions people keep asking.
Your company: the roadmap, research, founder notes, talks and results worth telling.
Your own back catalogue and analytics, to learn each author's voice and what your audience actually reads.

How it decides

What to make this week, planned as a calendar across formats and channels rather than one post at a time.
Which format fits each idea: docs, a tutorial, a long piece, a newsletter, a case study, a video script or short cuts for social.
Whose voice it goes out in, and what stays out: anything we cannot source, and anything you have said you do not want to talk about.

The rules it follows

Prepared daily. Approved by a person. Owned by you.

What it will never do

Publish without a named person's yes. Approved pieces go out through your CMS and tools; nothing else does.
Pad a draft with generic tips to hit a word count.
Ship a code sample or a number that has not been checked against its source.

Where it runs

Notion, Google Docs or your CMS
GitHub or Linear
Gong or Fireflies

Nothing to migrate. The system reads and writes in the tools your team already opens every morning, and everything it builds is yours.

In practice

The same content system runs the studio's own writing across six platforms. What it will not do is decide your opinions for you: the positions come from you, and the system keeps them consistent everywhere they appear.

How the content system works, step by step →

What we need from you

Access to the places your work already lives: the repo or changelog, call recordings, the roadmap and your drafts folder.
A handful of pieces you are proud of, and a few you are not.
A list of topics you will not touch.
One named approver per author, and twenty minutes a week each.

Questions

Questions about Content.

Will it sound like AI wrote it?

It is built not to. Each author's voice is learned from their own writing and calls, and every draft is checked against it before anyone sees it. You still edit; the point is that you edit a good draft rather than start from a blank page.

Where do the ideas come from?

From what your company already produces: what shipped in the codebase, what customers asked on calls, what the roadmap says is next and what your results show. The system plans the week around the best of it.

Can it write developer content?

Yes. It reads releases, pull requests and docs, drafts release notes, tutorials and technical posts, and checks that the code samples run before a person approves them.

Does it publish for me?

Once a named person approves a piece, it can publish or schedule it through your CMS and newsletter tool. Nothing goes out without that yes.

Works with