Catch a price overage before it becomes a chargeback
Every hour, WebRun opens Pruvan, compares each work order's logged estimate against the client's allowable price limit for that task, and posts your team a Slack flag for anything over the limit with no approved bid on file, so it gets approval before submission instead of a chargeback after.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch a Pruvan estimate over the client's allowable before it causes a chargeback?
Every hour, WebRun opens Pruvan and compares each unsubmitted work order estimate against the client's allowable price limit for that task. It checks whether an approved bid already covers any amount over the limit, then posts your team a Slack flag for anything still uncovered, so the overage gets approval before submission instead of a chargeback after.
- Overages get caught before submission, not after a chargeback
- Estimates already covered by an approved bid are never flagged twice
- The team gets a clear amount-over figure, not just a warning
Built for property preservation companies · field service estimators · REO vendor compliance staff · accounts receivable teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
direct.pruvan.com/v2/loginin a real browser with your saved login - no setup, no API keys. -
1
Pruvan - compare estimates against allowable limits
pruvan.com How to Automate Pruvan
WebRun opens Pruvan to compare estimates against allowable limits. - Open Pruvan and pull work orders with a logged cost estimate not yet submitted
- Compare each task's estimate against the client's allowable limit for that task type
- Check whether an approved bid already covers any amount over the limit
Done when Every unsubmitted estimate is checked against its allowable limit and bid status.
-
2
Slack - flag overages before submission
slack.com How to Automate Slack
WebRun opens Slack to flag overages before submission. - Post a flag for every order over its allowable limit with no approved bid on file
- Show the property, task, estimate, and allowable amount for each
- Keep the message internal so the team can get a bid approved before submitting
Done when The team has a flag in Slack for every unapproved overage.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it submit the work order?
No. WebRun only flags the overage before submission. Submitting the order to the client stays a manual step in Pruvan.
What if a bid already covers the overage?
It checks for an approved bid on the order first and only flags amounts that are not already covered, so approved overages are not flagged again.
Why does this matter for chargebacks?
Submitting a cost over the client's allowable limit without an approved bid is a common cause of a chargeback. Catching it before submission gives the team a chance to get approval first.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.