HVH Differentiation — Companion v0.1

Status: v0.1 product positioning note Date: 2026-07-03 Area: Market Intelligence / Competitive Learning Source context: Vienna reconstruction, Jakob Erich conversation, workspace discussion about HVH-flow as adjacent solution.

Important Uncertainty Note

This document is not a factual audit of HVH-flow features, pricing, customers or current roadmap.

It captures the current Companion Labs positioning logic based on what is known inside the workspace: HVH-flow appears as an adjacent solution around Handelsvertreter / sales-agent workflows. Any precise claims about HVH-flow must be verified separately before they are used externally.

Core Differentiation

HVH helps representatives manage their work. Companion helps interior sales people understand and develop their market.

Sharper version:

HVH is workflow software for representatives. Companion is a field intelligence companion for the interior ecosystem.

Why HVH Does Not Invalidate Companion

HVH-flow is useful as a boundary object. It shows that the problem space exists, but it also helps define what Companion should not become.

Companion should not try to win by becoming another representative administration tool.

Companion should win by understanding the Interior ecosystem better than generic sales software can.

Differentiation Axes

1. Vertical Ecosystem Instead of Generic Representative Logic

Companion starts from the specific world of Interior, Design, Furniture, Lighting, Lifestyle, Architecture, Retail, Planning Studios and Hospitality.

A generic sales tool may know that a customer was visited.

Companion should understand whether the place is a concept store, planning studio, architecture office, hospitality lead, public-space partner, hidden champion, cultural multiplier or no-fit.

2. Field Companion Instead of Administration

Companion should feel like a working partner in the pocket.

The user speaks naturally, adds photos and rough impressions, and Companion carries the structure.

The experience should not feel like filling out required CRM fields after a long day.

3. Field Intelligence Instead of Visit Report

A traditional visit report might say:

Customer visited. Interest present. Follow-up required.

Companion should capture:

studio phyne is a relevant planning lead in Vienna. Pedestal was introduced as a planning tool. A short product training happened. Next step: send Masterdata, product assets, pricing and colour samples. This belongs to Vienna Field Intelligence.

4. Ecosystem Graph Instead of Customer Database

Companion should connect people, places, brands, products, routes, recommendations, stores, studios, architects, follow-ups, product feedback and market signals.

The question is not only: Who is the customer?

The stronger question is: Who influences whom, which places matter, where do projects emerge, and which products fit into which context?

5. Route Discovery Instead of Static Account Lists

Companion begins before the visit.

A sales person should be able to say:

I am in Vienna tomorrow. I have two fixed appointments and four open hours. Find relevant interior stores, planning studios, Scandinavian design dealers and local tips, then build a realistic route.

That is not CRM. That is field expedition planning.

6. Product-Market Learning Instead of Pipeline Only

Companion should learn what happens in the market:

• Which products create interest?
• Which colours or finishes are understood?
• Which arguments work?
• Which objections repeat?
• Which assets are missing?
• Which new use cases emerge?

This turns sales work into product intelligence.

7. Brand Intelligence Instead of Boss-Control Dashboard

Companion must avoid the feeling of surveillance.

It should not primarily ask: Where were you? How many visits? How much pipeline?

It should ask: What did you learn? What should not be lost? Which relationship matters? What does the brand need to understand now?

8. Taste, Context and Atmosphere

Interior sales work is not only hard data.

Companion must preserve style, atmosphere, curation, visual quality, neighbourhood, audience, positioning and taste.

A photo of a store should not just become an attachment. It should become context.

Anti-HVH Rules

These are internal guardrails. They are not external claims about HVH.

• Companion is not representative administration.
• Companion is not a CRM skin.
• Companion is not a form-filling system.
• Companion is not a route list with notes.
• Companion is not a boss-control dashboard.
• Companion is not generic sales software.

Positive Companion Rules

• Companion is mobile-first field intelligence.
• Companion understands the Interior ecosystem.
• Companion turns conversations, images and routes into memory.
• Companion creates follow-ups, reports and product learnings.
• Companion helps sales people think, not just document.
• Companion makes field work reusable without making it bureaucratic.

Positioning Sentence

Companion is the mobile field intelligence layer for the interior ecosystem.

Expanded:

A sales person tells Companion what happened, gives it images and context, and Companion turns that field reality into memory, follow-ups, reports, route learning, relationship context and product-market intelligence.

Product Implication

The Sales Companion product should be built around the full field loop:

Plan the route → visit the field → capture each stop → generate follow-ups → update memory → improve the next route.

HVH-flow helped clarify the boundary. Companion must stay on the field-intelligence side of that boundary.

External Communication Rule

When speaking externally, avoid saying that HVH is limited or inferior unless this has been factually verified.

Use neutral language:

There are tools for managing representative workflows. Companion is different: it focuses on mobile field intelligence and relationship understanding for the Interior ecosystem.