The process is a person
In long-established family businesses the process frequently is somebody. They know which customers get which terms, which supplier to call when something is urgent, and which rules bend for whom.
That knowledge is genuinely valuable and it is also a single point of failure that nobody has planned around.
Documentation is the real deliverable
The most valuable output of the first project is often not the software. It is that thirty years of undocumented judgement finally gets written down, in a form somebody else could follow.
We do that by watching and asking, not by handing someone a template. People cannot list rules they apply unconsciously; they can correct a written version of what you observed.
Expect some rules to be indefensible
Automation surfaces decisions that have never been examined. Why does that customer get those terms? Why is this checked twice and that not at all? Sometimes there is a good reason; sometimes it is 1998.
That conversation is uncomfortable and it is the actual value. We raise it neutrally and leave the decision with you.
Handle the succession angle deliberately
- Which knowledge exists only in one head, and what happens if that person is unavailable
- Which relationships are personal rather than institutional
- What a new family member or manager would need to run this next year
- What a buyer would ask for during due diligence, if that is ever relevant
Keep what makes you different
Family businesses often win on judgement, flexibility and relationships. Automating those away in the name of consistency is a real risk and we will flag it.
Automate the administration behind the relationship, not the relationship. The customer who calls and asks for the owner should still get the owner.