Sell the finished job
Define what the customer receives, when, for how much, and what “done” means.
About Rollbook
Built for the work between the system and the deadline.
Small colleges do not need another abstract data platform. They need the report, feed, or responsible correction that lets a real office move forward.
The origin
A product shaped from direct responsibility.
Rollbook was conceived by a Director of IT at a small college who manages a student information system and sees the same gap repeatedly: the data exists, but the institutional output still depends on manual exports, local knowledge, and last year’s workbook.
That makes the problem bigger than convenience. When a reporting method lives in one person’s memory, the institution cannot easily review it, repeat it, or explain it. Rollbook keeps the number together with the definition and source so the work becomes institutional.
The first supported student information system is Populi, reflecting direct operating experience and an intentionally focused launch. Additional connections will follow customer demand. The ambition is not to replace the system of record. It is to complete the work around it responsibly.
Operating principles
Specific beats sweeping.
Keep the method
A number without its definition, rule, snapshot, and source is unfinished reporting work.
Make control visible
Read-only by default; preview, approval, and reconciliation for any supported write.
Have a job Rollbook should solve?
Describe the deliverable and the deadline. We will tell you whether it fits.