The problem we were given
A partner or inbound lead was not a CRM row. Sellers needed install base, a fit, a valid configuration, a price, and a registered deal. That lived in several tools. Packs took days. Pricing and install-base cannot sit in a public prompt.
Can the pack be complete, priced against policy, and still blocked from writing to CRM until a named seller submits?
What our engineers built
An orchestration on Foundation, with named specialists and a hard stop before any system of record is written.
Normalise the lead. Retrieve install base. Recommend fit against the catalog. Configure a valid bill of materials. Price against policy, not against a guessed discount. Draft the proposal pack. Hand off for deal registration.
Every tool call goes through the Model Gateway. Policy and DLP sit in the path. Nothing silent-posts to CRM or CPQ. A named seller submits. Commercial paper on the lead is read in place so nobody is typing from a screenshot.
What it is not
It is not a chatbot on the partner portal. It does not invent list price. It does not register the deal by itself.
Why the cloud answer fails here
Install-base, discount matrices and partner pricing are competitive. They cannot sit in a vendor-cloud prompt. Consequential writes into CRM or CPQ need a named approver, not a side door.
Controls in this workflow
These controls run on Private AI Foundation. Every ask goes through the same path.
- Work stays inside the customer perimeter. Inference does not require a network path out.
- You hold the encryption keys in every tier that touches your data.
- Every ask goes through the Model Gateway. There is no side door to a public model.
- Policy and DLP evaluate the request before weights run.
- RBAC names who may invoke which model class on which data class.
- Each step writes confidence and a citation back to the source. Originals are preserved.
- Consequential actions wait for a named approver. Nothing silent-posts to your core systems.
- Immutable audit is written on the same install: who, what, which model, which policy, outcome.
- Apache 2.0 and MIT weights only. Licence text and an SBOM ship on disk per release.
The paid proof of value
Thirty to forty-five days. Fixed fee. In the customer environment. One product family, one region: lead in, complete priced pack out. Success criteria and conversion price agreed in writing before starting.
Measured against a human sales engineer on accuracy and time-to-first-complete-pack, with zero unapproved writes. If it misses the threshold, the customer keeps the report and owes nothing further.