# Sales Module Strategy and MVP Plan (Dual-Market Expansion)

## Purpose

Create a practical, phased plan to add residential sales workflows to Invensure so agencies can run both lettings and sales in one platform, reducing dependency on legacy software.

## Strategic Position

- Core thesis: if we only solve lettings, many agencies will still keep legacy systems for sales.
- Expansion objective: become the operating system for dual-market agencies, not a partial tool.
- Competitive objective: improve positioning against major listing ecosystem players by covering both high-volume rental and high-value sales journeys.

## Sequencing Decision (Locked)

Sales module is planned in this order:

1. SureLetting reliability testing and hardening first.
2. Sales module build and pilot second.
3. Auto Migrate Hub after sales foundation is proven.

This sequencing reduces platform risk and avoids migration automation before model stability.

## Why This Upgrade Matters

1. Revenue upside: sales transaction workflows typically carry higher value per case than lettings.
2. Retention upside: dual-market support makes switching away from Invensure harder.
3. Expansion upside: branch-level adoption is easier when one system supports both desks.
4. Product credibility: agencies see full-operation intent, not a niche vertical tool.

## Product Principles

1. Reuse existing architecture where possible.
2. Keep role-safe control split:
- `SOLO_LANDLORD` for direct-led cases.
- `AGENT_MANAGED` for agency-led cases.
3. Keep all status changes auditable.
4. Keep onboarding and buyer/seller messaging clear and humane.
5. Ship MVP with clear launch gates, then expand.

## MVP Scope (Sales V1)

### Must-Have

- Sales listing creation and publish workflow.
- Sales property pipeline board (lead to completion stages).
- Viewing scheduling and response tracking (reuse invite/viewing model).
- Offer log (multiple offers, accepted/rejected/counter states).
- Sales diary timeline (all major milestones and notes).
- Basic progression tracking (memorandum issued, legal instructed, exchange/completion checkpoints).

### Out of Scope for V1

- Full chain simulation automation.
- Automated portal feed distribution adapters.
- Advanced valuation AI.
- End-to-end migration automation.

## Existing Foundations We Can Reuse

1. Property records and evidence structure from inventory workflows.
2. Diary and activity logging model.
3. Invite/viewing lifecycle framework already implemented.
4. Role-aware flows for agent-managed and landlord-led cases.
5. Listing publication patterns from SureLetting.

## New Sales-Specific Capabilities Required

1. Sales pipeline states:
- `LEAD`
- `VALUATION_BOOKED`
- `INSTRUCTION_WON`
- `LISTED`
- `VIEWINGS_ACTIVE`
- `OFFER_RECEIVED`
- `OFFER_ACCEPTED`
- `MEMO_ISSUED`
- `LEGAL_PROGRESS`
- `EXCHANGED`
- `COMPLETED`
- `WITHDRAWN`

2. Offer model:
- offer amount
- buyer position and funding status
- conditions
- counter history
- acceptance decision record

3. Progression model:
- seller solicitor and buyer solicitor details
- milestone dates
- risks/blocks
- accountable owner

4. Sales compliance model:
- required doc checklist
- critical legal notes
- communication audit trail

## Proposed Data Model (V1)

### salesListings

- `id`
- `workflowPrime` (`AGENT_MANAGED | SOLO_LANDLORD`)
- `controllerId`
- `controllerEmail`
- `source` (`invensure | manual`)
- `inventoryId` (optional link)
- address and property attributes
- pricing and status fields
- `pipelineStage`
- `createdAt`, `updatedAt`

### salesOffers

- `id`
- `salesListingId`
- buyer profile snapshot
- `offerAmount`
- `status` (`RECEIVED | COUNTERED | ACCEPTED | REJECTED | WITHDRAWN`)
- terms and notes
- `decidedByRole`, `decidedByEmail`
- timestamps

### salesProgression

- `salesListingId`
- solicitor and broker contact fields
- milestone object
- blocker log
- next action and owner
- timestamps

### salesViewingInvites

- Reuse existing `viewingInvites` collection pattern with `listingType: 'SALE'`.

### salesAuditEvents

- `salesListingId`
- actor identity
- action type
- payload/details
- timestamp

## UX Surfaces (MVP)

1. Agent side:
- new `Sales` nav section
- sales pipeline board
- listing editor
- viewings panel
- offers panel
- progression panel

2. Solo landlord side:
- sales workspace tab in manage-property or dedicated sales page
- controlled workflow with simplified actions and diary continuity

3. Shared:
- timeline/diary feed with sales tags
- response and milestone actions with audit records

## Monetisation Model (Initial)

1. Add-on module pricing:
- Sales module as paid add-on to base subscription.

2. Tier strategy:
- include limited active sales listings in pro tier.
- charge incremental packs for higher volume.

3. Optional progression package:
- premium features for legal progression and reporting.

## Commercial Hypothesis

If sales is available, agencies using Invensure for lettings can consolidate systems, increasing contract value and reducing churn risk.

## Delivery Phases

### Phase A: Discovery and Spec Lock (1 week)

- Finalise sales V1 schema and stage model.
- Define role-control rules and permissions.
- Confirm commercial packaging.

### Phase B: Core Build (2-3 weeks)

- Sales listing create/edit/publish.
- Sales pipeline board.
- Viewing and offer logs.
- Sales diary integration.

### Phase C: Progression Layer (1-2 weeks)

- Memo issued and legal milestone tracking.
- Basic blocker and owner model.
- Reporting snapshots.

### Phase D: Pilot and Hardening (1-2 weeks)

- Pilot with dual-market agencies.
- Fix operational blockers.
- Validate data integrity and audit reliability.

## Launch Gates

1. Role-safe control works for both workflow primes.
2. Sales listing lifecycle is stable and auditable.
3. Offer history is immutable and decision-safe.
4. Viewing and diary continuity works without regressions.
5. SureLetting core remains stable after integration.

## Key Metrics

1. Dual-market adoption rate (agencies using both desks).
2. Sales listing creation-to-live conversion.
3. Offer response cycle time.
4. % of instructions managed fully inside Invensure.
5. Net reduction in customer dependency on legacy systems.

## Risks and Mitigations

1. Scope inflation:
- lock V1 and defer advanced chain automation.

2. Workflow complexity:
- start with a clear stage model and strict audit events.

3. Role confusion:
- enforce workflow prime on every sales record and action.

4. Delivery overlap with migration tooling:
- keep Auto Migrate Hub after sales hardening.

## Immediate Next Actions

1. Confirm this sequencing and scope as baseline.
2. Create `sales-v1-schema` technical spec draft.
3. Create wireframe list for agent and solo-landlord sales screens.
4. Select 2-3 pilot agencies for discovery interviews.

## Companion Architecture Note

Domain and brand execution details are tracked here:

- [Sales Domain and Brand Architecture](sales-domain-and-brand-architecture-2026-05-28.md)

Current selected sales domain:

- `suresalespro.co.uk`

## Decision

This is a high-value, strategically aligned upgrade and should be treated as a planned core expansion after SureLetting testing, before Auto Migrate Hub.