ToolsOutreach PlaysGTM OperationsPersonasProduct MarketingPositioning & ICPsProduct narrative (core)Website
Messaging Hierarchy — as received from Marketing (Jul 12, 2026)
Status: marketing draft under review — NOT approved messaging. This is a faithful ingest of the six tabs of the "Foldspace — Messaging Hierarchy" sheet (downloaded Jul 12, 2026; Google Sheets → HTML export). Wording is preserved as written, including shorthand and typos. Do not pull copy from this page into assets. The refinement pass lives in review-refinements.md.
Tab 1 — Brand Messaging (current)
Brand Vision
Changing the way users engage with software.
Brand Mission
The agentic interface that transforms user intent into outcomes.
Positioning Statement (replaced by two motion definitions — no actual statement yet)
- TOOLING — "When the buyer is considering us as a tool added to the product to drive onboarding, adoption, increase usage visibility, and retention. Walk through guides, analytics, surveys, etc — all are designed to help drive a generic purpose of increase time to value, getting user inputs, reducing churns."
- BUILDING — "Being apart of the coding and release cycles and delivering features inside their product. They are activeling or see the need to rebuild and/or build their UI/UX. Company objective to be AI-Native/First — similar to being Mobile first."
- KEY differences — TOOL vs BUILD:
- Build (Rip + Replace) — Agentic Interface · more evolved · engineers are building with us · pain = urgency (nothing being shipped) · messaging is around coding stuff and more education · strategic decision (Q4 test to CSuite)
- Tooling (Complimentary) — Overlay to improve · less evolved · pain = adoption issues, lack of value with current market offerings · messaging is using better tools, more educated (Q3 + Q4 focus)
Personas: Growth Owners (Growth PMs, PLG Owners) · Product Management (CPO / VP of Product) · Engineering Owners (CTO / Engineering)
Key Messages (Brand) (four columns against three personas — column mapping unconfirmed)
| Growth | Product | Product (build?) | Engineering |
|---|---|---|---|
| Click Tax | Zero Coding | Agentic Interface (FE not IP) | Agentic Interface (FE not IP) |
| PLG → ALG | AI Native / First | AI Native / First | AI Native / First |
| Engineered Champions | Time to Value → Time to Outcome | Time to Ship | Build with Foldspace (A2A, MCP, SDK, Deployment, Testing) |
Value Proposition (same four columns)
| Growth | Product | Product (build?) | Engineering |
|---|---|---|---|
| Conversion Rates · Activation Rates · Engagement Rates · Churn · Avg. Revenue per User (ARPU) · Experiments | Informed Roadmap (Based on data not opinions) · Adoption (Emotional element) · Closed Loop Feedback (Full Circle back to Product) · Time to Value (Removes Complexity) | Ship Agentic AI · Ship AI-Native / AI-First · Agility · Speed · Experiments | Agility · Shiping Fast · Reduce Risk · Shipping with Quality · Associated with AI Building · Cost Control · Model Control · Testing, Inspecting, Iterating · AI Score = Latency, Cost, Quality |
Value Description
Going from guessing at clicks to knowing exactly what users want (informed roadmap decisions) · Going from forcing users to drive adoption (w/ dropoff) to Agent is driving adoption = every user is becoming a champion (engineering champions) · Going from sending a survey to sentiment, outcome, and usage (completes feedback loop) · Reporting on your roadmap vs actioning and building your roadmap with you (AI native)
(remaining cells: "XYZ" placeholders — unfinished)
Proof Points (same four columns)
| Growth | Product | Product (build?) | Engineering |
|---|---|---|---|
| Increase Conversion Rates · Decrease Acquisition Cost · Increase Time to Value · Increase ARR | Time to Launch AI Native | Time to Launch AI Native | Improve AI Score · Decrease Token Costs |
Tab 2 — Brand Messaging OLD (prior draft, kept for diff)
- Brand Vision: Changing the way users engage with software / products.
- Brand Mission: The agentic interface that turns user intent into conversational outcomes.
- Positioning Statement: "For SaaS companies whose users churn before seeing value, Foldspace turns any product into an agentic experience without rebuilding the UI." (+ same TOOL vs BUILD notes as Tab 1)
- Value Proposition: "Foldspace gives users a session-based AI that guides them to outcomes — eliminating click tax, reducing onboarding friction, and surfacing features that drive retention."
- Value Description: "Unlike chatbots or tooltips, Foldspace's agentic interface learns user intent in real time, guides them step-by-step, and measures session outcomes — all without changing your core product."
- Key Messages: PLG → ALG: Software that learns the user, not the other way around · AI Native · Click Tax is killing activation. We end it. · 374% increase in AI-driven activations — without a redesign.
- Proof Points: 374% increase in daily AI-driven activations · First session value: users reach outcomes in their first conversation · No UX overhaul required — ships on top of existing product · Reduce costs (Zendesk, Tokens, Spend to Achieve same outcome) · CAC decreases · CVR and Closed Won Rates increase · GRR/NRR.
Tab 3 — Persona Buckets
| Product / Engineering | Growth / PLG | CX / Customer Success | |
|---|---|---|---|
| Sub-personas | CPO · CTO · PM · AI Engineer · Developer/CIO | Growth PM | CX Leader |
| Lead with | AI Native · AI interface Layer | "First Growth" | Positive outcomes |
| Core job | Ship features that drive recurring revenue · Hit time-to-value targets each quarter · Differentiate roadmap vs. fast-moving competitors · Reduce Eng. dependency on UX fixes | Maximize trial-to-paid conversion · Reduce activation drop-off · Improve expansion revenue · Shorten time to first aha moment | Improve GRR/NRR · Scale onboarding without scaling headcount · Deflect repetitive support volume to self-serve · Increase product adoption |
| Pain points | Users churn before seeing value · Complex onboarding needing constant redesign · AI roadmap under pressure but ROI is unclear · Power features go undiscovered | Activation stuck despite repeated UX changes · Users sign up but never complete setup · Can't personalize onboarding flows at scale · Growth experiments blocked by engineering queue | Support team buried in 'how do I?' tickets · New users require heavy hand-holding · CS stretched thin · Hard to prove ROI of support investment |
| What they fear | Board pressure — building Agentic UX & getting it wrong · Another onboarding overhaul that doesn't move the needle · Competitors shipping agentic experiences first · Long implementation timelines | Missing activation targets · Attribution blind spots · Building in-product guidance internally (6+ months) · Compounding friction in freemium funnels | Churn blamed on CX that's actually a product problem · Silent churn before CS engages · Support costs scaling faster than ARR · Losing human touch in a race to automate |
| How they buy | Technical demo + sandbox trial · Needs engineering sign-off · Looks for SDK simplicity and clear integration docs · Peer referrals carry heavy weight | Data-driven — needs clear before/after metrics · Wants fast vendor time-to-value · Likely discovers Foldspace first · Strong influencer; rarely final budget approver | Advocates internally when it reduces ticket volume · Responds to peer testimonials · Wants product in real support scenarios · Brings Product/VP in to close |
Tab 4 — Sub-Persona Deep Dive (Product / Engineering bucket)
CPO — lead: "AI Native"
- Core job: Ship features that drive recurring revenue · hit time-to-value targets · differentiate roadmap · reduce eng dependency on UX fixes
- Pains: Users churn before seeing value · complex onboarding needing constant redesign · AI roadmap under pressure but ROI unclear · power features undiscovered
- Fears: Board pressure — building agentic UX & getting it wrong · another onboarding overhaul that doesn't move the needle · competitors shipping agentic first · long implementation timelines
- How they buy: Technical demo + sandbox trial · eng sign-off · SDK simplicity + docs · peer referrals
CTO — lead: "AI Native Interface Layer"
- Core job: Own technical architecture + platform roadmap · protect uptime/security/scalability · reduce eng spend on UI/UX rebuilds · integrate without technical debt
- Pains: Eng backlog dominated by UI rework instead of core infrastructure · every onboarding fix requires a front-end redesign cycle · security/compliance review slows tool adoption · legacy interface layer can't keep pace with product complexity
- Fears: Security/compliance gap from a new integration · vendor lock-in limiting architectural flexibility · eng time sunk into a rebuild that doesn't move retention · blamed for slow feature velocity caused by UI debt
- How they buy: Deep technical due diligence + architecture review · SOC 2 / security docs before any pilot · evaluates SDK quality, API stability, integration effort directly · final sign-off gate for CPO-initiated purchases
PM — lead: "AI Native"
- Core job: Prioritize roadmap items that move activation/retention · run adoption experiments · translate research into requirements · own onboarding + in-product experience
- Pains: Features ship but adoption stays flat · onboarding flows require constant manual iteration · can't personalize without eng support · limited visibility into where users get stuck
- Fears: Missing adoption/activation OKRs · blamed for churn tied to product complexity · losing a roadmap fight over UI · shipping a redesign that doesn't change behavior
- How they buy: Pilot on a single flow first · needs before/after analytics to justify expansion · strong advocate, rarely holds budget · escalates business case to CPO/VP
AI Engineer — lead: "AI Native Interface Layer"
- Core job: Build/maintain AI-agent logic · ensure model output is accurate, fast, and production-ready · integrate LLM behavior into UI + data flows · own reliability and performance of AI experiences
- Pains: Building agentic UX in-house pulls time from core model work · custom agent frameworks brittle and expensive to maintain · hard to measure real-world impact of AI features on retention · model-output-to-UI handoffs require constant patching
- Fears: Shipping an AI feature that hallucinates or feels bolted on · spending months building infrastructure a vendor already sells · accountable for AI ROI without clean success metrics · technical debt from a custom agent layer nobody else can maintain
- How they buy: Hands-on technical evaluation · wants API/SDK docs, architecture diagrams, sandbox · tests model flexibility, latency, data handling directly · technical opinion carries heavy weight
Developer / CIO — lead: "AI Native"
- Core job: Developer: integrate quickly with minimal custom code; CIO: govern tool adoption across the eng org · keep implementation/maintenance cost predictable · fit security + compliance standards
- Pains: Integration work competes with roadmap · tool sprawl inflates cost · shadow-IT security exposure · hard to prove tooling ROI
- Fears: Security/compliance failure from ungoverned integration · long dev ramp-up eating promised time-to-value · vendor that can't scale across teams · inheriting a maintenance burden
- How they buy: Developer needs clean docs + fast sandbox; CIO requires formal security/vendor-risk review · enterprise pricing + rollout plan upfront · procurement sign-off before broad rollout
(Growth PM and CX Leader rows repeat Tab 3 verbatim.)
Tab 5 — Persona Messaging
| Product / Engineering | Growth / PLG | CX / Customer Success | |
|---|---|---|---|
| Role / title | Director+ Product · Engineering · CTO | Director+ Growth · PLG · Demand Gen · Customer Marketing | Director+ CS/CX · Onboarding · Support |
| Buying-committee role | Economic Buyer (budget owner) | Internal Champion (builder of case) | Influencer (internal advocate) |
| Lead message | "Your product doesn't need an agentic redesign. It needs to stop asking users to navigate." | "Stop optimizing your funnel. Start completing it — every user, every session." | "What if the product answered 'how do I?' before the ticket was ever submitted?" |
| Value proof | "Users reach meaningful outcomes in their first conversation — without changing your core product." | "374% increase in daily AI-driven activations. Improve conversion rates — improve revenue." | "Fewer how-do-I tickets. More users adopting key ROI features without the hand-holding." |
| Language to USE | activation rate · time-to-value · feature discovery · agentic interface · click tax · session outcomes | activation rate · time-to-paid · first session value · PLG → ALG · click tax · conversion rates | activation rate · self-serve · support deflection · proactive guidance · time-to-resolution · retention rates |
| Language to AVOID | chatbot · AI assistant · front end · operator · tooltips | chatbot · interface platform · agentic layer · AI operator · tooltips | AI chatbot · replace your team · automate support · AI operator · no human needed |
| Best channels | LinkedIn / Reddit · Product Hunt · Lenny's Newsletter · Peer referral · G2 | LinkedIn · Outbound · Growth Newsletters (Exit Five) · PLG Benchmarks · G2 | LinkedIn · Email Nurture · CX Communities · Peer Case Studies · G2 |
Tab 6 — ICP Notes from In Person (raw field notes, lightly structured)
CPO / VP Product / PM
- Sets roadmap; AI is a company-level initiative; AI-First / AI-Native messaging lands.
- Wants to deliver on time (gets delayed by eng team) and with value; adoption is key ("I built the right thing") — where job satisfaction comes from.
- Justify/inform roadmap decisions — defend choices/role/success (gets many inputs: sales, CX).
- Measured against: vision working, on time, adding value, being adopted. (Note: "we need to define that.")
- Big open questions: what to build; what does AI-Native mean (flagged for definition).
- No time for free trials — will delegate. Prototyping with AI; trying to become more technical; needs to justify their existence. (Note: technical-training keywords for SEO/blog traffic.)
- Super busy, lots of meetings. "They have all the authority. They have zero budget/resources." Might have ~$25K budget; goes to CEO/CFO if more is needed. (Note: diagram this.)
- Discovery: understanding timeline to ship is critical.
- Tools: Chameleon · Pendo · WalkMe · Userflow · Amplitude. Channels: PM groups/WhatsApp (PLA, Silicon Valley PMs) · influencer newsletters/webinars (~30% attendance) · gated blog assets · social with engagement.
Growth PM
- PLG + AI; owns UX/onboarding flows; new-business revenue, CVR uptick, trial→paid, activation, retention (user retention, not YoY).
- Budget ~$16K; above that goes to CPO/CTO/CMO. If Growth PM comes in, must bring in VP Product and VP Engineering.
- Token-cost math: 2K users ≈ $400/mo, 20K users ≈ $4,000/mo — balloons quickly; Foldspace can save 20–50% of yearly token usage, paying for itself.
- Open question in notes: "can this swap out an existing AI-native solution, or is it objection-handling for 'we can build in-house'?"
- Relationships with Ramli (John) and Wes Bush help for this persona.
- Tools/channels: same stack as PM row above.
CTO / Engineering
- (Row empty in the sheet — notes were never filled in.)