Kit

Board & Investor Reporting

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.

Try it free

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.

Board packExample data
This month's update — what it still needs4 of 7 drafted
Cash & runwayFinisheddrawn from your kits
PipelineDrafteddrawn from your kits
Product & shippingNeededyours to write
Team & hiringNeededyours to write
Runwayread from Startup Finance & Runway
7.7

months, at last month's net burn of 23,000

Asks and follow-ups3 open

Two intros to enterprise security buyers

Northwind Ventures · 24 days out

A reference call with a portfolio CTO

Fabrikam Partners · call booked

Names for the open staff engineer role

Northwind Ventures · 9 days out

The 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

KPI snapshotsrecord

One row per figure per update — what it was, where it came from, and the arithmetic behind it.

Pack sectionsrecord

What your update has to contain — and which of it is drafted.

Investor asksrecord

What you have asked your investors for, and whether it came back.

Ask captureskill

Say what you asked an investor for — it lands on the list until it comes back.

Pack composeskill

Shape the update, or write the next draft now — from whatever your kits actually hold.

Board packdashboard

What this month's update still needs, the four figures it rests on, and the asks you have out.

Monthly packroutine

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

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

  • Monthly pack runs the 3rd of each month · 8am and keeps the Board pack dashboard fresh. The 3rd of each month — reads whichever Kits you run, writes the next update, and ticks the sections it drafted.
  • What is captured lands in the KPI snapshots record, which lives at Data/KPI Snapshots in your vault — yours to open, search, and edit like any other file.
  • What is captured lands in the Pack sections record, which lives at Data/Pack Sections in your vault — yours to open, search, and edit like any other file.
  • What is captured lands in the Investor asks record, which lives at Data/Investor Asks in your vault — yours to open, search, and edit like any other file.
  • The Board pack dashboard reads from the record and shows, at a glance: this month's update — what it still needs · cash in the bank · runway · weighted pipeline · arr · asks, where they stand · the last few packs · asks and follow-ups · every figure reported, and what it rested on · how this board works.

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.

Getting the most from it

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.

  • Spend the first sitting on the section list, not on the figures. What Tarn can draw is decided entirely by what your Pack sections record says the update has to contain, and which sections you mark as drawn from your Kits versus yours to write. Ten minutes there is the whole set-up, and it is the only part nobody else can do for you.
  • Look at the board on the third, after the Monthly pack has run. It answers one question — what is still yours to write — and it answers it as a gap rather than a tick list, because the sections you have to write yourself never tick until you write them. Everything marked drawn from your Kits will already be drafted.
  • Read the four figures with their sub-lines, never without. Each one says what it rests on: which month the burn was measured over, how many open deals were weighted and at whose probabilities, how many accounts the book value covers. That sentence is what makes a number safe to repeat to somebody who was not in the room, and it is the sentence people drop first.
  • Treat a dash as information. Where a figure reads as a dash, the Kit that owns it is not installed on this account — Startup Finance & Runway for cash and runway, Sales Pipeline & Forecast for the weighted pipeline, Customer Success & Renewals for the book value. Tarn will never put a zero there, and installing that Kit is what fills it.
  • Say your asks out loud as you make them: "I asked Northwind for two intros", "Fabrikam are going to look at the pricing page". Ask capture puts each on the list with the date, the asks section of the next update writes itself from the open ones, and nothing you asked for quietly expires.
  • Edit the draft, and let Tarn see the shape you settled on. The pack writes into Board Updates/ in your vault and stops there — it never sends anything. If you keep rewriting the same section, say so: the section list is yours to change, and a section you no longer report is one line to retire.

Make it yours

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.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

  • What the update contains. Add a section, rename one, or retire one you no longer report — say it and the list changes, and the next pack follows it.
  • Which sections Tarn drafts and which are yours. A section marked drawn from your Kits gets written from your records; one marked yours to write gets its heading and a line saying what it needs, and nothing invented in between.
  • When the pack is drafted, or pausing the routine and asking for a draft whenever you need one — "we have a board meeting Thursday" composes it on the spot from the same records.
  • How the update reads — its length, how it opens, what you never put in writing. Rewrite a draft and say what you changed, and Tarn keeps it.
  • When an ask stops being useful. Give a date and it ages against that; leave it blank and it simply stays on the list until it comes back.
  • Where the drafts live: Board Updates/ by default, anywhere in your vault you would rather keep them.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

  1. Adding the Kit opens a conversation rather than a sweep: "Meet Tarn". There is no connector to grant and nothing runs unattended until you have said what the update is, because this Kit reads your own records and your own words and nothing else.
  2. Tarn asks three things. Who the update goes to and how it reaches them — and says once, plainly, that it drafts and you send. What the update has to contain, offered as a short pick-list over the usual territory (cash and runway, pipeline, revenue and retention, product, team, risks, what we need from you) with room for your own sections. And how often it goes out.
  3. Each section you name is written straight to the Pack sections record as you say it, marked either drawn from your Kits — where the figures come off a record Tarn can read — or yours to write. That list is what the Board pack dashboard draws, so the board stops being empty during the conversation rather than after it.
  4. Near the end Tarn checks which sibling Kits this account actually holds and says which figures it will be able to read. Where one is missing it says so then, rather than letting you find out from a blank on the board a month later.
  5. From then on the Monthly pack runs on the third of each month, two days after the books close, drafts the next update into Board Updates/ in your vault section by section, ticks what it drafted, redraws the board and leaves one card. Until the section list has something in it, the routine stands down and leaves an invitation instead of running empty.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits

Put the Board & Investor Reporting kit to work.

Install it, run it once against something that already happened, and see whether what comes back sounds like you.

Try it free

Everything it installs can be retimed, paused, or removed.