Partner Light
A register is not a document. It is a state, and states need keeping.
For teams that have completed the AI Comms Sprint and need an owner for what comes next.
The register ages with every hire. Tools change. An automation that nobody maintains eventually breaks.
Everything we build has the same weakness: it is accurate on the day we leave. Three hires later the register is out of date, a source has changed its page structure, and the automation that ran perfectly in September quietly stops in January.
Partner Light is the answer to that, and it is deliberately light. One automation a month and two hours of advice: enough to keep the system honest, not so much that you are paying for capacity you do not use.
It exists after the Sprint, not instead of it. There has to be something to maintain.
How it runs
- One automation a monthNew or revised, your choice. This is the heart of it, and it is what makes renewing obvious rather than a decision.
- Two hours of advisoryThe real questions: can we use this tool, does this piece have to be disclosed, is this person covered. Usually asked in ten-minute pieces rather than one meeting.
- Register and policy kept currentIncluding everyone who joins. This is the part that silently expires if nobody owns it.
- A one-page note each monthOnly what changed and only what touches you. Not a newsletter.
What you leave with
- A working set of automations that survives staff turnover and tool changes.
- A register and policy that are current on any day someone asks, not just in the month we delivered them.
- Monthly written traces of the maintenance, which is itself evidence of measures taken.
- Someone to ask before you do something questionable, rather than after.
- Priority and preferential rates on other White Rabbit work.
Six months, renewable. Requires the AI Comms Sprint first.
€700 per month
€7,000 paid annually, which is two months free.
Talk about keeping it running Start with the free webinarQuestions
Why is there a minimum of six months?
Because one month of maintenance proves nothing. The value shows up the first time a source changes, a tool updates or someone joins, and that rarely happens in the first thirty days.
What if we do not need an automation in a given month?
Then we revise an existing one, or spend the time on the register, the policy or the workflow documentation. The hours do not roll over indefinitely, but no month goes to waste.
Can we start with this instead of the Sprint?
No. There would be nothing to maintain and no shared understanding of your workflow. The Sprint is where the system gets built; this is where it stays alive.
