The free PLYNT business scan asks about this directly: how many projects start with a written, agreed scope, and how often the scope grows without anyone billing for the extra work. The second question carries the highest weight in the scan’s Money category, because that is where the money is lost.

Why extra work goes unbilled

• There is no baseline. Without a written scope nobody can say what is extra, and the conversation becomes a matter of opinion.
• The request reaches the wrong person. A designer or developer agrees a small change directly with the client, and the account lead hears about it after the work is done.
• Nobody sees the effort. If time is not recorded against the specific task, the extra hours disappear into the project total.
• Asking feels awkward. Teams avoid raising money for small changes, then discover at the end that the small changes added up.

A routine that catches it

1. Write the scope down before work starts. A short list of deliverables, the number of revision rounds and what is out of scope is enough. Keep it with the project, not in an email thread.
2. Send every change through one door. Client requests go into a request with an owner, not straight to whoever is doing the work. The owner decides: included, extra or declined.
3. Price the change before you do it. An estimate in hours or money, even a rough one, turns “can you just…” into a decision the client makes knowingly.
4. Get the approval on record. A written reply attached to the request, not a verbal yes, so it can be found when the invoice goes out.
5. Record time against the change. Approved hours on the task show whether the estimate was right and improve the next quote.
6. Review the scope at every milestone. Compare what was agreed with what is being delivered. Small differences are easier to discuss early than at the final invoice.

What to say to the client

The conversation is easier when it is about the work rather than the money. “This is outside what we agreed and takes about six hours. Shall we add it to this phase or plan it for the next one?” gives the client a choice and a reason. Most clients prefer a clear option to a surprise on the invoice.

Retainers drift in the same way

A monthly retainer agreed a year ago often covers more work today than it did at the start. Once or twice a year, compare the approved hours and direct costs of the last months with the retainer fee. If the work has grown, you have a factual basis for a new price or a narrower scope.

Signs that scope is leaking

• Projects regularly finish later than planned without any change to the agreement.
• Time on client projects is logged to “general” or “admin” tasks.
• Invoices match the original quote even when the work clearly grew.
• Prices have not changed in more than two years. The scan treats this as a risk as well, because old prices absorb rising costs.

How PLYNT supports this

In PLYNT the agreed scope sits with the client and the project. Each request has an owner and a recorded decision, an accepted request becomes a task with the client and files attached, and approved time on that task shows what the change cost. Read more about requests and approvals and finance and costs.

To see where your business stands, take the free business scan: 21 questions, no account or email.

The free PLYNT business scan asks three questions in its Time category: whether the team tracks its working time, roughly what share of worked hours gets logged, and how many hours a week one person spends in internal meetings. In the scan’s published bands, logging more than 84% of worked hours is the lowest-risk answer; logging a quarter or less is among the highest.

Where the hours go missing

• Reconstruction at the end of the week. People fill in the timesheet on Friday from memory and calendars. Short tasks, calls and interruptions are forgotten.
• Switching between clients. Ten minutes here and twenty there are real work, but they feel too small to record.
• Time logged to the wrong place. Hours go to a general “admin” bucket instead of the task, so they exist but explain nothing.
• Distrust. If time tracking feels like monitoring, people record the minimum. Tools that take screenshots or log keystrokes make this worse.

Why it matters beyond the timesheet

Unlogged time is not free time. It is effort the business paid for but cannot see. It hides which clients are expensive to serve, makes estimates look better than they are and turns every pricing conversation into a guess. It also makes capacity planning unreliable: a team that looks 70% busy on paper may be fully booked.

A practical way to fix it

1. Agree what gets time. Client work, internal projects, sales and administration each need a clear place. If a category is missing, people will not know where to put the hours.
2. Log against the task, not the day. An hour on a task says what the hour was for. An hour on a date says nothing.
3. Log daily. Two minutes at the end of each day is more accurate than half an hour on Friday.
4. Keep review and approval as separate steps. The person checks their own entries first; a manager approves them afterwards. Only approved time should feed cost and billing.
5. Look at the gaps together. Compare logged hours with contracted hours each week. A gap is a question to ask, not a mistake to punish.

