# Invensure HMO Compliance Engine - Strategy, Commercial Model, and Delivery Plan

Updated: 2026-06-06
Owner: Product, Operations, Marketing, Compliance (proposed)
Status: Draft for leadership and marketing review

## 1) Executive Decision

### Recommendation

Build an **HMO Compliance Engine** as a **paid add-on plugin** first, then evolve into a deeper HMO workspace only after pilot evidence.

### Why this direction

- HMO regulation is complex, high-risk, and fragmented across tools.
- Current Invensure strengths (audit trail, evidence capture, workflows, role controls) are already the right foundation.
- A focused compliance product can command premium pricing because it reduces enforcement and renewal risk.
- Trying to build a full HMO property-management system in phase 1 would create unnecessary scope and delivery risk.

### Strategic positioning line

"Invensure helps HMO operators and agents run legally safer operations with council-aware compliance workflows, evidence trails, and ready-to-export inspection packs."

## 2) Market and Value Thesis

### Core problem to solve

HMO users often manage compliance in disconnected spreadsheets, calendar reminders, and generic PMS tools. That creates:

- missed licence conditions
- late renewals
- weak proof during inspections
- inconsistent fire and amenity records
- unclear ownership of duties across teams

### Why now

- HMO stock and demand are rising in pressured rental markets.
- Councils are increasingly active on enforcement and standards.
- Operators need certainty and proof, not just reminders.

### UK market size signal (2024-2025)

Using current official and research-based figures discussed in planning:

- England: approximately 362,000 HMOs
- Wales: 18,454 HMOs (estimated, 31 March 2024)
- Scotland: 15,274 licensed HMOs (31 March 2024)
- Northern Ireland: approximately 6,600 HMOs (up from 5,881 in 2018)

Working total: approximately 402,000 HMOs across the UK.

### Commercial implication from market size

Even modest penetration supports a meaningful add-on business:

- 1 percent penetration: approximately 4,020 HMO units/accounts addressed
- 3 percent penetration: approximately 12,060 HMO units/accounts addressed
- 5 percent penetration: approximately 20,100 HMO units/accounts addressed

This supports the plugin-first strategy, provided pricing, council-profile quality, and onboarding are disciplined.

### Value created

- lower probability of non-compliance events
- faster preparation for inspections and renewals
- clearer team accountability
- stronger trust signal for landlords, agents, and HMO management groups

## 3) Product Scope: What to Build (and Not Build)

### Phase 1 in-scope: HMO Compliance Engine

1. HMO classification and licensing requirement detector.
2. Licence condition tracker (national + council + property-specific).
3. Fire safety cadence and evidence logbook.
4. Amenity and room-size rules engine.
5. Certificate and inspection scheduler with evidence capture.
6. Occupancy and household-change alerts.
7. Compliance pack export (inspection-ready).
8. Legal Assistant integration for explainers and checklist guidance.

### Phase 1 out-of-scope

- full lettings CRM replacement
- full accounting stack replacement
- autonomous legal advice
- non-UK jurisdiction support

## 4) User and Role Model

Do not create separate systems for agent, landlord, and HMO manager. Use **one compliance core** with role-based views.

### Roles

- Landlord (self-managing): single or small portfolio, guided mode.
- Agent: multi-property, client reporting, delegation controls.
- HMO Operations Manager: advanced controls for high-density portfolios, inspections, incident workflows, and branch reporting.

### Dashboard model (confirmed)

Use a two-dashboard approach:

1. Agent Command Dashboard (existing): core day-to-day lettings operations.
2. HMO Operations Dashboard (new): compliance-heavy portfolio controls, licence risk, inspections, and enforcement readiness.

The HMO dashboard should be feature-gated behind paid HMO packages and available to eligible landlord-led and agent-led accounts.

### Capability flags

- `hmoComplianceCore`
- `hmoCouncilProfiles`
- `hmoOpsAdvanced`
- `hmoComplianceExportPack`
- `hmoLegalAssistant`

### Rule

Same data model, different dashboards and permissions.

## 5) Commercial Packaging and Pricing

