Master Product Architecture v0.1

Date: 2026-07-04 Status: Product architecture / source of truth Workspace area: 02-product/sales-companion/ Purpose: Bring the growing Sales Companion modules into one clear hierarchy after the Claude strategy feedback and the Companion Pipeline / Project Model update.

Core Decision

The In-Field Companion remains the user-facing core.

The Project Model becomes the deeper differentiation.

The Company Insight Layer becomes the strategic company value.

The In-Field experience is the entry point. The Project Model is the intelligence. Company Insight is the strategic output.

Master Flow

Route → Field → Capture → Relationship → Project → Map → Insight

A shorter strategic formula:

Field → Relationship → Project → Market → Company Insight

The Seven Product Layers

1. Mobile Field Companion

This is the entry point, daily use layer and trust anchor.

The Sales Manager uses Companion on a mobile device during real field work. They tell it what happened, add images, dictate impressions and use it as a practical companion rather than a reporting system.

Role: Human-facing field support.

Must feel like: A trusted work companion.

Must not feel like: A boss-control app, CRM duty or reporting burden.

2. Route Intelligence

This is how every city or regional trip begins.

Companion helps combine fixed appointments, existing customers, acquisition targets, local tips, Google Maps-style discovery and available time into a useful route.

It should adapt during the day when meetings take longer, prospects are closed, new recommendations appear or time windows change.

Role: Field-day planning and adaptive discovery.

3. Mobile Capture Flow

This is the post-visit or in-between-visit capture moment.

The Sales Manager speaks, types or uploads images. Companion extracts structured memory, follow-ups, uncertainty, product fit, sample tasks and possible project signals.

Role: Low-friction input layer.

Important: Capture itself is not the final differentiation. It is the input layer.

4. Relationship Memory

This is the layer that prevents real field knowledge from disappearing.

Companion remembers contacts, companies, roles, images, tone, product fit, objections, follow-up promises, sample needs and context.

This is not just a customer database. It is relationship memory with field context.

Role: Contextual memory for people, places and organisations.

5. Companion Pipeline / Project Model

This is the deeper differentiation for the Interior / Contract market.

Companion should resolve fragmented field conversations into projects: client, specifier, open or closed specification, competing dealers, offer status, award and realisation.

This is where Companion becomes more than visit capture.

Role: Project intelligence for Contract-Interior.

Core risk to test: Reference resolution from free narration across people and time.

6. Market Map Layer

This is where contacts, visits, no-fit learnings, local tips and product-fit signals become regional market intelligence.

The map should not track where the Sales Manager has been. It should show how the market is taking shape: clusters, white spots, product-fit hotspots, follow-up needs and local/regional development.

Role: Geographic and structural market understanding.

7. Company Insight Layer

This is the company-facing value layer.

The brand behind the Sales Manager receives aggregated market signals, product learnings, project patterns, regional insights and support needs.

Guardrail: Company insight must come from field support, not field burden.

Technical requirement: Aggregation thresholds must prevent individual-person drill-downs where they would turn Companion into boss-control logic.

Relationship Between The Layers

The layers are not separate products in the first version.

They are a value chain:

1. Route Intelligence prepares the day.
2. Mobile Field Companion supports the person in the field.
3. Mobile Capture Flow captures the field moment.
4. Relationship Memory stores the context.
5. Companion Pipeline detects projects when the market structure requires it.
6. Market Map reveals local and regional development.
7. Company Insight turns aggregated field knowledge into strategic learning.

Overlap With HVH

Companion should be honest about overlap.

There is overlap on the workflow layer:

• speech capture
• visit documentation
• tour / route planning
• customer context
• follow-up support

The differentiation is not the claim that Companion does none of these things.

The differentiation is that Companion specializes the workflow into a deeper Interior / Contract intelligence system.

Companion overlaps with HVH at the workflow layer, but differentiates at the market-intelligence and project-logic layer.

Differentiation Through Specialization

The concrete differentiators are:

• Interior / Contract specialization
• In-Field Companion experience
• Project / tender model
• specifier / dealer / client structure
• relationship memory
• market map and regional market structure
• product-fit and sample intelligence
• company insight without boss-control logic

HVH optimizes the representative’s workflow. Companion specializes that workflow into an intelligence system for Interior / Contract markets.

What This Changes In The Workspace

The previous start page was useful but too flat. Every module appeared at the same importance level.

The new structure needs to show hierarchy:

• product architecture first
• field operating layer second
• project and market intelligence third
• company insight fourth
• field evidence and governance after that

This makes the Workspace more understandable for external readers and future collaborators.

MVP Implication

The next MVP should not try to build all seven layers equally.

The recommended MVP focus is:

1. Route Intelligence as context.
2. Mobile Capture as input.
3. Relationship Memory as immediate user value.
4. Companion Pipeline as the risky differentiated test.
5. Minimal Company Insight from aggregated project signals.

The first technical risk to test remains:

Can Companion recognize that multiple free-form field conversations across different contacts may belong to the same project, without inventing facts?

Design Implication

The visual Workspace should stop behaving like a long list of files.

It should behave like a product architecture map.

The start page should therefore guide readers through:

1. What Companion is.
2. How the Sales Manager uses it.
3. Where the intelligence appears.
4. Why it is different from HVH / CRM.
5. What real field evidence supports the product.
6. Where the source-of-truth documents live.