Kit
The monthly update that writes its own first draft, and the asks tracked until answered.
The monthly update that writes its own first draft. Tell Tarn who the update goes to and what they expect to see in it, and on the third of each month it reads the kits you already run — the cash and the runway, the weighted pipeline, the ARR — writes a draft into your vault with a section for each thing your update needs, and ticks them off the list as it goes. Every figure it reports names what it rests on, so a number on a board pack can always be traced back to the record that produced it. Where a kit is not installed, the figure says there is nothing to read yet rather than showing you a zero. Beside it, the asks you have out with investors, aged, so nothing you have asked for quietly expires. It drafts; you edit; you send.
1 agent, 1 routine, 1 dashboard, 3 records, 2 skills. Installing ends with Meet Tarn — a short conversation sets it up, and everything can be retimed or paused after.
| Cash & runway | Finished | drawn from your kits |
| Pipeline | Drafted | drawn from your kits |
| Product & shipping | Needed | yours to write |
| Team & hiring | Needed | yours to write |
months, at last month's net burn of 23,000
Two intros to enterprise security buyers
Northwind Ventures · 24 days outA reference call with a portfolio CTO
Fabrikam Partners · call bookedNames for the open staff engineer role
Northwind Ventures · 9 days outThe crew
Tarn
Keeps the update you owe your board — drafted from what your records actually hold, never sent without you.
Faithful and unhurried; reports what the records hold, names the basis of every figure, and has no view on whether the news is good.
What else it installs
One row per figure per update — what it was, where it came from, and the arithmetic behind it.
What your update has to contain — and which of it is drafted.
What you have asked your investors for, and whether it came back.
Say what you asked an investor for — it lands on the list until it comes back.
Shape the update, or write the next draft now — from whatever your kits actually hold.
What this month's update still needs, the four figures it rests on, and the asks you have out.
The 3rd of each month — reads whichever Kits you run, writes the next update, and ticks the sections it drafted.
Runs the 3rd of each month · 8am
The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.
Data/KPI Snapshots in your vault — yours to open, search, and edit like any other file.Data/Pack Sections in your vault — yours to open, search, and edit like any other file.Data/Investor Asks in your vault — yours to open, search, and edit like any other file.The wiring, in one breath: Ask capture writes to Investor asks · Pack compose writes to Pack sections · Monthly pack writes to Pack sections · Monthly pack records KPI snapshots · Pack sections shown by Board pack · KPI snapshots shown by Board pack · Investor asks shown by Board pack · Board pack kept fresh by Monthly pack · Monthly pack run by Tarn · Tarn holds Ask capture · Tarn holds Pack compose.
A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.
Nothing here is fixed. The pieces are ordinary agents, routines, records and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.
Say any of these in chat, or edit them on the kit’s page in the app.
Installing starts a short setup conversation — not a form. Answer roughly, correct later.
Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.
Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.
Install it, run it once against something that already happened, and see whether what comes back sounds like you.
Try it freeEverything it installs can be retimed, paused, or removed.