A demo, running on three years of invented history

The dozen numbers a museum reports on — and the documents they turn into.

Every small museum produces the same four documents forever, and assembles each one by hand, on a deadline, from spreadsheets in four places. Tally keeps the numbers and writes the documents. Drop a CSV, or type it in. No integration, no IT ticket, no procurement.

Institution 36 months of history · through July 2026

Drop a CSV

Whatever you already run exports one — ticketing, POS, a spreadsheet. Map the columns once; Tally remembers the shape.

Drop a file here or click to choose · .csv
No file handy? Grab this and drag it back in.

Or just type it in

For the museum whose attendance number lives on a clipboard by the door. This month, five fields, ninety seconds.

What's feeding it

Connectors are optional accelerants, never prerequisites. Tally works standing completely alone.

  • Manual entryAlways on
  • CSV importAlways on
  • Field Trip DeskConnect later
  • DocentConnect later
  • Stripe · MailchimpConnect later

Deliberately not on this list: Altru, Tessitura, PastPerfect. Those integrations cost more than they return at this size — their CSV export is the integration.

Attendance, three years

Monthly total, with school groups underneath it. Summer peaks, the spring-break spike, the school-year shoulders.

Where the school groups come from

Students by district, this school year.

Membership

New against lapsed, twelve months. The gap is the number a development director watches.

Five fixed views, and that is on purpose. There is no query builder and no drill-through — a dashboard nobody opens was never the problem worth solving. These exist to feed the documents in the next step.

Every figure carries the record it came from. Nothing here is estimated.