Groundcrew catches refunds over limit, payment mismatches, and oversells the moment they happen — clears the routine ones by rule, and holds the rest for a named human with the whole story attached.
Inbound
Holding · 3
rule: refund > $200 → CS lead · held 3h 40m
Cleared today · 23
Reads the stack you already run
The back office runs on whoever's awake — until the auditor, the accountant, or the founder's calendar says it can't.
A refund request finds whoever's online. It gets handled — probably. Recorded — nowhere.
“Who okayed the $600 refund in March?” Someone did, in a thread, on a phone. Good luck.
Started with discipline in January. Three tabs, two owners, and zero updates since the busy week it was built for.
Every judgment call routes to one person — so the queue moves at the speed of their inbox, and so does the team.
That's the whole product — which is exactly why it works.
Every exception becomes a strip with its evidence attached — inbound, holding, cleared. One glance says whether the back office is fine.
Match the payment, restock the return, dedupe the order — the routine 83% never interrupts anyone.
Writes only through your platforms' own APIs, only after the rule or approver says yes.
Over a limit, a strip holds for its named approver — two of them past your thresholds. One click from the board or Slack, no self-approval, ever.
Who asked, who decided, what executed — one line each, exportable the day someone asks.
Three verbs, applied to every exception, every time — that's the whole discipline.
Every exception from your stack becomes a strip the moment it happens — with the order, the amount, the customer, and the evidence already attached.
Rules clear the routine instantly. Anything over a limit holds for its named approver — visibly, with an age timer, never in a DM.
Requested by, decided by, executed how — one line each, sealed when the strip clears, exportable the day the accountant asks.
“We turned refunds-by-DM into a queue with rules. The founder stopped being the approval bottleneck, and I stopped screenshotting Slack threads for our accountant.”
“The first week, the board caught a duplicate-order pattern we'd been eating for months. Every “who approved this?” now has a one-line answer.”
Start with one workflow free. Pay when the board runs your whole back office.
Prove it on one workflow.
The whole back office, boarded.
For teams with auditors.
Only through your platforms' own APIs, with scoped keys, and only after a rule or a named approver says yes. There's no direct database access, and read-only mode is the default for every new connection — you promote it to act when you're ready.
Each rule names its approvers. Past your four-eyes threshold, two must agree; nobody can approve their own request, including admins and including the founder. The board shows who's holding what, so approval latency is visible instead of personal.
The most restrictive rule wins — a strip that one rule would auto-clear and another would hold, holds. The strip shows every rule that fired, in order, so a surprising outcome is a readable one.
No, and we won't pretend otherwise. Groundcrew gives you an audit-ready trail — who asked, who decided, what executed. Certifications, controls, and legal sign-off are your organization's work; a queue doesn't make you compliant, it makes you answerable.
Nothing destructive. Your platforms keep running exactly as before — Groundcrew only ever acted through them. Strips queue up and the board catches up when it's back; holds stay held, because failing safe is the whole personality of the product.
Yes — export the full trail to CSV or JSON on any plan, any time. On Tower it's retained forever; either way it's your record, not our hostage.
Give them a board with rules, instead of a group chat with vibes.
Pilot is free · 2 seats · no card