Stuut's 47% DSO claim runs more than double its own ZoomInfo result

An invoice comes back rejected because the purchase order number is missing. It goes back in through the customer's AP portal, the payment lands short, and the gap turns into a deduction someone has to research. Stuut describes the problem with that same chain, and says its software follows it across thousands of invoices at once, logging into AP portals and reconciling cash as it arrives ^[7].

The launch announcement says customers can "automate 100% of their work" ^[4]. The production figures Stuut gives are narrower. By its count, 81.7% of outbound collections activity runs without human involvement and 95% of incoming payments are matched automatically ^[5]. On that outbound number, about 18% of collections activity still goes through a person ^[20]. Both rates cover outbound chasing and cash matching.

Stuut says it cuts the average customer's days sales outstanding by 47% ^[1]. ZoomInfo, the one customer with before-and-after figures in the coverage, went from 51 days to 40, according to SiliconANGLE ^[6]. The drop is 11 days, or about 22% ^[17]. A 47% cut from the same start would have put ZoomInfo near 27 days ^[18], and the advertised average is a little more than twice the named result ^[19]. Neither report explains how the 47% was calculated or over what period. An average can sit well above a single reference when other customers started from slower payment cycles and had more days to lose.

Two of the outside voices in the coverage have a commercial stake. Shawn Ryan, a partner and US working capital leader at EY-Parthenon, said: "Order-to-cash performance has always been capped by capacity: how many accounts a team can work, how many disputes it can chase. Stuut's autonomous execution removes that ceiling while holding to the controls a global enterprise requires." ^[15] EY is on Stuut's list of partners that help enterprises buy and deploy the platform ^[14]. Julian Marcu of Insight Partners, which led the round ^[2], said: "A single invoice error can trigger weeks of follow-up across teams and systems and at scale that adds up to real revenue left on the table." ^[16] Chief executive Tarek Alaruri said AI lets the company "deliver the only solution with continuous learning loops" ^[10].

The test I would apply before a pilot has two axes. One is whether the vendor's DSO claim comes with a named customer, a start figure, an end figure and dates. The other is where your own overdue balance sits: in outbound chasing and unapplied cash, which Stuut's two published rates cover, or in disputes and deductions, outside those rates.

With a named reference and a balance concentrated in chasing and cash matching, a pilot measured against your own trailing DSO is justified. If the balance is dispute-heavy, the same reference supports a narrower pilot, budgeted closer to ZoomInfo's 22% than to 47%. A platform-wide percentage with no named baseline is a sales figure, and I would keep it out of the cash forecast until the vendor can put a customer's dates beside it. The cost of the slower route is the receivables that stay uncollected while the pilot runs.