- Which community slipped last month?
- Was it census, labor or both?
- What is agency labor costing you?
- Will you see it before your capital partners do?
Querri for senior living. Querri it. Census, care, labor and the books, finally in one place.
Querri brings census, care, labor, sales and the books together for every community, so you, your regional VPs and every executive director decide from the same numbers. Connect the systems you already run and start in minutes, with no BI hire or data team first.
Querri only reads the data you connect and never changes a record. Your data, prompts and results never train a model. SOC 2 Type II and ISO 27001:2022 certified and HIPAA compliant. Querri signs a BAA.
By seat
Every seat, working from the same picture
Connect the dots between census, care, labor, satisfaction and profit in every community. Each seat asks its own questions, and every answer uses the same definitions, so the ED's P&L, the regional review and the owner report agree.
Finance
Every level of care billed, and each community's margin explained against budget.
- Did every community bill for the census and care it delivered?
- Where is each community's margin going: occupancy, labor or agency?
- Does the owner package match what operations reports?
Sales and marketing
See why census moved, and put next month's spend where move-outs are coming.
- Census dipped. Is it leads, tours, move-outs or price?
- Which communities have move-outs coming, and which sources fill them for the least?
- Are incentives filling rooms or giving away rate?
Resident experience
See which communities and residents need help first, before it shows up as a move-out.
- Which communities are slipping on resident experience, and what else changed there?
- Are new residents settling in during their first 90 days?
- Which residents are coming to fewer programs than usual?
Watch
Querri for senior living, in one minute
Which community moved and why, then the same picture from three seats, and what else the same data answers.
See which community moved, on your own numbers.
Bring your resident system, scheduling and the books to a 30-minute call. An agent sets up the connectors with you, with no BI build or data hire first.
How it works
Census, care, labor and the books, in one picture
Querri connects to the systems your communities already run and copies resident, care, CRM, labor and accounting data into one Library on a schedule you choose. Occupancy, hours per resident day and margin are defined once, and every person and AI agent uses those definitions. Files count too: Querri cleans them the same way every month.
The systems you already run
- Yardi
- PointClickCare
- MatrixCare
- Sage Intacct
NetSuite
QuickBooks
Salesforce- Workday
SQL Server
Microsoft Excel
Surveys, budgets and anything that only exports files come in too: upload Excel or CSV, or point Querri at a Google Drive folder.
Cleans, joins and checks every number before you see it
Answers where you work
- ChatAsk in plain language and get the table, the chart and how it was worked out.
- Dashboards and sitesDashboards and shareable sites for each community and region, refreshed on a schedule you set.
- PresentationsOwner reports and slides built from the same numbers, ready for the board or a capital partner.
- ExcelAnswers as a workbook when the next step happens in a spreadsheet.
- Your AI assistantYour governed numbers inside the assistant you already use, through MCP.
For your CIO and compliance lead
What your security review will ask
Resident, care and payroll records are the data you can least afford to have loose.
Certified
SOC 2 Type II and ISO 27001:2022 certified and HIPAA compliant. Querri signs a BAA.
Where your data lives
Every customer organization gets its own database and its own storage. AES-256 encryption at rest, TLS in transit, keys managed in AWS KMS.
Never used for training
Models run on Amazon Bedrock and Microsoft Azure in the United States. Your data, prompts and results never train any model, ours or anyone else's.
Read-only connectors
Querri reads from the systems you connect and never changes a record in them. Connected AI assistants are read-only until an admin turns on writing.
Access control
Role-based access with SSO and MFA. Row-level access rules apply before the AI sees anything, so an executive director gets answers from their own community and a regional VP from their region.
Connectors and files
125+ connectors, live database connections, and Excel or CSV uploads for the systems that only export files.
Comparison guide
How Querri compares for a senior living operator
Operators say no two systems talk, so the picture gets built by hand. Here is how the common approaches compare.
| Querri | Spreadsheets and an owner deck, by hand | Each system's own dashboards | A BI build: a consultant or a data hire | Each leader asking an AI assistant | |
|---|---|---|---|---|---|
| A new question from an owner or the board | Ask in plain language, across every system | An analyst rebuilds the deck | The reports each system ships with | Joins the builder's queue | Yes, for the data each person gives it |
| Census, care, labor and the books together | Joined on a schedule you set | Pasted together each month | Each stops at its own system's edge | Once each source is piped in and modeled | What each person uploads or wires up |
| Same occupancy in every community's numbers | Defined once; every answer, community and AI agent uses it | Depends on who built the sheet | Each system counts it its own way | Yes, while the model is maintained | Each person's own definition |
| Needs a warehouse or data team | No | No, but it takes someone's week | No | Yes, to build and keep the model | No for uploads; an internal build needs an owner |
Based on each approach's standard setup and the senior living research behind this page.
Pricing guide and ROI
What the numbers cost you now, and what you get back
Move the sliders to match your communities. The estimate adds four things: reports that re-run themselves, systems you stop tying together by hand, data stack you don't build, and census kept by seeing move-outs sooner. Tap the i beside each line to see its math. What Querri costs is on the pricing page.
- Reports that run themselves $73,440
5 people × 6 hours a week × 48 weeks × 60% automated × $85 an hour = $73,440. Each community's numbers, the regional review and the owner report re-run on new data on a schedule, so most of the rebuild time goes away (864 hours a year).
- Systems tied together for you $6,854
7 systems × 0.3 hours a week each × 48 weeks × 80% × $85 an hour = $6,854. The resident system, billing, scheduling, payroll, the CRM and the books are joined once on shared definitions, instead of matched by hand every month (81 hours a year).
- Data stack you don't build $134,500
A lean version of the stack operators build to join these systems: a warehouse contract from $50,000, a BI tool from $8,000 and half a data engineer at $125,000 base ($120,500), plus ingestion at $2,000 × 7 systems = $134,500 a year. Querri connects to each system and does each part itself, with no stack to build or run.
- Census kept by seeing move-outs sooner $200,000
0.2% of $100M revenue = $200,000. If monitors flag falling census, rising agency hours or residents pulling back in time to keep a fifth of a percent of revenue. At about $6,500 a month, that's roughly one resident staying a year for every $40M of revenue.
Estimates, not a quote. Each line's math is behind its i. The time lines assume 48 working weeks; the stack line uses the low end of each part's typical mid-market cost, and the census line is a conservative placeholder for your own figure.
Buying guide
Choosing analytics for a senior living operator
For CEOs and COOs choosing how to get one picture of every community.
One email with the guide. No sales sequence unless you ask for one.
Senior living buying guide
One picture of every community: what owners ask and where each number lives
- Where census, care, labor and margin each live, and why community numbers drift apart
- How the common options compare, and what a BI hire really costs in year one
- What your CIO will ask any vendor about resident and payroll data
Questions
Senior living analytics for census, care, labor and margin: common questions
How do senior living CEOs get one picture of census, care, labor and margin across every community?
Querri joins the resident system, billing, scheduling and payroll, the CRM and the books into one Library, and defines occupancy, revenue per occupied unit, hours per resident day and margin once. The owner report, the regional review and each executive director's numbers all read those definitions, so you can connect the dots between census, staffing, satisfaction and profit in each community. Click any figure to see the tables behind it. How Querri gets to an answer
Can Querri show which community moved, and whether it was census, labor or move-outs?
Yes. Monitors judge each community's census, agency hours, move-ins and move-outs against its own history and say which one moved, not just that the total did. Every night Querri leaves what it found in your Inbox, so the regional VP and the executive director see it before the call. Nightly insights and Monitors
How can a senior living operator get portfolio reporting without a BI hire or a data team?
Connect the systems you already run, such as Yardi or PointClickCare for residents and billing, Sage Intacct, NetSuite or QuickBooks for the books, and Workday, ADP or UKG for labor. An agent sets up each connection with you, and exports come in too. A blueprint installs a working portfolio view in minutes, with no warehouse, BI tool or analyst to hire first. How the connector agent works
Why would a senior living CEO use Querri instead of letting each executive director ask an AI assistant?
Because each person's assistant works out occupancy its own way, so an executive director and the regional VP bring different numbers to the same call. Querri keeps the company's definitions in one place, so every answer uses the same math, whoever asks, and every number shows its query. You can use both: Querri works inside your AI assistant through MCP, read-only until an admin turns on writing. Querri inside your AI assistant
What does Querri do differently if we already have reports in our resident system and our ledger?
Querri works alongside them, so keep both. Each reports well inside its own system. Querri joins census, care, labor, sales and the books on one set of definitions, so the numbers each team brings to the leadership meeting agree. When an owner asks something new, ask it in plain language instead of waiting for a report. See how asking works
Is Querri secure enough for senior living resident and payroll data?
Yes. Querri is SOC 2 Type II and ISO 27001:2022 certified and HIPAA compliant, and signs a BAA. Each organization has its own database and storage, encrypted with AES-256 at rest, and your data, prompts and results never train any model. Connectors are read-only, and an agent sets up each connection without ever seeing your passwords. Row-level access rules apply before the AI sees anything. Visit the Trust Center
Is Querri free to start for a senior living operator, and how should we weigh the cost?
Yes. Querri is free to start, and no credit card is required. To weigh the cost, compare it with what the other route needs before a first answer: a BI consultant or data hire, a warehouse and pipelines. Then set that against the hours your business office and regional teams spend each month on community reports and the owner package. Current plans are on the pricing page. See pricing
Which systems should a senior living operator connect first to get started with Querri?
Connect census and the books first, such as your resident system plus Sage Intacct, NetSuite or QuickBooks, then add scheduling and payroll. An agent sets up each connector with you and never sees your passwords. The Evergreen community operations blueprint opens with portfolio occupancy, hours per resident day and agency hours by community, and each team adds its own blueprint on the same data. Sign up free
One picture of every community, before the next owner call.
Connect your resident system, scheduling and the books, and ask which community moved in one conversation. Querri only reads your data; every record stays as it was.