Two licences. One brain underneath.
Beyond RFP.
You don’t buy a knowledge base. You license who gets to reach it. Respond is for the team that answers documents. Engage is for the sellers sitting in front of buyers. Both read from and write back to the same governed layer.
Start with the job that’s hurting. The knowledge outlasts it.
Respond
RFPs. DDQs. Security questionnaires. For proposal, security and diligence teams. A first draft they can defend, with a source on every answer and the uncertain ones routed to the person who owns them. Licensed to the team, not the seat.
Engage
Deal prep. Live buyer support. Follow-up and CRM. For sellers. The brief before the call, the approved answer during it, the follow-up and CRM update after. Call recording is part of it — that’s Scribe. Licensed per seller.
Tribble Brain underneath
The Brain is the governed answer layer both products run on: every source with an owner, a version and a review state. It isn’t a separate line on the invoice and it isn’t something you buy on its own. Respond and Engage are how you license access to it.
Where to start
One of these lists will sound like your week.
Respond is for
The packet is the bottleneck.
- Dozens of RFPs, DDQs or security questionnaires a year, not the occasional one-off.
- A dedicated proposal or response function, roughly five or more people writing, coordinating or reviewing.
- SMEs in security, legal, product or clinical are the bottleneck, not the writers.
- Answers leave in the buyer’s Word, Excel or portal and have to survive legal review.
- Last year’s answers live in SharePoint, email and leftover workbooks, so every packet starts from memory.
- You want one response team live first, without a company-wide rollout.
Most popular among proposal leaders
Engage is for
The rep is answering from memory.
- Reps walk into calls having read the CRM record and nothing else.
- Buyers ask about security, roadmap or a commitment made in a past proposal, and the rep guesses.
- Sales asks the same questions the proposal team already answered last week.
- Call notes, action items and CRM fields get written on Friday, from memory, or not at all.
- Reps live in Slack, Teams, the CRM and call recordings, not in a proposal workspace.
- You have enough sellers that coaching one at a time has stopped scaling.
Most popular among sales and revenue leaders
Most teams that live in both worlds end up with both. Start with the one that’s on fire this week.
How it’s licensed
Two shapes, because the work is two shapes.
Respond
Licensed to the response team.
- A team licence, not a per-seat one. Writers, coordinators and project owners all work in it.
- Reviewers, approvers and SMEs are included. Pulling a security lead in for four questions shouldn’t cost a seat.
- Sized by response volume — how many packets a year the team ships.
- A project is one completed buyer response: an RFP, DDQ, security questionnaire or compliance response.
Sized by response volume
Engage
Licensed per seller.
- Per user, per month, for the people in front of buyers.
- Scribe is included. Call recording is a feature of Engage, not a product you buy beside it.
- Sized by how many sellers you put on it, so a pod can go first and the floor can follow.
- Managers and enablement read the same answer layer without a separate tool.
Sized by seller headcount
There’s no separate Brain licence. Numbers depend on volume and headcount, so we do them on the call rather than putting a made-up figure on a page.
Respond, the workflow
Same RFP, very different endings.
Intake to approval looks like every other tool. What happens to the answers afterward isn’t.
- 1
Intake
The buyer’s RFP, DDQ or security questionnaire becomes one reviewable project.
- 2
First draft
Source-cited answers from approved knowledge, with a confidence level on every question.
- 3
Review
Uncertain or sensitive questions route to the named expert. The decision is recorded.
- 4
Approved
The packet ships in the buyer’s format, with an audit trail behind it.
Engage, the workflow
Before the call, during it, after it.
The same approved answers the proposal team defends, in the rep’s hands at the moment the buyer asks.
- 1
Deal prep
A brief from CRM, calendar, prior calls and any open response work. What changed, what the buyer cares about, where the conversation goes next.
- 2
Live buyer support
Security, roadmap, integrations, a commitment made in a past proposal — the approved answer with its source attached. Sensitive questions route to an expert.
- 3
Follow-up and CRM
Scribe records the call. Tribble drafts the follow-up, the action items, the CRM fields and the methodology notes. The rep approves.
Both workflows, one layer
Every draft, edit, approval and call lands as governed, source-cited knowledge. The next RFP starts ahead, and the rep on tomorrow’s call gets the answer the proposal team already defended. Generic tools stop at the draft. That’s why the ending is different.
What each licence includes
Same trust model. Different job.
Respond is the response workflow. Engage is the seller’s workflow. The Brain is the layer both of them answer from, and it’s included in each.
| Capability | Respond | Engage |
|---|---|---|
| Who it’s for | Proposal, security and diligence teams | Sellers, and the managers coaching them |
| How it’s licensed | Team licence, sized by response volume | Per seller, per month |
| Where the work happens | The response workspace, Word, Excel and buyer portals | Slack, Teams, the CRM and the call itself |
| Access to Tribble Brain | Included | Included |
| Source citations on every answer | Included | Included |
| SME routing and audit trail | Included | Included |
| Questionnaire and proposal drafting | Included | Reads the answers, doesn’t build the packet |
| Reviewer and SME seats | Included in the team licence | Not applicable |
| Standard exports: Word, Excel, PDF, portal | Included | Not included |
| Pre-call briefs from CRM and prior calls | Not included | Included |
| Call recording (Scribe) | Not included | Included |
| Follow-up drafts and CRM write-back | Not included | Included |
| Answers in Slack and Teams | Review and routing only | Included |
| Knowledge-gap analytics | Across responses | Across calls |
| SSO, SCIM, RBAC | Scoped | Scoped |
Rated on G2
FAQ
Questions answered before the call.
If yours isn’t here, bring it to the call.
What is Respond?
Respond is the questionnaire workflow. It parses RFPs, DDQs and security questionnaires, drafts source-cited answers, routes reviewers, and exports in the format the buyer asked for.
What is Engage?
Engage is the seller’s workflow: the brief before the call, approved answers with sources during it, and the follow-up, action items and CRM updates after. It runs where reps already work — Slack, Teams and the CRM.
What is Scribe?
Scribe is the call recorder inside Engage. It captures the conversation so the follow-up, the CRM fields and the methodology notes are drafted from what was actually said. It’s a feature of Engage, not a separate product to buy.
What does Tribble Brain cost?
Nothing on its own, because it isn’t sold on its own. The Brain is the governed answer layer underneath both products, and access to it is included in a Respond or an Engage licence. What you’re choosing is who reaches it: the response team, the sellers, or both.
Why are there no numbers on this page?
Respond is sized by how many responses a year your team ships. Engage is sized by how many sellers you put on it. Both move enough between companies that a figure on a page would be wrong for most readers. Bring your volumes to the call and we’ll price it there.
Are reviewers and SMEs included?
Yes, in Respond. Reviewers, approvers and SMEs are part of the response workflow and don’t consume a seat. Engage is licensed per seller, so it counts the people in front of buyers.
What counts as a project?
One completed buyer response package: an RFP, DDQ, security questionnaire, compliance response, or similar request.
Do we start with both?
No. Start with the product that matches the work hurting now. Many teams start with Respond, then add Engage once sales wants the same approved answers on live calls. Adding the second one later costs nothing in setup, because the knowledge is already there.
What should we bring to the conversation?
For Respond, a recent RFP, DDQ or security questionnaire plus the source documents your team already trusts. For Engage, three questions your buyers ask on every call that reps currently answer from memory.
How is this different from ChatGPT or a generic assistant?
Generic tools draft text. Tribble retrieves approved sources, cites them, routes exceptions to experts, and keeps a record of what was approved.
What buyers said after they bought it.
G2 awards come from verified customer reviews. Worth reading before a pricing conversation rather than after.
Fall 2026, across RFP, AI Sales Assistant and AI Meeting Assistants. Read the reviews on G2 →
See it on your workflow, not a sample deck.
Bring the questionnaire, or the three questions your reps can’t answer on a call today. We’ll map Respond, Engage or both, and price it against your actual volumes on the call.
Book a demo