Eligibility, pricing and approval rules
When the rules for who qualifies, what they pay and who can approve it live in people's heads.
I can build owned operational software that applies agreed rules consistently, shows how an answer was reached and keeps exceptions with the people accountable for approving them.
Problem diagnosis
A decision becomes hard to trust when its rules are scattered.
- Different people reach different answers from the same facts.
- Pricing or eligibility depends on exceptions known by one experienced person.
- Rule changes arrive by email, while overrides happen without a lasting reason.
Customers, staff and managers can receive inconsistent decisions without a clear record of which rule applied or who approved an exception.
Responsibility
Software can apply an agreed rule. It should not replace accountable judgement.
I can diagnose the decision path, design and build the workflow, test examples and document how rule changes are controlled. Responsible people own the rules and approvals. If a CRM or workflow product already models the decision safely, I will recommend keeping it.
This is a more specific version of Bespoke operational software.
What I would build
The first useful version would be concrete.
- 01
A clear rule catalogue
Each operational rule is recorded in plain language with an owner and effective date.
- 02
The facts each decision needs
The minimum inputs are collected once in a consistent form before the rules are applied.
- 03
A visible decision trail
The record shows which rules applied and what answer they produced.
- 04
Controlled exceptions and overrides
An exception can require the right approval and keep the reason with the decision.
- 05
Safe rule testing and change history
Known examples can be checked before a new rule replaces the current one.
Fit filter
Probably right, probably not.
Probably right when…
- The rules are stable enough to explain, own and test.
- Inconsistent decisions create a real operational or commercial risk.
- Responsible people want a visible route for exceptions and overrides.
Probably not me when…
- The decision must be made by a licensed professional rather than software.
- Rules change continuously and nobody is accountable for owning them.
- A CRM or workflow product already models the decision safely.
- You want unreviewed automated decisions with no accountable approver.
First step
Start with diagnosis, not a big commitment.
The first step is to compare a few decisions that should pass, fail or need an exception, then identify who owns each rule.
The initial consultation is free and can take up to 60 minutes. Paid work is £150 per hour plus VAT where applicable, billed in 30-minute increments. No retainer or lock-in. Your project code is yours and your accounts stay under your control.
Useful things to send before a call
- Examples that should pass and fail
- Current pricing or eligibility spreadsheets
- Exception and override emails
- The people allowed to approve an override
Objections
Questions you may have before you get in touch.
Could our CRM or spreadsheet keep doing this?
Yes, while the rules, permissions and change history remain safe and understandable. A custom build is for the point where that is no longer true.
How do existing rules and exceptions move across?
They first need to be written down, assigned an owner and tested against real examples. Conflicting rules should be resolved by the responsible people, not guessed during migration.
Can we define the boundary before building?
Yes. A paid diagnosis can produce a rule map, exception route and recommendation without committing you to a full implementation.
Let's solve difficult problems.
We'll talk through your current infrastructure and systems, any problems or opportunities, and the goals you want to achieve. I'll be honest about where I can and can't help.