The Challenge
14 enterprise contracts paying 17 days late, every quarter.
CloudCo is a $12M ARR B2B SaaS that sells infrastructure monitoring to mid-market and enterprise customers. The product is sticky. NRR is 118%. Customers love it.
The problem was on the back end. Stripe handled the 266 self-serve accounts cleanly: autopay, retries, churn dashboards. But the 14 enterprise contracts (the ones doing $80k–$340k ARR each, the ones the company depended on) paid on net-30 wire and consistently paid 17 days late on average. Priya, the head of finance, had inherited a manual chase cadence: a Tuesday morning ritual of QuickBooks, Stripe, Mercury, then her inbox.
At any given moment, ~$320,000 sat outstanding across the enterprise book. The cost wasn’t just the cash. It was the fact that every Tuesday morning Priya was doing the same six tasks: pull aging, identify late accounts, draft reminders, send, log, repeat next week.
CloudCo had a budget approval to hire a second AR specialist in Q3. The req was 90% done. Priya pulled it back the day after the Tally demo.
The Solution
An AR agent that lives in Slack and speaks like the team.
CloudCo deployed Tally in a 30-minute call. Read-only OAuth to Gmail, QuickBooks, Stripe, Plaid (Mercury), and Slack. Two weeks of shadow mode while the agent tuned its voice on 28 samples of Priya’s past customer correspondence. Then the team flipped it live.
Stripe + QuickBooks, finally one source of truth.
The agent read Stripe payouts net of fees, matched them to QBO invoices, and posted the reconciliation entries automatically. Wires landing in Mercury for the annual contracts got matched to the QBO invoice on the same day. The Tuesday ritual stopped being a manual reconciliation problem.
Cadence built for net-30 enterprise AP.
Tally tuned the dunning cascade for the enterprise book: a friendly Day +1 nudge addressed to the AP contact, a Day +14 reminder that CC’d the deal’s AE, a Day +30 firm follow-up with a statement attached, and a Day +60 escalation flag to Priya for approval. Tone-matched to Priya’s actual writing: no generic dunning template, no “Dear Sir/Madam.”
The payment confirmation loop.
The biggest unexpected win was a class of error CloudCo didn’t know they were making. Three times in the first month, an enterprise AP team replied to a reminder with “we wired this last week.” Pre-Tally, CloudCo’s playbook was to apologize and confirm receipt. With Tally, the agent first checked Mercury and Stripe: the wires hadn’t landed. It pinged Priya in Slack: “CloudCo AP says they wired $24k Friday. Not on the feed yet. Confirm before responding?” Two of the three turned out to be wires sent to the wrong routing number. The third was a real wire that arrived two days later. In all three cases, the right next email got sent, and CloudCo never accidentally confirmed a payment that hadn’t landed.
Ask Tally for board and AE prep.
Within a month, the company’s use of Tally extended beyond the AR loop. The CFO asked in #leadership: “What closed vs. what billed last month?” The head of sales asked in #revenue: “What’s outstanding on my book heading into pipeline review?” The agent answered from the same unified Stripe + QBO + Mercury layer the AR cascade ran on. Board prep stopped being a multi-hour stitching exercise. The dashboard exists for the controller audit; the chat is where the team lived.
Process Discipline
Why the cadence held, and why the team trusted it.
CloudCo’s deployment worked because of process discipline as much as agent capability. Three things stand out.
Read-only first. The team didn’t flip Tally live on day one. Two weeks of shadow mode (agent drafts every email, sends nothing) gave Priya and the controller time to read 40 outbound drafts and correct three. By the time the agent went live, the voice was right and the team trusted it.
Approval gates that match how the team thinks. CloudCo configured DOA at $25k: anything above goes to Priya in Slack before sending. Below $25k, Tally auto-sends with an audit trail. After six weeks the threshold moved to $50k as confidence grew. The point isn’t the number; it’s that the gate maps to a real human decision boundary.
One channel, one ritual. CloudCo collapsed three weekly meetings (AR sync, collections review, payout reconciliation) into a single Friday-morning Tally digest in #ar-ops. Cash collected, items needing eyes, nothing else. The Tuesday ritual disappeared. The Friday digest became the whole rhythm.
The Results
$186K recovered, 14 days off DSO, and one hire avoided.
In 75 days on Tally, CloudCo reached $186,000 in past-due recovery across the enterprise book. The agent matched and posted $1.4M in Stripe + wire payments without manual intervention.
The DSO improvement on enterprise contracts was 14 days, from a 47-day baseline to 33 days. The Stripe-driven self-serve book didn’t change (it was already automated), but the enterprise book stopped being the “always 17 days late” problem it had been for the previous six quarters.
The avoided hire was the headline result internally. CloudCo budgeted $115k all-in (salary + benefits + recruiter + ramp) for a second AR specialist. Priya pulled the req. CloudCo paid Tally $1,995/mo on the Scale tier (roughly 21% of the all-in hire cost) and got higher AR throughput than the hire would have delivered, with an audit log the controller actually wanted.
The team also recovered 22 hours per week across Priya, the AR specialist, and the controller. Most of that time went into a finance hiring process for an FP&A analyst, a role that actually needed a human.
Takeaways
Takeaways for finance leads at $5M–$25M B2B SaaS.
CloudCo’s first 75 days offer a useful reference for any finance team weighing a hire vs. an agent. Three things stand out.
The hire isn’t the only path to throughput.
The default response to AR volume growth is “hire another AR person.” That math has worked for decades. At CloudCo’s scale, it stopped working. The agent ran the cascade more consistently than a junior hire would have, with full audit trail, and at 21% of the cost. The hire might still be right at $50M ARR. At $12M, it wasn’t.
Read-only mode is the only honest way to evaluate.
Two weeks of shadow mode let CloudCo see exactly what Tally would have sent before anything went out. It killed the “we won’t know until we’re committed” objection. Every finance team should require it from any agent vendor. (If a vendor won’t offer it, that’s the answer.)
The payment confirmation loop is the moat.
The single feature CloudCo describes as “the one we can’t live without” isn’t the invoicing or the cadence: it’s the confirmation loop. Catching three not-yet-landed wires in the first month prevented a class of error (confirm a payment that hasn’t arrived, then discover it 30 days later in close) that previously cost CloudCo serious customer trust. Every B2B finance lead has had this exact problem. Most don’t know it’s solvable.