Your First 100 Days With an Atlas Operator

Key takeaways

The first two weeks are preparation on both sides. You do not meet an operator until you both know exactly what is being handed over.
By day 30 the inbox and calendar have moved. By day 60 the recurring work is written down and the first automations are running. By day 100 you are deciding what the next layer is.
A weekly rhythm holds it together: a Monday brief, a daily end-of-day note, and a Friday wrap. Ten minutes of your attention a day.

Most EA relationships fail in the first ninety days, and almost never because of the person. They fail because nobody had a plan for what happens on day one. The founder hands over a login and a vague "just help me get organised", the assistant does their best to guess, and three weeks later both of them are quietly disappointed.

So here is the plan. This is the sequence every Atlas client goes through, with what we do, what you do, and what you should expect to notice along the way.

Before Day One: The Clarity Call

Everything starts with a conversation about outcomes, not a job spec.

We ask where the hours are going, what you have tried before, and the one thing you most want off your plate. We ask the question we ask everyone: what percentage of your week goes to the thing that would grow the business? We ask what your business looks like twelve months from now if this works, and what it looks like if nothing changes.

Then we are straight about whether this is the right moment. Some founders need a bookkeeper first, or a sales hire, or a month of sleep. If that is you, we say so. If it is not, we move to the audit.

What you do: one call, about forty-five minutes. What you notice: a written summary of what you said, in plainer words than you said it.

Most EA relationships fail in the first ninety days, and almost never because of the person. They fail because nobody had a plan for what happens on day one.

Days 1 to 7: The Energy Audit

Before anyone is matched to you, we map where your time and energy actually go.

You track a working week, hour by hour, in a simple template. Not to judge it. To see it. Then we go through the forty hours together and sort every block into one of three buckets: delegate, automate or delete.

The result is usually some version of the same number. Of a forty-hour week, around twenty-four hours did not need you. Some of it needed a person who was not you. Some of it needed a system that did not exist yet. Some of it needed to stop.

Out of the audit come two documents. Your ideal week, the version of the calendar with your focus time protected and your growth work at the proportion it should be. And the first draft of your Executive Support Checklist, every recurring task in the business, by cadence, with a note on who should own it.

What you do: track a week, one ninety-minute review call. What you notice: the list is longer than you expected and almost none of it needs you.

Days 7 to 14: The Match

Now we know what is being handed over, we pick the person.

Your operator is chosen from the bench on four things: the hours you work and the time zone you need them in, the mix of work on your checklist, the pace and communication style you described, and the industry context that will help them in week one. We send you their profile, the recording from their interview process, and a short note on why we picked them for you specifically.

Then an introduction call. Thirty minutes. If it is right for both of you, you have a start date. If it is not, we pick again, and you have lost thirty minutes rather than three months.

What you do: read a profile, take one call. What you notice: the person on the call already knows your checklist.

Weeks 3 and 4: Inbox and Calendar Move Across

The first fortnight with your operator is about the two systems that eat the most time: inbox and calendar. Everything else waits.

Inbox first. Access is set up at whatever level you are comfortable with. Your operator builds the labels, rules and filters, learns who matters, and starts drafting replies in your voice for you to approve. Within the first week you are reviewing flagged items for ten minutes instead of living in the inbox for ninety.

Calendar second. The ideal week from the audit becomes the real calendar. Focus blocks are protected. Meetings that should be emails become emails. Your operator starts sending the next-day brief every evening: what is on, who you are meeting, what you need to have read.

What you do: approve drafts, answer your operator's questions in a daily ten-minute note, give feedback bluntly and early. What you notice: the first morning you open your laptop and the inbox has already been handled.

Day 30: What Has Left Your Plate

A month in, the recurring work is moving across in order. After inbox and calendar come travel, meetings and follow-ups. Your next trip is booked end to end, with the car at both ends and the aisle seat, because that is on the checklist now. Meetings come with an agenda in advance and notes afterwards, and every follow-up is chased without you remembering to ask.

