Teams | Collaboration | Customer Service | Project Management

There's a Reddit thread that's currently ranking for this exact topic, and the whole premise is that project profitability is "basically a guess." I get why people feel that way. But forecasting profit before you start isn't fortune-telling, it's a repeatable calculation you can run on any project in about an hour. This guide walks through the five-step method I used in my agency days to predict a project's margin before a single hour is logged.

Before I joined Teamwork.com, I directed client accounts at agencies, and the most uncomfortable meeting of every month was the profitability review. We'd pull time out of one tool, costs out of another, and rates out of a spreadsheet someone updated when they remembered to. By the time the numbers lined up, the project was already over, and so was any chance to fix it. That's the real problem with most "profitability tracking." It tells you what happened after you can't do anything about it.

There's a question that consulting leaders don't ask themselves enough: if AI created 10% more delivery capacity in your teams tomorrow, would you actually know where to deploy it? That provocation sat at the heart of the session I ran at Leaders in Consultancy Munich, and judging by the room, it landed.

Every agency ops leader eventually hits the same wall. A deal closes in HubSpot. Someone copies the client details into a spreadsheet. Another person builds the project manually, and by the time delivery starts, three days have passed and half the context is missing. That gap between "sold" and "started" is where client relationships quietly erode.

You already live in Microsoft Teams. Your standups happen there, your files live there, and your quick "can you check this?" messages fly through it dozens of times a day. So when project work starts falling through the cracks, the instinct is obvious: find a project management app that plugs right into Teams. The problem? Microsoft Teams surpassed 250 million monthly active users as of 2021, according to Statista, and has continued growing since.

Before joining Teamwork.com, I spent years running delivery at agency firms. Back then, "PSA" meant either an overpriced system nobody wanted to use or a Frankenstein stack of spreadsheets and disconnected apps. The ticketing tool didn't talk to the billing tool. The billing tool didn't talk to the project tracker. And the project tracker was, let's be honest, a shared Google Sheet held together by hope.

A few years back, I was managing six client accounts at once with a stack of tools that didn't talk to each other. Time tracking in one app, project tasks in another, and a spreadsheet held together by hope to figure out whether any of it was actually profitable. That setup cost us hours every week in manual reconciliation, and we still missed billing for work that fell through the cracks.

Professional services teams are often convinced they have a "people problem" when what they really have is a visibility problem. Tasks scattered across three tools, time logged in a spreadsheet nobody checks, and deadlines that only surface when a client emails asking for an update. Before I joined Teamwork.com, I spent years managing client projects at agencies where this was just how things worked. Monday mornings started with a 45-minute standup that could have been a dashboard.

These three small but mighty updates we shipped in June are here to make working in Teamwork.com that much easier.

Every agency runs on time. Whether you bill hourly, use retainers, or run fixed-fee projects, knowing where your team's hours actually go is the difference between profitable delivery and slow-motion margin erosion. Before I joined Teamwork.com, I spent years at agencies wrestling with exactly this problem: timesheets submitted days late, hours logged to the wrong project, and month-end reviews that felt more like forensic accounting than business management.