Match your SAP SKUs, own IP, and services
to every RFP — automatically.
Purpose-built for SAP partners and systems integrators who juggle resale SKUs, proprietary accelerators, and productized services on every deal. Declare your catalog once; get a ranked solution bundle on every RFP.
One RFP, four classes of offerings
A generic proposal tool treats “what you sell” as a single bucket. That works for a boutique consultancy. It falls apart for SAP partners, global SIs, and anyone who both resells software and delivers services.
A real opportunity might need S/4HANA (resale) + your finance migration accelerator (own IP) + 12-month managed support (service) + 4 named architects (roles). The win comes from proposing that bundle confidently, with evidence, within 48 hours.
Resale Products
SAP Ariba, S/4HANA, SuccessFactors, BTP
Third-party SKUs with vendor, version, pricing model, and licensing metadata. The matcher cites specific modules against RFP requirements.
Own IP
Migration accelerators, industry templates, proprietary tools
Your differentiators. These are the win-theme material strategy agents use to ghost competitors. The matcher guarantees they appear on every relevant RFP.
Productized Services
Managed services, implementation packs, support tiers
Named offerings with scope, capabilities, and rate data. Complementary to resale products — the matcher pairs them automatically.
Resource Roles
Sr. SAP Architect, Integration Lead, Functional Consultant
Rate-card roles with onsite / nearshore / offshore tiers, certifications, and years of experience. Used on single-resource RFPs and as staffing for service bundles.
How the RFP-to-catalog matcher works
A dedicated agent sits between qualification and strategy in the 9-agent pipeline. It answers the question capability matching can't: “what do we propose?”
1. Requirement indexing
Every extracted requirement gets a synthetic ID (M1, R1, C1, S1, G1) so the matcher can cite evidence precisely.
2. Engagement routing
The matcher uses the RFP’s engagement classification (product / consulting / single resource) to shortlist eligible catalog kinds.
3. LLM scoring
Each candidate item is scored 0–50–100 with matched requirement IDs, unmatched gaps, and a one-line rationale.
4. Deterministic bundle
Scored items are partitioned into Primary / Complementary / Optional by fixed score floors and caps. No LLM coin-flips.
Primary. Complementary. Optional.
Every bundle fits on one screen. No 12-item kitchen sinks.
Primary
The single offering that anchors the proposal. Engagement-type-aware — product RFPs get a resale or IP primary; consulting RFPs get a service or accelerator.
Complementary
Items that reinforce the primary and extend requirement coverage. Think: the accelerator + the managed-services wrapper that makes the primary deliverable.
Optional
Upsell candidates worth mentioning as add-ons — not core to the win, but surface-worthy for account growth.
Coverage gaps are first-class
Any RFP requirement no item in the bundle addresses appears as a coverage gap. These feed directly into the strategy and gap-analysis agents — they become either clarifying questions to the customer or flags for partner / subcontractor coverage. Nothing falls through the cracks.
Built for SAP partners and multi-offering SIs
Generic proposal tools treat catalog matching as a stretch feature. For SAP partners, it's the whole game.
Your IP never gets forgotten
If you’ve built a procurement accelerator, it appears on every procurement RFP. The matcher guarantees it. Solution architects can’t miss what’s in the catalog.
Right-size the bundle every time
The Primary / Complementary / Optional split forces the tight pitch. No diluting margin with kitchen-sink proposals.
Evidence-grade traceability
Each match card shows which RFP requirements the item satisfies, by ID, with evidence phrases. Strategy and content agents pull from the same map.
Overrides survive re-runs
Promote a SKU from Optional to Primary. The override persists across pipeline re-runs — strategy picks it up on the next generation.
Plan-limit generous
25 items on Starter, 500 on Business. Enough to cover a real SAP partner’s catalog without artificial ceiling.
SAP seed import on the roadmap
Phase 3 ships a curated ~300-SKU SAP seed (BTP, S/4HANA, Ariba, SuccessFactors, Concur, BN, DataSphere, SAC, Signavio, LeanIX) as one-click import for Business tenants.
Manual catalog + LLM matcher
- Add, edit, archive, and reactivate items across all four kinds
- RFP-to-catalog matcher runs automatically after qualification
- Three-column Solution Bundle view with coverage gaps and rejected audit
- User overrides survive pipeline re-runs
- Plan limits: 25 items Starter, 500 Business
Auto-extract + SAP seed
- Taxonomy agent auto-populates catalog from KB uploads (Phase 2)
- Hybrid catalog retrieval — semantic + keyword (Phase 2)
- Curated SAP SKU seed — one-click import, Business tier (Phase 3)
- Bundle-aware strategy and content prompts (Phase 3)
- Drag-to-reassign match review UI (Phase 3)
Populate your catalog this afternoon.
Start with your 10 most commonly pitched offerings. Run one recent RFP through the pipeline. Compare the matcher's bundle against what your team would have proposed — and tune from there.