Customer-project P&L: see true margin (and cost of goods)
Average margin lies. It hides customers and projects that destroy value while others carry the company. This guide explains how to build P&L by customer and by project — with a real cost of goods — so commercial and finance leadership decide on facts.
The average-margin problem
When the committee only sees blended margin, loss-making accounts survive for whole quarters. Sales chase volume; ops absorb complexity; finance finds the hole at close. Customer-project P&L flips the script: every account and every engagement carries its revenue, direct costs, and a realistic share of shared costs.
Language matters: we mean cost of goods / cost of sales (materials, labour, subcontracting, direct costs) — the operational truth behind contribution, not a vague “cost of revenue” slogan.
From ERP to actionable P&L
Your ERPs (Dynamics 365 Business Central, QuickBooks, Sage 50, Acomba, and others) already hold much of the truth — but split across billing, work orders, inventory, and timesheets. A warehouse or consolidated marts align recognized revenue, cost of goods, and time by project.
Without that layer, every leader recalculates “their” margin in Excel. With it, the cockpit shows top / bottom accounts each month, and AI can flag drift (margin under threshold for three weeks, four orders driving it).
Cost of goods: what to actually track
In manufacturing and project services, cost of goods combines materials, standard vs actual labour, subcontracting, and variances. Quarter-end surprises often come from variances not watched in-period. Thresholds on cost of goods by line, plant, or project let you act while time remains.
- Recognized revenue by customer / project (not only billed)
- Direct costs: materials, labour, subcontracting
- Standard vs actual variances on cost of goods
- Contribution after explicitly defined shared costs
Decisions P&L unlocks
Pricing and discounts: stop burning structurally loss-making accounts. Service load: align support with real contribution. Commercial priorities: push segments that create margin, not only revenue. Capacity trade-offs: choose projects that maximize contribution under constraint.
These decisions are executive decision support — the core of the Génosa offer — far more than email automation.
Realistic rollout
Do not aim for analytic perfection on day one. Start with the 20% of customers that represent 80% of revenue or risk. Validate definitions with finance and ops. Then industrialize via marts and cockpit. A free AI diagnostic often clarifies in one session which dimensions (customer, project, product family) are worth the effort.
Three-wave rollout
Wave 1: top customers by revenue and by internal complaint — often 15 to 30 accounts. Compute simplified contribution (recognized revenue minus direct costs). Wave 2: projects with timesheets and subcontracting. Wave 3: shared-cost allocations only once waves 1 and 2 are credible.
This discipline avoids six months debating overhead keys while loss-making customers keep getting white-glove service. Cost of goods by line or project should enter early for manufacturers: that is where material and labour variances silently eat margin.
Margin data governance
Who may see customer P&L? Often GM, finance, and senior sales — not the whole company on day one. Who may correct a cost imputation? A clear owner (controller, project lead) with an audit trail. AI that explains a variance must cite the same definitions as the cockpit, or you recreate the Excel problem in natural language.
Then tie pricing, discounts, and service load to bottom accounts. That is the real use of P&L: to decide, not only to observe.
Link to the Génosa diagnostic
The free AI diagnostic (60–90 minutes) chooses the grain (customer, project, family, plant) and estimates foundation effort. We do not start with an academic costing model; we start with decisions the committee wants to make next quarter in Montréal or elsewhere in Québec.
Frequently asked questions
How is this different from a sales report?
Sales reports show revenue; customer-project P&L shows contribution after cost of goods and direct costs — what the committee must trade off.
Do we need a data warehouse?
For a shared single truth, yes over time. You can prototype first, then harden foundations.
Do you work with Québec manufacturers?
Yes — cost of goods, material/labour variances, and contribution by line are common use cases.
Clarify your true margin
Book a free diagnostic to frame customer-project P&L and cost of goods.
Book a free diagnostic