Plan-versus-actual workflows grounded in the same model history used for forecasting.
Built for FP&A workflows
What variance analysis gives your team
Bridge Town is the versioned product layer beneath your AI agent: model storage, collaboration, run outputs, and review history that agents and finance teams can both understand.
Source data and model outputs kept together for review.
Agent-assisted investigation of the drivers behind material movement.
Versioned explanations that can be revised without losing the original context.
How it works
Variance workflow
- 1
Load actuals and the relevant plan version into the project.
- 2
Ask your agent to identify the largest movements and inspect the driver logic.
- 3
Review the calculation path, output tables, and explanation draft.
- 4
Commit the accepted explanation with the model version that supports it.
Common use cases
Where teams use this page of the product
Budget versus actualsForecast bridgesDepartment spend reviewsBoard variance packs
Frequently asked questions
Product details
Can Bridge Town explain variances automatically?
Your own connected agent can inspect model state and draft explanations. Bridge Town provides the versioned data, model, and output surfaces the agent works against.
How does this differ from a spreadsheet variance tab?
The explanation remains connected to versioned model logic, source data, and run outputs rather than living as a separate static worksheet.
Connect your agent to Bridge Town
Start with a versioned workspace, then let your own MCP-compatible agent build, inspect, and revise the finance model with you.
Start Free