Start with your process
Discuss a recent billing cycle, the tools you use and the exceptions that still require manual review. If your existing setup handles it, that is useful to know.
For managed IT service providers · Early prototype
Review the work.
See the evidence.
Then invoice.
Know what’s covered. Review what’s billable. Compare service tickets with agreement terms — with evidence for every human decision.
Fictional sample data. No account or client uploads in this demo.
Illustrative billing review / October
A short queue.
A clear reason for every case.
Mailbox password resetIncluded
New office network setupReview for billing
After-hours VPN incidentClarification needed
No automatic invoices. No assumed recoverable revenue.
01 / Read the ticket02 / Check the agreement03 / Record your decision
Explore the workflow
Open a case. Follow the evidence.
Three fictional cases show what a review could look like. Change the decisions, add notes, then export the reviewed rows.
Prototype disclosure: cases and suggested classifications are prewritten. This demo does not analyse uploaded documents or run an AI model. Decisions stay in this page's memory until reset or reload.
0 of 3 cases reviewedHuman decision required · No invoice is created
A narrow starting point
Test one billing cycle before connecting anything.
Agree a small sample
For a potential pilot, agree the necessary fields and data handling before sharing a limited, redacted export. No system credentials are needed for an export-based test.
Measure useful outcomes
Compare review time and confirmed billing decisions against your current process. A flagged ticket is not automatically billable or collectible.
Built by an independent developer
Could this help your next billing review?
I'm Yves Marie Combot. I'm testing this workflow with IT service providers before building a full product. The first step is a brief remote conversation about a real example.
Discuss your workflow ↗Opens your email app. Please do not send client documents or credentials in your first message.
What we would establish together
- A specific recurring review problem.
- A limited dataset and agreed handling terms.
- Clear acceptance criteria and a fixed pilot scope.
- Pricing agreed before any paid work begins.
No production service, PSA integration or automated billing is available through this page.
Before you try it
Practical questions
Is this a replacement for our PSA?
No. The hypothesis is a focused review step for exceptions that remain after existing PSA rules. Whether that gap exists is what we are testing.
Can I upload our tickets or contracts?
Not on this page. It uses only fictional examples. A real-data pilot would require a separately agreed scope, handling arrangements and secure transfer method.
Does this automatically identify money we can collect?
No. Contract scope, prior approvals and commercial decisions matter. The proposed workflow supplies evidence for a human decision; it does not establish an entitlement to payment.
What does the demo store?
Your sample decisions and notes are held only in browser memory and disappear on reload. Export creates a file on your device. This page contains no analytics or tracking scripts; hosting infrastructure may process standard access logs. Email enquiries are handled through OVHcloud and may be managed in Gmail.