Case Study · Senior Care

Sticky Notes to Systems

A senior living placement service was already thriving on relationships and reputation — it just didn't have the structure to grow beyond what one person could carry. In under 2 months, it has a fully built operation across content, communications, competitive intelligence, compliance, and finance, and the team continues to extend it on their own.

This is a founder-led senior placement business, and it runs the way trust-based, referral-driven businesses run: on the founder's reputation, their relationships, and word of mouth. That's a real asset — it's also why the business had almost no documented systems. The knowledge that made it work lived with the founder and their team, not in any process that could be handed off, taught, or scaled. Getting that knowledge out of people's heads and into something usable was the first challenge, before any system could be built.

The engagement started with a full evaluation of the business, not a single project. The finding was straightforward: nearly everything needed structure. Rather than build all of it at once, the work began by prioritizing what mattered most — the data a future CRM would need, the financial visibility a real accounting system would provide — then building alongside the founder and their team, one workflow at a time.

Before

  • No documented workflows or processes, anywhere in the business
  • No shared calendar; tasks scattered across notes in different places
  • Team communicated by personal text, including late at night
  • Content posted sporadically, with no planning, strategy, or record of what had been covered
  • Little visibility into what competitors were doing or how the business was positioned against them
  • Compliance was valued but never written down
  • No accounting system at all

Zandra Built

  • Ongoing 1-on-1 coaching with employees and the founder to turn ideas into implemented processes
  • Personalized daily AI assistants: email + calendar + Slack + task list → one morning brief
  • Internal communications hub (Slack) — team comms, content repository, AI-workflow channel
  • 5-channel content engine (blog, Google Business Profile, LinkedIn, Facebook, Instagram), biweekly
  • Competitive intelligence + content-history tracking system
  • Written, HIPAA-aware compliance framework
  • Phased CRM build: data capture → software evaluation → implementation
  • QuickBooks Online for bills, invoices, and reporting

After

  • ~3–5 hrs/week returned per employee EST.
  • No more after-hours texting between team members
  • 5 content channels live, up from sporadic, single-channel posting
  • Ongoing competitor visibility and a documented content history
  • Multiple compliance gaps identified and closed
  • Invoices now sent same-day, up from no consistent process
  • One employee continues to extend their own AI workflows, unprompted

Completed — Phase 1, Opportunity Identifications + New Builds

Coaching

Before

Ideas for how things could work better existed — with the founder and with employees — but couldn't turn them into an actual process, let alone make sure a good idea from a conversation actually got built.

Built

Ongoing 1-on-1 coaching with employees and the founder — helping each of them bring their own ideas to life, and shaping processes that work both for them personally and for the team and business as a whole. Every session ends with next steps: implemented immediately, or scheduled.

After

A standing practice where what gets discussed gets built — not a conversation that goes nowhere.

SEQUENCED

A CRM was an obvious need, but a CRM needs data it didn't have yet — so data collection came first. Financial visibility was urgent, so QuickBooks came early too. Coaching sessions are where that kind of sequencing gets decided, not guessed at.

CRM

Before

No CRM, and no consistent record of leads or clients to build one from — information about families and communities lived in memory and scattered notes, not in one place.

Built

Phase 1 of a phased CRM build: collecting and structuring all client and lead data in a HIPAA-compliant Google Workspace — the data foundation an actual CRM platform will need, built before choosing or paying for one.

After

A structured, HIPAA-compliant record of leads and clients where none existed before — ready to move into a real CRM platform.

Next

Evaluating CRM software against what's been learned from running this structured data manually (Phase 2), ahead of full implementation (Phase 3).

Daily operations

Before this, one employee had no idea what a given day would look like or what to focus on. The other kept notes scattered across different places and was losing track of what was in motion. Neither had a shared calendar or a way to see how work was tracking.

Before

Priorities reconstructed from memory each morning. No calendar. No visibility into what was falling behind.

Built

A daily assistant reads email, calendar, a Slack "brain dump" channel, and a task list — and delivers one morning brief with priorities, schedule, and outstanding items. Paired with direct coaching on time management and on bringing metrics to leadership proactively.

After

A single daily source of truth, every morning, for both employees — replacing scattered notes and guesswork.

Next

Weekly and monthly KPI summaries against goals, so progress is visible over time, not just day to day.

CAUGHT

The daily brief surfaced an event flyer correction a speaker had requested that had gone unanswered — before it became a missed commitment.

COVERED

When the employee who owns event materials was traveling, we resolved a second flyer change entirely through AI — no manual design work, using the practice's Claude-Canva integration.

EXTENDING

One month after launch, that same employee independently connected Canva to Claude and built a workflow to generate event flyers from a plain-language description — and they've continued extending their own AI workflows on their own since, unprompted.

Internal communications

Before

No shared system — team members communicated by personal text, including late at night, with no boundary between work and off-hours.

Built

Slack, implemented as the team's internal communications hub. It now does triple duty: day-to-day team communication, a content repository, and the channel AI workflows (like the daily brief and the brain-dump channel) run through.

After

One shared, searchable home for communication and content — and no more after-hours texting between team members.

Content engine

Before

Posting was sporadic, with no planning or strategy behind it — whatever got posted, got posted, whenever there was time.

Built

A biweekly content engine covering blog, Google Business Profile, LinkedIn, Facebook, and Instagram. Drafts land in a Google Doc for an employee to review and schedule; blog updates publish automatically.

After

Five channels running on a real cadence, with a human review step, instead of sporadic single-channel posting.

Next

Evaluating social-management and analytics platforms to close the loop with real performance data.

Competitive intelligence & content repository

Before

No visibility into what competitors were doing or saying, and no record of what content topics the business had already covered.

Built

A system that tracks competitor activity on a regular basis, identifies messaging and positioning gaps, and keeps a running record of what topics have already been discussed — so new content builds on what exists instead of repeating it.

After

Ongoing competitive visibility and a documented content history feeding directly into what gets written next.

Next

Feeding everything this surfaces — competitor moves and topic history — directly into the content repository, so it actively shapes what gets written next instead of just logging what's already been said.

Compliance

Before

Compliance was something the business cared about, but nothing was written down and nothing was formally reviewed.

Built

A written compliance guide and structure, built through a full review of how the business handles sensitive client information — surfacing multiple avenues of potential exposure along the way, each one identified and closed.

After

A documented, HIPAA-aware compliance framework where none existed, with every identified exposure closed before it became a problem.

Next

A recurring quarterly compliance review, plus QA on any new software systems added to the stack.

Financial operations

Before

No accounting system existed. Bills, invoices, and financial reporting had no consistent process.

Built

QuickBooks Online, implemented and tied to the same daily-assistant cadence that surfaces outstanding tasks.

After

Invoices now go out the same day — leading to faster, more predictable payment cycles.

Next

Routing QBO reporting into the same weekly and monthly KPI summaries once those exist — while maintaining security and never routing financial information through public AI systems.

In Progress — Phase 2, Evaluations + Implementations

  • Content: evaluating social-management and analytics platforms to make the content loop smarter over time
  • Daily operations: building weekly and monthly KPI summaries against goals
  • CRM: moving from structured data collection into software evaluation ahead of implementation

This engagement runs on an ongoing monthly retainer, delivered through 1-on-1 training with individual employees — listening to what they actually need, then building the specific automated or AI-powered workflow that solves it. The business was already thriving on relationships and reputation; this gave it the structure to grow without losing what made it work in the first place.