### Recommended packaging

Treat HMO as a **paid plugin add-on** for both agent and landlord-led accounts.

## Package A - HMO Essentials (entry)

- classification
- licence renewal tracking
- certificate schedule
- basic reminders

Indicative price:

- GBP 59 to GBP 99 per account per month
- optional per-HMO property cap in this tier

## Package B - HMO Compliance Pro (default)

- all Essentials
- council profile loading
- fire logbook cadence
- amenity + room-size checks
- full evidence pack export
- Legal Assistant compliance Q and A

Indicative price:

- GBP 149 to GBP 299 per account per month
- overage or add-on for high portfolio volumes

## Package C - HMO Operations Plus (high-touch)

- all Pro features
- branch/team governance controls
- risk heatmap and enforcement prep workflows
- priority onboarding and quarterly compliance review

Indicative price:

- GBP 399 to GBP 999 per month (account scope based)

### Pricing principle

Price against **risk reduction and compliance readiness**, not just reminder volume.

## 6) Legal Assistant (RAG) Integration Model

Your existing Legal Assistant direction is a major advantage here.

### What RAG should do in HMO

- explain obligations in plain operational language
- answer "what is missing" against current record state
- provide source-linked rationale for each required task
- generate evidence checklists before renewal or inspection
- suggest next safest sequence for the user role

### What RAG must not do

- act as legal advice or counsel
- provide unsupported jurisdiction guidance
- override mandatory human review for high-risk outputs

### Source model

- national law corpus (Housing Act, Management Regs, etc.)
- council profile corpus (local licensing and amenity standards)
- Invensure policy layer for product behavior and wording

### Output guardrails

- source citations on all material compliance answers
- confidence/coverage signal
- "guidance only" disclaimer
- escalation route when source confidence is low

## 7) "Council-Profile Update Process Operational" - What This Means and How to Achieve It

This phrase means you have a **repeatable, auditable process** to keep council-specific rules current before launch.

Without this, the product risks drifting out of date.

### Operational definition

A council-profile process is operational when all are true:

1. You have a canonical council schema.
2. You have named owners for updates and approvals.
3. You have a regular update cadence.
4. You have QA checks and effective dates.
5. You can roll back to prior versions.
6. You can prove when a profile was last reviewed.

### Practical way to implement (recommended)

## Step 1 - Canonical schema

Create one structure for every council profile:

- council name and scope
- profile version
- effective date
- licensing triggers
- amenity standards
- fire and inspection expectations
- evidence/document requirements
- source links
- reviewer and approval fields

## Step 2 - Editorial workflow

- Draft: compliance analyst enters changes.
- Review: second reviewer verifies source and interpretation.
- Approve: accountable owner approves publish.
- Publish: profile version goes live with timestamp.

## Step 3 - Cadence

- monthly sweep for all active councils
- urgent hotfix process for critical updates
- quarterly deep audit of top-usage councils

## Step 4 - QA and tests

- schema validation checks
- regression tests on representative HMO scenarios
- profile diff review before publish

## Step 5 - Product controls

- show profile version/date in UI
- alert users when profile changes affect active HMOs
- maintain immutable change log

## Step 6 - Launch gate

Do not sell council-aware features until this process is live and staffed.

## 8) Data and Workflow Architecture (Invensure-Fit)

### Suggested object model additions

- `hmoProfile`
- `hmoLicence`
- `hmoConditions[]`
- `hmoFireLog[]`
- `hmoAmenityAssessment`
- `hmoOccupancySnapshot`
- `hmoComplianceEvents[]`
- `hmoCouncilProfileRef`

### Workflow stages

1. Classify property.
2. Detect licensing requirement.
3. Build baseline obligations matrix.
4. Assign owner and due dates.
5. Run scheduled checks and reminders.
6. Capture evidence and attestations.
7. Generate compliance pack.
8. Renew and repeat with versioned audit trail.

### Agent portfolio indexing at scale (important)

For large agencies (for example 500+ properties), the dashboard must not render the full list on each login.

Design standards:

