Lesson 4 — Tactical Operations: Calendars, Pre-Wiring, and Juice¶
"The tiny little stuff, like, did you get the deck ready, is really more of a manifestation of, did you work with the people properly to get the deck ready? The deck ready is not a technical skill. The deck ready is a person skill."
— David Russell
The Org You Operate Inside¶
Before the tactical habits, understand the structure you are operating inside — because the Project Coordinator role only makes sense in context.
At Cortado, the people who sell the work are not the people who do the work. This is intentional.
"The best proposition, frankly, is that the sellers who are good at selling keep selling. They don't get bogged down in doing."
— David Russell
Bill, Dan, and George win engagements. They are good at building relationships, identifying pain, and closing deals. The moment they get pulled into day-to-day delivery, they are no longer selling. That is a bad trade for the firm.
So they do not deliver. Consultants (staff or 1099) do the technical work. The Project Coordinator keeps the engine running between them.
The Seller's role does not end when the contract is signed. It evolves:
"It evolves. In the end, it is still his relationship and it is still his on the line. If we don't deliver, he doesn't get more money, right? Like, he won't get another commission check from this client if he can't sell them another gig... Are we serving you? Does your leg feel better? Just every week, another touch point."
— David Russell
The account lead's job during an active engagement is relationship maintenance — regular touchpoints with key client stakeholders to make sure they feel heard and confident. Not delivery. Not project management. Relationship.
That leaves a gap. Someone has to own the operational machinery: the calendar, the deck, the Asana board, the risk log, the action items, the stakeholder map. That is the Project Coordinator. You are the connective tissue between the Seller who holds the relationship and the Consultant who does the work — making sure neither drops a ball that costs us the next engagement.
1. The Consultant Time Crunch¶
As a Project Coordinator, you are the guardian of our team's most precious resource: consultant time.
In a virtual organization, it is dangerously easy to accidentally over-schedule people. A consultant who is booked on two overlapping projects does not have twice the capacity — they have half the focus on each, and they will work until midnight to compensate.
"A virtual organization can make people do two people's worth of work. You do Client One conversation between 9 and 10. You do Client Two conversation between 10 and 11. You do Client One conversation again between 11 and 12... You slice up all the time, and now the time you actually get to do their work is between 5 p.m. and 10 p.m. That's the life."
— David Russell
Your operational mandate: Your primary job is to ensure projects do not run longer or cost more than we estimated. When timelines drag, consultants overlap onto new client kickoffs. Balls get dropped. The client that was already in-flight suffers, and the new client does not get full attention at the start.
This is not an abstract process risk. It happens constantly, and the Project Coordinator is the person positioned to catch it before it becomes a crisis.
2. Executive Calendar Management: The 3–4 Week Rule¶
One of the most common operational failures at the Project Coordinator level is waiting too long to book critical checkpoint meetings.
"A lot of the people that we need to talk to have calendars that are booked out pretty far... We try to get on their calendar two weeks out, and what a surprise — nobody has any time. And we can't get any decisions made because we can't meet with the people we need to talk to... You need to book these checkpoints in up front."
— David Russell
The rule: The moment a project kicks off, look down the timeline and map out every major stakeholder milestone. Book those calendar invites 3 to 4 weeks in advance.
If you wait until you "need" the meeting to book it, you will find an empty, uncooperative calendar. And when the meeting doesn't happen and the project slips, the delay is 100% your fault — not the executive's full schedule.
Project Coordinator Habit: Front-Load the Calendar
On kickoff day, open the project plan, identify every meeting that requires a senior stakeholder (PortCo executives, PE deal leads, department heads), and send all those calendar invites before the first weekly status meeting. It takes 30 minutes. It prevents weeks of compounding delays.
3. The 24-Hour Pre-Wire Strategy¶
A pre-wire is the practice of sharing information and aligning key stakeholders individually before they step into a group meeting.
If a senior PortCo leader or PE executive sees a challenging slide for the first time in a room full of peers and bosses, their first instinct is to protect themselves — which means pushing back publicly. A data point that should generate a productive conversation instead triggers a defensive argument.
Pre-wiring prevents that.
"How can we shape our client's perspective of our success? We can do that by having the deck to them 24 hours in advance of a meeting... Now that I have it available 24 hours in advance, I can do a pre-wire with all of my key stakeholders. All of my key stakeholders can understand what we're about to share before we share it so that they can work on making sure they support what we're saying rather than fighting us in front of everyone else."
— David Russell
The Project Coordinator's Pre-Wiring Process¶
Step 1 — Build the deck incrementally. The weekly status deck is built throughout the week, not in a panic Thursday afternoon. Your job is to push the consulting team to have their sections ready by Wednesday so the deck can be reviewed internally.
Step 2 — Deliver 24 hours out. Send the completed deck to key PortCo and PE stakeholders at least 24 hours before the live meeting.
Step 3 — Create space for private questions. A brief Slack message or email alongside the deck gives them room to flag questions or concerns before the meeting. By the time the call starts, they have already processed the information. The live meeting becomes a validation — not a surprise.
The Thursday-Night Trap
If the deck is not ready until Friday morning at 9 a.m. and the client call is at 10 a.m., there is no time for a pre-wire. The executive walks into the call cold. Anything uncomfortable on that deck becomes an in-room confrontation.
The solution is not to work harder on Thursday. The solution is to treat the deck as a living document built across the full week.
4. Delivering "Juice" in Week 1¶
Imagine the PE firm just signed a $300,000 engagement with Cortado. They wire the first $100,000. Friday afternoon arrives. It is time for the first Week 1 status deck.
If our deck says: "This week we learned that you bought a pizza company that sells to schools" — we have failed. They already knew that.
"We want juice. Tell me some meaningful s***. 'Your sales team seems weak. Your marketing team seems strong. They're not communicating.' They're paying all the money. They want to hear something valuable."
— David Russell
What "juice" looks like:
| Not Juice | Juice |
|---|---|
| "We reviewed the company's product portfolio." | "Their product catalog has 340 SKUs, but 80% of revenue comes from 12 of them. Nobody on the sales team knows which 12." |
| "We interviewed the marketing team." | "Marketing is producing strong top-of-funnel content, but it never reaches the sales team. There is no handoff process at all." |
| "We're analyzing the pipeline." | "Their Q3 pipeline looks healthy, but deal age skews long — average deal is 9 months old. Something is clogging the close stage." |
The second column says what we learned and why it matters. That is what earns confidence on Week 1.
The Project Coordinator's role in producing juice: You are not the one writing the insights. But you are the one structuring the deck, pushing the consulting team to articulate their observations in precise language, and making sure the output answers "what does this mean for the client?" not just "what did we do this week."
5. The Relationship and the Repeat Business¶
Everything in this lesson — the calendar management, the pre-wire, the juice — is in service of a single goal: making the client feel that we succeeded, so they hire us again.
The seller (our account lead) maintains the relationship. The consultant does the technical work. The Project Coordinator keeps the engine running between them. If the engine runs cleanly — decks on time, meetings booked, risks escalated early, client feeling heard — the relationship grows, and we get the next project.
"They buy confidence that the solution will be delivered, regardless of how messy, how muddy, how long it takes. If you have to work until midnight, you said we're going to have that driveway done by the 30th, and I need to sell on the 1st, so get the driveway done by the 30th."
— David Russell
Knowledge Check¶
Scenario
It is Thursday morning. The live weekly status meeting with the PE deal lead and the PortCo VP is scheduled for tomorrow, Friday, at 2:00 PM. The consulting team tells you they are still working on the data analysis and hope to have slides ready by Friday at noon.
- Based on the 24-hour pre-wire strategy, why is a Friday noon delivery a major operational risk?
- What are the specific consequences — political and relational — if we skip the pre-wire and the PortCo VP sees the data for the first time live on the Friday 2:00 PM call?
- What should you do on Thursday morning to recover the situation?
Discussion guide
1. Why Friday noon delivery is a major operational risk: The meeting is at 2pm — less than two hours of buffer. Not enough to review the deck, catch errors, brief the account lead, or reach any stakeholder before the live call. The 24-hour pre-wire standard exists because executives need time to process uncomfortable information privately before encountering it in a room with their boss or investor. Two hours eliminates that entirely.
2. Specific consequences of skipping the pre-wire: The PortCo VP sees challenging findings cold, in front of the PE deal lead. Their instinct is self-protection: they push back publicly, dispute the data, or shut down. The PE deal lead — watching this happen — loses confidence in Cortado's ability to manage the engagement. The call becomes about managing a defensive reaction rather than advancing the project. Even if the data is correct, the framing is adversarial because we created an ambush instead of a conversation.
3. What to do Thursday morning: Push the consulting team to produce a rough deck — even with placeholder slides — by Thursday at 5pm. Simultaneously, reach out to key stakeholders now: "Deck coming this evening — flagging a few things we'll walk through tomorrow." This sets expectations and buys goodwill even if the deck is imperfect. If the team genuinely cannot produce anything by Thursday, escalate to the account lead immediately so they can call the client before the Friday morning scramble begins.
Where You Go From Here¶
You have covered the full business context:
- Lesson 1: Why PE firms exist, how they make money, and what pressure is already on your clients when we walk in the door.
- Lesson 2: The difference between a project and a process, and why our estimates are built the way they are.
- Lesson 3: Why technical delivery is not enough — perception is reality, and you have to manage three corners of a political triangle simultaneously.
- Lesson 4: The specific weekly habits that keep an engagement on track — calendar management, pre-wiring, and delivering Week 1 insights that earn confidence.
Continue to Lesson 5 — The Hypothesis Problem to understand why we can never fully know the answer before we get in the door.