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.
Map the components needed to fulfil the chosen Customer / Market Segment's compelling reason to buy.
Import either:
The tool detects the framework type automatically and routes accordingly.
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.
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.
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.
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.
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.
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.
This is the final view -- the handoff document for the client. Three things to do:
Configure how the tool calls Claude. Without this, the tool falls back to copy/paste prompts.
The shared Sofos Intelligence Layer Worker. Same endpoint as Traction Sandbox — this tool uses different call_type values.