1. Debounced search input (avoid full re-render on every keypress).
2. Page-window rendering (for example 50 rows per page).
3. Default sort by freshest operational signal (updated date, alert state).
4. Prioritized views first: Red Flags, Expiring Compliance, Unassigned Access, Active Incidents.
5. Progressive data loading for deep pages and export actions.
6. Lightweight row model in list view, with detailed payload loaded only on open/manage actions.

Outcome target:

- fast first render for portfolio views
- lower client memory load
- less user friction when triaging high-volume accounts

## 9) 90-Day MVP Plan

## Days 1-30: Foundation

- finalize scope and schema
- implement HMO classification + licensing detector
- implement core certificate and renewal schedule
- stand up first 5 council profiles
- define sales and marketing claims boundaries

Exit criteria:

- internal users can create an HMO compliance record end-to-end

## Days 31-60: Pilot-ready

- add fire logbook cadence
- add amenity and room-size checks
- enable evidence pack export v1
- integrate Legal Assistant with citations for HMO FAQs
- onboard 1 to 2 pilot agencies

Exit criteria:

- pilot users can complete weekly workflows without support blockers

## Days 61-90: Commercial readiness

- tighten UX and risk alerts
- finalize package limits and billing hooks
- add usage and margin telemetry
- create marketing pages and sales scripts
- publish launch scorecard dashboard

Exit criteria:

- contribution margin and pilot satisfaction meet go/no-go gates

## 10) Pilot KPIs and Go/No-Go Gates

### Product KPIs

- weekly active HMO compliance users
- task completion on required compliance steps
- evidence completeness rate
- citation coverage rate for Legal Assistant outputs

### Commercial KPIs

- HMO add-on attach rate
- average revenue per HMO account
- support hours per paid HMO account
- gross margin by package

### Go/No-Go gates

1. Pilot usefulness >= 4.0/5.
2. Evidence pack completeness >= 90% for target scenarios.
3. Council profile freshness SLA met for pilot councils.
4. Paid-tier modeled margin >= 65%.
5. Sales and marketing sign-off on compliant messaging.

## 11) Risks and Mitigations

1. Risk: local rule drift.
Mitigation: operational council-profile workflow, ownership, cadence, QA.

2. Risk: over-claiming legal certainty.
Mitigation: strict messaging, guardrails, citation policy, escalation rules.

3. Risk: product scope creep into full PMS.
Mitigation: phase boundaries and feature gate discipline.

4. Risk: support burden from complex portfolios.
Mitigation: tiered onboarding and premium support package.

5. Risk: weak adoption.
Mitigation: pilot around top pain points and inspection-prep outcomes.

## 12) Sales and Marketing Briefing Points

### Allowed claims

- "Council-aware HMO compliance workflows"
- "Evidence-first inspection and renewal readiness"
- "Source-linked operational guidance"

### Not allowed claims

- "Guaranteed legal compliance"
- "Replacement for legal counsel"
- "Automated legal advice"

### Simple value pitch

"Invensure helps HMO teams stay inspection-ready by turning fragmented obligations into one evidence-backed workflow with clear ownership and council-aware rules."

## 13) Immediate Next Steps

1. Confirm HMO as paid plugin strategy.
2. Approve package hypothesis (default: Compliance Pro).
3. Appoint council-profile owner and reviewer.
4. Select 5 councils for first profile set.
5. Start 90-day MVP execution with weekly decision review.
6. Prepare pilot invite and pricing test script.

---

## Appendix A - First Council Profile Template (Operational)

Minimum fields to launch profile system:

- Council name
- Profile version
- Effective date
- Licensing trigger rules
- Room and amenity standards
- Fire-specific local requirements
- Mandatory document list
- Renewal windows
- Source URLs and retrieval date
- Reviewer + approval timestamp

## Appendix B - Suggested Internal RACI

- Product Owner: scope, sequencing, and launch gate
- Compliance Analyst: profile drafting and legal-source mapping
- Compliance Reviewer: verification and sign-off
- Engineering: rules engine, workflows, telemetry, exports
- Marketing: claims, positioning, launch narrative
- Sales: packaging validation and objection handling