Run the close calendar, check dependencies and gates, chase owners, assemble evidence and report status — with cut-off rules, evaluation, audit trails and a named human signing every task.
A close that lands on time can hide concentrated risk
Aggregate close performance can look acceptable while a small number of task cohorts carry most of the gate breaches and nearly all of the adjustments booked after sign-off. Nestack reports performance by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Multi-entity intercompany tasks
5.1%
3.3×
Review
Foreign-currency revaluation tasks
3.9%
2.5×
Review
Re-opened and adjusted periods
2.9%
1.9×
Watch
Steady-state single-entity tasks
1.1%
0.7×
Normal
Bar: lift vs. steady-state baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
Each breach becomes a standing gate check
The close repeats every month, so each cycle is a dated test of the last one's fix — a breach found in one period becomes a check the next one has to pass.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Gate breaches, late tasks or post-close adjustments rise in a cohort.
02Diagnose
Traced to a stale dependency, a gate rule, an evidence source or the owner routing.
03Improve
The dependency, gate rule or threshold is re-approved by the controller and version-linked.
04Verify
The change is re-run against the recorded state of the close that failed.
05Learn
That breach becomes a standing check and the calendar change enters the runbook.
Learn → DetectThe return edge. Next month's close is measured against every gate the last one failed.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, calendar and gates, agent workflow, evaluation, then a shadow close and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Close-calendar and dependency-map discovery.
02ERP, sub-ledger and close-tool API assessment.
03Gate, evidence and threshold definition.
04Task, owner and period-state ingestion.
05Dependency and cut-off checking logic.
06Confidence scoring and exception routing.
07Chase, escalation and notification workflow.
08Human review and sign-off workflow.
09Guardrails, period-lock and approval controls.
10Evaluation suite and regression closes.
11Status reporting and close-pack preparation.
12Observability, deployment 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 entity, one closeProductionProduction integrationAdvancedMultiple entities / systems
Introduced at Pilot
Readiness and gate checks✓✓✓
Human sign-off✓✓✓
Baseline evaluation✓✓✓
Introduced at Production
Dependency and cut-off logic—✓✓
Evidence collection and linking—✓✓
Owner chasing and escalation—✓✓
Approved status write-back—✓✓
Observability and evaluation—✓✓
Introduced at Advanced
Intercompany and revaluation gates——✓
Multi-entity consolidation close——✓
Enterprise controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on entity count, ERP and close-tool integrations, calendar and gate complexity, 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 close calendar, task list and named owners→Close-calendar and dependency-map discoveryWeek 1
02Gate definitions, evidence requirements and thresholds→Gate, evidence and threshold definitionWeek 1
03Access to the ERP, sub-ledgers and close tooling→API assessment, then task, owner and period-state ingestionWeek 2
04The dependency order between tasks and sub-ledgers→Dependency and cut-off checking logicWeek 2
05Materiality thresholds and period-lock policy→Guardrails, period-lock and approval controlsWeek 4
06Recent closes, including one that ran late→Evaluation suite, regression closes and failure-mode testingWeek 4
07Named preparers, reviewers and the controller→Sign-off workflow, then a shadow close and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. The close runs once a month, so week 5 is timed to land on a real one.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Close-calendar mapping, dependency order and the automation boundaryW2ERP, sub-ledger and close-tool ingestion, and the readiness baselineW3Gate checks, confidence logic and the chase and escalation workflowW4Evaluation suite, period-lock guardrails and failure-mode testingW5Shadow run against a live close, reporting status but writing nothingW6Approved write-back, production validation and Agent Care handover
Reading the bandBars span only the weeks their work is named in. Evaluation and the shadow close genuinely overlap in week 5.
At the end of W6One month-end close has run in shadow and been checked task by task, then Agent Care takes over monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks, sequenced so the shadow run lands on a live close.
Next step · Accounting AI agent
Build a close orchestration agent around your close calendar.
Show us your close calendar, the dependency order between tasks and the gate each one has to clear. We'll walk the calendar task by task, agree which gates the agent may check and start where the close stalls.
