Tend
Shepherd OS
Shepherd OS is a pastoral workspace for church staff. We designed and built the product surface around preparation, care, and team clarity—so ministry work feels organized, not scattered.
Outcome: Estimated +30–50% staff activation / weekly active use in 90 days for evaluating teams vs. doc/chat chaos.
Growth story
Church teams drown in docs, chats, and calendars. Shepherd OS exists to give pastoral staff one workspace. What changed: product language for pastoral jobs; workspace UI staff can evaluate; foundation for the wider Tend ecosystem. Estimated growth (90 days): +30–50% activation among pilot staff; +25–40% weekly active use; −20–35% tool-switching for core prep tasks.
Challenge
Pastoral work was spread across tools that were never designed for church staff.
What we changed
Estimated growth impact
| Lever | Directional estimate (90 days) |
| --- | --- |
| Staff activation (pilots) | **+30–50%** |
| Weekly active use | **+25–40%** |
| Tool-switching for prep | **−20–35%** |
Results
A pastoral workspace prototype that church staff can evaluate and use.
Growth journey
Key milestones and outcomes.
Name the jobs
Made pastoral tasks first-class workspace areas staff recognize.
Ship the workspace
Released the live product UI for staff evaluation.
Grow staff activation
Target: +30–50% activation and stronger weekly use in pilot teams.