Automated Revenue Schedule Rate Change Notices
When a pricing or contract update modifies revenue schedules in Leapfin, WebRun identifies every affected customer, drafts a rate-change notice email in Gmail for each, queues a contract amendment envelope in DocuSign where a signature is needed, and notifies your finance and legal teams in Slack that drafts are ready for review. Nothing is sent until your team approves.
How do I automatically draft rate-change notices when revenue schedules are updated?
WebRun identifies every customer affected by a revenue schedule update in Leapfin, drafts a rate-change notice in Gmail for each, queues a contract amendment envelope in DocuSign where a signature is required, and notifies your finance and legal teams in Slack. No notice or amendment is sent until your team reviews and approves every draft.
- Every affected customer gets a drafted notice within minutes of a schedule update
- No rate-change notice reaches a customer without finance and legal sign-off
- DocuSign amendment envelopes are queued and ready for legal review before the effective date
Built for SaaS finance teams · legal and compliance teams · revenue accounting managers · CFOs
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
app.leapfin.comin a real browser with your saved login - no setup, no API keys. -
1
Leapfin - identify affected revenue schedules
leapfin.com
WebRun opens Leapfin to identify affected revenue schedules. - Open Leapfin and identify all revenue schedules updated in the current batch
- For each changed schedule, capture the customer, old rate, new rate, effective date, and contract type
- Group customers by change type: price increase, term extension, or plan change
Done when Every customer with a changed revenue schedule is listed with old and new rate details.
-
2
Gmail - draft rate-change notice for each customer
gmail.com
WebRun opens Gmail to draft rate-change notice for each customer. - Draft a rate-change notice email for each affected customer with the specific change, effective date, and any action required
- Leave every draft unsent in Gmail for the finance and legal teams to review and approve
- Do not send any rate-change notice to a customer without explicit review and approval
Done when A rate-change notice draft exists in Gmail for every affected customer, unsent and awaiting approval.
-
3
DocuSign - queue contract amendment envelope for review
docusign.com
WebRun opens DocuSign to queue contract amendment envelope for review. - For customers whose contract requires a signed amendment, create a DocuSign envelope with the amendment document in Draft status
- Tag the correct signers and set the expiry date to match the effective date of the rate change
- Leave the envelope as a draft. Do not send any DocuSign envelope without legal review
Done when Draft DocuSign envelopes are queued for every customer requiring a signed contract amendment, unsent and pending legal review.
-
4
Slack - notify finance and legal that drafts are ready
slack.com
WebRun opens Slack to notify finance and legal that drafts are ready. - Post a summary to the finance and legal Slack channels listing the number of affected customers, draft emails in Gmail, and draft envelopes in DocuSign
- Tag the finance manager and legal lead to review and approve before the effective date
- Include the effective date and any compliance deadline relevant to the rate change
Done when Finance and legal teams are notified in Slack with a full summary of pending drafts.
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
Will it send rate-change notices to customers without my approval?
No. Every notice is drafted in Gmail and left unsent, and every DocuSign envelope stays in Draft status. Your finance and legal teams review and approve each one before anything reaches a customer.
How does it know which customers need a signed amendment versus an email notice only?
You define the rule during setup: for example, customers on enterprise contracts with a signed MSA require a DocuSign amendment, while month-to-month customers receive an email notice only.
What if a customer's rate did not actually change after the Leapfin update?
WebRun compares the old and new rate for each schedule and skips any customer where the net recognized amount is unchanged.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.