Motion deep-dive
The TOOL motion: complementary overlay
When the buyer adds Foldspace to their product to fix adoption, activation, visibility, and retention. We enter alongside their stack, not instead of it. Sheet timing: the Q3 + Q4 focus.
What defines this motion
- The buyer's mental model: "a better tool." They have a budget line and a stack (adoption, analytics, surveys) that is not moving numbers. We are evaluated as the replacement for a disappointment, not as a strategic bet.
- Pain: adoption issues; lack of value from current market offerings (sheet). The old stack teaches users the product; users stopped tolerating being taught.
- Buyer maturity: less evolved on agentic concepts. Messaging is "use a better tool" plus education, light on architecture.
- Decision profile: team-level, faster cycle, lower perceived risk. Champion-led with an exec sign-off, not a board decision.
Sales mechanics: land & expand
- Land small and specific: one team, one use case, one activation flow. Research is unambiguous that single-use-case entry outperforms multi-product pitches at landing (Dock, Endgame).
- Expansion fuel is usage + champions: the growth/CX win generates the intent data that pulls in VP Product, which opens the build conversation later.
- Pricing/entry: pilot-friendly, low-friction start; value must be provable inside a quarter (their evaluation window).
Buyer behavior facts that shape tool messaging
61–70% of the journey happens before they talk to us, and ~8 in 10 buyers have requirements set before first contact (
Omnibound). Tool buyers arrive with a Pendo-shaped requirements doc: our content has to reframe the requirement (outcomes, not walkthrough features) before the call.
~4 of 5 shortlist spots are filled on day one, and the day-one favorite wins ~80% of the time (
Corporate Visions). If we are not already in the growth buyer's head via content and community, the deal was lost before it started.
64% trust peer recommendations from private channels most; 73% of research is anonymous, in Slack groups, DMs, podcasts (
Sopro,
Higher Pitch). Growth communities and the Wes Bush / Ramli John partnerships are distribution, not decoration.
The competitive frame (negative space)
Every vendor in the tool buyer's head (Pendo, Userpilot, Appcues, Chameleon) now leads with "AI-powered," a "system of agents," a "Copilot," and "personalization." None leads with a customer outcome stat; none attacks PLG's premise; all extend it. Our tool-motion negative space: lead with outcome stats and the reframe: "PLG removed the salesperson and dumped the complexity on the user. The tools taught. The agent does."
Message architecture for this motion
| Layer | Tool-motion version |
| Promise | Users reach outcomes without learning your product. Numbers move in a quarter. |
| Pillars | Eliminate the Click Tax (activation) · Engineer champions (retention) · Read intent, iterate in hours (experiments) |
| Proof | MixMax 57→90 day-1 · Qonto 8→16% activation · AskCody +344% · TTV under 60s (anonymize externally) |
| Classification line | "Drops in alongside your stack. Zero coding (Remote plugin). No release-cycle dependency." State it early: buyers burn energy classifying overlay-vs-replace, and ambiguity kills (GTM Playbook). |
| CTA ladder | clicktax.ai diagnostic → demo on their product → single-flow pilot |
Features to emphasize in tool conversations
- Remote plugin (zero coding, live in days) is the motion's defining feature.
- Generative onboarding, starters, agentic-surface experiments: the visible wins.
- Intent signals as the upgrade over their current analytics; Conversational Analytics stays early access in framing.
- Keep A2A/MCP/SDK/Trust Lab depth out of it unless engineering enters the room (then see the engineering page).
Tool-motion vocabulary
Say- "Click tax" · "time to outcome" · "the agent does the job"
- "Works with your product as it is"
- Outcome numbers, always ahead of adjectives
Never- "AI-powered," "AI Copilot," "personalization at scale," "next-best action," "predictive guidance" (category wallpaper)
- "Tours/tooltips" as our value language; "PLG is dead"
- Build-motion vocabulary (layers, protocols) that re-classifies us as a platform decision and slows the deal