Opskeep Keep Clients

Protect trust after and around delivery.

Use For

• Client check-ins, relationship health, retention, renewals, referrals, and testimonials.
• Follow-up wording when the user wants to keep trust or recover momentum.
• Relationship risks surfaced by delivery or closeout.

References

• Load references/keep-clients.md for the lane workflow.
• Load references/examples/keep-clients.md when an example shape helps.
• Load references/sole-trader.md when the requester is a solo tradesperson/freelancer, not a team engagement.

Output Contract

• Client or relationship signal.
• Why now.
• Suggested touch or ask.
• Owner and timing.
• Source/evidence or TBD.
• Watchlist items.

Boundaries

• Do not send messages or schedule reminders unless explicitly asked.
• One-shot self-email reminders go through opskeep-tools to opskeep-follow-up-reminders.
• Active delivery status stays opskeep-deliver-work unless relationship health dominates.

Gotchas

• Do not fake relationship history; mark unknown context as TBD.
• Generic follow-up is client work, not a reminder, unless future self-email wording is explicit.
• Testimonials, referrals, and renewals should be grounded in delivered value or client signal.