RFx Creation.
From kickoff to publish in days, not weeks.
Leah ingests stakeholder requirements, prior RFx history, category benchmarks, and contract policy. She auto-generates the RFx package, routes for stakeholder review, and publishes to your sourcing platform.
Every RFx event is a six-week assembly project. It does not have to be.
RFx kickoffs delayed by stakeholder gathering
Sourcing managers chase requirements across business units for weeks before the first draft. Spec sheets sit in inboxes, scope creeps as new stakeholders join, and the event slips before any supplier ever sees a document.
Templates drift across categories
Every category lead keeps a personal master template. Over time the IT RFP, the facilities RFP, and the logistics RFP each evolve in different directions, with overlapping clauses, inconsistent structure, and no single source of truth.
Scoring criteria inconsistent across events
Weightings are set ad hoc, evaluation rubrics differ by drafter, and quantitative criteria are mixed with subjective questions. Award decisions become hard to defend and impossible to benchmark across categories.
Legal terms vary by drafter
Sourcing managers paste in T&Cs from prior events, and legal reviews each one from scratch. Approved fallback positions, jurisdiction-specific clauses, and the latest policy updates rarely make it into the document on the first cut.
Supplier shortlist built from memory
Invitations go to the suppliers the category manager remembers, not the suppliers the data supports. Performance history, diversity targets, and qualification status sit in separate systems that nobody opens during shortlisting.
Sourcing platform integration is manual
Once the package is approved, somebody copy-pastes the questionnaire, the criteria, and the supplier list into Coupa, Ariba, Jaggaer, or Keelvar. Errors slip in, version drift starts, and the platform becomes a publish-only tool.
Stakeholder requirements gathered without the chase
Leah runs the requirement intake for you. She opens a structured brief, prompts each stakeholder for the inputs that actually matter for the category, ingests technical specs and prior context, and reconciles conflicts before the package is ever drafted.
“The first week of every event used to be chasing stakeholders for inputs. Leah turned that week into an afternoon. By the time we sit down to draft, every requirement is already on the table.”
Director of Strategic Sourcing, Industrial Manufacturer
Five steps from kickoff to a published sourcing event
Leah works upstream of your sourcing platform. No rip and replace. Value from the first event you run.
Connect
Leah integrates with your CLM, ERP, supplier master, and sourcing platform. Templates, clause library, prior RFx events, and supplier performance data all flow into a single sourcing intelligence layer.
Capture Requirements
Stakeholders answer category-aware briefs. Specs, prior contracts, and benchmark data flow in. Conflicts are surfaced and resolved before drafting begins.
Generate RFx Package
Leah assembles questionnaire, scoring rubric, pricing schedule, and legal terms from approved templates and your clause library. Deviations are flagged with reasoning.
Route Approvals
Sourcing lead, legal, and category sponsors review only what changed or escalated. Approval chains run in parallel, not in sequence.
Publish to Platform
Once approved, Leah publishes the full package to your sourcing platform with questionnaire, criteria, supplier invitations, and timelines all configured.
Got Questions? Get Answers.
No. Leah operates upstream of your sourcing platform. Requirements, package generation, and approvals run in Leah, then she publishes the finished event into your platform. The platform remains the system of record for the live event, supplier responses, and award. There is no rip-and-replace, and your existing sourcing platform investment is preserved.
Leah ingests your approved templates, prior events, clause library, and category playbooks during onboarding. She also benchmarks against industry-standard structures for each RFx type. Over time she learns from every event you run, the criteria that drove award decisions, and the deviations your legal and sourcing leads accept. Every deployment compounds in quality.
Leah is built for non-standard sourcing. Engineering specs, statements of work, complex pricing models, and category-specific clauses all flow into the brief. Where stakeholder inputs are ambiguous or contradictory, Leah surfaces the conflict and routes the decision instead of guessing. Bespoke events still get faster, and the audit trail is stronger.
Yes. Leah generates a draft and sourcing managers retain full control to edit any section. Manual edits are tracked, and if they touch a clause from the approved library, the deviation is logged for legal visibility. The goal is to remove the blank-page problem, not the human judgment.
The shortlist is built from your qualification database, prior performance, certifications, and diversity flags. Every recommendation comes with reasoning visible to the sourcing lead, who can accept, swap, or add suppliers manually. Leah does not auto-publish a shortlist; she proposes one with full transparency. Final supplier selection always goes through your existing approval process.
Yes. Leah is deployed by major manufacturers, energy companies, and financial services firms with strict data security requirements. Sourcing data, supplier information, and contract clauses are not used to train Leah's underlying models. Customer data is encrypted in transit and at rest. SOC 2 Type II, GDPR, CCPA, and ISO 27001 aligned. Private instance deployment is available where data isolation is required.
