Childcare Marketing CRM & Operations Platform

The problem

Account managers tracked client work across disconnected tools, so nobody could see workload distribution or catch a client message that had gone unanswered. Client records also had to stay continuously in sync with an external CRM whose API failed in ways that silently corrupted state.

Key decisions

1. 01

   Built an Operations Report module around the questions managers actually ask

   Workload per account manager, task management with client-approval workflows, and a communications overview that surfaces unresponded messages rather than waiting for someone to notice.

2. 02

   Hardened the GoHighLevel integration at its failure points

   OAuth token refresh, opportunity-search pagination, and error handling were rebuilt so partial failures stop rather than propagate — the integration's reliability problem was in its edges, not its happy path.

3. 03

   Moved slow work off the request path

   Background job processing with pg-boss workers and Sentry monitoring, plus data-fetching performance tuning — parallelized queries, lazy-loaded modals, and paginated directories for large data sets.

4. 04

   Audited database security rather than assuming it

   Supabase's splinter linter plus RLS policy audits, with owned schema migrations and type generation keeping environments consistent.

Screens

Outcome

Core CRM, Operations Report, and Onboarding modules shipped and in daily use, with Vitest coverage and synced Drizzle schemas across environments.