Meetings are part of the picture

Internal meetings are real time, and they compete with client work. The scan scores up to two hours a week per person as low risk and more than twelve as high risk. Measuring it is simple: count one ordinary week of internal meetings for a few people. If status meetings dominate, a written update kept with the work often replaces most of them.

Respect the person

Time tracking works when people trust it. Record what the work needs, such as the task, the client and the duration, and nothing that feels like watching someone. Let the person see and correct their own record before anyone else does.

How PLYNT supports this

Time tracking, timesheets and attendance are available on every PLYNT plan, and approved time is linked to the task and the client, so it explains project cost. Private desktop and browser capture is in development and is designed to record only application names, domains and active duration: no screenshots, keystrokes, page contents or document titles. Read more about time tracking.

To see how your team scores, take the free business scan.

The free PLYNT business scan has three questions in its Margin category: what share of revenue comes from the single biggest client, whether retainers have been re-costed against today’s real costs in the last 12 months, and what share of clients you suspect are unprofitable. The last one carries the most weight, because a suspicion that nobody has checked is the most common margin problem.

Contribution before overhead

The measure that answers the question is contribution before overhead: what a client or project brings in, minus what it cost to deliver, before company-wide costs such as rent or management are shared out.

A worked example. A project is worth $8,000. The team spent approved hours on it that cost $4,700 at internal cost rates, and there were $500 of direct expenses. Delivery cost is $5,200, so the project contributes $2,800, or 35% of its value. That contribution is what pays for the rest of the company.

Finding an internal cost rate

To turn hours into money you need a cost rate per person or per role: the full monthly cost of that person, including employer taxes and benefits, divided by the hours they are available for work in the month. For example, a monthly cost of $3,000 and 140 available hours gives a rate of about $21.40 an hour. Use the same method for everyone and review it once a year.

A three-month client review

1. Take the last three full months, so one unusual month does not decide the result.
2. List every client with the value invoiced for that period.
3. Add the approved hours for each client, multiplied by the cost rates.
4. Add direct expenses: freelancers, media, licences bought for that client.
5. Calculate contribution and contribution as a percentage of value.
6. Sort the list and look at the bottom three first.

This only works if the hours are real. If a large share of worked time is never logged, the result will flatter every client. Fix time tracking first, or treat the numbers as a lower limit on cost.

What to do with a low-contribution client

• Reprice when the work is right but the fee is old.
• Narrow the scope when the client asks for more than the agreement covers.
• Change the process when rework or long approval cycles drive the cost.
• Let the client go only when none of the above is possible, and with the numbers in hand.

Concentration is a separate risk

A client can be highly profitable and still be a risk. In the scan, more than half of revenue from one client falls in the highest-risk band. The answer is not to drop that client but to know its real contribution and to plan how the company would cope if the relationship changed.

Retainers need re-costing

A monthly retainer priced a year ago was based on last year’s salaries and last year’s workload. Once a year, compare its fee with the approved hours and direct costs of recent months. If the contribution has fallen, you have a fact to discuss rather than a feeling.

Common mistakes

• Sharing overhead across clients by revenue, which hides the real difference between them.
• Using hours that were estimated rather than hours that were approved.
• Comparing a client’s value for one period with costs from another.

How PLYNT supports this

In PLYNT each client shows payments, outstanding invoices, approved time and direct costs together, and unallocated company overhead stays separate, so the figure you read is contribution before overhead. See finance and costs, client context and the glossary.

To see how your margins score, take the free business scan.

The free PLYNT business scan asks three questions in its Cash category: how many days pass on average between sending an invoice and getting paid, what share of revenue is currently overdue, and whether you take deposits or prepayment before work starts. Overdue revenue carries the most weight. In the scan’s bands, payment within 15 days is the lowest-risk answer and more than 60 days the highest.

Why 13 weeks

Thirteen weeks is one quarter, seen week by week. It is long enough to see a problem coming, such as a large payment falling in the same week as a slow client, and short enough to plan with real invoices and real bills rather than guesses.

