Mobile Field Companion Principle v0.1

Date: 2026-07-03
Status: Core product principle / source of truth
Workspace area: 02-product/sales-companion/
Related files: product-principles.md, WORKING_CONTEXT.md, 01-company/decision-log/decision-log.md

Core Idea

Companion Labs is not just a knowledge base and not just a CRM.

The central product idea is a mobile companion for sales people, Handelsvertreter and employed Sales Managers in the interior, design and lifestyle ecosystem.

The user in the field should be able to use Companion on a mobile device like a trusted working partner:

• tell it what happened during a visit,
• upload photos from stores, showrooms, offices, hotels or customer meetings,
• dictate impressions, product reactions, objections and opportunities,
• capture names, places, follow-ups and context immediately,
• and trust that Companion will process, understand, structure and remember the information.

Product Sentence

Companion is the mobile field intelligence layer for the interior ecosystem: a sales person tells it what happened, gives it images and context, and Companion turns that into memory, structure, follow-ups, reports and market understanding.

What Companion Does With Field Input

Companion turns unstructured field material into structured operational intelligence:

1. Relationship context
   Who was met, what was discussed, what matters to that person, and what should happen next.

2. Lead and follow-up logic
   What needs to be sent, prepared, sampled, scheduled or clarified.

3. Product-market learning
   Which products resonate in which environments, which use cases emerge, and where product positioning needs to adapt.

4. Visual field memory
   Photos are not just stored as images. They become context: store type, atmosphere, fit, potential, brand environment, product relevance.

5. Reports and reusable outputs
   Field notes become emails, visit summaries, city reports, sales briefings, customer profiles, presentation input and strategic learnings.

6. Ecosystem intelligence
   Companion connects people, places, brands, products and markets into one growing operating system for the interior ecosystem.

Difference From A CRM

A CRM mainly asks:

• Who is the customer?
• What is the deal stage?
• When is the next follow-up?
• What is the sales value?

Companion asks additionally:

• What did we learn in the field?
• What did the customer actually care about?
• Which product use case became visible?
• Which relationships belong together?
• Which market pattern is emerging?
• What should the sales person do next?
• What story, report or strategic insight can be created from this visit?

Design Implication

The interface should not feel like database entry.

It should feel like talking to a highly attentive field partner who understands interior, design, sales context, products, relationships and follow-up discipline.

The mobile experience should therefore prioritise:

• fast voice capture,
• image upload and image context,
• visit summaries,
• automatic follow-up extraction,
• customer and location memory,
• product-fit suggestions,
• city and field-report generation,
• and later dashboard views for patterns, relationships and open actions.

Example: Studio Phyne Vienna

A classic Companion input could be:

End of Day 2, Vienna. Visited Studio Phyne. Presented Pedestal for their planning work and did a short product training. Follow-up: send full email with all key information, Masterdata, product files and pricing. Also send colour samples.

Companion should turn this into:

• a lead entry,
• a relationship note,
• a follow-up task,
• an email draft,
• a product relevance marker,
• a field-report update,
• and a reusable market-learning signal.

Operating Principle

The sales person should not have to think in database fields while standing on the street after a meeting.

They should be able to speak naturally, add photos and move on.

Companion should carry the structure.