Built for · Content & creative
Publish more. Scramble less.
Bash outlines, drafts, schedules and posts — held until you say go.
Nami keeps your series, your voice, what landed.
Bash · on its own machineWorking
YouTurn Tuesday’s Field Notes into a week of posts
Read №61 — the argument and the three examples
Cut the thread: seven posts, the chart lands fourth
Write the LinkedIn version, longer, first person
Caption three carousel frames, hold the whole weekHeld · waiting on you
A week of posts, drafted“The handoff broke on a Thursday. Nobody noticed until Monday, because every dashboard we had was green.” Post one of seven, in your voice.
Held for your wordWatch it work
WhatsAppOutline the next Field Notes on agent handoffs↵DelegateRead the 14 loudest posts on handoffs this monthPull the three long posts your audience actually saved
Check what the first 61 issues already coveredWrite the outline: angle, six sections, your line
One ask. The whole week of posts.
Pick a delegation — Bash makes the whole thing, held before it publishes.
WhatsAppOutline the next Field Notes on agent handoffs↵DelegateRead the 14 loudest posts on handoffs this monthPull the three long posts your audience actually savedCheck what the first 61 issues already coveredWrite the outline: angle, six sections, your lineOutline · ready in your Docs
Field Notes №62, the angle
Everyone is writing that agents will replace tools. Nobody is writing the migration. You have nine months of it, including the week you lost to a broken handoff. Open there.
Done · 38 seconds
From wherever you areWhatsApp9:12 AM
#studioWed 11:04
GmailFwd
or press ⌃ ctrl anywhere on your Mac
Ask it from the shoot. The week is drafted before you’re back.
From the shoot — WhatsApp, Slack, Gmail, iMessage, Telegram, or a key on your desk.
WhatsApp9:12 AMwhat should tuesday’s field notes be about9:12 AM
Outline’s in your Docs. Field Notes №62 — the migration story nobody else is writing. 14 posts read, 61 issues checked, six sections, two you already have.9:13 AM · 38 seconds
#studioWed 11:04@Bash turn Tuesday’s Field Notes into a week of posts11:04 AM
Drafted a 7-post thread, the LinkedIn version and three captions. Held for you — say go and they go out Tuesday through Friday.11:06 AM
GmailFwdFwd: Lantern 3.0 launch doc — deck by Thursday?2:19 PM
Deck’s in your gallery. 14 slides, your template, the chart redrawn. Slide 4 is the one claim with no number behind it, left blank and flagged.2:22 PM
or press ⌃ ctrl anywhere on your MacSigned into your world
Works inside your stack, as you.
The doc, the channels, the sheet — and a thousand more, a click away.
Google DocsOutline the issue, draft the essay, build the deck.
InstagramCaption the carousel, schedule the frames, read the saves.
XCut the thread, hold it, post it on your word.
LinkedInRewrite it longer, publish it, answer the good comments.
NotionKeep the calendar honest, file the archive, park the ideas.
Google SheetsTrack reach and saves, rank the formats, show the trend.
SlackDrop it in #studio, answer the thread, share the numbers.
GmailDraft the newsletter, hold the send, read the replies.
Google CalendarSet the publish day, stagger the week, keep the slots full.
— and 1,000+ moreSee everything it connects to
Stripe
Teams
Github
Salesforce
ZoomSay it like this
Delegate in plain words.
No setup, no syntax — it already knows your series, your voice, what landed.
Read what’s already been said about agent handoffs, then outline Field Notes №62 with the angle only we can write.
Outline
Turn Tuesday’s Field Notes into a seven-post thread, a LinkedIn version and three carousel captions. Sound like me. Hold them.
Repurpose
Make three cover images for №62 in our template, dark type on cream, and put them in the gallery beside the draft.
Visuals
Schedule the approved week: thread Tuesday 9:00, LinkedIn Wednesday, carousels Thursday and Friday.
Schedule
Pull last month’s posts into a sheet, rank them by saves per thousand, and tell me what to make more of.
Digest
Build the launch deck from the Lantern 3.0 doc: 14 slides, our template, every claim sourced to a cell in the sheet.
Deck
Routines that fire themselvesThree times your median saves inside six hours → the follow-up drafted while people are still reading, held for your word.Instagram → X · held
On a schedule, or on a signal.
Set it once. You hear about it when it’s published — and only then.
Mon8:00
What slipped, what’s unassigned, what’s two days from its slot. In #studio before standup.ScheduledThe calendar, kept honest
Daily9:00
Reach, saves and the three replies worth answering. Three lines in your inbox, nothing else.ScheduledYesterday’s numbers
TriggeredA post breaks out
Instagram → X · heldFri15:00
Five slots filled from the outline bank, captions written, covers made. Held for Monday morning.ScheduledNext week, drafted
Nami · the keeperContent calendar · Thu 12 · unassignedField Notes №58 · the closing lineCalendar · changed 2 hours ago
It remembers the series. So you never repeat yourself.
Every issue, every promise, every number — filed once, raised when it matters.
Nami · entity
Field Notes
SeriesWeekly · Tuesdays 9:00 · 61 issues out
VoiceShort lines, no hashtags, never “excited to share”
BestTeardowns · 3.1x saves · №47 still being cited
Promised“Part two on handoffs” — №58, five weeks ago, unwritten
FilesCover template · chart colors · 12 stills from the shoot
Kept since issue №1Noticed on its own
Thursday’s slot is still empty. Draft it from the №58 leftovers?
Content calendar · Thu 12 · unassignedNot nowHandle it
Noticed on its own
№58 promised a part two. Five weeks now. Outline it?
Field Notes №58 · the closing lineNot nowHandle it
Caught a change
The Lantern launch moved to the 24th. Reschedule the four posts?
Calendar · changed 2 hours agoNot nowHandle it
Asks before it matters
It publishes nothing you haven’t seen.
A post, a thread, a reply in your name — held until you say go.
Held · waiting on you
Post the Field Notes thread as you?
To X · your account, 11.2k followersRe Field Notes №61 · seven posts, Tue 9:00
The handoff broke on a Thursday. Nobody noticed until Monday, because every dashboard we had was green. Here is what we changed, and the one thing we would do differently…
EditHoldApprove & sendX · as you
Only the tools you connectDocs, Instagram, X, the calendar — nothing else. Disconnect any of them, any time.
Every step, in the openThe plan, each tool call, the draft, the cover it made — visible while it works. Peek in, or take the wheel.
Your work stays yoursYour drafts, your archive and your numbers live with you, not with a model. Switch minds; the work comes along.
Taught once, done your way
ContentTopic to finished piece. Research, outline, draft, covers and decks — in your voice, your template.ResearchDraftingVisualsRepurpose
DistributionThe week scheduled, the slots kept full, the numbers read back — what landed, what to make more of.CalendarSchedulingNumbers
Create your ownYour playbook, encoded. Teach it your formats, your voice, what you never post — in plain words.Your rulesYour voice
Install the Content playbook. Or teach it yours.
An Ability is everything the job needs — bundled, installable in a click.
ContentTopic to finished piece. Research, outline, draft, covers and decks — in your voice, your template.ResearchDraftingVisualsRepurposeDistributionThe week scheduled, the slots kept full, the numbers read back — what landed, what to make more of.CalendarSchedulingNumbersCreate your ownYour playbook, encoded. Teach it your formats, your voice, what you never post — in plain words.Your rulesYour voiceContent & creative · FAQ
Questions, answered.
Does it post on its own?
Not unless you tell it to. Anything public, a post, a thread, a reply in your name, is drafted and held for your word. Research, outlines, covers and calendar moves keep going. Approve a week at a time, or let a routine you trust publish on schedule.
Will it sound like me?
It reads what you’ve already published — your line lengths, your openers, the words you never use. Nami keeps the rules you state once ("no hashtags", "never open with a question"). You’ll edit the first few drafts. After that you mostly approve.
Can it actually make the visuals and the deck?
Yes. It builds decks, sheets, covers, carousels and small sites on its own machine, in your template and your colors, and they land in your gallery ready to post or hand off. It works in Canva and Figma the way you do when the file lives there, and it writes the description, chapters and titles when you drop in a YouTube cut.
What does it know about my content on day one?
Whatever’s in the tools you connect: the docs, the archive, the calendar, the last few months of posts and their numbers. From there Nami keeps building — the voice rules, what performed, what you promised and never wrote — so the next brief starts from all of it, not from a blank page.
Where does the work run?
On its own computer in the cloud — a real machine with a browser, files and a terminal — or on yours when the footage and the fonts live there. Its screen streams as it works; you can peek in or take the wheel.
The door
Come back to published.
Tell us what you publish and where. We’ll show you what Bash would make, what Nami would keep, and how your week changes.