Their only SharePoint-savvy employee quit. Nothing broke.
One office manager had built every site, flow and permission over four years — then resigned with two weeks' notice. Nobody else in the firm knew how any of it worked.
Every site, flow and permission lived in one head.
Over four years, one office manager had quietly become the firm's entire SharePoint department. She built the client document libraries, the approval flows, the permission groups — every site, flow and permission the firm ran on. When something misbehaved, people walked to her desk. When someone joined or left, she sorted the access. None of it was written down, because it had never needed to be: she was always there.
Then she resigned, with two weeks' notice. The partners' first question — who else knows how this works? — had an uncomfortable answer: nobody. Nobody else knew which flows sent the reminders clients actually replied to, which permission groups guarded which client files, or what would stop working the day her account was disabled.
For an accounting firm, that is not an inconvenience. Client records, filing deadlines and confidentiality all ran through systems that were about to lose the only person who understood them — and recruiting a like-for-like replacement inside a notice period was never a realistic plan. The job was not to change anything. The job was to make sure nothing broke.
A handover to us, instead of to nobody.
No rebuild, no migration — continuity was the deliverable. We onboarded on a Starter retainer during her notice period, so the handover ran while the person who built everything was still in the building.
We joined on a Starter retainer while the office manager was still there, so every "how does this work?" could be put to the person who built it — and every answer went straight into the handover notes instead of out the door with her.
Every site, flow and permission group written down: what it does, who relies on it, what it connects to and what to check first when it misbehaves. The firm's setup now lives in documentation, not in one person's memory.
Joiners, leavers and access requests now come to us. Permissions stay aligned to the structure she built — reviewed and changed deliberately, instead of drifting with every ad-hoc request until nobody can explain them.
When a library misbehaves or a flow stops sending, the partners call us — not a recruiter. Questions get answered by the people holding the documentation, so the firm never again depends on a single irreplaceable memory.
The handover happened. The outages didn't.
No vanity metrics — these are the three numbers the partners measured the engagement on.
Who's your SharePoint person — and what happens if they resign?
Book a free 30-minute audit — we'll map what your setup depends on, flag what lives in one person's head, and show you what a documented handover looks like.