Board & Investor Reporting

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 dataset, 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 dataset, 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 dataset, which lives at Data/Investor Asks in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Board agenda dataset, which lives at Data/Board Agenda in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Board actions dataset, which lives at Data/Board Actions in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Update readers dataset, which lives at Data/Update Readers in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Board resolutions dataset, which lives at Data/Board Resolutions in your vault — yours to open, search, and edit like any other file.
• The Board pack dashboard reads from the dataset and shows, at a glance: this month's update — what it still needs · asks, where they stand · the last few packs · cash in the bank · runway · weighted pipeline · arr · cash in the bank, update by update · arr, update by update · resolutions and consents, where they stand · board actions, open first · walk the board agenda · every figure reported, and what it rested on · how this board works.

The wiring, in one breath: Tarn holds Ask capture · Tarn holds Pack compose · Tarn holds Board meeting · Tarn holds Resolutions register · 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 · Board meeting writes to Board agenda · Board meeting keeps Board actions · Resolutions register keeps Board resolutions · Pack compose keeps Update readers · Monthly pack reads Update readers · Board agenda shown by Board pack · Board actions shown by Board pack · Board resolutions shown by Board pack.

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.
• Before a board meeting, ask for the agenda: "the quarterly board is on the 15th, and we need to approve the budget". Board meeting builds it from what you say, the board actions still open and the resolutions you mean to put. In the room, Walk the board agenda on Board pack takes you through it a point at a time, with a tick and a minute for each. Afterwards ask for the minutes: Tarn writes a draft from those minutes and nothing else, for the chair to approve, and the actions go on the board, where you tick them off and the next agenda opens with whatever is still open.
• Tell Tarn when a resolution passes or a consent comes back, and who approved it, and the Resolutions register keeps when and by whom. Paste the wording you or your counsel settled and it is copied on exactly; Tarn never writes a resolution's wording, and it never says one was properly passed.
• Say who reads the update and what each of them looks for ("Lena always wants net retention"). Tarn checks each draft against your Update readers and tells you when someone looks for something no section covers; whether to add one is yours.
• Look at the board for charts, not the draft. A chart cannot go into a document in your vault, so the draft carries a small table of each figure at past updates, and Board pack draws cash and ARR update by update from the same figures.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, datasets 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/ in your vault, one document per update, named by its month, with draft minutes in Board Meetings/. The folders are fixed, so the board can always find the last few packs; copy a draft anywhere you like once it is written.
• Who reads the update and what each of them looks for. Add a reader, retire one, or say that someone now wants to see something else, and the next draft is checked against it.

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. Before it asks you anything, Tarn starts from what 1Presence already knows: what you have told it, and a past update or an investor list in your vault. It offers what it finds for you to confirm, uses a past update's headings as the starting section list, and never copies a figure off an old update. Then it asks only for what is still missing.
3. That is three things at most. Who the update goes to and how it reaches them — each person you name goes on your Update readers list, with what they look for if you say it — and it 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, leaving out the ones it already found. And how often it goes out.
4. 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.
5. 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.
6. Whatever is still missing waits on the Kit page with a way back to Tarn, and Tarn offers it once the next time you talk. Tell it a part does not apply to you, such as naming who reads the update, or that you have finished setting up, and it stops asking.
7. 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