3quip.me — Claude Workflow Automation for Senior Living Operators
3quip.me logo 3quip.me Claude automation for senior living
Built on Claude · IL, AL & Memory Care operators

Your team has Claude. They're still staring at a blank chat box.

A subscription isn't a system. We take the SOPs your communities already run every week — census roll-ups, license renewals, rate audits — and turn them into working Claude workflows your staff actually use. Live in 20 days, with two training sessions for the team.

Weekly Census Roll-Up
MON 7:00am
✓ Pulled IL / AL / MC counts from 3 systems
✓ Reconciled move-ins, move-outs, notices
2 variances flagged — waiting on the ED
Draft ready in 4 min · was 2h 40m
Claude
Capable. Patient.
Waiting for instructions.
3quip.me
3quip.me
Turns your SOPs into
workflows Claude can run.
Your community
IL, AL & Memory Care —
and the SOPs behind them.
SOPs IN · REVIEWED WORK OUT · EVERY WEEK
WHAT THEY HAVE TODAY
How can I help you today?

Powerful, patient, and completely unopinionated about how your community runs. So the ED opens it, doesn't know what to paste, and goes back to the spreadsheet.

→
WHAT WE HAND OVER
Weekly Census Roll-UpMon 7:00am
Renewal & Survey WatchDaily
Rate & Promo Verification1st & 15th

Named workflows with the prompt, the source data, the checks, and the output format already decided. Staff press go and review the result.

THE FOUR WE BUILD FIRST

High-effort, low-judgment. Every SOP becomes three steps.

Intake, draft, review. Claude does the stitching and the cross-checking. Your people keep every decision that requires judgment.

Occupancy & Census Roll-Up

WEEKLY · PER COMMUNITY

Today an ED pulls IL/AL/MC counts, move-ins, move-outs and notices out of separate systems and stitches them into the corporate rollup — same formulas, same reconciliation checks, every week.

STEP 1 — INTAKE

Exports from each community's PMS land in one folder. Claude reads every format you actually get — CSV, PDF, the one that's still a screenshot.

STEP 2 — DRAFT

It builds the rollup in your existing template, runs your reconciliation checks, and flags anything that doesn't tie out to last week.

STEP 3 — REVIEW

The ED gets a finished rollup plus a short list of variances to explain. They interpret the trend and decide the action — as they should.

Licensing Renewal & Survey Prep Tracking

DAILY WATCH · MULTI-STATE

State licensing renewals, staff certification expirations, fire and life-safety cycles — tracked across frameworks that don't agree with each other. A calendar-and-documents problem, not a judgment problem.

STEP 1 — INTAKE

Every license, cert and inspection cycle is loaded once, per state, with its own renewal window and document list.

STEP 2 — DRAFT

Claude issues the reminder ladder — 90/60/30/7 days — names the missing documents, and drafts the chase email to the person who owns each one.

STEP 3 — REVIEW

Compliance opens one board: what's due, what's collected, what's late. They still run the survey — they just stop rebuilding the tracker.

Competitor & Market Rate Intelligence

MONTHLY · PER COMP SET

Comp-set rates, occupancy signals and promo activity from public listings and licensing databases. High-effort and low-judgment by hand, and it feeds your pricing committee directly.

STEP 1 — INTAKE

Your comp set is defined once per market: who counts as a competitor, which public sources are fair game, what fields matter.

STEP 2 — DRAFT

Claude refreshes the grid, notes what moved since last month, and cites the source line for every number so nothing is unverifiable.

STEP 3 — REVIEW

The pricing committee gets a current, sourced comp grid and a one-page "what changed" note. Strategy stays with the humans.

Rate & Promo Verification Across Communities

TWICE MONTHLY · ALL SITES

Published rates, level-of-care tiers and live promos versus what's actually in the PMS and CRM. Today a QA person cross-checks PDFs against spreadsheets, community by community.

STEP 1 — INTAKE

Website pages, rate sheets and marketing PDFs on one side; the PMS and CRM export on the other. Both sides, same run.

STEP 2 — DRAFT

