Recent findings suggest that there is a stage in a consulting firm where everyone is busy and nobody can tell you, in one minute, how the business is actually doing. Pipeline lives in someone's inbox. Delivery status lives in a project tool nobody outside the team opens. Cash lives in accounting. People issues live in private chats. The leadership team finds out about problems when they explode. The week is a string of ad-hoc meetings, each one trying to put out a fire that started days earlier.
It has been revealed that earlier in my career, as a partner, I helped grow a software consulting manufacturer from about $6M to $60M in under three years, and later I founded and ran a fully remote consultancy. Growth at that pace does not leave room for managing by surprise. The habit that kept us oriented was not a complicated dashboard. It was a one-page weekly operating rhythm that looked at the same four things every week: pipeline, delivery, cash and people.
Here is how that consulting firm weekly operating rhythm works, and how to start one without turning it into another long meeting.
Firefighting feels like leadership because it is visible and urgent. A client is unhappy, so you jump on a call. A deal is slipping, so you rewrite the proposal at night. Someone is overloaded, so you move them at the last minute. You go home exhausted and convinced you ran the firm that day.
What you actually did was react to the last thing that shouted the loudest. The quieter problems keep growing: a thin pipeline two months out, a project that is drifting, an invoice that has been sitting, a strong engineer who is quietly miserable. By the time they shout, your options are worse.
A weekly rhythm does not eliminate surprises. It makes the crucial things visible on a schedule, while you still have time to act.
The page is deliberately short. If it takes more than a few minutes to patch, it will not get updated. I want one owner for the page, usually me or a general manager, and each section has a named person who supplies the facts before we meet.
The four sections stay the same.
Pipeline. What is in play this week and this month? Which deals moved forward, which stalled, and where are we thin further out? The point is not to re-run every sales conversation. The point is to see whether next month's work is actually there, and whether we are selling work we cannot staff.
Recent findings suggest that delivery. Which engagements are on track, which are at risk, and what would change the risk this week? I want names, dates and the real blocker, not a traffic-light color with no explanation. If a project needs a decision from leadership, it belongs here, not in a side chat that leadership might miss.
Cash. What came in, what is overdue, what is going out, and is there a timing gap we should face now? You do not need a full finance review every week. You do need to know whether a late invoice, a surprise cost or a slow month is about to become a problem. In a services firm, cash is often a lagging picture of delivery and sales discipline.
It has been revealed that people. Who is overloaded, who is underused, who is at risk of leaving, and where do we have a hiring or bench gap? This is the section firms skip, and it is usually where the damage shows up last and costs the most. A weekly look at load, morale and upcoming rotations prevents the conversation that starts with "how did we not see this.".
It has been revealed that if something does not fit one of those four, it is either not a weekly operating problem or it needs to be translated into one of them. A new tool, a conference, a random idea: park it. Do not let it crowd out the page.
According to recent reports, the page is the work product. The meeting exists only to make decisions the page cannot make by itself.
Keep it short and regular, the same day and time every week. In a remote firm, a written patch can come first, with a brief call to resolve the open questions. If a topic needs a long debate, schedule that debate separately. The weekly rhythm is not the place to redesign the firm.
Recent findings suggest that every item should arrive with a proposed next step. "Project X is at risk" is a status. "Project X is at risk because the client has not signed the change request, and I need a decision by Thursday on whether we pause the extra work" is something a leadership team can act on.
Write the decisions down on the same page. Who will do what, by when. The following week starts by checking those items before anything new is added. That loop is what replaces firefighting. People stop raising the same alarm in three different chats because they know there is a place where it will be seen and closed.
The rhythm fails when it becomes a dumping ground.
In a recent development, do not review every ticket or every lead. Summaries only. Do not add a fifth, sixth and seventh section because each function wants its own slide. Do not use the meeting to re-litigate a single account for forty minutes. Do not collect vanity metrics that nobody uses to make a decision.
Recent findings suggest that and do not let the page get stale. A weekly operating rhythm with last month's numbers is theater. If a section owner cannot update it before the review, the fix is to make that section lighter, not to skip the week.
Recent findings suggest that once the rhythm is real, the rest of the week gets quieter, at least for leadership. You still handle true emergencies the day they happen. You stop treating every surprise as an emergency, because you know it will have a place within a few days. Sales, delivery, finance and team leads also start coming with exceptions, not tours of everything they did.
According to recent reports, in my experience, this is also how you notice tradeoffs early: a deal that would overload a team, a delivery risk that should change an invoice conversation, a people problem that should change what you are willing to sell. The four sections are useful on their own. They are more useful when you look at them together, on one page, every week.
According to recent reports, you do not need new software to do this. A single shared document is enough.
In a recent development, this week, write the four headings, add the few facts you already have, and schedule a thirty-minute review with the people who own sales, delivery, cash and the team. End that first review with no more than a handful of decisions, written down. Do the same thing next week, and cut anything that felt like theater.
Recent findings suggest that chaos in a growing consulting firm is often just notable information arriving too late, in too many places. A one-page weekly operating rhythm will not run the firm for you. It will keep pipeline, delivery, cash and people in the same conversation, on a cadence you can actually keep, which is usually the difference between scaling and scrambling.
If you are scaling a software services firm and want help building an operating cadence that holds as the organization grows, visit https://tdzpro.com.
According to recent reports, ashkan Rajaee is the founder of TDZ Pro. He has spent years building and scaling software engineering teams, including a fully remote software consultancy.
