Assemble quotes from your own price, lead-time and availability data, disclose the terms that travel with each line, and hold the quote for the named approver who decides whether it is issued.
Ingest the request, its line items and the account record from supported ERP, CPQ, portal or email sources.
02
Normalise each part to its full orderable number, and stop on a partial match rather than quoting a neighbour.
Reason
03
Price each line from the account's own contract price file and configured band, never from pooled or competitor data.
04
Read lead time and availability from the seller's own feeds, and carry the as-of timestamp onto the quoted line.
05
Attach the term set the account is configured for, stating NCNR, MOQ, standard pack and allocation status.
Decide
06
Run the restricted-party, end-use and destination screens configured for the seller against each party on the quote.
07
Stop the quote where a screen returns a hit, and route it to the named trade-compliance officer as a hard block.
Out
08
Retain the sources, the price basis, the screening result and the approver's amendments against the quote.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent assembles the quote; a named approver decides whether it is issued — and a seller who advertised full autonomy has conceded the risk of its own pricing errors.
Example workflow
One quote, request to issue
AgentHuman
1Request receivedRFQ email, ERP quote request, CPQ record or customer portal
2Sources assembledContract price file, availability feed, lead-time basis and account terms, each timestamped
3Quote draftedLine pricing, lead time, attached terms and confidence
4Controls appliedBand checks, term-set checks, configured party and destination screens, and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is issued at any of them — the agent is assembling, and the desk's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the sales desk to approve.
Low confidence
Adds a pricing-manager read first.
Sales-desk approval
The quote is held with its sources, its flagged lines and the confidence.
Approve · Amend · Send to compliance review
Approved — released to issue▼
6ERP and CPQ updatedOnly where write access and approval policy allow it
7Outcome evaluatedAmendment distance, flagged-line outcomes, screening stops and post-issue corrections
Amendments
Every approver amendment is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Issuing the quote to the customer.
Accepting the buyer's purchase-order terms.
Pricing outside the configured band.
Releasing anything a screening hit stopped.
Automation boundaryAgent acts unaided
✓Assemble the quote from your own price and availability data.
✓Carry each figure forward with its source and timestamp.
✓Apply the configured price band and standard term set.
✓Flag the lines the desk should weigh, and hold the quote for it.
Any write happens inside the boundaries agreed at implementation, never ahead of the approver.
Promising a lead time or an allocation.
Waiving NCNR, MOQ or standard-pack terms.
Classifying a part or deciding a licence.
Changes to the band, terms or screening rules.
Example output
One quoted line, annotated
Everything the agent assembles is attached to the source it was drawn from.
Quote output · single lineIllustrative example
Customer
Quoted line
Quantity
Price basis
Confidence
Terms attached
Contract manufacturer
Power connector, full orderable part number, tape and reel
2,500 pcs
Account contract price file
93%
Seller terms, NCNR stated
As receivedRead from the seller's own price file and availability feed — nothing on this side is priced by the agent.
Across a quarter the amendment rate reads low, because the accounts carrying it are the fewest — new customers, quoted once, with no pricing history behind them. Nestack reports the rate by slice.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
New accounts with no pricing history
4.8%
3.7×
Review
Allocated and long-lead parts
2.9%
2.2×
Review
Non-standard terms or pack sizes
2.0%
1.5×
Watch
Repeat lines on a current price file
1.0%
0.8×
Normal
Bar: amendment-rate lift vs. the repeat-line baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends in the suite, not the post-mortem
The cycle does not end in a post-mortem. It ends in a case the next release has to clear, and that suite is what the next quote out is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Amendment rate rises in one quote slice.
02Diagnose
If the rise holds a second week, a quote-desk manager reads back through the quotes and the price basis behind each until one cause is left.
03Improve
Each change carries a version and the quotes that forced it.
04Verify
Release waits on the affected cases going green again.
05Learn
The case is kept for good, and the quoting rules are rewritten around it.
Learn → DetectThe return edge. The next detection is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, quoting workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Quoting workflow discovery and boundary definition.
02ERP, CPQ and price-file assessment.
03Price-band, term-set and screening-configuration mapping.
04Request ingestion and part normalisation.
05Pricing logic and price-basis binding.
06Confidence scoring and exception routing.
07Sales-desk approval workflow.
08ERP and CPQ integration.
09Price and term regression cases.
10Guardrails and approval controls.
11Quote-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne price file, one deskProductionProduction ERP and CPQAdvancedMultiple entities / regions
Introduced at Pilot
Assembly from your own sources✓✓✓
Approver sign-off✓✓✓
Quote-accuracy baseline✓✓✓
Introduced at Production
Reporting by customer tier—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
ERP and CPQ integration—✓✓
Introduced at Advanced
Multi-entity price and term rules——✓
Multi-stage desk approvals——✓
High quote volume——✓
Multi-entity quoting controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, quote volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your contract price files and account term sets→Price-file ingestion and band mappingWeek 1
02Representative quotes you have already issued→Quoting baseline, price-basis binding and term attachmentWeek 2
03Your standard terms and your non-offer legend→Term-set, band and screening-configuration mappingWeek 1
04Access to relevant APIs, feeds or exports→ERP, CPQ and availability-feed assessment, then integration setupWeek 2
05Quotes you would not want honoured→Term cases and failure-mode testingWeek 4
06What a quote may never commit on its own→Confidence scoring, screening configuration, guardrails and approval controlsWeek 3
07Named approvers on the sales desk→Sales-desk approval workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The bands sit on the weeks the work occupies, which is why the fifth carries two kinds at once.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Quoting workflow discovery, term mapping and the automation boundaryW2Source integration and the quoting baselineW3Quoting workflow, confidence logic and approval controlsW4Evaluation suite, screening configuration and failure-mode testingW5ERP and CPQ integration, pilot quotes and targeted correctionsW6One quoting cycle assembled under the sales desk, then Agent Care handover
Reading the bandEach bar covers only the weeks its work is named in. The week 5 overlap is real work, not padding.
At the end of W6The cycle closes the validation and Agent Care takes over monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Electronics AI agent
Build a quoting copilot around the desk that already signs your quotes.
Show us your price files, your availability feeds and the terms that travel with a quote. Who is allowed to issue one outside the band today, and would you know afterwards if they had? We'll set the band, wire the screens and leave the issuing where it already sits.
