Teams | Collaboration | Customer Service | Project Management

I spent years managing client services teams before I joined Teamwork.com, and software implementation projects were always the ones that kept me up at night. A go-live date would slip, a consultant would get double-booked across two rollouts, and the billable hours nobody logged would quietly eat the margin. Most of that chaos came from running implementations across a spreadsheet, a time tracker, and a separate billing tool that never talked to each other.

Monday morning shows up, your calendar's already full of meetings, and your to-do list is quickly turning into a novel. You know what needs doing, but what you don't have is fifteen free minutes to figure out when. That's the gap our AI Teammate, Scout, just stepped in to fill. Meet Plan my week, Scout's newest job and the fastest way to turn a pile of tasks into an actual, workable schedule.

To be clear from the outset: this guide is about reserving people and time for probable client work, not building oil and gas pipelines. If you plan projects for a living, "pipeline" means the deals moving toward a yes, and the work you'll have to staff the moment one lands. According to Teamwork.com's own product data, only 42% of expected work is mapped to a plan before it's confirmed, which leaves a lot of resourcing to guesswork.

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.

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.

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.