# Relationship Memory Layer v0.1

**Date:** 2026-07-04  
**Status:** Product layer / source of truth  
**Workspace area:** `02-product/sales-companion/`  
**Related files:** `mobile-capture-flow-v0.1.md`, `market-map-layer-v0.1.md`, `companion-pipeline-project-model-v0.1.md`, `company-insight-layer-v0.1.md`

## Definition

Relationship Memory is the layer that turns scattered field moments into durable context.

It is not a CRM account record.

It is the remembered working context around a person, company, place, product fit, conversation, image and next step.

> Relationship Memory remembers why a contact matters, not only that a contact exists.

## Why It Matters

In Interior and Contract sales, valuable knowledge often lives in fragments:

- a sentence from a planner
- a photo from a showroom
- a product objection
- a sample request
- a local recommendation
- a no-fit learning
- a gut feeling about brand fit
- a hint about an upcoming project

Without Companion, this knowledge often disappears into WhatsApp, notes, memory, email drafts, camera rolls or Excel comments.

Relationship Memory makes it reusable.

## What It Stores

Each relationship can contain:

- company / organisation
- people and roles
- category and market role
- visit history
- images and atmosphere
- product fit
- objections and needs
- follow-up promises
- file packs sent
- samples requested or sent
- project signals
- confidence and uncertainty
- no-fit reasons
- source of information
- next action

## What It Must Avoid

Relationship Memory must not become:

- a generic CRM profile
- a surveillance record
- a diary
- a report book
- a dumping ground for every trivial note

It should store what changes future action, understanding or market intelligence.

## Relationship To Mobile Capture

Mobile Capture is the input moment.

Relationship Memory is what remains after the input has been structured, confirmed and connected.

Example:

A Sales Manager says:

> I was at studio phyne in Vienna. Pedestal was presented for their planning work. Short training done. Follow-up: Masterdata, assets, prices and colour samples.

Relationship Memory should preserve:

- studio phyne as planning-related lead
- Pedestal fit
- training happened
- follow-up package needed
- colour samples needed
- source: confirmed field visit
- open uncertainty: contact details if not confirmed

## Relationship To Companion Pipeline

A relationship can create or strengthen a project signal.

Not every relationship is a project.

But several relationship memories across different organisations may point to the same Contract-Interior project.

This is where Relationship Memory feeds the Companion Pipeline.

## Relationship To Market Map

Relationship Memory also feeds regional intelligence.

A relationship can become a map point with category, role, product fit, status and confidence.

The Market Map then reveals clusters, white spots and regional market development.

## Relationship To Company Insight

The company should not receive private diary-like notes.

The company should receive aggregated and useful patterns, such as:

- many planners request samples
- a region has strong project signals
- a product creates repeated objections
- several warm prospects need the same assets
- a category is emerging in a specific city

## Core Guardrail

> Relationship Memory serves the field person first. Company insight is derived from structured patterns, not extracted from personal surveillance.