Product Catalog
Declare what you sell — resale products, proprietary IP, productized services, and billable roles. The catalog feeds the RFP-to-catalog matcher, which proposes a ranked bundle for every incoming RFP.
What the catalog is — and isn't
The Product Catalogis a structured list of offerings your organization can sell. It's managed under Settings → Product Catalog and is scoped to your company profile (row-level isolated).
The Catalog is what you sell. The Knowledge Base is evidence of what you've done (past RFPs, case studies, datasheets). The two work together: the catalog tells the matcher what to propose, the KB supplies the grounding for the content agent to write about it.
The four catalog kinds
Every catalog item belongs to exactly one kind. The kind drives which RFPs the item can anchor (as a Primary bundle role) and which pricing & licensing metadata the matcher pays attention to.
Resale ProductRESALE_PRODUCT
Third-party software you sell (SAP, Oracle, Microsoft, etc.).
Example: SAP Ariba Sourcing, S/4HANA Finance, SuccessFactors Employee Central.
Use when: Use when the offering is a vendor-defined SKU with a known licensing model.
Own IPOWN_IP
Your proprietary platforms, accelerators, templates, and tools.
Example: Finance migration accelerator, public-sector RFP template, data quality tool.
Use when: Use for anything you built that differentiates you from competitors pitching the same modules.
ServiceSERVICE
Productized services with a named scope.
Example: Managed AMS tier 2, 12-week S/4HANA implementation pack, 24×7 cloud ops.
Use when: Use when the offering has a defined scope and unit economics — not a body-shop arrangement.
Resource RoleRESOURCE_ROLE
Billable roles from your rate card.
Example: Sr. SAP Architect, Integration Lead, Functional Consultant (onsite / nearshore / offshore).
Use when: Use for single-resource RFPs and as staffing inputs for service bundles.
How RFP-to-catalog matching works
After an RFP is qualified, a dedicated CATALOG_MATCHER step runs. It sits between capability matching (should we bid?) and strategy (how do we win?), answering the middle question: what do we propose?
1. Requirement indexing
Every RFP requirement gets a synthetic ID (M1 mandatory, R1 functional, C1 certification, S1 security, G1 geographic). The matcher cites these IDs when it scores each item.
2. Engagement routing
The intake agent classifies each RFP as product / consulting / single_resource. The matcher uses this to decide which kinds can anchor the bundle as Primary. Others can still land as Complementary or Optional.
3. LLM scoring
Every catalog item is scored 0–100 in a single LLM call with matched requirement IDs, unmatched gaps, and a one-line rationale. Hallucinated items (IDs not in the catalog) are dropped at parse.
4. Deterministic bundle
Scores are partitioned into Primary (≥75, 1 item) / Complementary (≥60, ≤4) / Optional (≥50, ≤3) / Rejected. No LLM coin-flips — the buckets are deterministic given scores.
Bundle tiers: Primary, Complementary, Optional
Every bundle fits on one screen. The tiers and their caps are deterministic:
| Tier | Score floor | Cap | Engagement-gated? |
|---|---|---|---|
| Primary | ≥ 75 | 1 item | Yes (kind must be eligible for the RFP's engagement type) |
| Complementary | ≥ 60 | Up to 4 | No |
| Optional | ≥ 50 | Up to 3 | No |
| Rejected | < 50 | Unlimited | — |
Coverage gaps are first-class
Any RFP requirement that no item in the selected bundle (Primary + Complementary + Optional) addresses becomes a coverage gap. These feed into the gap-analysis agent — they become clarifying questions for the customer or flags to find a partner / subcontractor.
Field reference
Not all fields are required. High-signal fields are the ones the matcher relies on most — prioritize filling them in.
| Field | Purpose | Signal |
|---|---|---|
| Kind | One of the four kinds above. Drives engagement-type eligibility. | HIGH |
| Vendor | Parent vendor if resale (e.g., SAP). Leave empty for own IP. | HIGH |
| Name | Product or offering name. Appears on match cards. | HIGH |
| Summary | 1–2 sentence pitch. The matcher reads this when scoring fit. | HIGH |
| Capabilities | Explicit feature list (comma-separated). The highest-signal field for matching. | HIGH |
| Category / Subcategory | E.g., "Procurement / Strategic Sourcing". Helps the matcher disambiguate. | MED |
| Version / SKU | For precise identification of resale products. | MED |
| Pricing model | Per-user, per-core, fixed-bid, T&M, etc. Matcher uses to flag budget-model mismatches. | MED |
| Target industries & personas | Where this item fits best. Boosts matching on relevant RFPs. | MED |
| Certifications | SOC2, FedRAMP, ISO 27001. Critical for government and regulated RFPs. | MED |
| Prerequisites | "Requires SAP BTP". Surfaces dependency gaps to the strategy agent. | LOW |
| Companions | Items usually bundled together. Helps the matcher build coherent bundles. | LOW |
| Geographies | Where you can deliver. Critical on geographic-constrained RFPs. | LOW |
| Tags | Free-form labels. Useful for filtering in the settings UI. | LOW |
Best practices
Start with your own IP
If you can only add 10 items today, make them your proprietary accelerators and productized services. That's where the matcher pays for itself fastest — your differentiators are the ones solution architects most often forget to pitch.
Be specific in capabilities
Vague items score conservatively on everything. “SAP services” will never anchor a bundle. “SAP Ariba Sourcing — RFQ events, reverse auctions, supplier scorecards, public-sector ready” will be picked when it fits and dropped cleanly when it doesn't.
Archive, don't delete
Archiving a retired item preserves the audit trail on past RFP matches and frees a plan-limit slot. Only hard-delete items that were created in error.
Use overrides to teach the matcher
If the matcher keeps dropping an item you'd pitch, override it to Complementary or Primary on that RFP. Overrides persist across pipeline re-runs and signal where your catalog metadata needs tightening.
Plan limits
| Plan | Catalog items | SAP seed import | Matcher + bundle UI |
|---|---|---|---|
| Starter (Free) | 25 active items | — | Full |
| Business | 500 active items | ✓ (Phase 3) | Full |
| Enterprise | Unlimited | ✓ | Full |
Archived items do not count toward the limit. The matcher only considers ACTIVE items when scoring.
Related
Ready to get started?
Create your free account and generate your first AI-powered proposal in minutes.
Start Free