Product · Sales Companion

Sales Companion Module

Module guide for Sales Companion product layers.

← Back to Workspace Open Markdown Source
Product structure

Sales Companion Module

Module guide for Sales Companion product layers.

Role
Module overview
Version
v2.4.8
Structure
Seven-layer architecture

Sales Companion

The Sales Companion module defines the product logic for Companion as used by sales people, Handelsvertreter and Sales Managers in the field.

It is intentionally not framed as a CRM module. Its role is to preserve field reality, relationship context, product-market learning and next actions with as little friction as possible.

Core Files

  • mobile-field-companion-principle-v0.1.md — core product idea: Companion as a mobile field intelligence layer.
  • mobile-capture-flow-v0.1.md — first concrete mobile product flow: raw visit input becomes structured operational intelligence.
  • route-intelligence-flow-v0.1.md — trip planning, partner discovery, route optimisation and nearby field recommendations.
  • competitive-differentiation-v0.1.md — product guardrails: how Companion differs from CRM, representative administration and adjacent tools such as HVH-flow.
  • company-insight-layer-v0.1.md — company-side market intelligence layer without Berichtheft, diary or boss-control logic.
  • market-map-layer-v0.1.md — regional market map and categorisation layer for prospects, customers, tips, no-fits, clusters and white spots.
  • companion-pipeline-project-model-v0.1.md — Contract-Interior project model and MVP priority: projects, specifiers, competing dealers and Kanban-style project intelligence.
  • product-principles.md — practical guardrails for the Sales Companion product experience.

Module Position

Sales Companion should feel like a working partner in the pocket:

  • voice-first capture,
  • photo-aware memory,
  • visit understanding,
  • follow-up extraction,
  • customer and location context,
  • product-fit learning,
  • report and email generation,
  • trip planning and route intelligence,
  • nearby discovery of potential partners and local tips,
  • clear differentiation from CRM and representative administration,
  • company-side insight that turns field work into market learning without reporting burden,
  • market mapping that turns contacts into regional ecosystem intelligence,
  • project intelligence that links field conversations into Contract-Interior project pipelines.

The user tells Companion what happened. Companion carries the structure.

Current Product Logic

The module now has seven connected layers:

  1. Mobile Field Companion defines the product identity: not a CRM form, but a mobile field intelligence partner.
  2. Route Intelligence Flow defines the beginning of the field day: fixed appointments, acquisition targets, local discovery, route building, nearby tips and live adaptation.
  3. Mobile Capture Flow defines the operational post-visit flow: speak, add photos, let Companion extract structure, confirm, then generate follow-ups and memory.
  4. Competitive Differentiation defines the product boundary: Companion should help sales people understand and develop their market, not merely administer their work.
  5. Company Insight Layer defines the second tool surface: the company behind the Sales Manager receives market signals, product learnings, regional intelligence and support needs without Berichtheft or diary logic.
  6. Market Map Layer defines how visited contacts, prospects, local tips and no-fits become a living regional ecosystem map.
  7. Companion Pipeline / Project Model defines the sharper MVP: fragmented field conversations become Contract-Interior projects with specifiers, clients, competing dealers, offer statuses and phases.

The next product step should prioritise Companion Pipeline / Project Model as the v2.5 MVP, using Mobile Field Companion, Route Intelligence Flow, Mobile Capture Flow, Competitive Differentiation, Company Insight Layer and Market Map Layer as supporting architecture.

Master Product Architecture v0.1

Source: master-product-architecture-v0.1.md HTML: master-product-architecture-v0.1.html

Defines the seven-layer product structure:

  1. Mobile Field Companion
  2. Route Intelligence
  3. Mobile Capture Flow
  4. Relationship Memory
  5. Companion Pipeline / Project Model
  6. Market Map Layer
  7. Company Insight Layer

Relationship Memory Layer v0.1

Source: relationship-memory-layer-v0.1.md HTML: relationship-memory-layer-v0.1.html

Defines the contextual memory layer between capture, projects, market map and company insights.