Three Ways to Be a Navigator: The Fractional CMO, the Program Manager, and the Client Lead

A few years ago I watched two marketing leaders take over the same kind of company in the same month. Both were good. Both had run teams at Series B SaaS companies before. Six months in, one had a bookings plan the CFO trusted and a team that knew what Monday was for. The other had a beautiful strategy deck and a team that was busy. The difference was not talent. It was where each of them started on day one, and what each of them accepted as proof that something was working.

That is the thing about the Navigator, the leadership seat among the four Syntropy roles from my book. The job is the same everywhere: own the map of who it's for and what it's for, guard the signal, keep the other three roles pointed at one story. But the people who do it well do not all do it the same way. Over the years I have seen three distinct ways of being a Navigator, each with a different first move and a different definition of evidence. I have given them names, because a name is easier to argue with than a category. They are composites, not colleagues: each one is built from a dozen practitioners I have worked alongside at T2D3 and inside the companies we have served.

We have started using them inside T2D3 OS as well. When the app does Navigator work, it says which of the three did it. More on that at the end.

Marieke de Vries, the Fractional CMO

Marieke's first move is an audit, not a plan. Before she writes a single objective she has pulled customer acquisition cost by channel, pipeline coverage against the bookings target, the ARPU and net revenue retention trends, the SaaS Magic Number, and the time-tracking data that shows where the team's hours actually go. She reads the last three board decks and writes down what was promised next to what was delivered. Only then does she write the plan, and the plan is one page.

She explains every decision in ROI and stage fit. She will not call a plan ambitious. She will tell you what it costs, what it returns, and in which quarter the return shows up. The stage matters enormously to her: a company at $2M ARR gets protected from the tactics that belong at $10M, however much the founder wants the bigger-company playbook.

Her craft is running the quarter on a small number of owned outcomes. Each has a named person, a leading indicator, a lagging metric, and a date. She knows roughly what a Sculptor, a Scribe, and an Engineer each cost per hour and produce per week, and she reallocates monthly instead of annually. Her board deck is built so a CFO can forward it without her in the room.

What she hands over: the audit, the one-page plan, a weekly priority list the whole team can see, and a board update that takes ten minutes to read. Her hardest deliverable is telling a founder that the product is not ready for the demand the plan would generate, and staying employed afterward.

The evidence she cares about: a company that hit its bookings plan four quarters running on a smaller marketing budget than the year before.

Santiago Ibarra, the Program Manager

Santiago's first move is a drawing. Before he schedules anything he maps the dependency graph: which work is waiting on which, who owns each node, and where one person is the bottleneck for three streams at once. His view is that most missed deadlines are visible a month early on that drawing. The discipline is looking at it.

He explains decisions in throughput, cycle time, and what got unblocked this week. He never says a team is busy. He says what shipped and what is waiting.

Where Marieke runs a quarter on outcomes, Santiago runs it on a cadence. Quarterly objectives with measurable key results. Weekly priorities reviewed every Monday. A rule that anything shippable ships within 72 hours of being done, because work that sits loses its signal. Every task has one owner, never two. Status is red, yellow, or green with a sentence attached. A meeting exists to make a decision or it gets cancelled. When a ball gets dropped he treats it as a system failure and changes the cadence, not the person.

What he hands over: the OKR set, the weekly priority list, the dependency map, and a monthly note on what the cadence caught and what it missed. He can run a review with a founder, a designer, and an engineer in twenty minutes and leave each of them with exactly one thing to do.

The evidence he cares about: a quarter where every key result was either hit or called early, and nobody worked a weekend to make that true.

Aisha Rahman, the Client Lead

Aisha's first move is reading. Before her first call with a client she has read the contract, the last three status reports, and the last three escalations. She wants to know what was promised, what the client believes was promised, and where those two diverged. Her experience is that most account problems are expectation problems, and that they were visible in writing months before anyone called them a problem.

She explains decisions in three terms: the client's outcome, the health of the relationship, and what the team can sustain. She never calls an account strategic. She says what it renews at, what it could expand to, and what would make it leave.

Her craft is expectation-setting in numbers and dates, then meeting them, then confirming in writing after every conversation so no version of the agreement lives only in someone's memory. She sits between two parties who speak different languages. She turns a founder's frustration into a prioritized change request the roles can execute, and a technical constraint into a business trade-off the founder can decide on. She never forwards a raw complaint in either direction. Bad news, in her hands, is a deliverable with a deadline.

What she hands over: a status note the client can forward to their board, a running list of open commitments in both directions, and a monthly early-warning read on every account that says which ones are at risk and why. She can hold a call where the client is angry, agree with the parts that are fair, and end with a plan.

The evidence she cares about: a client who calls before something goes wrong rather than after, and who renewed without a negotiation.

Same seat, three first moves

Put the three side by side and the pattern is clear. Marieke starts with the numbers. Santiago starts with the graph. Aisha starts with the record. All three end up guarding the signal, which is the whole Navigator job, but each guards a different part of it: the economics, the flow of work, and the relationship. A founder hiring a Navigator should know which one the company needs this year, because the wrong fit is not a bad hire, it is a good person aimed at the wrong problem.

I have also found the names useful for the people in the seat. Most Navigators I know are strongest as one of the three and competent at the other two. Knowing which is which tells you what to build up and, more usefully, what to delegate.

What T2D3 OS does with this

T2D3 OS runs as a Syntropy team, so it does a great deal of Navigator work: the ICP, the personas, the value propositions, the growth-stage assessment, the budget mix, the objectives and key results, the weekly ask to the founder. Until now, the app said "the Navigator did this." Starting with this release it says who, specifically. The ICP and the plan are Marieke's. The OKRs, the scorecard, and the workshop cadence are Santiago's. The weekly founder ask and the engagement status are Aisha's.

This is deliberate on two counts. First, the archetype is chosen by the kind of artifact, never by the model deciding on the fly which persona it feels like today. A budget mix is always Marieke's work; the routing is a table, and a test in our codebase fails if someone maps a Navigator artifact to an archetype from another role. Second, the name carries the standard. When the app says Marieke produced the plan, you should hold it to Marieke's bar: cost, return, and when the return shows up. If it cannot answer those three, it is not done.

The people named here are composites, not staff or candidates. If you recognized yourself in one of them, the Navigator careers page shows all three next to the growth ladder for the role, and the open roles are there when you are ready. The other three seats get the same treatment: the Scribe, the Sculptor, and the GTM Engineer.