Moovila Project Profitability
Overview
For an MSP, projects are where margin quietly leaks: fixed-fee
onboardings that run long, migrations where labor exceeds the quote.
Moovila holds both sides of the calculation. Budget lines say what was
planned; tasks and time entries say what was spent.
All tools used here are read tier. No Moovila tool is admin-gated in
Conduit. Cost and rate data (payRate, hourlyCost,
fullyBurdenedCost) is visible to anyone granted the Moovila connection,
so treat the output as internal and keep it out of customer-facing
reports.
Anti-triggers
The three sources of numbers
| Source |
Tool |
What it gives |
| Budget lines |
moovila_project_budgets_get (one project) or moovila_project_budgets_list (all) |
totalBudgetAmount, allocatedCost, unallocatedCost, percentageCommitted, by category and costCode |
| Task rollups |
moovila_tasks_list_for_project or moovila_tasks_list |
totalBudget, totalActual, remainingBudget, workEstimate, laborActualSummary per task |
| Time entries |
moovila_time_entries_list |
totalHours, billableHours, payRate, billRate per entry |
Prefer task rollups for "is this project over budget": Moovila computes
totalActual against totalBudget per task, so a sum across the
project's tasks is the project's burn. Use budget lines to explain where
the budget sits (labor versus hardware versus subcontract) and time
entries when you need labor cost and revenue the rollups do not carry.
Per-project review
moovila_projects_get for the project header: organization,
projectValue, revenueType, dueDate, isComplete.
moovila_project_budgets_get for its budget lines. Sum
totalBudgetAmount; note lines with high unallocatedCost (budget not
yet assigned to work).
moovila_tasks_list_for_project, paging to the end. Drop isDeleted
tasks. Sum totalBudget, totalActual, remainingBudget.
- Burn = sum(
totalActual) / sum(totalBudget). Compare it with
completion: average percentageComplete weighted by totalBudget.
Burn well ahead of completion means an overrun is coming even if the
project is not yet over.
- For labor cost, page
moovila_time_entries_list with a
lastChangedDate at or before the project start, keep entries whose
projectID matches, and sum totalHours x payRate. Where payRate
is empty, resolve the user's resourceTypeID via
moovila_labor_types_list and use fullyBurdenedCost.
- Revenue: for fixed-fee projects use
projectValue; for time and
materials, sum billableHours x billRate.
- Margin = revenue minus costs. Time entries carry labor only, so add
hardware and subcontract actuals when you can identify them without
counting labor twice. If you cannot, call the result labor-only
margin, not total profit.
Cross-customer roll-up
For "which projects are losing money" across the portfolio, avoid one call
per project:
- Page
moovila_projects_list once; keep active and recently completed
projects, excluding isTemplate and isDeleted.
- Page
moovila_tasks_list once and group by projectID.
- Page
moovila_project_budgets_list once and group by projectID.
- Compute burn and completion per project, then group by
organization.name (fall back to customer.name when the tenant
leaves organization empty).
Over budget is not the same as losing money: a fixed-fee project can
overrun its budget and still make a margin. For "which projects are
losing money", rank by margin (revenue minus actual cost, as in steps 5-7
above), lowest first, and say whether it is labor-only. For "which
projects are over budget", rank by overrun amount (sum totalActual minus
sum totalBudget), not by percentage, so a large overrun on a big project
outranks a small one on a tiny project.
Report shape
Customer Project Budget Actual Burn Complete Flag
Acme Server refresh 12,000 13,450 112% 85% Over budget
Globex M365 onboarding 6,500 4,100 63% 40% Burning ahead of progress
Follow with the top three overruns, the task or budget category that drove
each, and the owner from ownerUser.
Gotchas
- Budget and actual units follow the
budgetMethod on each line (hours
versus currency). Do not add an hours line to a currency line; group by
method first.
projectValue can be empty on time and materials projects. Say so
instead of reporting zero revenue.
- Time adjustments (
timeEntryType 2) can be negative. Include them, or
labor cost is overstated.
- Moovila may already push actuals to the PSA. A project that looks
over budget here can be under a PSA change order; ask before calling it
a loss.
1---2name: moovila-project-profitability3description: >4 Budget versus actual for MSP projects in Moovila: reading project5 budget lines (total, allocated, unallocated, percentage committed),6 task-level totalBudget/totalActual/remainingBudget, labor cost from time7 entries at pay rate or labor type fully burdened cost, revenue from8 billable hours at bill rate or projectValue, and rolling these up to a9 per-project and per-customer margin view.10when_to_use: >-11 When reviewing whether projects are on budget or profitable, preparing12 a project post-mortem, or comparing fixed-fee projects across13 customers. Use when: moovila budget, project over budget, project14 margin, project profitability, budget burn, fixed fee project review,15 cost overrun, or "which projects lost money".16metadata:17 source: https://skillmd.com/skills/wyre-ai/moovila-project-profitability18---1920# Moovila Project Profitability2122## Overview2324For an MSP, projects are where margin quietly leaks: fixed-fee25onboardings that run long, migrations where labor exceeds the quote.26Moovila holds both sides of the calculation. Budget lines say what was27planned; tasks and time entries say what was spent.2829All tools used here are read tier. No Moovila tool is admin-gated in30Conduit. Cost and rate data (`payRate`, `hourlyCost`,31`fullyBurdenedCost`) is visible to anyone granted the Moovila connection,32so treat the output as internal and keep it out of customer-facing33reports.3435## Anti-triggers3637- **Schedule and lateness** - use38 [project-health](../project-health/SKILL.md).39- **Whether individual time entries were billed correctly** - use40 [time-reconciliation](../time-reconciliation/SKILL.md).4142## The three sources of numbers4344| Source | Tool | What it gives |45|--------|------|---------------|46| Budget lines | `moovila_project_budgets_get` (one project) or `moovila_project_budgets_list` (all) | `totalBudgetAmount`, `allocatedCost`, `unallocatedCost`, `percentageCommitted`, by `category` and `costCode` |47| Task rollups | `moovila_tasks_list_for_project` or `moovila_tasks_list` | `totalBudget`, `totalActual`, `remainingBudget`, `workEstimate`, `laborActualSummary` per task |48| Time entries | `moovila_time_entries_list` | `totalHours`, `billableHours`, `payRate`, `billRate` per entry |4950Prefer task rollups for "is this project over budget": Moovila computes51`totalActual` against `totalBudget` per task, so a sum across the52project's tasks is the project's burn. Use budget lines to explain where53the budget sits (labor versus hardware versus subcontract) and time54entries when you need labor cost and revenue the rollups do not carry.5556## Per-project review57581. `moovila_projects_get` for the project header: `organization`,59 `projectValue`, `revenueType`, `dueDate`, `isComplete`.602. `moovila_project_budgets_get` for its budget lines. Sum61 `totalBudgetAmount`; note lines with high `unallocatedCost` (budget not62 yet assigned to work).633. `moovila_tasks_list_for_project`, paging to the end. Drop `isDeleted`64 tasks. Sum `totalBudget`, `totalActual`, `remainingBudget`.654. Burn = sum(`totalActual`) / sum(`totalBudget`). Compare it with66 completion: average `percentageComplete` weighted by `totalBudget`.67 Burn well ahead of completion means an overrun is coming even if the68 project is not yet over.695. For labor cost, page `moovila_time_entries_list` with a70 `lastChangedDate` at or before the project start, keep entries whose71 `projectID` matches, and sum `totalHours` x `payRate`. Where `payRate`72 is empty, resolve the user's `resourceTypeID` via73 `moovila_labor_types_list` and use `fullyBurdenedCost`.746. Revenue: for fixed-fee projects use `projectValue`; for time and75 materials, sum `billableHours` x `billRate`.767. Margin = revenue minus costs. Time entries carry labor only, so add77 hardware and subcontract actuals when you can identify them without78 counting labor twice. If you cannot, call the result labor-only79 margin, not total profit.8081## Cross-customer roll-up8283For "which projects are losing money" across the portfolio, avoid one call84per project:85861. Page `moovila_projects_list` once; keep active and recently completed87 projects, excluding `isTemplate` and `isDeleted`.882. Page `moovila_tasks_list` once and group by `projectID`.893. Page `moovila_project_budgets_list` once and group by `projectID`.904. Compute burn and completion per project, then group by91 `organization.name` (fall back to `customer.name` when the tenant92 leaves `organization` empty).9394Over budget is not the same as losing money: a fixed-fee project can95overrun its budget and still make a margin. For "which projects are96losing money", rank by margin (revenue minus actual cost, as in steps 5-797above), lowest first, and say whether it is labor-only. For "which98projects are over budget", rank by overrun amount (sum `totalActual` minus99sum `totalBudget`), not by percentage, so a large overrun on a big project100outranks a small one on a tiny project.101102## Report shape103104```105Customer Project Budget Actual Burn Complete Flag106Acme Server refresh 12,000 13,450 112% 85% Over budget107Globex M365 onboarding 6,500 4,100 63% 40% Burning ahead of progress108```109110Follow with the top three overruns, the task or budget category that drove111each, and the owner from `ownerUser`.112113## Gotchas114115- Budget and actual units follow the `budgetMethod` on each line (hours116 versus currency). Do not add an hours line to a currency line; group by117 method first.118- `projectValue` can be empty on time and materials projects. Say so119 instead of reporting zero revenue.120- Time adjustments (`timeEntryType` 2) can be negative. Include them, or121 labor cost is overstated.122- Moovila may already push actuals to the PSA. A project that looks123 over budget here can be under a PSA change order; ask before calling it124 a loss.