No system today
Start with Proposal Automation.
Use the first edition when the urgent job is getting RFPs, DDQs, and security reviews out with source citations, owners, and review flow.
Tribble pricing
Start with proposal automation. Scale into deal intelligence.
Tribble is packaged around the work buyers can measure: response projects, governed knowledge, sales users, integrations, and enterprise controls. Start with the response bottleneck, then expand as the same intelligence powers more of the revenue team.
Annual contracts only. Intelligence Services are scoped separately when a team needs a custom industry workflow.
Annual model
30 / 60 / 120$30K
Proposal Automation
For teams replacing manual RFP, DDQ, and security questionnaire work.
50 projects
$60K
Deal Intelligence
For teams connecting response work, sales answers, and knowledge reuse.
200 projects + 25 users
$120K+
Enterprise
For scale, governance, custom integrations, and multi-team rollout.
600 projects + 50 users
Each step lowers the effective project cost while adding scope: more workflows, Sales Agent users, deeper governance, and more connected systems.
Find your starting point
Buy the first workflow. Keep the expansion path obvious.
Most teams arrive with one of three situations: no response system, an existing RFP platform or answer library, or a regulated response operation that already spans teams.
Existing RFP platform
Move the library into governed sources.
Bring forward useful answer history, map source systems, keep the review discipline, and decide whether sales context belongs in scope now.
Regulated or high volume
Scope the operating model.
Use Deal Intelligence or Enterprise when response work needs sales answers, analytics, governance, integrations, or multi-team rollout.
Financial services
RFPs, DDQs, ODD, investor diligence, fund and operating knowledge.
Healthcare
Health system RFPs, vendor assessments, privacy reviews, and security evidence.
Enterprise tech
RFPs, security reviews, SE answers, product docs, and deal follow-up.
Choose where you start
Three clear ways to buy.
Start with response projects, move into the full deal intelligence platform, or scope an enterprise rollout with deeper governance and volume.
First workflow
Proposal Automation
A complete starting point for teams that need source-cited drafts, review routing, and exports for RFPs, DDQs, and security questionnaires.
$30K
/ year
50
projects included
Add later
Sales Agent users
$600
effective project cost
- AI drafts for RFPs, DDQs, security reviews, and similar buyer response packages.
- Governed answer generation from approved content, past responses, and connected sources.
- Citations, confidence context, SME review routing, and approval workflow.
- Exports for Word, Excel, PDF, and client-required response formats.
- CRM context and basic analytics for response time, project status, and reuse.
Full platform
Most teamsDeal Intelligence
Unify proposal automation, AI Knowledge Base, and AI Sales Agents on one governed graph so every buyer answer improves the next.
$60K
/ year
200
projects included
25
Sales Agent users
$300
effective project cost
- Everything in Proposal Automation, plus AI Knowledge Base and AI Sales Agents.
- 25 Sales Agent users for deal prep, buyer question answering, follow-up, and knowledge reuse.
- Call intelligence, CRM context, buying signals, and deal risk surfaced into response work.
- Bidirectional integrations across CRM, call intelligence, chat, storage, and support systems.
- Advanced analytics for knowledge gaps, answer quality, project throughput, and outcomes.
Enterprise scale
Enterprise
Bring deal intelligence into large, regulated, or multi-division environments with enterprise governance, volume, and implementation support.
$120K+
/ year
600
projects included
50
Sales Agent users
$200
effective project cost
- Everything in Deal Intelligence, plus enterprise controls and deployment support.
- 50 Sales Agent users, multi-team rollout paths, and higher-volume response operations.
- SSO, SCIM, audit logs, advanced permissions, and data residency options.
- Custom connectors, API access, webhooks, and multi-language support.
- Dedicated customer success, premium SLA, QBRs, and custom reporting.
Additional projects
Add proposal project capacity in blocks of 100 projects for $20K. Volume discounts apply at 300+ and 500+ additional projects.
Additional Sales Agent users
Deal Intelligence adds users at $300 per user per month. Enterprise adds users at $200 per user per month.
Intelligence Services
Custom industry workflows are scoped separately after the platform scope, sources, owners, and business outcome are clear.
One governed operating model
Every edition runs on source-cited, governed answers — not a pile of prompts.
The difference between editions is scope and scale. The compliance model — citations, permissions, review routing, and audit trail — is consistent from the first response project to a company-wide rollout.
Approved sources
Connect content from the systems your teams already trust instead of forcing every answer into a manually maintained library.
Citations and confidence
Answers show source context and confidence signals so reviewers can decide what is ready and what needs an expert.
Expert routing
Uncertain answers route to the people who own the source, policy, product area, or compliance language.
Reusable learning
Approved answers, corrections, project outcomes, and sales context become part of the next buyer answer.
What each edition unlocks
Proposal Automation is complete. Deal Intelligence is where the platform compounds.
All editions cover the response workflow. Deal Intelligence adds the connected sales, knowledge, and outcome context that turns response work into a repeatable advantage.
Proposal automation
AI draft generation with source citations, confidence context, and reviewer auditability
All editions
RFPs, DDQs, security questionnaires, compliance audits, and buyer response packages
All editions
Export, collaboration, expert routing, approvals, and project status
All editions
Go/No-Go analysis, quality scoring, deal fit, and knowledge-gap analytics
Deal Intelligence
Multi-language proposals, custom branding, custom reporting, and advanced rollout needs
Enterprise
Deal intelligence
AI Knowledge Base connected to proposal answers, source owners, and approved corrections
Deal Intelligence
AI Sales Agent users for deal prep, buyer questions, follow-up, and knowledge reuse
Deal Intelligence
Call intelligence, CRM context, buying signals, and outcome learning
Deal Intelligence
SSO, SCIM, audit logs, data residency options, APIs, and dedicated rollout support
Enterprise
Moving from a static RFP library
Keep the workflow discipline. Move beyond the static library.
Static RFP libraries proved response teams need owners, approval history, exports, and repeatable project workflow. The takeaway is not to throw that muscle memory away. It is to connect it to live source systems, citations, sales context, and outcome learning so the answer base does not go stale between requests.
Migrating should not mean asking every SME to rewrite a library. The right motion is to bring forward useful answer history, identify authoritative sources, attach owners and citations, and rebuild the workflow around governed knowledge that stays current.
Export what is worth saving.
Bring over active libraries, prior responses, review notes, owners, and tags from your current tool or the shared folders that replaced it.
Find the source of truth.
Map which answers should come from Drive, SharePoint, Confluence, product docs, security policies, CRM notes, or support systems.
Clean the stale layer.
Deduplicate old Q&A pairs, retire risky language, preserve strong approved answers, and attach owners where policy or product language needs review.
Run a real buyer request.
Pilot on an active RFP, DDQ, or security questionnaire so the team sees citations, confidence, SME routing, approval context, and export workflow against live pressure.
Expand once the answers work.
Use the same governed graph for sales follow-up, call prep, knowledge-base questions, and deal risk so response work becomes the first surface of deal intelligence.
Total cost picture
The license is not the whole cost. Neither is the software.
Buyers usually compare subscription price first. The real difference shows up in content upkeep, SME time, implementation burden, governance risk, and the work required to make answers improve over time.
Cost area
Manual or static library
Generic LLM or internal build
Tribble operating model
Content upkeep
Teams keep rewriting Q&A pairs, chasing stale owners, and patching old answers.
The team still has to prepare sources, prompts, permissions, citations, and retrieval rules.
Approved sources, citations, owners, corrections, and outcomes become part of the next answer.
SME time
Experts answer the same questions repeatedly across RFPs, DDQs, and security reviews.
Experts get copied into chat threads because the model cannot own review workflow.
Uncertain answers route to the right owner with source context and review history already attached.
Governance risk
Stale approved language can look safe until it reaches a buyer, security reviewer, or compliance reviewer.
Drafts may be useful, but citations, permissions, approvals, and audit trail have to be engineered separately.
Citations, confidence, permissions, approvals, and audit context travel with the answer.
Scale economics
More volume usually means more coordinator work and more SME interruptions.
More scope means more engineering, security review, integrations, and maintenance.
Edition pricing includes project capacity; additional projects are added in predictable blocks.
Why not just use a general LLM?
An LLM can write. It cannot prove the answer is compliant, sourced, and ready for a buyer.
Claude, ChatGPT, and other assistants are useful drafting tools. But regulated response work needs more than text generation. It needs source citations that survive audit, permission-aware retrieval that respects who can see what, expert approval that creates a review record, and the learning loop that turns every approved answer into a reusable asset. That is an operating model, not a prompt.
Requirement
Generic LLM
Tribble
Source citations
No chain of custody. Answers go out without evidence of where the language came from, what was approved, or who reviewed it.
Every answer traces to its source document. Citations, confidence scores, and review history are visible to the response team and any compliance reviewer who needs them.
Compliance and audit
Chat history is not an audit trail. There is no record of what document an answer drew from, who approved it, or when it changed.
Built for regulated response operations. Permissions, review routing, source lineage, and approval history mean every answer that reaches a buyer has a verifiable path back to an authorized source.
Security and governance
Depends on individual user behavior. No role-based access to knowledge, no permissions on what the model can retrieve.
RBAC, SSO, audit logs, and permission-aware retrieval ensure the model only accesses sources the user is authorized to see.
Deal context
Can summarize what it is given, but does not naturally know the CRM, call, or account state.
Connects response work to CRM fields, calls, prior answers, knowledge gaps, and outcomes.
Learning loop
A corrected answer may stay in one conversation and never improve the next response.
Turns approvals, edits, and outcomes into reusable knowledge for the next buyer question.
Separate engagement
Need a workflow that does not exist in the market yet?
Tribble Intelligence Services can scope custom industry workflows after the platform foundation is clear: mapped sources, owners, review paths, integrations, and the business outcome worth automating.
Pricing FAQ
Questions buyers should not have to save for the call.
Why publish pricing?
Because a champion should be able to qualify budget before booking a demo. The call should be about fit, source systems, workflow scope, and implementation path.
What counts as a project?
A project is one completed buyer response package: an RFP, DDQ, security questionnaire, compliance audit response, or similar request.
Can we start with RFP automation and add Deal Intelligence later?
Yes. That is the intended expansion path. Start with the response work slowing revenue now, then connect sales questions, knowledge delivery, calls, and outcomes once the first workflow is working.
Can we buy Proposal Automation only?
Yes. Proposal Automation is a complete starting point for response teams that need sourced drafts, project workflow, review routing, and exports without Sales Agent users on day one.
What if we do not have an RFP tool today?
Start with your highest-friction response motion. Bring a recent RFP, DDQ, security questionnaire, or compliance response, then use that workflow to define sources, reviewers, exports, and project volume.
How hard is it to migrate from an existing RFP platform or static library?
The work is mostly source mapping and governance design, not a blank-page rebuild. Bring forward useful answer history, connect authoritative sources, assign owners, and pilot on a real request.
Why not use Claude directly?
Use a general LLM for drafting and thinking. Use Tribble when the answer needs approved sources, source citations, permission-aware retrieval, reviewers, audit context, exports, CRM context, analytics, and a learning loop.
Do SMEs and reviewers need to be priced like sales users?
Packaging is scoped around annual edition, projects, workflow breadth, and defined user blocks. The buying conversation should not punish the team for routing answers to the right experts.
What happens if we exceed the included project count?
Additional proposal projects are added in blocks of 100 projects for $20K. The effective project cost improves as teams move from Proposal Automation to Deal Intelligence to Enterprise.
How do additional Sales Agent users work?
Deal Intelligence includes 25 Sales Agent users and adds more at $300 per user per month. Enterprise includes 50 Sales Agent users and adds more at $200 per user per month.
Can Tribble help with compliance and security questionnaires?
Yes. Tribble helps teams respond to security and compliance questionnaires, including SOC 2, ISO, FedRAMP, privacy, and vendor-risk requests, from their own approved documentation and review workflow.
How should financial services, healthcare, and tech buyers scope the first edition?
Financial services teams often start with RFPs, DDQs, ODD, and investor diligence. Healthcare teams usually bring health system RFPs, vendor assessments, privacy reviews, and security evidence. Enterprise tech teams often start with RFPs, security reviews, product answers, and sales engineering follow-up.
Bring the real workflow
We will price the work you actually need to automate.
Bring a live RFP, DDQ, security questionnaire, sales question workflow, or migration plan. We will show where Proposal Automation is enough, where Deal Intelligence changes the economics, and what belongs in an Enterprise scope.
Book a demo