Build bids in power and gas from your own positions and forecasts, record why each order exists, check it against your configured limits — and hold it for an authorised trader to release.
4Controls appliedLimit checks, prohibited-pattern screens, cross-book review and confidence threshold
No human action required
Stages 1 to 4 run unaided and nothing reaches a market at any of them — the agent is building an order, and the trader's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to an authorised trader to release.
Low confidence
Picks up a surveillance read first.
Trader release
The order is held with its reason, its limit checks and the confidence.
Authorise · Amend · Send to surveillance review
Authorised — sent to market▼
6Trading systems updatedOnly where write access and release policy allow it
7Outcome evaluatedAmend rate, screen outcomes, fill quality and post-trade surveillance findings
Amends
Every trader amendment, and every post-trade query, is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Releasing an order into a power or gas market.
Declaring a unit unavailable or off automatic control.
Trading outside the limits configured for the desk.
Using data from outside the customer's own book.
Automation boundaryAgent acts unaided
✓Build a bid from the customer's own positions and forecasts.
✓Record why each order exists, in terms a trader can defend.
✓Run the proposed order against the limits configured for the desk.
✓Hold the order, with its reason and its limit checks attached for the named owner.
Nothing is released ahead of a trader — exposure accrues per violation, per day, and disgorgement sits on top of it.
Enabling a newly discovered trading strategy.
A loss on one leg justified by another book.
Orders whose only rationale is an allocation.
Changes to limits, thresholds or release rules.
Example output
One order, annotated
Everything the agent proposes is attached to the book it was built from.
Bidding output · single orderIllustrative example
Market
Proposed order
Volume
Reason on file
Confidence
Limit check
Day-ahead power
Offer at a single configured node, morning block
25 MW
Own generation position
91%
Inside desk volume and price limits
As receivedTaken from the desk's own positions and forecasts — nothing on this side is written by the agent.
Book evidence usedOwned unit positionOwn load forecastDesk limit set
Why this order existsIt sells a position the desk already holds and a person still decides.
ActionAuthoriseAmendSend to surveillance review
What the score decidesBelow the configured threshold the order picks up a surveillance read before a trader sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every proposed orderFrom the desk's own book
03Bid construction
Build from the book
Draw only on the customer's own positions, forecasts and desk limits — pooled or competitor data is out of scope by construction.
01Approved path
A pattern is not a strategy
Routine bids and offers arrive already built, with their reason attached.
02Human review
Send review where risk sits
Flagged patterns and low-confidence orders are marked, so the trader's read starts where exposure concentrates.
04Build an evidence trail
The bid, the position and signals behind it and the trader who released it stay on the order.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Base rates differ sharply by market and by product, so a single desk-wide amendment rate says very little about where the rework actually sits. Nestack reports the trader-amendment rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Virtual and financial products
9.6%
3.3×
Review
Cross-commodity positions
8.1%
2.8×
Review
Newly configured markets
4.9%
1.7×
Watch
Established power nodes
2.6%
0.9×
Normal
Bar: trader-amendment-rate lift vs. established-node baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
The loop closes on a case, not a view
Explaining a bad fill does not close the cycle. A standing regression case does, and that suite is what the next order sent out is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Trader-amendment rate rises in a market slice.
02Diagnose
If the cause is the inputs, the limits or the reasoning, orders are read with a trader until it narrows to one.
03Improve
The fix is versioned against the orders that produced it.
04Verify
The release stops until every affected case is passing.
05Learn
The case stays in the suite, and the trading limits are amended.
Learn → DetectThe return edge. The next detection runs 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, bidding workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Trading workflow discovery and boundary definition.
02Market, ETRM and data-source assessment.
03Desk limit, prohibited-pattern and market mapping.
04Position and market-data normalisation.
05Bid construction and reason binding.
06Confidence scoring and flag routing.
07Trader release workflow.
08Trading-platform and market integration.
09Intent and pattern cases.
10Guardrails and release controls.
11Order-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 market, one deskProductionProduction trading systemsAdvancedMultiple markets / entities
Introduced at Pilot
Bid construction from your book✓✓✓
Trader authorisation✓✓✓
Bid-quality baseline✓✓✓
Introduced at Production
Reporting by market and product—✓✓
Authorisation workflow in your systems—✓✓
Write-back to your trading systems—✓✓
Trading-platform integration—✓✓
Introduced at Advanced
Multi-market and cross-product rules——✓
Multi-stage desk approvals——✓
High order volume——✓
Multi-market trading controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction 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 book structure and position sources→Position and market-data ingestion and mappingWeek 1
02Representative historical orders→Bid-construction baseline and reason bindingWeek 2
03Your desk limits and prohibited patterns→Desk limit, prohibited-pattern and market mappingWeek 1
04Access to relevant APIs, feeds or exports→Market, ETRM and data-source assessment, then integration setupWeek 2
05Orders you would not want filled→Pattern cases and the evaluation suiteWeek 4
06Where an order must stop and wait for a trader→Confidence scoring, flag routing, guardrails and release controlsWeek 3
07Named authorised traders to release orders→Trader release 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
Phases occupy the weeks the work really needs, so week 5 runs evaluation and launch side by side.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Trading workflow discovery, limit mapping and the automation boundaryW2Source integration and the bid-construction baselineW3Bidding workflow, confidence logic and release controlsW4Evaluation suite, pattern screens and failure-mode testingW5Trading-platform integration, pilot orders and targeted correctionsW6One trading period run under the desk, then handover
Reading the bandA bar spans only the weeks its work is named in. Week 5 carries two because that is how it runs.
At the end of W6The period closes validation and Agent Care picks up the monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Energy AI agent
Build a trading agent around your desk's release chain.
Show us your book, your desk limits and who releases an order. Could you explain, months later, why each of yesterday's bids existed? That is the record we build and the boundary we set.
