Two licences. One brain underneath.
Beyond RFP.
You don’t buy a knowledge base. You license who gets to reach it.
Start with the job that’s hurting. The knowledge outlasts it.
Respond
For the team that answers the documents. RFPs, DDQs, security questionnaires.
Buy it when
- Dozens of RFPs, DDQs or security questionnaires a year, not the occasional one-off.
- 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 are scattered across SharePoint, email and leftover workbooks.
- You want one response team live first, without a company-wide rollout.
Engage
For the sellers in front of buyers. Deal prep, live answers, follow-up.
Buy it when
- Reps walk into calls having read the CRM record and nothing else.
- Buyers ask about security, roadmap or a past commitment, and the rep guesses.
- Sales asks the same questions the proposal team already answered last week.
- Call notes and CRM fields get written on Friday, from memory, or not at all.
- You have enough sellers that coaching one at a time has stopped scaling.
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.
Most teams that live in both worlds end up with both. Start with the one that’s on fire this week. Numbers depend on volume and headcount, so we do those on the call rather than putting a made-up figure on a page.
Side by side
Same trust model. Different job.
Two products, one place they both answer from. What you are choosing is who reaches it.
01
Respond
Licensed to the response team
RFPs, DDQs and security questionnaires drafted from approved sources, with the uncertain ones routed to whoever owns them.
02
Engage
Licensed per seller
The brief before the call, the approved answer during it, the follow-up and CRM after.
- Proposal desk
- Experts and approvers
- Sellers
- Enablement
Tribble Brain
- KnowledgeEvery approved answer, with the document it came from
- GovernanceAn owner, a version and a review state on each one
- AutomationThe same answer, wherever in the business it is asked for
- Approved answersThe reply someone already wrote and someone already signed off
- Policy and controlsSecurity posture, certifications, the evidence behind each claim
- Product factsWhat ships, what is committed, what the limits actually are
- Customer proofNamed references, outcomes, who can be cited and for what
- Pricing and termsPackaging, discount bands, contractual commitments
- Prior responsesEvery completed packet, with the owner on each answer
Fed fromCRM · content and CMS · call recordings · SharePoint and Drive · Slack and Teams · security and policy · prior response library
Buy either one. They answer from the same place, so adding the second is a licence change rather than another implementation.
| Capability | Respond | Engage |
|---|---|---|
| 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 |
| 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 |
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 →
FAQ
Questions answered before the call.
If yours isn’t here, bring it to the call.
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 here would be wrong for most readers. Bring your volumes to the call.
What does Tribble Brain cost?
Nothing on its own, because it isn’t sold on its own. It’s the governed answer layer underneath both products, and access is included in a Respond or an Engage licence. What you’re choosing is who reaches it.
What counts as a project?
One completed buyer response package: an RFP, DDQ, security questionnaire, compliance response, or similar request.
Is Scribe priced separately?
No. Scribe is the call recording inside Engage. It’s part of an Engage licence, not a product you buy beside it.
Can we add the other one later?
Yes, and most do. Start with the work that’s hurting now. Because the knowledge is already in the Brain, adding the second product later is a licence change rather than another implementation.
What should we bring to the conversation?
For Respond, a recent RFP, DDQ or security questionnaire plus the sources your team already trusts. For Engage, three questions your buyers ask on every call that reps answer from memory today.
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.
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