Account-risk rules
Agree which signals matter, how to interpret them, and which exceptions should reach a person for review.
Custom retention systems
A clearer path
from risk to action.
For the work beyond a report: a repeatable retention process shaped around your accounts, your team, and your workflow.
Scope and quote after discovery. Deliverables agreed before work begins.
An illustrative workflow
Signals
Review
Action
Clear ownership and human review
A concept to discuss. The actual tools, rules, and process depend on discovery and agreed scope.
What the work can include
A system shaped around
the decisions you need to make.
Custom work is scoped as a project. The right combination depends on the information available and how your team will use it.
Reporting or dashboard
Define the views, priority information, and review steps that help the team decide what to do next.
Build and test
Implement the agreed scope and test the rules, outputs, and workflow against agreed acceptance criteria.
Documentation and handoff
Agree what your team needs to use and maintain the work, including documentation and a practical handoff.
From discovery to handoff
Get clear on the work.
Then agree the project.
The quote follows the scope. There is no universal project price.
Discuss the workflow
Start with the problem, the decisions your team makes, and what you want to improve.
Agree a proposal
Confirm deliverables, responsibilities, timing, acceptance criteria, price, and any ongoing support.
Implement, review, and hand off
Complete the agreed work with testing and a handoff. Any further work is discussed separately.
Before we begin
A few useful distinctions.
How is this different from a retention report?
A retention report is a deliverable you receive: a review of customer patterns and a prioritized follow-up list. A custom system is project work to support a recurring process for your team, with the outputs and implementation agreed after discovery.
Can it work with our existing tools?
Discovery establishes what is feasible with your tools and available information. Any connection to another system, its permissions, and implementation work must be assessed and agreed in scope.
Who contacts the customer?
Your team decides whether and how to contact customers. The illustrative workflow describes human review and follow-through; automatic customer contact is not included in this proposal.
What happens after handoff?
Support, maintenance, and future changes are discussed and agreed separately. The project proposal defines what is included at handoff.
Tell Matt about the work.
A short description of the workflow and the decision you want to improve is a useful starting point.
Customer data is transferred only after qualification. No payment details, passwords, private notes, or sensitive customer information are needed.