## Frame the decision Choose the single homepage message that should lead the launch and the proof needed to make it credible. **Evidence threshold: Moderate.** Four independent customers provide specific, largely consistent evidence about recurring reporting work. However, only two are in the initial RevOps target, so the evidence is not strong enough to generalize across the full market. ## Build the evidence ledger | ID | Evidence | Speaker / segment | Situation or trigger | Narrowly supports | |---|---|---|---|---| | E1 | “Every Monday I lose half a day copying HubSpot numbers into the board deck.” | Maya — RevOps, 42-person logistics SaaS | Weekly board reporting | Manual recurring reporting consumes substantial time | | E2 | “The dashboard is fine for me; the problem is explaining the week to people who will never open HubSpot.” | Maya — RevOps, 42-person logistics SaaS | Communicating performance to stakeholders | The unmet need is explanation, not another dashboard | | E3 | “If it could draft the narrative and show where each number came from, I’d trial it this quarter.” | Maya — RevOps, 42-person logistics SaaS | Evaluating a possible solution | Narrative generation plus source visibility could trigger a trial | | E4 | **Paraphrase:** Security review is required before any CRM connection. | Maya — RevOps, 42-person logistics SaaS | CRM integration approval | Security is a prerequisite for adoption | | E5 | “I’m not short on dashboards. I’m short on a clean answer when the CRO asks why pipeline moved.” | Luis — Sales Ops, 120-person cybersecurity firm | Explaining pipeline changes to leadership | Existing dashboards do not provide decision-ready explanations | | E6 | **Paraphrase:** He exports Salesforce data to Sheets, then writes a weekly memo. | Luis — Sales Ops, 120-person cybersecurity firm | Weekly performance reporting | The current workflow requires manual data transfer and narrative writing | | E7 | “A black-box summary would die in security. I need every sentence tied back to a field or record.” | Luis — Sales Ops, 120-person cybersecurity firm | Assessing generated summaries | Sentence-level traceability is both a trust and security requirement | | E8 | “I spend two hours on Friday turning project data into client updates.” | Nina — Founder, 9-person agency | Weekly client communication | The data-to-narrative problem also appears outside RevOps | | E9 | **Paraphrase:** She wants polished client emails, setup under an hour, and has no security objection. | Nina — Founder, 9-person agency | Product adoption | This smaller segment prioritizes output polish and rapid setup | | E10 | “The board pack takes a day because the numbers change and the commentary doesn’t.” | Owen — Finance manager, 70-person marketplace | Preparing board materials | Commentary becomes stale when underlying data changes | | E11 | **Paraphrase:** He wants variance explanations and says CRM is not the system of record. | Owen — Finance manager, 70-person marketplace | Financial performance reporting | Explanation demand extends beyond CRM, but the required data source differs | ## Find patterns without manufacturing consensus ### Repeated patterns 1. **Recurring data-to-narrative work is the shared pain.** All four customers describe manually converting changing business data into board, executive, client, or finance communication: **4/4 customers** (E1, E6, E8, E10). 2. **The core RevOps need is explanation, not more dashboards.** Both customers in the initial target explicitly distinguish dashboards from the answer stakeholders need: **2/2 target-segment customers** (E2, E5). No target-segment counter-evidence appears in the material. 3. **Traceability is central to credibility in the target segment.** Both target-segment customers require either visible sourcing or security approval: **2/2 target-segment customers** (E3, E4, E7). Nina provides counter-evidence outside the target segment: she reports no security objection and prioritizes setup speed instead (E9). ### Isolated signals - A source-linked narrative could create near-term trial intent for Maya (E3). - Setup under one hour may be important for very small teams, but only Nina states it (E9). - Automatically explaining variances may matter in finance workflows, but only Owen raises it (E11). ### Contradictions and boundaries - CRM connectivity fits the two RevOps workflows (E1, E6), but Owen explicitly says CRM is not the system of record (E11). A CRM-led message therefore fits the launch target better than the broader market. - Security is decisive for the two target accounts (E4, E7), while Nina has no security objection (E9). The difference appears segment-related rather than a market-wide consensus. ### Segment differences - **RevOps / Sales Ops:** Executive explanation, pipeline movement, CRM data, traceability, and security approval (E1–E7). - **Small agency:** Polished external communication and very fast setup (E8–E9). - **Finance:** Variance explanations and synchronization between changing numbers and commentary, using systems beyond CRM (E10–E11). ## Preserve the customer’s language ### Triggers - “Every Monday” (E1) - “when the CRO asks why pipeline moved” (E5) - “on Friday” (E8) ### Pains - “I lose half a day” (E1) - “the problem is explaining the week” (E2) - “I’m not short on dashboards” (E5) - “I spend two hours” (E8) - “the numbers change and the commentary doesn’t” (E10) ### Current workarounds - “copying HubSpot numbers into the board deck” (E1) ### Desired outcomes - “draft the narrative” (E3) - “show where each number came from” (E3) - “a clean answer” (E5) - “why pipeline moved” (E5) ### Objections - “A black-box summary would die in security.” (E7) ### Decision rules - “I’d trial it this quarter.” (E3) - “every sentence tied back to a field or record” (E7) ## Make the call **Observed:** Both target-segment customers already have dashboards but still manually create recurring explanations for leadership; both require generated claims to remain traceable to source data (E1–E7). **Interpretation:** The strongest launch wedge is not automated reporting in general. It is turning CRM changes into a defensible explanation that RevOps can pass to executives without producing another black-box dashboard. **Implication:** The homepage should lead with the executive question the product answers and make source traceability part of the core promise, not a secondary feature. **Recommendation:** Lead with: > **Explain why pipeline moved—not another dashboard.** > Turn HubSpot or Salesforce data into a weekly performance narrative, with every sentence linked to its source fields and records. The page should immediately show a concrete proof sequence: 1. A visible pipeline change from sample CRM data. 2. The generated explanation shown beside it. 3. Clickable sentence-level links revealing the supporting field, record, and reporting period. 4. A concise security and connection-review statement adjacent to the demo. **Strongest reason this could be wrong:** The recommendation rests on only two target-segment customers. Traceability may attract attention while integration approval, data quality, or another workflow requirement ultimately controls purchase. **Smallest test that would expose the error:** Show the proposed hero and source-linked proof mockup to five new RevOps buyers at 30–200-person B2B companies. Ask each to explain what the product does, identify what would prevent a trial, and choose what evidence they would need next. Reconsider the message if fewer than three independently identify pipeline explanation and source traceability as the primary value. ### Ranked next actions 1. Build the source-linked narrative proof shown above and test whether target buyers understand and trust it without additional explanation. 2. Interview five new target-segment buyers to test whether explanation and traceability outrank integration, security, data quality, and setup concerns. 3. Document the minimum security and CRM-connection evidence required to support the homepage promise without overstating readiness. ## Show the boundary ### What the material does not establish - Whether this message converts better than alternatives in live acquisition. - Whether RevOps buyers will pay for the product. - Which security controls or certifications are required. - Whether source links alone create sufficient trust in generated explanations. - Whether HubSpot and Salesforce cover enough of the initial target market. - Whether logistics SaaS and cybersecurity findings generalize across B2B companies. - Whether the product can reliably explain causation rather than merely describe changes. ### Missing evidence most likely to change the recommendation Evidence from additional RevOps buyers showing whether their primary unmet need is explaining performance changes—or whether CRM integration, security approval, data quality, forecasting, or another workflow concern dominates the buying decision. ### Follow-up questions 1. Walk me through the last time leadership asked about a change in pipeline. What did you do from that moment until you gave them an answer? 2. When evaluating a generated performance explanation, what would you inspect before deciding whether to share it? 3. What, if anything, would prevent your team from using a tool that connects to your business systems and drafts the weekly narrative?