01
Add what you have
Start from a project file, estimate, bid tab, budget, feasibility assumption, or historical record.
How it works
Keep project numbers tied to the decision behind them.
Beacon is the review layer teams use before carrying project financial numbers forward. It keeps the number, source evidence, caveats, and next action in one record.
02
Connect what changed
Review the number beside evidence, caveats, scope movement, budget basis, economics pressure, and open questions.
03
Carry the decision record
Move forward with a clearer basis, a visible next action, and the notes the team needs before commitment.
Before
Project finance decisions live in scattered files.
Feasibility in one model.
Bid tabs in another spreadsheet.
Scope and assumptions buried in emails and meeting notes.
The team argues over what changed and which number still works.
With Beacon
The financial story stays with the number.
See cost, scope, timing, funding, and business-case movement together.
Compare scenarios before choosing what to carry forward.
Level bids before treating prices as comparable.
Turn reviewed actuals into support for the next decision.
Project path
One financial path, six review moments.
01 / Feasibility
Does it still work?Test early cost, scope, timing, funding, revenue, or business-case assumptions before one path hardens.
02 / Scenario Review
Compare the tradeoffsCompare cost, scope, timing, funding, ROI, margin, and revenue impact before choosing what to carry forward.
03 / Budget Carry
Carry one numberKnow which estimate, scenario, or budget number the team is taking into the next meeting or approval.
04 / Bid Leveling
Compare bids cleanlyLevel exclusions, alternates, allowances, and scope gaps before treating submitted pricing as comparable.
05 / Project Economics
See the deal impactConnect budget movement and bid exposure to ROI, margin, revenue, funding, debt, schedule, and approval pressure.
06 / Closeout Learning
Use what happenedTurn reviewed actuals and closeout lessons into better support for the next project decision.
Review posture
Clear support, not automatic approval.
Beacon helps the team keep evidence, caveats, and next actions findable before a number becomes the basis for funding, award, or approval.
Source notes stay attached
Files, assumptions, caveats, and next actions stay near the number the team is carrying.
Human review stays in charge
Beacon flags what needs support. It does not certify, approve, or replace the team decision.
Company records stay scoped
Review records are organized around your company workspace and the teams who need access.
See when teams use Beacon.
Use cases show where Range Check, Scenario Review, Budget, Bid Review, Economics, and Closeout fit in the real project path.