Professional Services
Stop losing margin in the approval gap
Scope changes, discounts and client sign-off routed the moment they are raised, not the next time someone checks a shared inbox.
What this usually looks like today
A scope change is agreed on a call and nobody writes down who approved it.
Discounts get granted by whoever the client asks first.
Creative goes to the client before the account lead has seen it.
Workflows
What professional services teams run in Branchsolve
Each of these is a description away. None of them is a template you have to adopt.
Scope changes
Hours, fee impact and client named on the form. Anything above the delegated limit reaches the engagement partner.
Discount authorisation
Percentage off list decides the approver, so a 5% call never waits behind a 40% one.
Statement of work
Legal and finance review in parallel, both must complete, and the signed PDF is attached to the record.
Creative review
A task step, not an approval — the reviewer marks it done and can be required to record what changed.
New client acceptance
Conflict check and credit check gated before commercial terms are discussed.
Subcontractor engagement
Rate, duration and insurance certificate collected, then routed by total contract value.
Routing
Thresholds you can see before you commit
Branchsolve derives the boundary cases from the workflow’s own rules and shows you where each one lands. Nobody types this table out — it falls out of what you described.
Discount request
- Up to 5%Account lead
- 6–15%Account lead, then Practice director
- Over 15%…plus Managing partner
- Any discount on a fixed-fee SOW…plus Finance
Questions we get from professional services teams
Do our clients need accounts?
No. Approvals are for your own people. Client-facing sign-off is captured as an attachment on the request.
Can we run this per client?
Yes — the client is a field on the form, and conditions can route on it, so one workflow covers every account.
How long does it take to change a threshold?
Say the new number in chat. You get a diff and a fresh simulation, then publish. The old version keeps running the requests already on it.
Your process doesn’t have to be on this list
If you can describe it, Branchsolve can run it. Bring the one that causes the most arguments.
Request a demo