Proof of work

The Poindex

A product I built, run and pay for: money, gig work, meals and the household in one place, with an assistant you tell things to in plain words. It is the largest piece of proof on this site — the same three rules I build client systems around, carried all the way out to something other people sign into and trust with what they earn.

Live since September 2026 Built and run by me Cloudflare Workers + D1
The Poindex's Today view: a greeting about rent being due Friday, then rows for rent due Friday tagged Money, an Uber Eats shift tagged Gig, thawing short ribs tagged Meals, and Saturday's dinner with menu, grocery and budget chips
A morning on Today, as The Poindex’s own front page draws it. The working screens sit behind a sign-in, because what’s in them is somebody’s actual money.

Why it’s on a consulting site

Three rules, and here they are holding up something real

A consultant’s principles are easy to print on a page. These are load-bearing in a product that would break in public if they weren’t — which makes it the honest version of what I’d build for you.

Store what happened, derive the judgment.

The Poindex never stores “you can afford rent.” It stores the bills, the payouts and the shifts, and works the answer out on every request. Change what counts as a bill and every past week re-reads itself.

In your business: the same reason a vendor’s score re-computes when you tighten your standards, instead of going stale the day somebody typed it in.

AI drafts, humans approve.

You say “I’m driving tonight and rent’s due Friday” and it files both. When it is sure, it just does it; when there is real doubt, it asks — and it never re-does a thing you undid. Nothing becomes a record because a model felt confident.

In your business: the review bench between an extracted receipt and your books.

Honest numbers or no numbers.

If a payout hasn’t landed, the week doesn’t show an estimate dressed as a balance. A blank you can go check beats a number you’d have planned your month around.

In your business: the dish with one unpriced ingredient that refuses to show a plate cost at all.

And the one this product taught me: nobody should have to take the whole system.

Every section stands on its own. Somebody who only wants to know what a night of driving actually paid never sees meals, the household or anything else — there is no grid of empty boxes advertising the parts they didn’t ask for.

In your business: the reason I won’t quote you modules you don’t need, and why my fixed-price ladder starts at an audit instead of a platform.

What’s in it

Pick one part; add more when it helps

Available now

Money

What’s due, what’s coming in, and where the balance is heading before it gets tight.

Available now

Gig work

Shifts, payouts and what each one really paid once hours, miles and tips are counted.

Coming

Meals

Plan the week, cook, and keep the grocery list honest against the budget.

Coming

Home

Who lives here, what the house needs, and when. The filter change, the vet, the card that’s due.

Coming

Shopping

One list, drawn from everything else rather than typed again.

Coming

Social

Posts and presences, planned alongside the rest of the week.

One thing is often several things at once — a Saturday dinner is a menu, a grocery run, a budget and a guest list. The Poindex keeps them joined, so you see the whole thing instead of four fragments in four apps.

How it’s built

The same boring stack I hand clients

Nothing in here is a technology I wouldn’t put in your business, and nothing in here bills per seat.

Runs onCloudflare Workers + D1 — the same platform this site runs on. Cheap enough to sit idle, simple enough to hand over.
Ownership checkEvery record belongs to one person, and that is verified on every single request rather than trusted from the screen that asked. It is the same check that keeps one client’s job off another client’s page.
Bank dataRead-only, through Plaid, for accounts a person connects themselves. Access tokens are sealed in the database, never written to a log, and disconnecting actually removes the connection upstream instead of just hiding it. Linking is still switched on for my own household only, until a security review says otherwise — that switch exists so the decision has to be made on purpose.
BackupsEvery table exported nightly to object storage, plus an endpoint that reads the newest export back and compares it against live counts — because a backup nobody has ever restored is a rumour.
Sign-inOne Google sign-in across every part, the same accounts service this site uses.
Per-seat feesNone, anywhere in it.

Want the version of this shaped like your operation?

The Poindex is mine and stays mine — it isn’t a template I resell. What travels is the method: store what happened, let AI draft and people approve, refuse to show a number you can’t prove, and build it in parts you can take one at a time. First conversation is free and worth your time either way.