A note on why we built Cruma
Approvals and receipts

Nothing falls through. Nothing slips past you.

The crew prepares real work: messages, estimates, reminders. Anything consequential stops at your desk, and the record keeps every yes with the facts behind it.

Draft mode is the default. Replay is forever.

How approvals work

Nothing sends, commits, or moves money on its own, and weeks later you can replay any run: what was read, what went out, who said yes.

Ops is finishing this. Waiting on your approval

Estimate, revised for 310 guests

Numbers stay checked against QuickBooks until someone approves.
Guest count220310
Catering$18,700$27,280
AV, priced as an upgrade$5,400
Total$73,500$97,300
One thing to know: the 4:15 AV rig overlaps catering prep by 25 minutes. Rentals can start at 1:30 to give the buffer back.

Where it came from. Your QuickBooks estimate, read at 9:41, and the client's July 11 email.

Who signs off. Maya, unless the margin floor breaks. Then it comes to you.

Freshness checked 2 minutes ago. If a source changes before approval, this pauses itself.
Waiting on Maya. Nothing sends until she says so.
One approval, mid-flight The sources are attached. The button is yours.
On the record · Cascadia
  1. MayaWed 9:41am
    Approved the revised estimate for 310 guests.
    Read: the QuickBooks estimate, the July 11 client email.
  2. YouTue 4:03pm
    Gave the ok on this week's deposit nudges.
    Read: four invoices, each thread's history.
  3. CrumaTue 8:15am
    Held a payment reminder: the invoice settled the day before.
    Read: QuickBooks, re-checked at send time.
Names, times, and sources kept. Nothing reconstructed after the fact.
The receipt ledger Ask later. Replay it exactly.
A bright lineExternal messages, vendor commitments, invoices, and money all wait for a person.
Your yes cannot go staleAn approval binds to the facts you saw. If the invoice got paid between your review and the send, the send stops itself and asks again.
Autonomy is earnedApprove the same kind of work a few times and you can loosen the leash for exactly that, reversible any time.

Approve Monday, act Wednesday, still safe. The action re-reads its sources at the moment it runs, not the moment you clicked.

Loosen it, tighten it, revoke it. Autonomy settings are per task category and yours alone. The leash never disappears; you just decide its length.
Between two of your businesses, the wall holds. If work crossed over, the record shows exactly what was shared and what was withheld.
The trust guide covers the fine print

Trust it because you can check it.

Autonomy that shows its work beats autonomy that asks for faith. Bring the crew in and read the receipts yourself.

Request an invite Invites go out in small waves.

The work moves
while you sleep.

Point Cruma at the business. It works across the tools you already use and speaks up before you ask. Your mornings can start somewhere else.

  • Works across the tools you already use
  • Advises, unasked, with its sources
  • Nothing consequential without you
Request your invite

Two fields. You'll hear from a real person within two days.

We onboard in small waves, with real help getting set up. Read why we built this.

Already have an invite? Open Cruma