commit
07a41ebd97
1 changed files with 138 additions and 0 deletions
@ -0,0 +1,138 @@ |
|||||
|
<br>Project profitability tracking for design agencies tells you whether each client engagement earns its keep, while a P&L shows whether the whole business made money in a period. Choose by the decision in front of you. Pricing and client selection need project-level tracking, and cash planning for next quarter starts with the P&L.<br> |
||||
|
|
||||
|
What a P&L tells a design agency, and what it hides |
||||
|
<br>A profit and loss statement lists revenue, the direct cost of delivering work and operating expenses for a period, and it ends with a net result. For a design studio, the revenue line reflects either the work completed or the invoices issued, depending on how the books are kept. Designer and project manager salaries, freelancers, software subscriptions, rent and insurance all sit below it. Lenders and investors usually ask for this report first, so you should expect to keep it anyway.<br> |
||||
|
|
||||
|
<br>What the P&L does not show is which client carried the month. Two projects can both be billed in March, and one can be solidly profitable while the other loses money on hours alone. The statement adds them together, so the good work covers the weak work and nobody sees the gap. That is not an error in the report. It is what a period summary is built to do.<br> |
||||
|
|
||||
|
<br>In practice, a P&L averages across clients, and averages are easy to misread. A good quarter can hide a fixed-fee identity project that used far more hours than it was quoted. A weak quarter can come from a retainer that will pay off once a large deliverable is accepted in the next period. Owners often treat the P&L as a verdict on the whole studio, when it is closer to a forecast for the company as a whole.<br> |
||||
|
|
||||
|
<br>Here is the catch: the statement can look healthy while the studio quietly loses money on part of its work. If three of your ten active clients consume most of the senior designers' time at low rates, the total can still be positive because two large brand projects carried the year. That is a pricing and staffing problem, and the P&L will not name it. You need a view that points to the work itself.<br> |
||||
|
|
||||
|
<br>The P&L also lags. It reflects what has already happened, usually after a monthly close. By the time a project overrun reaches the statement, the hours have been spent, the client has been invoiced under the original plan, and your options are narrower. The P&L is good at telling you where you ended up. It is poor at telling you where an open job is heading.<br> |
||||
|
|
||||
|
Choosing between the two by the decision you need to make |
||||
|
<br>Start with the decision, not the report. Most owners who ask whether to track projects are really asking one of a few questions: which kinds of work to price higher, which clients to decline or renegotiate, whether a new hire pays for itself, or whether the studio can afford to borrow for working capital. Each question calls for a different level of detail. Naming the decision first keeps you from building a system that answers the wrong question.<br> |
||||
|
|
||||
|
<br>Project profitability tracking answers questions about a unit of work: one engagement, one client, or one service line such as packaging or web design. It asks what the work cost in hours and direct costs, what it billed, and what it will cost to finish. A P&L answers questions about the business over a period: whether revenue covered costs, how cash moved, and whether the studio can carry its fixed expenses. Both are honest. They simply measure different things.<br> |
||||
|
|
||||
|
|
||||
|
|
||||
|
AttributeProject profitability trackingProfit and loss statement |
||||
|
|
||||
|
|
||||
|
Question it answersDid this engagement make money, and why?Did the business make money this period? |
||||
|
Level of detailSingle client, project or service lineWhole company, usually by month or quarter |
||||
|
Main inputsLogged hours, direct costs, billing, budget and forecast to completeRevenue, cost of services and operating expenses from the ledger |
||||
|
Typical timingWeekly or biweekly while work is openAfter each monthly close |
||||
|
Main blind spotOverhead and fixed costs, unless they are allocated on purposeWhich clients and services drive the result |
||||
|
|
||||
|
|
||||
|
|
||||
|
<br>For a small studio, the honest answer is usually both, but the order depends on the question. If pricing is the pressing problem, build the project view first, because it will show which work is underpriced before the books do. If cash is the pressing problem, start with the P&L and a cash forecast, because a profitable project can still leave you short when payments arrive late. Do not wait for a perfect system before you choose.<br> |
||||
|
|
||||
|
<br>There is a useful test. Ask which decision you would make differently depending on the answer. If the number would not change what you do this month, you probably do not need it yet. If a lower margin on one client would make you renegotiate the scope or raise the rate, the project view earns its place. This sounds obvious, but many studios collect data they never use.<br> |
||||
|
|
||||
|
<br>The criterion also helps at the owners' table. One partner says the studio is fine because the bank balance is healthy. Another says the logo project lost money and should not be repeated. They can both be right. The bank balance speaks to the business, and the logo project speaks to one kind of work. Separating those two claims lets the group decide without talking past each other.<br> |
||||
|
|
||||
|
<br>The criterion also changes as the studio grows. A studio with a few long engagements may rely on project reviews for almost every decision. A larger shop with many small jobs and a stable retainer base may lean on the P&L and a work-in-progress report. The method should follow the business, not the other way around.<br> |
||||
|
|
||||
|
Mistake one: treating the fixed fee as the margin |
||||
|
<br>The most common error is simple. A studio quotes a fixed fee, estimates the work in hours, and then assumes the difference between the fee and a rough internal cost is the profit. On paper the project looks healthy. Nobody checks the hours until the work is nearly finished, and by then the margin has already moved. The fee is a price, not a result.<br> |
||||
|
|
||||
|
<br>Here is a hypothetical example. A studio sells a packaging design for a fixed fee and plans 60 hours across a senior designer and a project manager. Revisions, a late change to the product name and two extra calls push the actual hours to 85. The client pays the same fee. The P&L shows the revenue and the salaries in the right months, but nothing in the statement says that this one project absorbed more than a third more time than planned. The studio finds out only when the next quote is built on the same assumptions.<br> |
||||
|
|
||||
|
<br>The correction is to track hours against each project from the start. Set the budget in hours by role before the work begins, record actual time to the same project code, and compare the two at each milestone. A useful review asks three questions: how many hours are spent, how many are left according to the team, and whether the remaining plan fits what the client approved. If the answers [Do I Need A Part-Time Cfo In Massachusetts](https://Venturegrowthpartners.com/locations/massachusetts-boston-part-time-cfo-services/) not match, the project is already drifting.<br> |
||||
|
|
||||
|
<br>Use a short checklist to keep this routine:<br> |
||||
|
|
||||
|
Budget hours by role for every fixed-fee project before kickoff. |
||||
|
Log time to the project code on the same day, not at the end of the month. |
||||
|
Compare hours to budget at each milestone and write down the reason for any gap. |
||||
|
Record the forecast to complete, not only the hours spent to date. |
||||
|
|
||||
|
|
||||
|
<br>Here is the catch: timesheets only work if people fill them in honestly. In many studios, designers see logging as surveillance, and project managers estimate from memory when the tool is annoying. The fix is less about software and more about a clear reason. Explain that the hours are used to price the next job and to protect the people doing the work from unrealistic deadlines. Without that, the data is a guess with a timestamp.<br> |
||||
|
|
||||
|
<br>Tracking hours also does not fix a bad quote. If the original estimate ignored review rounds or client approval steps, the tracking will show the gap clearly, and the studio still has to decide what to do about it. The next quote should carry those hours. A CFO can build the method and review the numbers, but nobody can force a client to accept a higher fee after the work has started.<br> |
||||
|
|
||||
|
Mistake two: leaving revisions and client calls off the timesheet |
||||
|
<br>Many studios do work they never record. A revision round after sign-off, a call to explain a file format, a quick search for stock imagery and a review of the client's new copy all feel like part of the job. People rarely log them, because they seem too small to matter or because they fall outside the official tasks. Added together, they can consume a meaningful share of the budget. The P&L will never see them.<br> |
||||
|
|
||||
|
<br>Consider a hypothetical website project. The plan includes two rounds of design feedback. After the designs are approved, the client asks for three more rounds, plus a new page structure, and the team absorbs each request as a favor. Each round looks small on its own. The final tally shows that the unbilled work is larger than the scope the client originally approved, and the margin on that project falls well below the plan.<br> |
||||
|
|
||||
|
<br>The correction has two parts. First, record every hour, including revisions and calls, against the project code, and mark revision time separately so it can be counted on its own. Second, set a change-order step for any request outside the approved scope. The studio should send a short written note that describes the extra work, its hours and the change in price or timeline, and wait for approval before starting.<br> |
||||
|
|
||||
|
<br>The problem is that a change order only works if the client accepts it. Some clients will push back, and some will read the request as a sign that the studio is difficult to work with. Decide in advance how much goodwill you will absorb and at what point you stop. A studio that writes a clear policy and applies it the same way to every client is in a better position than one that negotiates each case from scratch.<br> |
||||
|
|
||||
|
<br>There is also an internal side. If account managers are rewarded only for keeping clients happy, they will tend to say yes to everything. If they are judged partly on project margin, the conversation changes. That is not a finance decision alone. It is a conversation between the owner, the project leads and whoever reviews the numbers, and it needs to happen before a difficult request arrives.<br> |
||||
|
|
||||
|
<br>In practice, the first month of this change is uncomfortable. Revisions that used to disappear now show up in the review, and the team may look slower than before. That is the point. The records are not there to punish anyone. They show where the work is going, so the next scope can be drawn more carefully and the price can reflect the real effort.<br> |
||||
|
|
||||
|
Mistake three: spreading overhead by headcount without checking utilization |
||||
|
<br>Overhead is the cost of running the studio that does not belong to any one project: rent, software licenses, insurance, bookkeeping, and the share of management time that supports every job. Most studios need to allocate some of it to projects, or each engagement will look more profitable than the business really is. The mistake is choosing an allocation method out of habit, or accepting whatever the software suggests by default, without asking whether it reflects the work.<br> |
||||
|
|
||||
|
<br>Three common methods are headcount, revenue share and hours. Headcount divides overhead equally across people, which ignores how much of each person's time goes into client work. Revenue share charges more overhead to larger invoices, even when the work is simpler and uses fewer hours. Hours spreads cost by the time each project consumes, which is closer to how the studio actually uses its space and systems. The table below compares them.<br> |
||||
|
|
||||
|
|
||||
|
|
||||
|
MethodEasy to calculateReflects time usedMain risk |
||||
|
|
||||
|
|
||||
|
HeadcountYesPoorlyCharges idle staff the same as busy ones |
||||
|
Revenue shareYesPoorlyPenalizes large fees that need little effort |
||||
|
HoursOnly if time is trackedWellDepends on honest timesheets |
||||
|
|
||||
|
|
||||
|
|
||||
|
<br>This is where utilization comes in. Utilization is the share of available working time that goes to billable client work. A designer with a low rate, perhaps because they are building internal templates or waiting on approvals, carries a cost that someone has to pay. If that cost is spread by headcount, the projects they touch look worse than they should, and the projects of a fully booked colleague look better. The numbers then point the owner at the wrong problem.<br> |
||||
|
|
||||
|
<br>The correction is to pick one method, write it down and keep it stable for at least a few reporting periods. Many studios start with hours, because it is the most defensible when time is already logged. Calculate each project's share of total logged hours, multiply that share by the monthly overhead pool, and add the result to direct costs. Then compare the fully loaded margin with the direct margin. The gap is the overhead the project consumed, not a penalty.<br> |
||||
|
|
||||
|
<br>Here is the catch: no allocation method is neutral. Hours-based allocation favors projects that are light on senior time, and it can make a research-heavy project look expensive. Revenue-based allocation can make a premium brand project look like it is subsidizing the rest. Each method changes the answer, so the purpose of the review should decide which one you use. Do not switch methods just to make a bad project look better.<br> |
||||
|
|
||||
|
<br>A fractional CFO can build the allocation rule and show its effect beside the direct margin. That helps, because it lets the owner see the difference without arguing about the spreadsheet. What a CFO cannot do is decide alone that a senior designer should spend less time on internal work or that a client should be dropped. Those choices belong to the people who run the studio and the people who deliver the work.<br> |
||||
|
|
||||
|
Mistake four: finding out a project ran over only at month-end |
||||
|
<br>The monthly close is a good time to check the books and a poor time to discover that a project has gone off course. By the time the close is done, the hours have been logged, the invoices have gone out, and the team has moved on to the next job. A project that has been over budget for six weeks shows up as one line in a summary, and the owner learns about it from a number instead of a conversation. Waiting for month-end turns a manageable overrun into a surprise.<br> |
||||
|
|
||||
|
<br>Work in progress, often shortened to WIP, is the value of work done but not yet billed. For a studio, it is the clearest early signal. A large WIP balance on a fixed-fee job can mean the team has done most of the work and has not reached a billing milestone, which is fine. It can also mean the work is slipping and the team cannot reach the next milestone, which is a problem. Without a WIP view, the two cases look identical until the invoice either goes out or does not.<br> |
||||
|
|
||||
|
<br>The correction is a short, regular review. Every one or two weeks, the project lead and the account manager sit down with whoever owns the numbers and go through each open project. A one-page status can carry the essentials: hours to date against budget, percent complete as the team judges it, billing to date, and the forecast to complete. The meeting should end with a decision for each project that is off track, such as a scope conversation, a staffing change or a billing adjustment.<br> |
||||
|
|
||||
|
<br>The review fails in a predictable way when nobody prepares for it. It turns into a status update that everyone skims. Assign the one-page status to a named person, and give the project lead time to fill it in before the meeting. Keep the list short. A studio with forty open items will spend the hour on paperwork, while a studio that focuses on its five largest or riskiest projects will actually change decisions.<br> |
||||
|
|
||||
|
<br>The review shows problems early, but it does not solve them. A fractional CFO can prepare the status page, challenge the forecast and point out when the percent complete looks too optimistic. The owner and the project leads still have to renegotiate the scope, move people or talk to the client. If nobody has the authority to make one of those calls, the review will produce accurate reports about overruns that nobody acts on. Settle who decides before the first meeting.<br> |
||||
|
|
||||
|
Setting up the tracking without building more than you need |
||||
|
<br>Many studios try to build a complete project accounting system before they know what they need to know. The result is a tool that takes months to configure and that nobody trusts. A better start is a spreadsheet for the five to ten active projects that matter most, run for a few months, until the team agrees on the definitions. Once the numbers are stable, decide whether they belong in the accounting system, a dedicated project tool or a planning platform.<br> |
||||
|
|
||||
|
<br>The main options are familiar. QuickBooks can tag transactions with classes or projects, which lets you sort costs and revenue by job with a moderate amount of setup. NetSuite and Sage Intacct both offer project accounting modules built for businesses that bill against projects, with more structure and more configuration work. Adaptive Insights is a planning and forecasting platform, so it is more useful for budgets and forecasts to complete than for daily time capture. None of them is the right answer for every studio, and configuring any of them has a real cost, so compare them against a clear list of the decisions you need to support.<br> |
||||
|
|
||||
|
<br>Revenue timing is the part many owners underestimate. Under ASC 606, a service delivered over time is recognized as the work progresses, which may not match the invoices sent. A fixed-fee project billed at milestones can therefore show revenue ahead of billing or behind it, creating a contract asset or a contract liability on the balance sheet. The P&L may look smooth while the billing schedule is lumpy, and the reverse can also happen. Ask your accountant how the studio's contracts are recognized before you read a margin report as a picture of cash.<br> |
||||
|
|
||||
|
<br>A tool does not make definitions consistent. Before you configure anything, agree in writing on what counts as a project, what counts as direct cost, which hours are billable, how revisions are coded, and how percent complete is estimated. Two people who use different definitions will produce two margins for the same job, and the tool will record both without complaint. The definitions matter more than the software.<br> |
||||
|
|
||||
|
<br>When the spreadsheet works, move the pieces that need repeated entry into the system, and keep the review routine unchanged. The goal is not a perfect report. It is a dependable picture that the owner trusts enough to make a pricing decision. A studio that has that picture on a single page, updated every two weeks, is usually better off than one with a sophisticated dashboard that nobody opens.<br> |
||||
|
|
||||
|
Where a fractional CFO fits, and where the work stops |
||||
|
<br>Owners often use the terms controller, accountant, bookkeeper and CFO as if they were interchangeable. They are not. A bookkeeper records transactions and keeps the ledger accurate. An accountant prepares financial statements and tax filings and may advise on compliance. A controller runs the close, manages internal controls and oversees the people who keep the books. A chief financial officer, in the full-time sense, sets financial strategy, leads planning and speaks for the finances to the owner, the board and outside capital providers. A fractional CFO does that senior work on a part-time, defined scope.<br> |
||||
|
|
||||
|
<br>For a design studio, the fractional role usually covers the design of the project view, the review of margins, pricing guidance, the cash forecast and the reporting the owner needs. A typical engagement might include a monthly review of open projects, a standing conversation about upcoming hires, and help preparing lender or investor materials when they are needed. The work is measured in deliverables and a defined schedule, and the scope should be written down before work starts, not inferred from a call.<br> |
||||
|
|
||||
|
<br>The limits matter as much as the scope. A fractional CFO does not own project delivery, does not decide creative direction and cannot make a client pay on time. They cannot guarantee that a studio will become profitable, that a loan will close or that a sale will happen. A candidate who promises those outcomes is selling something other than competent finance work. Ask what they will own, what the owner and project leads will still own, and what they will hand over at the end.<br> |
||||
|
|
||||
|
<br>When you interview candidates, ask for a description of how they would run the first three months, and compare it with the studio's real problems. A candidate who wants to start with a full system rebuild may be wrong for a studio that needs a clear pricing view in weeks. A candidate who only offers bookkeeping cleanup may not be the senior partner you need. Ask how they work with the owner, the accountant and any board or investors, and listen for specifics about meetings, reports and decision rights rather than general confidence.<br> |
||||
|
|
||||
|
<br>Here is the catch: a fractional arrangement works best until the work grows into a full-time job. Watch for signs such as weekly requests that exceed the agreed scope, approvals that stall because nobody senior is available, or a board that wants reporting at a level the fractional schedule cannot cover. At that point, the choice is not between two candidates. It is between a bigger part-time commitment and a full-time executive. Make that decision on the workload, not on the fact that the studio has grown in size.<br> |
||||
|
|
||||
|
A worked example: deciding whether to keep a retainer client that runs over |
||||
|
<br>Consider a hypothetical design studio with about a dozen staff and a mix of fixed-fee projects and monthly retainers. One retainer client, a regional nonprofit, has steadily increased its requests over several months. The monthly fee has not changed, and the team has been absorbing the extra work. The owner wants to know whether to keep the client, renegotiate the retainer or let the account go. The P&L shows that the studio is still profitable overall, which is why the question has been easy to put off.<br> |
||||
|
|
||||
|
<br>Step one is to pull the logged hours for that client over the last three months and separate revision time from planned work. Suppose the plan allowed a fixed number of hours per month, and the logged total runs well above it, with a steady share of revision and call time. Step two is to compare the fee with the fully loaded cost, using hours to allocate overhead. The direct margin may still look positive, but the fully loaded margin is lower, and the gap is the overhead the client consumes. Step three is to check revenue timing with the accountant, so the retainer's billing is not confused with the work delivered.<br> |
||||
|
|
||||
|
<br>Step four is the decision itself. The owner has three realistic options: write a clearer scope and a change-order process into the retainer, raise the fee at renewal with a clear reason, or end the arrangement once the notice period passes. Each has a cost. Renegotiation may lose the client, a higher fee may not be accepted, and ending the work removes revenue the studio has come to rely on. The hours and margins help the owner see the trade-off, but they do not make the choice for them.<br> |
||||
|
|
||||
|
<br>Step five is to change one thing first. In this case, the first move could be a written scope with two revision rounds per deliverable and a change-order note for anything beyond that. Track the next two reviews against that scope. If the hours fall back toward the plan and the client accepts the new structure, the relationship can continue on new terms. If the client refuses, the data supports the decision to walk away, and the owner has a record of why.<br> |
||||
|
|
||||
|
<br>The example is hypothetical, and your studio's numbers will differ. What carries over is the sequence: start with the decision, use project-level hours, allocate overhead on purpose, check revenue timing and change one thing at a time. Begin with the one-page project status for your three largest open jobs, and let that page show you where to look next.<br> |
||||
Loading…
Reference in new issue