KolBo Calculator: maaser tracking where the math already happens

Maaser is the mitzvah with a bookkeeping problem. The commitment is mainstream and beloved — a tenth of the parnassah to tzedakah, figured with the seriousness this community brings to any cheshbon — and the record-keeping is where the seriousness meets reality: the paycheck arrives, the mental note is made, the notebook is elsewhere, the spreadsheet is on the other machine, and by Elul the reconstruction project begins. Every family that keeps maaser knows the shape of the gap, and it was never a gap in devotion. It is a workflow gap: the moment of calculation — what came in, what a tenth is, what was already given — happens on the calculator, and the tracking happens somewhere else entirely. Systems that separate the event from its record lose the record; every bookkeeper alive knows it.

The kolbo.life homepage's tile for KolBo Calculator closes the gap by refusing the separation: "With a built-in maaser tracker. A calculator that knows who's using it — maaser tracking built directly in. Every calculation of tzedakah, tracked and totaled where the math already happens."

"Where the math already happens"

The tile's closing phrase is the whole design insight. The calculator is where the parnassah arithmetic already lives — the paycheck's tenth, the invoice's share, the yontif appeal weighed against the year's total — so the tracker belongs in the instrument, not in a separate app the moment never reaches. "Tracked and totaled where the math already happens" means the record is a byproduct of the calculation instead of a second task after it — the same grammar as the alarm that wakes by the zman and the camera whose protection rides the capture pipeline: the frum requirement built into the tool's own motion, not appended to it.

And "a calculator that knows who's using it" names the deeper design stance, gently: the general market's calculator is the most anonymous app on any device — a component so generic no vendor ever considered that its user might have a standing relationship with one particular fraction. This one was built for the user it actually has: a community for whom the tenth is not a tip but a ledger — which makes the humble calculator, of all the suite's twenty-two apps, perhaps the purest example of the homepage's thesis that this market deserves technology "built for it — not handed down to it." (The platform story in full.)

“The record was always lost in the hand-off between the calculation and the notebook. So the design removes the hand-off.”

kolbo.life

The year the cheshbon runs itself

Walk the tracker through a fiscal frum year and its value compounds at every station. The weekly paycheck's tenth, figured at the moment it is figured — recorded in the same motion. The Purim season, when the giving accelerates past any notebook's ability to keep up — each matanah counted where it was calculated. The yontif appeals, weighed against a running total that actually runs — the dinner pledge made knowing the year's position rather than guessing it. The bonus month and the lean month, each adjusting the obligation in real time. And Elul — the traditional season of the great reconstruction — arriving to find nothing to reconstruct: the cheshbon current, the totals totaled, the year's tzedakah a record instead of an archaeology project.

The suite's spine carries the rest: the totals living on the family's own cloud rather than a stray spreadsheet, following the household's devices like its notes — one running cheshbon, never behind, because it was never separate from the arithmetic that feeds it.

The boundaries, per this library's standard: percentage options, reporting features, and halachic configurations aren't stated on the homepage — the built-in tracker and its placement are the stated claims, quoted exactly. For the many real questions maaser raises — what counts as income, which obligations qualify — the address was never an app at all: ask your rov, as the community always has. The Calculator's job is humbler and, for once, fully solved: when you and your rov have your answers, the counting finally happens where the counting was always done.

Frequently asked questions