This is also when your Executive Atlas starts to fill up. Every task your operator takes on gets written to the four-part standard: trigger, how it is done, what done looks like, when to escalate. You explain something once, it goes in the Atlas, and you do not explain it again.

In practice. a founder told his operator in week three, "chase invoices on day seven, call on day fourteen, then escalate to me." It became a written process that afternoon. Two months later his operator was on leave for a week, the cover person ran the same process from the Atlas, and he did not notice the difference until he was told.

What you notice: you are explaining things once. Your Friday afternoons are different.

Day 60: The Automations Arrive

With the recurring work mapped and running by hand, your operator starts building. This is the part the old assistant model never got to.

The weekly report that used to take two hours on a Sunday night becomes an agent that pulls the numbers, drafts the summary in your voice, and sends it to your operator first. They read it, fix the two things the agent got wrong, and send it to you and the team. Invoice reminders go out on schedule. CRM records are updated from meeting notes. Research and first drafts arrive before you ask.

Every automation has a human reading its output before it reaches you. That is the rule, and it is why you get the speed of the tools without inheriting their mistakes.

What you notice: things arrive finished. Your operator starts telling you what they automated last week rather than asking what to do next.

Day 100: Compound

By now the first layer is done. The inbox is at zero at the end of every day. The calendar is yours. Travel, meetings, follow-ups and reporting run without you. Your checklist has somewhere between thirty and sixty tasks on it, and your name is next to a handful.

The hundred-day review with your account manager is about the next layer. Usually that is one of three things: the household and family logistics that have been eating the hours you got back, the operations work your senior people are drowning in, or the one project you have been meaning to start for a year.

Behind the scenes, your operator has had three months of coaching, one new skill added through the Atlas training, and a pod of other operators to learn from. They are better at your business than they were on day one, and they will be better still at day 200.

What you notice: you are answering the growth question with a number that starts with a three or a four.

The Weekly Rhythm That Holds It Together

None of this depends on heroics. It depends on a rhythm.

Monday brief. Fifteen minutes. The week ahead, the priorities, anything that changed.
Daily end-of-day note. Written by your operator. What was done, what needs you, what is coming tomorrow. Two minutes to read.
Friday wrap. Thirty minutes. What moved, what did not, what to change next week. Your operator comes with the list.

That is roughly ten minutes a day of your attention, and it is the whole management overhead.

What You Do and What We Do

Stage	You	Atlas
Clarity call	One 45-minute conversation	Written summary, honest fit assessment
Energy audit	Track one week, one review call	Sort every hour: delegate, automate, delete. Ideal week and first checklist
Match	Read a profile, one intro call	Select from the bench on hours, work mix, pace and context
Weeks 3 and 4	Approve drafts, daily ten-minute note	Inbox to zero, calendar rebuilt, next-day brief
Day 30	Explain things once	Travel, meetings, follow-ups owned; Executive Atlas filling
Day 60	Read what arrives	Automations built and checked by a human
Day 100	Decide the next layer	Review with your account manager; coaching continues

If you want to know what happens before any of this, how the person on the intro call was chosen in the first place, that is here. If you want to see what the hundred days produced for other founders, start here.

Frequently Asked Questions

How Long Until I Am Actually Matched?

Most clients are matched within 14 days of finishing the Energy Audit. The audit itself takes about a week, so from the clarity call to meeting your operator is usually two to three weeks.

How Much of My Time Does This Take?

The first two weeks are the heaviest: the clarity call, the audit, and the handover conversations, roughly three to four hours in total. After that it settles to about ten minutes a day plus a thirty-minute Friday wrap.

What If the Match Is Wrong?

You tell your account manager, we work on it, and if it does not improve we rematch you. Your Executive Atlas, the checklist and every written process carry across to the new operator, so you do not start again.

Can I Give Access Gradually?

Yes, and most people do. Inbox and calendar come first, usually in week three. Payments, travel accounts and personal systems come as trust is built, with permissions set at whatever level you are comfortable with.

Atlas places and trains executive operators, and coaches the founders who work with them. See what you are actually buying or book a call.