Claude matches every LOC tier and promo line and produces a discrepancy list — community, field, published value, system value.

STEP 3 — REVIEW

QA works a short exception list instead of a full audit. Flagging discrepancies is the job; pricing strategy stays untouched.

Four workflows are included in the setup fee. Yours may differ — we scope them in the audit call.

DO THE MATH YOURSELF

What those hours are actually costing you a year.

We don't have a case study to sell you yet — so use your own numbers. Set the hours your team spends on these four SOPs each week and what that hour costs you loaded.

{{ hoursLabel }}
{{ rateLabel }}
MANUAL COST OF THESE SOPS
{{ annual }}
per year · {{ weeklyLabel }} a week × 52 weeks
Year one with 3quip{{ yearOne }}
Setup pays for itself in{{ payback }}
Net year-one difference{{ net }}

Illustrative arithmetic from your inputs, not a promise. Hours recovered go back into residents, tours and move-ins — not headcount reduction, unless that's your goal.

TWENTY BUSINESS DAYS

From first call to your team running it without us.

DAYS 1–4

Shadow & scope

We sit with the people who run the SOP today, capture the real steps — including the undocumented ones — and lock the four workflows.

DAYS 5–12

Build in your Claude

Everything is built inside your own Claude workspace, on your data, with your templates and your checks. Nothing lives on our side.

DAYS 13–17

Run it side by side

One full cycle done the old way and the new way at once. We tune until the output matches what your reviewer would have produced.

DAYS 18–20

Train & hand over

Two live training sessions, the written runbook, and a named owner per workflow. Then we get out of the way.

What you get on day 20

◆

Four working workflows in your own Claude workspace, each with its owner named.

◆

Two live training sessions — one for the people who run it, one for the people who review it. Recorded, so new hires get the same onboarding.

◆

A written runbook per workflow: inputs, the prompt, what good output looks like, and what to do when it looks wrong.

◆

A clean handover — you own the prompts, the templates and the outputs. No lock-in, no black box.

A TUESDAY, BEFORE AND AFTER
BEFORE

7:00am — ED opens four tabs and last week's spreadsheet. 9:40am — still reconciling two move-outs. Corporate asks for the rollup at 11.

AFTER

7:00am — the rollup is drafted with two variances flagged. 7:20am — ED has reviewed both, added a sentence of context, and sent it. The rest of the morning is on the floor.

PRICING

One price, published, no discovery theatre.

Your Claude subscription is separate and stays in your name. We don't resell it and we don't mark it up.

The retainer is not support-desk padding. State rules change, your templates change, and a workflow that isn't maintained quietly stops being trusted. Monthly we tune the four, fix drift, and re-train whoever is new.

Cancel the retainer whenever you like. The workflows are yours either way.

20-day setup
Four workflows, two training sessions, runbooks
$5,500 one-time
Ongoing retainer
Tuning, drift fixes, re-training new staff
$700 / month
Each additional workflow
Added any time, same three-step build
$950 one-time
Book a 20-min SOP audit

No deck. We look at one SOP and tell you whether it's worth automating.

The four things operators ask us first

"We already pay for Claude and nobody uses it."

That's the whole reason we exist. Adoption doesn't fail on capability, it fails on the blank page. Named workflows with an owner and a runbook get used; a general-purpose chat box doesn't.

"What about resident data and HIPAA?"

We start with the SOPs that don't touch PHI — census counts, licensing dates, rates, comp data. Where resident-level data is unavoidable, we scope it with your compliance lead against your BAA before anything is built.

"Our EDs are not technical."

They don't need to be. Drop the files in, press go, review the output. If a workflow needs explaining twice, we built it wrong and we rebuild it during the side-by-side week.

"What happens when that person leaves?"

The runbook and the recorded training are the onboarding. Turnover is the norm in this industry — a workflow that only one person understands is a workflow we failed to document.

Bring one SOP to the call. We'll tell you if it's worth automating.

Twenty minutes, no deck, no discovery phase. If the honest answer is "keep doing that by hand", we'll say so — and you'll have lost twenty minutes, not a quarter.

Book a 20-min SOP audit or email hello@3quip.me