Working Context

Current Focus

• Use GitHub as the single source of truth for Companion Labs.
• Treat the current workspace as Companion Workspace v2.4.
• Continue from the Vienna Field Report #001 and the Companion Workspace visual launchpad.
• Ensure every important idea becomes Markdown before it becomes HTML.
• Keep Companion focused on the Interior ecosystem and not generic CRM.
• Treat the Mobile Field Companion principle as the clearest current product core for Sales Companion.
• Treat the Mobile Capture Flow as the first concrete operational UX flow for Sales Companion.
• Treat Route Intelligence Flow as the missing beginning of the field day: trip planning, partner discovery, fixed appointments, acquisition routes, nearby tips and live adaptation.
• Treat HVH-flow as an adjacent reference point that clarifies differentiation: Companion must be field intelligence, not representative administration.
• Treat the Company Insight Layer as the second key tool surface: company-side market intelligence without Berichtheft, diary or boss-control logic.
• Treat the Market Map Layer as the regional ecosystem surface: visited contacts, prospects, local tips and no-fits become categorised market intelligence on a map.
• Treat the Companion Pipeline / Project Model as the sharpened MVP priority: Contract-Interior projects connect Auftraggeber, Spezifizierer, multiple dealers, offer statuses and project phases.

Current Workflow

ChatGPT → Strategy, product thinking, documentation, knowledge extraction Claude → Visual design, HTML, CSS, frontend Codex → Engineering, repository operations, implementation GitHub → Single source of truth Netlify → Live preview

Core Product Position

Companion is not a CRM.

Companion is an operating system for the Interior ecosystem.

Companion is also 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. The first concrete expression of this is the Mobile Capture Flow: voice/photo input → structured visit summary → human confirmation → follow-up outputs → relationship memory. The preceding field-day layer is Route Intelligence Flow: fixed appointments and acquisition targets become an adaptive, realistic route with nearby discovery and tips. The strategic boundary is now explicit: Companion should not become HVH-like representative administration; it should remain a mobile field intelligence companion for the Interior ecosystem. The second major product surface is the Company Insight Layer: the company behind the Sales Manager receives aggregated market signals, product learnings, regional intelligence and support needs without turning the field user into a reporting machine. The Market Map Layer connects route planning, visit capture and company insight by showing how prospects, customers, local tips, no-fits, clusters and white spots form a regional market picture. The Companion Pipeline / Project Model now sharpens the product beyond pure capture: Companion should resolve fragmented field conversations into Contract-Interior projects with clients, specifiers, competing dealers, offer statuses and project phases.

Core sentence:

Wir verwalten keine Kunden. Wir verstehen Geschäftsbeziehungen.

Current Key Files

• 01-company/companion-book/the-companion-book-v0.1.md
• 01-company/companion-book/companion-principles.md
• 01-company/product-strategy/product-positioning-v0.1.md
• 01-company/business-model/business-model-v0.1.md
• 01-company/development-partners/pedestal-development-partner.md
• 01-company/decision-log/decision-log.md
• 02-product/concierge-mvp/concierge-mvp-v0.1.md
• 02-product/sales-companion/product-principles.md
• 02-product/sales-companion/mobile-field-companion-principle-v0.1.md
• 02-product/sales-companion/mobile-capture-flow-v0.1.md
• 02-product/sales-companion/route-intelligence-flow-v0.1.md
• 02-product/sales-companion/competitive-differentiation-v0.1.md
• 02-product/sales-companion/company-insight-layer-v0.1.md
• 02-product/sales-companion/market-map-layer-v0.1.md
• 02-product/sales-companion/companion-pipeline-project-model-v0.1.md
• 03-design/companion-feeling.md
• 03-design/design-principles.md
• 04-field-knowledge/vienna/reconstructions/vienna_master_reconstruction_v1.0.md
• 02-product/field-reports/001-vienna/field-report-vienna-001.html
• 05-knowledge/market-intelligence/hvh-flow-learning.md
• 05-knowledge/market-intelligence/hvh-differentiation-companion-v0.1.md
• 08-founder/digital-product-journey/AI_Journey_Patrik_Salewski_v0.2.md

Vienna Source Files

• 04-field-knowledge/vienna/reconstructions/vienna_master_reconstruction_tag1_v0.1.md
• 04-field-knowledge/vienna/reconstructions/vienna_master_reconstruction_tag2_v0.2.md
• 04-field-knowledge/vienna/reconstructions/vienna_master_reconstruction_v1.0.md
• 04-field-knowledge/vienna/raw/html/Wien_Sales_Report_Tag1_Bilder_HTML.html.zip
• 04-field-knowledge/vienna/raw/html/Field_Report_Vienna_Day_02_Editorial.html.zip
• 04-field-knowledge/vienna/raw/photos/tag-1/
• 04-field-knowledge/vienna/raw/photos/tag-2/
• 04-field-knowledge/vienna/raw/photo-contact-sheets/

Confirmed Vienna Additions

• Tag 1 includes: Wohnzeile 4, Mood Wien, dasmöbel, STEFFL Marketplace, AREA Wien, Scandinavian Design House, raumkomplett, HABARI Design Store.
• Tag 2 includes: Repertoire, MAK Design Shop, Casa del Design, AllesWirdGut Architektur, Nikisha, Designflagship, Lederleitner Tuchlauben, DreamAudio.
• Tag 2 includes the industry lunch with Jakob Erich from mobiles as Market Intelligence / Industry Conversation.
• Casa del Design includes the note that Andreas Schmid/Schmied gave the tip for AllesWirdGut Architektur.

Open Checks

• Final spelling: Andreas Schmid vs. Andreas Schmied.
• Final spelling / contact data for MAK Design Shop: Stella Jegosch vs. Stella Maria Jagsich; service@makdesignshop.at vs. designshop@MAK.at.
• Confirm Casa del Design contact spelling: Claudia Störck.
• Confirm missing direct emails before follow-up sends.

Next Milestones

1. Push Companion Workspace v2.4.8 to GitHub.
2. Deploy v2.4.7 to Cloudflare Pages preview.
3. Use 02-product/sales-companion/companion-pipeline-project-model-v0.1.md as the MVP priority and keep the existing field loop as supporting architecture.
4. Build v2.5 as a first Companion Pipeline prototype around project model + Kanban UI + reference resolution from free narration.
5. Define the first data objects for Project, Visit, Contact, Specifier, DealerOffer, SpecificationStatus, ProjectPhase, ProductFitSignal, Follow-up, File Pack and Sample Task.
6. Continue refining the Field Report Vienna #001 and its English counterpart only when needed.

v2.4.8 — Master Product Architecture / Visual Workspace Restructure

v2.4.8 introduces the master product hierarchy:

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

The Workspace start page was restructured from a flat module list into a clearer product architecture. New source-of-truth files:

• 02-product/sales-companion/master-product-architecture-v0.1.md
• 02-product/sales-companion/relationship-memory-layer-v0.1.md

This keeps the In-Field Companion as the daily user-facing core, while positioning the Companion Pipeline / Project Model as the deeper Interior/Contract differentiation.