Introducing Playbooks. One Place to Teach Stuut How to Run Your AR.

Read More

Playbooks: One Place to Teach Stuut How to Run Your AR

Ben Winter
COO
Table of contents

See Stuut in action

Get a personalized demo of Stuut and see how it can help with AR automation.

Get started

One place to teach the agent your business

Playbooks is a single surface where you define everything the agent needs to know about how your AR operation runs. It combines your business knowledge and your collection strategy into one place: your payment terms by customer segment, what your reason codes actually mean, who to escalate to and when, how your outreach cadence should work, and the policies that govern how exceptions get handled. Everything the agent needs to make good decisions, in one surface instead of scattered across settings pages and uploaded documents.

The agent doesn't just follow the Playbook. It learns from what's working and suggests updates. If a customer consistently pays on day 45 despite net-30 terms the agent surfaces the pattern and proposes a Playbook edit for your team to approve.

You stay in control. The agent gets smarter.

Why this matters

The biggest barrier to trusting an AI agent isn't capability. It's visibility. If you can't see what the agent "knows," you end up babysitting the technology instead of setting strategy. Playbooks makes every agent action traceable. When you want the agent to act differently than it has in the past, you're one click away from updating the Playbook.

It also changes onboarding. Instead of configuring 15 different screens, you build your Playbook. For existing customers, we're generating a starting Playbook from your email data and collection history. Send us your SOP and we'll layer that in too.

We're starting with Collections and expanding across Cash Application, Disputes, Deductions, and Credit. Each module gets its own section, but the agent carries context across all of them. That's the power of one agent with shared memory across everything it does.

See it in action

If you're a Stuut customer, reach out to your account team to turn Playbooks on. If you're not yet working with us, this is a good reason to start a conversation.

[Book a walkthrough →]

Ben Winter

COO

Ben brings over a decade of go-to-market and operations expertise to building AR automation that actually works. He was VP Marketing at Fairmarkit (where he met Tarek) and GTM executive at Waldo before co-founding Stuut. He focuses on operations, product, and marketing—ensuring the platform integrates seamlessly with existing ERP systems and delivers results in days rather than months.

Frequently asked questions  about DSO

Is a higher or lower DSO better?
Lower is better because it means cash reaches your account faster. A DSO of 35 days is better than 55 days if your payment terms are the same.
Does DSO include current AR?
Yes. DSO reflects the total dollar amount you're owed from outstanding invoices, including invoices that aren't yet due.
How does bad debt affect DSO?
Writing off bad debt reduces your AR balance, which artificially lowers DSO even though no cash was collected. Ensure your AR figure is net of bad debt reserves for accurate measurement.
Should I calculate DSO monthly or annually?
Both. Annual DSO tracks long-term trends, while monthly DSO helps you spot process problems quickly and take corrective action before they compound.
What's the difference between DSO and CEI?
DSO measures collection speed in days. CEI measures collection quality as a percentage. A company can have low DSO but poor CEI if they're writing off accounts aggressively.
Can I reduce DSO without upsetting customers?
Yes. Proactive communication before due dates, helpful reminders, and fast dispute resolution improve customer experience while accelerating payment.

Related posts

Setup time to learn more