Teams | Collaboration | Customer Service | Project Management

AI is used on 43.6% of professional services projects in 2026, nearly double the 23.1% in 2025, according to SPI Research's 2026 Impact of AI on Professional Services study of 245 firms. But the payoff is uneven: 84.8% of firms say AI saves them time, while only 29.9% say it generates revenue. The study covers management and IT consultancies, professional services teams inside software and SaaS companies, and other professional services firms across the Americas, EMEA and APac.

Every services firm I talk to is measured on three things: delivering on time, keeping billable utilization healthy, and delivering projects profitably without over-servicing. AI should help with all three. So far, it's helping firms deliver faster. It isn't yet making them more profitable. SPI Research's 2026 Impact of AI on Professional Services study shows the gap. AI now touches 43.6% of projects, nearly double a year ago, and firms using it on most of their projects deliver far more of them on time.

AI budgets have moved to the CEO and CFO, and they want proof. That was the clearest message at TSIA World 2026 in Las Vegas. "These budgets are at the C-suite. This is your customer now. The CEO, the CFO... they want to see the results." Thomas Lah, Executive Director, TSIA Most services firms aren't ready to give them that proof. TSIA's survey of its advisory board found: We spent three days in sessions, on the floor and at our booth.

Before I joined Teamwork.com, I spent years inside professional services firms watching the same pattern play out. A project would close, the team would celebrate, and then finance would run the numbers and discover we barely broke even. The margin had eroded slowly across dozens of small scope additions that nobody tracked individually but that collectively ate the entire profit.

Agentic PSA is professional services automation where AI agents do parts of the operational work, such as drafting a client update, and a person approves the result. A PSA, or professional services automation platform, connects projects, resources and financials in one system, and the "agentic" part is about who does the work inside it. At Teamwork.com, I run AI on my own project admin, status updates and reporting, and nothing goes out until a person has checked it. That check is why I trust the output.

Workload management tools earn their place when they show who's actually free, person by person, and whether the next project fits before you say yes. Plenty of tools display workload, but far fewer show it honestly enough to staff and price from. Before I joined Teamwork.com, I spent nine years in agency account teams, and during busy periods it was often the same few people staying late while others left on time. That imbalance, more than the total workload, is what burned people out.

Knowing how to spot at-risk projects before margin goes comes down to one weekly check: what each project has spent against what it has delivered. Before I joined Teamwork.com, I worked agency-side, where clients kept asking for more inside the same retainer and nothing in our process recovered the cost. The lesson stuck: by the time a report said overspent, the decision behind it was long past cheap to fix. This guide gives you four leading signals with thresholds, a worked example and the fix for each.

Leading vs lagging indicators for professional services comes down to timing. Lagging indicators like margin and realization report what delivery already decided; leading indicators are the delivery signals that move weeks earlier. Before I joined Teamwork.com, resourcing forecasts were consistently the hardest numbers I owned as an agency Account Director, and hard-to-build forward numbers are the ones worth checking weekly.

Your billing model decides who pays when an estimate turns out wrong, so choose it per engagement rather than by habit. Professional services billing is how a professional services firm turns delivered hours, phases or ongoing access into invoices a client agrees to pay. Before I joined Teamwork.com, I managed agency accounts where underbidding at the pitch caused most of the scope disputes that followed. That's why this guide treats the model as a risk decision.

Halfway through a project, someone asks the question every delivery lead gets: are we still making money on this? The honest answer usually lives in three places: what you planned to earn when you booked the team, what you scoped when you sized the work, and what you've actually earned from the hours logged so far. Financial Overview puts all three on one row. When they don't agree, and they usually don't, the gap is the story of the project: scoped low, booked heavy, burned faster than planned.

I've spent years watching teams outgrow their PM tools. Visibility disappeared the moment headcount crossed 50. According to Teamwork.com's 6 Strategic Shifts for 2026 report, 92% of business leaders say their current tech falls short on data management and reporting. Half believe they're losing revenue due to those inefficiencies. That stat didn't surprise me. What surprised me was how many teams accept it as normal.

