Change requests as a revenue line — automated with Claude Code
Banks on a platform always want changes. At Vegapay I made those requests a priced, prioritised product line, then built the internal workflow to run it using Claude Code.
The problem
Client change requests (CRs) competed with the core roadmap for the same engineering time. Without a clear way to weigh them, the loudest request won, and work that could have been billed often wasn't. Tracking lived in spreadsheets, so proposals, negotiations, purchase orders and payouts were hard to follow and hard to audit.
Part 1: Commercial prioritisation
I took ownership of commercial prioritisation and the P&L for CRs, balancing three things for every request: what the customer needed, how much engineering capacity it would take, and its business impact. I converted 50+ partner and customer requirements into prioritised product enhancements and ran the change-request lifecycle from discovery and scoping through development and deployment.
Part 2: Building the workflow with Claude Code
Instead of writing a spec and waiting for an engineering slot, I built and digitised the internal CR and business workflows myself with Claude Code. Proposals, negotiation, PO tracking, payouts and operational reporting moved out of spreadsheets into one flow with approvals and a clear record of who did what.
Results
- 25% incremental revenue across 2 quarters from the CR program
- 50+ requirements turned into prioritised enhancements
- Clearer process visibility and auditability across proposal, negotiation, PO and payout
What I learned
Pricing change requests changes the conversation: when work has a cost, clients self-prioritise and the roadmap gets protected. And the fastest way to fix an internal process is often to build the tool yourself.