A FINANCE LEAD ASKS
“What does this process cost me, and where does it leak?”
BILLY ANSWERS, FROM THE PERFORMANCE FACTS ATTACHED TO EACH STEP
Audio arrives when the production voice is finished. The transcript is the whole answer, word for word.
Meter-to-cash runs eleven steps from read to payment. Four of them carry a target, and three of those four are being met.
The exception path is where the cost sits. Roughly one in seven billing documents goes down it, and it adds two approval steps and a manual check. The cycle-time target for the standard path is four days; nothing on the exception path carries a target at all.
There is a contradiction worth knowing about. The documented target says a rebill is resolved within five days. The flow has a wait state after the credit review with no owner and no time limit on it. Those two statements cannot both be true, and the source document does not resolve it.
I am not going to guess which one is right. The target came from page twelve of the service standard; the wait state came from page thirty-one of the design document. Both are quoted in the record if you want to look.
THE VOICE AGENT
One process. Four people. Four different answers.
Billy answers from the record itself, not by searching your files. He knows who is asking, and he cites the evidence behind what he says.
No credit card. Five design partner places. A person replies.
How he is grounded
Billy is not a chatbot reading your files. He answers from the structured record, the same one you can browse, edit and export, and he cites the evidence behind what he says. He works from a small, relevant slice of it rather than the whole corpus, which is why the answers stay specific.
When the record does not say, he says the record does not say. That is not a personality choice. Empty beats invented is a rule in how the record is built, and he inherits it.
Notice what he did in the answers above: he distinguished confirmed from unconfirmed, he named a contradiction rather than smoothing it over, and he pointed at a gap in the documentation instead of filling it in. That is the whole idea.
| Ask Billy, typed or spoken | Grounded in the capture, not in a search over your files. | Beta |
|---|---|---|
| Stakeholder-framed playback | The same process, answered as a CFO, an auditor, a new joiner or an owner. | Beta |
| Narrated walkthroughs | The visual focus follows the narration, step by step. | Beta |
| Barge-in | Interrupt mid-walkthrough with a question, get an answer, resume. | Roadmap |
| Meeting presence | Billy joins a Teams or Zoom call and answers from the record. | Roadmap |
WHAT WORKS TODAY, AND WHAT DOESN’T
Billy is in testing. Here is exactly where.
These labels come from the same file that drives the features page, so the two can never drift apart.
Ask Billy about your own process.
He runs inside your workspace, on your own documents. Start the free trial and put a real question to him.
No credit card. Five design partner places. A person replies.