Building the view

1. Start with today’s bank balance. Use the money that is actually available, not the balance after invoices you expect.
2. List expected receipts by week. Take every open invoice and place it in the week you realistically expect payment, not the due date. If a client usually pays 20 days late, plan for that.
3. Add invoices you will send. Retainers, milestones and work that will be finished in the period, again placed on realistic payment weeks.
4. List planned payments by week. Salaries, rent, taxes, suppliers, freelancers and software. Put each in the week it leaves the account.
5. Calculate each week. Opening balance plus receipts minus payments gives the closing balance, which becomes the next week’s opening balance.
6. Update it every week. Replace expectations with what actually happened and roll the view one week forward.

The week with the lowest closing balance is the one to act on now, while there is still time.

Shortening the wait

• Invoice on time. An invoice sent two weeks after the work is finished adds two weeks to every payment.
• Take a deposit. A prepayment before work starts reduces the amount at risk and signals commitment on both sides.
• Bill by milestone. Long projects paid only at the end put the whole cost on your balance sheet until the last day.
• Follow up on a schedule. A reminder a few days before the due date, on the day and a week after is routine, not confrontation.
• Compare real collection time with your terms. If terms say 14 days and clients pay in 45, either the terms or the follow-up needs to change.

What the view does not replace

A 13-week view is an operational tool. It does not replace your accountant, statutory reporting or tax planning, and it is only as good as the invoices and bills you put into it. Confirm important decisions against your accounting records.

How PLYNT supports this

PLYNT keeps invoices, recurring invoices, payments, expenses and receivables with the client and project they belong to, and its cash flow overview brings expected receipts and planned payments for the next 13 weeks into one view on every plan. Read more about finance and costs.

To see how your cash position scores, take the free business scan.

These are the three questions in the Focus category of the free PLYNT business scan. The founder question carries the most weight. In the scan’s bands, up to four tools, up to two parallel projects per person and up to 20% of the founder’s week in delivery are the lowest-risk answers.

Tools: every switch has a cost

Each tool is usually added for a good reason: one for tasks, one for chat, one for files, one for time, one for invoices. The cost appears later, in the gaps between them. Information is copied by hand, the latest version lives in someone’s head and a simple question such as “has this been invoiced?” needs three windows to answer.

How to measure it: list every tool the team uses for delivery, communication and money, and next to each, what the team would lose without it. Tools that hold the same information as another tool are the first candidates to go.

Parallel projects: the hidden queue

A person working on six projects at once is not six times as productive. Each switch costs time to remember where things stood, and every project waits while the others move. The result is that everything is in progress and little is finished.

What helps: make each person’s open work visible in one place, agree a limit on active projects per person and finish before starting. When a new request arrives, look at the person’s current workload before promising a date.

The founder’s week

In small service companies the founder is often the best designer, strategist or developer on the team, and so ends up doing the work instead of running the company. That is sometimes necessary. When it becomes most of the week, pricing, hiring, cash and client relationships wait until something breaks.

A simple test: for two ordinary weeks, note how many hours go into delivery and how many into running the business. Then choose one recurring delivery responsibility to hand over, with a clear owner and a written brief.

Where to start

1. Remove one tool that duplicates another.
2. Agree a limit on active projects per person and make workloads visible.
3. Hand one delivery responsibility from the founder to a named owner.
4. Repeat the scan in a month and compare.

How PLYNT supports this

PLYNT brings tasks, clients, people, time and operational finance into one workspace, so fewer tools hold the same information. Assignments sit next to attendance and leave, so a person’s real workload is visible before new work is promised. See people and workload and what your current tools cost.

To see how your focus scores, take the free business scan.

The free PLYNT business scan asks three questions in its Execution category: what share of work ships later than the date you promised, how often finished work comes back for rework, and whether every project has exactly one accountable owner. In the scan’s bands, up to 5% of work shipping late is the lowest-risk answer and more than 30% the highest.

Where late work begins

