# People in Place - product and pilot web capture

Captured 10 August 2026 for the Martin Oettli pre-meeting dossier.

## Current public proposition

People in Place describes PiP as a senior-first retirement-village app and operating system connecting residents, families, staff and operators.

The site currently presents:

- Resident, family, staff and operator portals.
- A browser/PWA experience intended to avoid app-store and resident-email friction.
- First-name and four-digit PIN resident sign-in, large text and tap targets, read-aloud options, font controls, calm themes and a Display Hub.
- Resident events, meals, notices, welfare check-ins, photos and games.
- Family updates, notes, photos and weekly summaries.
- Staff rosters, handover, tasks, incidents and welfare checks.
- Operator maintenance, announcements, tasks, incidents, people, engagement, analytics, audit logs and property records.
- Automation that drafts material for staff approval.

## Stage and evidence boundary

- PiP's customer page says the product is in pilot phase with early village and sector conversations underway.
- It explicitly says there are no published customer logos, testimonials or case studies yet.
- The main site labels its operating metrics as placeholders that must be replaced with verified pilot data.
- Public claims about reducing calls, staff time, maintenance delays or increasing adoption are therefore objectives to test, not established results.
- The public security page says PiP uses AWS and does not claim other current security certifications. The four-digit PIN model, family access, role permissions, continuity, export and incident response need operator-specific assurance review.

## Pricing questions for Martin

- The pilot page advertises access from $6 per resident per month.
- The current build-versus-buy page shows Connect examples equivalent to about $8 per resident per month at 50 and 250 residents and a lower effective rate at 1,000 residents, based on marginal volume bands.
- Ask Martin whether the buyer expects per-resident, per-unit, per-site or portfolio pricing; what implementation and support are included; and what measurable outcome would justify renewal.
- The in-house build and run-cost comparisons are PiP planning estimates, not independent benchmarks.

## Product questions to pressure-test

1. Is PiP primarily an engagement layer, an operating workflow tool or an attempted system of record?
2. What is the narrowest paid wedge for a smaller multi-site operator?
3. Which portal should earn daily use first?
4. Which existing village systems must remain authoritative?
5. What assisted and non-digital channels are required for residents who do not use the app?
6. Which features are must-have, later or never?
7. What proof would make a chief executive renew after a pilot?

## Sources

- PiP home: https://peopleinplace.co.nz/
- Why PiP: https://peopleinplace.co.nz/why-pip
- Customers and pilot status: https://peopleinplace.co.nz/customers
- Security: https://peopleinplace.co.nz/security
- Operators: https://peopleinplace.co.nz/operators
- Display Hub: https://peopleinplace.co.nz/display-hub