ClickUp can be configured to do almost anything, and for a services team that's the catch. It tracks tasks, not money, so rate fields, budget formulas and utilization views all have to be built and maintained by someone on your team. If you're comparing ClickUp alternatives, that build cost is the number to measure first. I work at Teamwork.com. Before that, I spent nine years in agencies, where the numbers I trusted least were always the ones that depended on someone remembering to fill in a field.

For most of my nine years in agencies, moving tasks along was the easy part. The hard part lived in spreadsheets: who was free next week, which hours never got logged, and whether a retainer still paid its way. I had a basic timer and a lot of tabs, and the tabs were always a few days behind. I work at Teamwork.com now, and I see the same thing in teams shopping for Trello alternatives. Trello is still a strong board, and Premium adds Timeline, Table, Calendar, Dashboard, and Map views.

Before I joined Teamwork.com, I spent years running delivery in agencies. Most switches I saw started with the right complaint and the wrong cure: Wrike felt heavy, so teams moved somewhere lighter. Adoption jumped, but by the next quarterly review nobody could say which projects had made money. That gap is common. When Teamwork.com's The Sprint to AI report asked senior leaders at client service firms where their tools fall short, 38% cited profitability management.

The quotes that hurt in my agency years weren't the ones we lost. They were the ones we won, priced fast from a blended rate and a gut feel on hours, then underwater a few weeks into delivery. I work at Teamwork.com now, after nearly a decade in agencies. Back then, quoting lived in spreadsheets next to a basic timer, so no quote ever saw what the team actually cost. Most guides judge quoting software on how fast and how good a quote looks.

Every ticket your team closes today makes the next one a little easier. That's not a metaphor, it's literally how Dotty works. Dotty is the AI Teammate built into Teamwork Desk. It drafts replies from your help docs and resolved tickets, surfaces the ticket that already solved this exact problem, and summarizes hand-offs so context isn't lost. Your agents review and send: nothing goes out untouched. But the real story isn't any one of those skills. It's what they're building together.

Teamwork.com is introducing AI credits. If your first question is “what’s this going to cost me?”, the short answer is that your credits come included with your plan, at no extra cost. Your plan price stays the same, and most of the AI you use day to day doesn’t use credits at all. What changes is how the bigger jobs you hand to AI are covered, like asking Ask AI for a report or having an agent prepare a client update.

A market positioning project that used to take a consulting team four to five weeks now takes two and a half days. That's not a forecast. It's what Michael Nenninger, former EVP of digital consulting at msg, described on a recent episode of the Leaders in Consulting podcast. His team built the work as an AI workflow: around 60 prompts, 15 sub-tasks, and a human checking quality along the way. The host did the math on air: that's 5% to 10% of the effort it used to take.

I have spent enough time in agencies to know how to price professional services projects badly. The reason most projects lose money has little to do with the pricing model on the proposal. It comes down to two things nobody systematises: what the work truly costs to deliver, and what happens to that cost after the client signs. This guide fixes both with a repeatable four-gate method.

In a services firm, your people are both the product and the cost, so service business profitability gets decided in five places at once. It's what you charge, what you collect, how much capacity you sell, who does the work and what the firm costs to run. This guide runs all five through one worked model. Then a Lever Sensitivity Test shows which lever to pull first, and it's rarely the one leaders reach for.

A project's margin is an output: it's whatever is left once pricing, staffing, hours, scope and billing have all had their say. Project profitability analysis is the work of tracing that number back to the decisions that produced it. In this guide, I'll walk you through the Five-Lever Margin Bridge and a six-step review that prices each cause in dollars. Then we'll test both on a worked example that reconciles exactly.

Most advice on cost overruns is really advice about the next project. Estimate better, add contingency, tighten the SOW. All true, and none of it helps the project that's 40% delivered and 55% spent right now. This guide is about that project. You'll get a weekly check I call the Burn Gap Triage, three moves for closing the gap, and the delivery habits that stop small leaks becoming write-offs.