• Requests arrive everywhere. Email, chat, phone and meetings. Without one place to land, some are lost and others start without a decision.
• Nobody owns the decision. If three people can say yes, nobody is responsible for saying no.
• Dates are promised before capacity is checked. The person who will do the work finds out about the deadline after it has been agreed.
• Dependencies are invisible. A task that waits for approval or for another task looks as if it is in progress.
• The brief changes quietly. Work finished against yesterday’s instructions comes back as rework.

One owner per project

An accountable owner is not the person who does all the work. It is the person who knows the state of the project, makes or escalates decisions and speaks for it. Many people can contribute; one person answers the question “will it be ready?”. When that person changes, the handover is explicit.

A routine for keeping dates

1. Collect requests in one place, each with the client, what is needed and how urgent it is.
2. Give each request an owner who decides whether it is accepted, changed or declined.
3. Check the workload before promising a date. Look at the assignee’s open tasks, planned leave and other deadlines.
4. Turn the accepted request into tasks with the brief, files and dependencies attached, so nothing has to be asked twice.
5. Record changes where the work is. If the brief changes, the task changes, and the date is reviewed with the owner.
6. Review late work weekly. For each late item, note the reason in one line. After a month the pattern is usually obvious.

Rework is a signal, not bad luck

When finished work comes back, the cause is usually one of three things: the brief was unclear, it changed after work started, or the person reviewing it was not the person who approved the brief. Each has a simple fix: a written brief, recorded changes and a named approver.

How PLYNT supports this

In PLYNT every request has an owner and a recorded decision, and an accepted request becomes a task with the client, files and agreement attached. Tasks have assignees, deadlines and dependencies, and assignments sit next to attendance and leave, so capacity is visible before a date is promised. See requests and approvals, projects and tasks and people and workload.

To see how your delivery scores, take the free business scan.

The Data hygiene category of the free PLYNT business scan asks three questions: could you state last month’s profit within ±10% right now, how many systems hold your money data, and can you see anywhere which clients are profitable. The scan also calculates an AI data readiness score from five inputs: time tracking, the number of systems holding money data, visible client profitability, confidence in profit and the number of tools. Time tracking and money-data systems count twice. Below 40 is Low, 40 to 69 Medium and 70 or more High.

Why these inputs matter

• Time tracking. In a service business most cost is people’s time. Without it, no analysis can explain where money went.
• One place for money data. When invoices, payments and expenses live in different systems, every answer starts with reconciling them, and each copy can disagree.
• Visible client profitability. If the business itself cannot see it, an AI cannot either.
• Confidence in profit. Knowing last month’s profit within ±10% means the basic figures are recorded and trusted.
• Fewer tools. Every additional tool is another place where the same fact can be recorded differently.

A checklist

1. One record per client. The same client should not exist under three spellings in three tools.
2. Time on tasks and clients. Hours linked to the work they were spent on, approved by a person.
3. Costs allocated to work. Direct expenses such as freelancers and media assigned to the client or project.
4. Collected, invoiced and estimated kept apart. A figure is only useful if you know which of the three it is.
5. Consistent names for stages and statuses. “Done”, “complete” and “finished” should not mean three different things.
6. Access rules decided in advance. Decide which roles may see financial and personal data before any AI reads it.
7. A named owner for the data. Someone who notices when records stop being updated.

What AI should and should not do

Useful AI in operations explains a change, shows the records behind a finding and suggests a next step that a person reviews. It should not invent missing numbers, hide its sources or act on important decisions without approval. A good test is simple: for every conclusion, can you open the entries it is based on?

Where to start

Most businesses do not need a data project. They need two habits: logging time against the work, and keeping invoices, payments and expenses in one place linked to clients. Three months of both is enough for meaningful analysis.

How PLYNT supports this

PLYNT keeps tasks, approved time, invoices, payments and expenses in one workspace, linked to clients and projects, and keeps collected cash, unpaid invoices and estimates distinct. Its AI capabilities are in development and are designed to work within each user’s access, show the records behind each finding and leave decisions to people. Nothing is presented as available before it is. See Intelligence and reports and analytics.

To see your AI data readiness score, take the free business scan. The answers stay in your browser, and no external AI receives them.