S

Sofos Tools β€” AI Access

This tool uses AI features hosted on Sofos's secure backend. Running AI actions (Strategic Insights, candidate research, segment scoring, etc.) incurs cost per call and is part of your Sofos engagement.

By entering your access code, you acknowledge AI actions will be billed under your engagement terms. Please be deliberate when triggering AI features.

If you don't have a code, contact JO at jose@sofos.com.au.

Whole Product Model Design

Map the components needed to fulfil the chosen Customer / Market Segment's compelling reason to buy.

Customer / Market Segment not yet named — go to Setup
Restored your last session from this browser.

Import to start (optional)

Import either:

  • A Sofos Traction Sandbox export — pre-fills business context + Customer / Market Segment + research insights, ready for the AI brainstorm.
  • A previously-saved Whole Product Model Design JSON (this tool's own export) — resume your work.

The tool detects the framework type automatically and routes accordingly.

Your business context

The more specific you are here, the more targeted the AI brainstorm will be. When you import from Traction Sandbox these are pre-filled and locked — uncheck the toggle if you want to edit.

Designing for multiple segments?

Add another whole product model to compare side-by-side — e.g. different segments, present vs aspirational, or different value-prop angles. Capped at 3 models per tool instance.

Brainstorm components

AI flushes out all possible additional components needed by a pragmatist buyer in your Customer / Market Segment to fulfil their compelling reason to buy. You curate: keep / edit / drop / add manually. Re-running the AI MERGES new components into the existing list (deduped by title), so you can run multiple times to expand the candidate set, then prune. Owner (YOU vs PARTNER) and layer assignment happen in the next step.

Add a component manually

Founder-added components carry the same weight as AI-suggested ones. Edit any of them as you go.

Pick an existing cluster from the list or type a new one. Leave blank if the component is standalone.

Categorise & layer

For each component decide: owner (YOU vs PARTNER), partner type if partner (Bundled / Complementary / Compatible), layer (Expected / Augmented / Potential), "In Minimum Whole Product" (the smallest set required to deliver the compelling reason to buy), and risk if missing. AI auto-categorise uses upstream insights; you adjust inline.

Visualise

Three views of the same component map. Orbital map shows who owns each gap. Concentric layered shows how each component sits in customer perception (Generic / Expected / Augmented / Potential). Compelling Reason Build Plan shows the priority play -- what gets built / recruited to deliver the compelling reason.

View:

Summary — deliverable for handoff

This is the final view -- the handoff document for the client. Three things to do:

  1. Scroll the sections below to verify the design captures everything correctly. If anything looks off, jump back to the earlier step (Brainstorm / Categorise / Visualise) and edit -- the Summary always reflects the latest state.
  2. Click "Generate Gap Recap narrative" -- AI synthesises a 2–4 sentence Lawson-style retrospective connecting your core product, MWP additions, and partner needs back to the compelling reason. (Optional but recommended for client conversations.)
  3. Hand off via Export (JSON) or Print as PDF. By default, Export and Print act on the active segment only (the tab selected in the segment anchor) -- this matches how the next tool, Channel Partners, expects one segment per file. When two models are designed, "Export all" and "Print all" produce a combined deliverable covering both. To re-import a saved design later, use the Import button on the Setup step.