Fractional Ops

Fractional Director of Operations & Customer Experience · Remote · Two days a week · $9,000 for the quarter

There are five places where most trips break. Fixing them is a job, and for one quarter it can be mine.

I work with multi-day tour operators, boutique hoteliers, and transportation providers whose growth has outrun their process. Not as a consultant who writes a report. As the operations director you don't have a full-time budget for yet.

Rob Fielding · 25 years in cruise, resort, hotel, and tour operations

The situation

Your company got good, then it got busy.

In the beginning the founder knows every booking, every supplier, every guest by name. Quality is high because one person is holding the whole picture. Then the company grows. More programs, more suppliers, more staff. The picture gets bigger. It's still living in two or three heads, because nobody has time to write it down.

That's the trap, and it only happens to companies that are working. It also has a shape you can recognize.

Response

A guest question that used to be handled in an hour now takes a day. Nobody is certain whose question it is.

Consistency

Excellent when your senior person is on. Fine when they're not. Your consistency is a person, and that person takes vacations.

Leverage

The founder is confirming transfers again. The GM is in the group inbox. Your most expensive hours are doing your cheapest work.

Burnout

People who genuinely care are leaving anyway. Effort is covering for structure, and effort doesn't renew.

Three or more and I'd stop looking at the people. Someone resigning or having a bad week doesn't cause this. It shows you what was already true.

The five

Different countries, different price points, the same five breakdowns.

Twenty-five years in and I keep waiting to find a sixth. Count how many you've seen in your own operation in the last ninety days.

  1. 01

    The unconfirmed transfer

    The booking existed. The confirmation loop did not. The guest stands at arrivals watching everyone else leave.

    COST: the first hour of the trip, and the tone of every hour after it.

  2. 02

    The note that never reached the kitchen

    The allergy was in the file. The file was not in the room where dinner was made.

    COST: guest safety, an apology dinner, and a review that writes itself.

  3. 03

    The staff member on last week's information

    Two versions of the itinerary in circulation. The guide has the wrong one. Nobody finds out until the bus is moving.

    COST: a missed visit, a scrambling driver, and a refund conversation.

  4. 04

    The process that lives in one head

    One person holds the whole picture. Then that person goes on vacation, resigns, or simply has a bad week.

    COST: every decision waits. Response times triple until they return.

  5. 05

    The problem nobody owned

    Something went wrong. The guest knew. Two days passed before anyone answered, because nobody knew whose job the first move was.

    COST: the difference between a loyal client and a public complaint.

Not one of those is a people problem. Each is something a system should have caught, and it didn't.

The work

What I actually do, once I'm in.

Two days a week, remote, working inside your operation rather than alongside it. I hold the operations seat: decisions, escalations, supplier conversations, and the building that never gets done because everyone is busy running trips.

  • One live version of every itinerary, and a team that knows where it lives.
  • A named owner for the first hour when something goes wrong, so the response stops depending on who happens to be awake.
  • Supplier and guide briefings as structured documents instead of forwarded email threads.
  • Special requests, from dietary to mobility to celebrations, on a written path from intake to delivery.
  • Run sheets and pre-departure checklists your team will actually use, because they were built with the people who run them.
  • A response-time number you know rather than one you estimate.
  • Your senior people back on the work only they can do.

Every system gets handed over with the person who will own it after I leave. That handover is the deliverable, not a document.

How it works

Four steps, about three weeks from application to running.

  1. You apply

    The form below, about five minutes. I read every one myself and reply within a business week either way.

  2. We talk for thirty minutes

    No pitch. I ask what broke most recently and what it cost you. You'll leave that call with at least one thing worth fixing whether or not we work together.

  3. Two weeks of diagnosis

    I sit inside the operation, talk to the people running it, and come back with what's actually breaking and in what order I'd fix it. No charge, and it happens before either of us commits to the quarter. If the answer is that you don't need me, that's what I'll say.

  4. The engagement runs

    Two days a week for the quarter, with a named owner inside your team for every system we build.

