Why project finance still hides in spreadsheets
Most CFOs inherit a patchwork: ERP for payroll, billing for revenue, and delivery teams tracking costs in slides. By the time finance reconciles, the team already committed to scope that no longer fits the budget.
Project finance data belongs inside the same workspace where tasks, packages, and approvals live. When ledger entries sit next to work breakdown, leaders can ask sharper questions early — not after a variance report lands in email.
Symptoms and cost of ignoring delivery-aligned finance
You know finance visibility is broken when:
- PMs report "green" while contractor spend on one package is 20% over plan with no tagged entries.
- Executives debate headcount using velocity charts, not cost-per-delivered-milestone.
- Approvals queue up because nobody knows if the change order is funded.
- Audit asks for project-level spend and the answer is a folder of emailed PDFs.
The cost is not only overrun — it is slow decisions. CFOs who see money beside work can freeze scope, re-phase hiring, or accept overrun with a named owner before the quarter closes.
A seven-step weekly CFO brief framework
Use this rhythm every Monday or before your leadership slot:
- Pull portfolio finance_summary — income, expense, net by project and rolling 30-day window.
- Run executive_brief with role=cfo — ranked hypotheses on variance with explicit data gaps.
- Cross-check one delivery signal — aging WIP, blocked approvals, or overdue milestones on the same project.
- Map variance to work packages — "Integration +18%" beats "Project 14 misc +18%."
- Name three decisions — each with owner, timing, and expected impact on burn or margin.
- Log the decision via log_decision or decision_inbox so next week can calibrate forecasts.
- Close the loop with PMs — five-minute package closeout ritual: confirm entries, attach invoice reference, mark complete.
This framework takes 30–45 minutes once finance tags and package structure exist. Week one is setup; week four is habit.
What a useful CFO brief actually contains
A CFO brief is not a 40-slide deck. It answers:
| Question | Where in WKFGo |
|---|---|
| Which projects burn faster than planned? | finance_summary by project |
| Where does revenue lag delivery? | finance entries vs milestone dates |
| Which cost categories trend up? | Tagged expense lines by category |
| What needs a signature this week? | decision_inbox + pending approvals |
Pair finance_summary with delivery signals and the brief becomes actionable, not archival. If a field is empty, the brief should say so — honesty builds trust in AI-assisted workflows.
Anti-patterns to avoid
- Spreadsheet shadow systems — PMs maintain a "real" budget in Excel while the tool stays empty.
- Surveillance framing — finance visibility presented as monitoring individual task clicks instead of package health.
- Invented precision — AI or humans filling gaps with guessed numbers instead of calling out missing tags.
- Quarterly-only reviews — waiting for close when weekly 30-day windows would catch drift early.
- Finance without packages — flat task lists make variance impossible to explain to stakeholders.
How WKFGo supports finance-aware delivery
WKFGo keeps project finance beside Kanban, work packages, and approvals:
- finance_summary aggregates project-level entries without CSV export gymnastics.
- executive_brief (role=cfo) prioritizes ledger truth, cash-adjacent risks, and advice grounded in visible data.
- Work packages roll spend to deliverables executives recognize.
- Feature access hides sensitive ledger lines from contributors while executives get a single pane.
- import_finance_entries supports dry-run imports from Excel before committing.
- simulate_scenario can model cut_scope or delay_release against finance when trade-offs are real.
Demo accounts are read-only — fine for tours, not for real ledger decisions.
Governance without slowing delivery
Frame the CFO brief as early help:
- Shared cost category definitions before the project starts.
- Finance entries required at package close, not daily micro-entry.
- Read-only dashboards for stakeholders; write access for finance owners.
When finance_summary shows spend accelerating on a package with blocked tasks, name that correlation. Under-spend with rising completion may mean deferred hiring — a different conversation than overrun.
FAQ — AI CFO briefs and project finance
Does the AI replace our finance system?
No. WKFGo project finance complements ERP/accounting. It gives delivery-aligned visibility; your GL remains authoritative for statutory reporting.
Can we export for auditors?
Yes. Treat WKFGo as the operational layer; export summaries your policy requires.
What if our data is incomplete?
The brief should surface gaps. Incomplete tags are a process fix, not a reason to hide the dashboard.
How often should we run executive_brief for finance?
Weekly for active portfolios; bi-weekly for stable programs. Always use the same rolling window so trends compare apples to apples.