Build, Position, Win: One Evidence Base for Product, Marketing, and Sales

Take one example. A rival ships a release on a Tuesday. Three teams at your company need to act on it, and each needs something different. Product needs to know whether it opens a gap customers care about. Marketing needs to know whether your positioning still holds. Sales needs to know what to say on Thursday's call.

In most software companies, each team finds out on its own, from its own sources, and decides from its own copy of the facts. A seller hears the rival's name in a deal. Product hears about it weeks later in a feature request. Marketing reads the press release and rewrites a slide. The facts drift apart, and the decisions follow.

That drift is common. In HubSpot's 2024 Sales Trends Report, only 30% of sales professionals said sales and marketing are strongly aligned at their company.[1] Crayon's 2025 research found that fewer than a third of compete teams engage with sales on a daily or weekly basis, and that 44% don't have visibility into which competitors are in which deals.[2]

Three copies of the facts

The cost is not that teams disagree. It is that they can't see why they disagree. A product manager ranks a gap from feature requests; in ProductPlan's 2023 survey of over 1,500 product managers, reviewing customer feature requests was the number one source of actionable product ideas.[3] A product marketer writes positioning from analyst notes, review sites, and the rival's own pages. A seller handles objections from a battlecard someone built last quarter; in Crayon's 2024 survey, 58% of CI professionals said keeping battlecards and content updated is a struggle.[4]

Each choice is reasonable on its own. None of the three teams can check the others' evidence, because it sits in someone else's tool.

Meanwhile the buyer does not wait. In G2's 2024 survey of more than 1,900 B2B software buyers, 69% said they usually engage a salesperson only when they have made their decision.[5] By the time a seller hears the rival's name, your positioning has already done its work, or failed to.

One evidence base does not mean one team decides for the others. It means each team decides from facts the other two can open and check.

One release, traced through three teams

Here is the Tuesday release worked through PYRAMYD, from the first signal to the sales call. Each step names the screen where the work happens today, and its limits.

1. The signal: see what the rival shipped

New signals are collected every day. A product marketer opens the rival's record in Competitors › Competitor 360 and reads its Pulse tab: recent public signals about the rival, each with its source, grouped into Narrative, Newsroom, What changed, and Coordinated moves. The same signals appear on the rival's battlecard. For a quick read, ask APEX "what's new with this rival this month?" and it lists the main items with dates and sources. Before the weekly meeting, pick a weekly brief on Competitors › Competitor 360 › Reports for the observed facts, with links and capture dates, set against the week before.

Two limits today: signal scoring is paused, so new signals arrive without a significance score, and Pulse shows public signals only, not what your own customers said on calls.

2. The gap: decide whether customers care

The product manager's question is not whether the rival shipped it, but whether your customers want it. Open Products › Gaps › Matrix and sort by the Customers column: each gap shows how many distinct customers it touches and which kinds of evidence back it, from lost deals and help-desk tickets to interviews, surveys, and calls. The count covers features whose evidence names a customer, so read it as a floor.

For the head-to-head view, the battlecard's Capabilities tab compares the two products feature by feature, with review or AI scores and who wins each one. APEX also searches reviews by meaning: ask what reviewers say about the rival's reporting, and it quotes the reviews with their sources. The public review collection runs to mid-June 2026, so a brand-new release will not have reviews yet.

The call stays with the product manager: close the gap, answer it another way, or leave it. What changes is that the call has customers and evidence behind it, and marketing and sales can open the same view.

3. The positioning: adjust the story

Product marketing decides whether the story still holds. Pin the rival, your product, and a win/loss document as APEX context (Add to APEX, in any record's menu), then ask APEX for a positioning brief. APEX can create a document for it in Workspace › Studio › Documents, where reviewers leave comments, suggest edits with tracked changes, footnote each claim with its source, and compare saved versions. To see where the rival is weak with buyers, Competitors › Win/Loss › Competitive turns its public reviews into what buyers praise and criticize.

Studio has 9 tabs, and 7 are open today; Slides and Schemas are not. The positioning itself stays a human decision: APEX drafts from the evidence you pin, and your marketer decides what the company will say.

4. The battlecard: rebuild what reps read

When the story changes, the card changes with it. In Competitors › Battlecards, generate a fresh card for your product against the rival, with a customer and a deal as optional context, or keep the current card and rewrite only the sections the release touches, with an instruction such as "reflect their new reporting module". The Context Manager sets which companies, products, people, and deals the AI reads when it writes. The card's Evidence and confidence section lists its numbered sources, so a seller can check a claim before using it; sources are listed for the card as a whole, not section by section.

Then save the card to the Organization Library and share it with the sellers who face this rival, by invitation or by a tracked link.

5. The conversation: what the seller says

On Thursday the seller opens the card. Its Overview tab has three short lists for a call: landmines to plant, objection handlers, and discovery questions, and the Proof tab adds recent wins. The Proof and Trust tabs hold your weaknesses with their mitigations, the rival's strengths with counters, and answers to its fear, uncertainty, and doubt. In the APEX panel, the seller can ask for the top three talking points from the card, or for what win/loss interviews say about the rival. Answers that draw on your CRM or calls are only as fresh as the last connector sync, and a sync runs when you choose Sync now.

6. Back to the start

Then the loop closes. Library › Usage ranks the pieces you own by views, viewers, and average reading time, and the card's Usage and readers panel shows which tabs and sections reps open. If reps skip the new section, marketing learns it from the data instead of a quarterly survey. When the rival moves again, the next round starts from the same records.

What one evidence base means in practice

• Same records. The rival, its product, and the feature in question are the same nodes in the gap view, the battlecard, and the deal, so nobody retypes a competitor into three tools.
• Sources travel with the work. Gaps show their evidence, battlecards list their sources, and APEX answers list the records and sources they used.
• One shelf. Battlecards, documents, and reports are saved to the Library for you, a team, or the organization, and its Shared tab shows what has been shared with you and by you.
• People decide, agents draft. APEX drafts, and it asks for approval before it adds a relationship to the graph. The roadmap call, the positioning, and the deal plan stay with the teams that own them.

How to start in two weeks

• Day 1. Pick one rival that cost you a deal last quarter. Track it, and open its Competitor 360 record with someone from each team.
• Day 2. Connect your CRM from Workspace › Library › Connectors and choose Sync now.
• Days 3 to 5. Product sorts Products › Gaps › Matrix by customers and names the three gaps that matter most against this rival.
• Week 2. Marketing drafts the positioning brief from pinned evidence, rebuilds the battlecard, and saves both to the Organization Library for the sellers who face this rival.
• Day 14. Check Usage, then ask each team which fact it still had to find outside PYRAMYD. Fix that one first.

Three teams, one set of facts

Build, position, and win are three decisions owned by three teams, and they should stay that way. What should not stay separate is the evidence. When product, marketing, and sales work from one base, a rival's Tuesday release becomes a ranked gap, a revised story, a rebuilt card, and a better Thursday call, and the next team in line can check every step.