Rolling Knurl out at a property management firm
Property managers run 5–50 buildings with thin centralised operations and rotating field teams. The classic CMMS pain point — per-seat pricing makes adding a building economically painful — disappears with Knurl: unlimited users per facility, flat tier pricing.
Day 1 — Account & first property
- Owner signs up: typically the operations director.
- Plan choice: Portfolio if you have 2–5 buildings, Enterprise if 6+ or if you need bulk import + central vendors.
- Set up your first property as a facility. Pick a smaller one to learn the loop on.
Day 2–3 — First building
- Assets: shared infrastructure — HVAC, lifts, plumbing risers, electrical panels, fire safety, generator, common-area lighting circuits.
- Locations: floor / wing / common area. The location tree is helpful for buildings over 5 floors.
- QR stickers: place on service-side surfaces (panel doors, mech rooms, sub-station).
Week 1 — Roll out to remaining properties
Once one building is live, the rest follow a template. On Portfolio plan and above:
- Bulk import assets via CSV. Copy the column layout from the first property.
- Cross-site asset templates — define your "standard generator", "standard fire panel", clone into each building.
- Central vendors — your HVAC contractor, your lift contractor. Promoted to org-scope so they're available across every building.
- Per-site permissions — local building engineers see only their building; central operations sees the rollup.
Week 2 — Standard PM library
Define the standard PM cycles once:
- HVAC quarterly
- Fire panel monthly
- Lifts monthly statutory
- Generator weekly + monthly
- etc.
Use PM templates (Portfolio+) to push the standard library into each building. Per-building tweaks happen on the building side without touching the template.
Month 1 — The portfolio view
- Cross-site analytics — MTTR by building, backlog age by building, throughput by technician. (Operations+ on a per-facility view; Portfolio+ for the rollup.)
- Benchmarking — see which buildings outperform on response time; ask why.
- Budgets — per-facility maintenance budget vs actual spend.
- Tenant request portal — public QR / public deep-link gives tenants a frictionless way to report without an account.
Month 2+ — Scale out
- API + webhooks if you have a property-management system you want to sync with (rent rolls, lease data, billing).
- ERP integration for finance sync (work-order costs flow to the GL).
- Custom roles (Enterprise) — fine-tune permissions for unusual structures (e.g. "leasing manager" who can see common-area work but not individual unit maintenance).
What property managers ask us most
How does pricing scale with our portfolio?
Portfolio covers up to 5 facilities; Enterprise is unlimited. Most property managers in the 6–20 building range land on Enterprise. There's no per-seat fee at any tier — add as many building engineers, contractors, and tenant operations staff as you need. Plans & pricing →
Can each building's on-site team see only their building?
Yes. Per-site permissions (Portfolio+) scope each user's access to specific facilities. The X-Knurl-Facility header switches active facility in the UI; cross-facility access without a membership row returns 404.
Can tenants report without an account?
Yes. Public QR reporting: place a sticker in the building lobby or service corridor; tenants scan, fill name + brief description; the report lands in triage. No tenant account required.
Multiple companies in our holding structure?
Each operating company gets its own organisation. Within an org, multiple facilities, shared vendors, shared templates, shared user pool. Cross-org access is hard-blocked.
Custom branding / white-label for tenant-facing pages?
Not in the hosted version. The on-prem option (Enterprise) gives you full UI control. Contact [email protected] for a white-label conversation.