Terms

What it costs, and what it doesn't include.

Investment

$9,000 for the three-month engagement.

Three payments of $3,000, one a month. Nothing is due until we start, and the two-week diagnosis happens before either of us commits to the quarter.

That is an introductory rate, and I'll tell you exactly why it exists. This is the first engagement I'm running in this format, and I want the case study more than I want the margin. In exchange I'll ask permission to write up what we fixed and what changed, anonymized if you'd rather. The next engagement is priced differently.

Whether $9,000 is a lot depends on numbers you already have. Work out what one refunded program costs you. Or what a founder's day is worth against a coordinator's, then count how many founder days went into confirming transfers last month. Most operators find the quarter pays for itself on a single failure that doesn't happen. If your arithmetic says otherwise, don't apply. I'd rather you kept the money.

  • One engagement this quarter. When it's filled, this page will say so.
  • Fully remote, up to two days a week, working in your time zone for the hours that matter.
  • Three months, reviewed at the end. No auto-renewal and no retainer that quietly continues.
  • Either of us can end it with thirty days' notice, and every system built is yours regardless.

What this isn't

It isn't a software implementation, and I don't sell one. It isn't a reorg, and I won't recommend one in the first month. It isn't a report: I build inside your operation and leave the systems running. And it doesn't come with guaranteed revenue or guest scores. What I can promise is that the work is done in your operation, with your team, on the failures you're actually having.

Who I am

Twenty-five years, and the pattern stopped surprising me.

Cruise, resort, hotel, and tour operations, in the field and in the office. I've run programs where the margin lived or died on whether a driver got the right sheet, and I've cleaned up after the ones where he didn't. Currently operating Inbound Spain, a boutique experiential travel company, which means the systems I'd build for you are systems I run myself.

Right now I'm publishing a thirty-day series on LinkedIn called Too Busy to Be Good: one failure pattern a week, what it costs, and the system that stops it. If you want to see how I think before you talk to me, read that first. It's free and it's the same material.

Questions

The things you'd want to ask.

How is this different from hiring a consultant?

A consultant analyzes and recommends. I hold the seat. I'm in your systems, on your supplier calls, and accountable for whether the thing we built is still running in month three. The work product is a functioning operation, not a deck.

We're small. Are we too small for this?

If you're running multi-day programs and the founder is still confirming transfers, you're the size this is built for. Companies large enough to have a full operations director don't need a fractional one.

What do you need from us to be useful?

Access and one decision-maker who can say yes. I need to talk to the people running trips, see the real documents rather than the tidy ones, and have someone who can approve a change without a committee. That's it.

Two days a week doesn't sound like much.

It isn't, and that's deliberate. Most of what breaks in an operation breaks for structural reasons, and structure is built in focused blocks, not by being permanently available. If your operation genuinely needs someone five days a week, you need a full-time hire and I'll tell you so.

What happens to the systems when the quarter ends?

They stay, and they stay with a named owner on your team who has been running them alongside me before I leave. A system that only works while I'm in the building isn't a system.

Do you work with competitors?

One engagement at a time, and I won't take a directly competing operator in the same market during or immediately after yours. Ask me about your specific market on the call and I'll be straight with you.

Nine thousand seems low for this. What's the catch?

There isn't one, but there is a reason. This is the first engagement I'm running in this format, and a documented result is worth more to me right now than a higher fee. You get the introductory rate, I get a case study I can point at. That trade only works once, so the next engagement won't be priced this way.

What if it isn't working?

Thirty days' notice, either direction, no penalty. The two-week diagnosis exists partly so we both find that out before the quarter starts rather than during it.

Apply

One engagement this quarter.

Five minutes. I read every application myself and reply within a business week, including the ones I turn down and why.

Be specific. This is the question I actually read first.

What you send here reaches one inbox, mine, and is used only to reply to your application and to have the conversation that follows. It isn't sold, shared, or added to a mailing list. Ask me at rob@terraversed.com to delete it and I will.