
Margin Guard compares each project with its plan, budget and invoices every morning. It shows how each amount was calculated, drafts the fix, and waits for your approval.
What happens to a finding, step by step.
Six checks review the plans, budgets, timesheets and invoices of every project. If an input is missing, the project is listed as not checked instead of reported as zero.
Every finding shows its formula in plain words, each input with its value, and the documents behind it, followed by the action KPilot suggests.
Lone Star was sold at a 28.0% margin and has used 395 of 300 planned days. Margin Guard drafts the change order with the raise, the extra days and the reason.
Each finding moves from found to approved, invoiced and collected. An unpaid invoice is not counted as collected.
Your team labels findings, and KPilot reports the precision of each check. Backtests show what Margin Guard would have found at past month ends.
Every Monday, each partner gets the findings for the projects they can see, with a link to every number.
Every day, as of the day before. An administrator can also run it by hand from Margin Guard runs.
No. It proposes. When a person accepts, KPilot creates an invoice request, which goes to finance for approval before anything reaches accounting.
What a run could not check is listed apart, with the input each one was missing: a budget, a billing period, a loaded cost.
Your team labels each finding as a leak, not a leak, or data cleanup. Margin Guard runs shows each detector’s precision on those labels, and backtests show what it would have found in past months.
The recipients chosen in the settings. Each brief covers only what that person may see, and briefs can be held for review first.
Start a 14-day trial, connect your books, and read your first brief on Monday.