Core executive support

A dedicated executive assistant for the leader who holds the week together.

A CEO, founder, or senior leader who needs one dependable operator across the recurring work of the week.

Book a free consultationSee the scope of work
A support team coordinating the working day in an open officeDaily ownership, not ad hoc tasks

The role

Executive Assistant, defined before it starts.

An executive assistant is not a faster task list. The role is a layer of ownership between the leader and the coordination work that would otherwise consume their attention. The assistant prepares the meeting, protects the calendar, moves the inbox toward decisions, and follows up until an answer exists.

We place assistants for leaders who need that ownership on a predictable schedule. The scope is written before the first week, including the work the assistant owns, the work they prepare, and the decisions that stay with the executive.

When a leader carries their own coordination, the cost appears in small places: a meeting without context, a follow-up that depends on memory, a calendar with no room to think, or an inbox that turns every routine request into a decision. The leader is not failing at delegation. The role has never been defined.

Scope of work

What the assistant owns.

The written scope names the work, the standard, and the boundary. It is the reference point for onboarding and the first review, not a marketing description.

Calendar ownership across internal and external commitments, including protected focus time and preparation buffers.

Inbox triage with an agreed escalation path, drafted replies, and a daily summary of decisions that need the executive.

Meeting preparation that includes agendas, read-aheads, attendee context, and a clear record of next steps.

Travel coordination from itinerary and ground transport to backup plans and post-trip expense reconciliation.

Follow-through on commitments made in meetings, including owner, date, and status.

A working record of preferences, recurring tasks, and access boundaries that both sides can inspect.

Inputs and outcomes

What goes in. What comes out.

A role works when both sides know what they are responsible for supplying. These are the inputs we ask for and the outputs the engagement is designed to produce.

Inputs required

What we need from your team

  • The leaders in scope and the hours or days when coverage is needed.
  • Access to the calendar, inbox, and document systems your organization approves.
  • Existing priorities, recurring commitments, and the meetings that carry the most consequence.
  • Named decision rights, escalation contacts, and any confidential work that must be handled differently.

Deliverables

What the engagement produces

  • A written role scope and communication rhythm for the first month.
  • A maintained calendar with preparation attached to decision-making meetings.
  • A triaged inbox with a daily decision summary and clear ownership of follow-ups.
  • A travel and logistics record with confirmations, backups, and expenses reconciled.

How it works

A realistic first month.

No engagement starts with a perfect process. It starts with a clear scope, a controlled access set, and a short review cycle that corrects early.

Map the week

We inventory the recurring meetings, inbox volume, travel pattern, reporting cycles, and the points where the leader currently loses time.

Write the scope

The assistant's ownership, preparation work, access, escalation rules, and executive-only decisions are documented before matching begins.

Match and onboard

Candidates are assessed against the scope and the leader's communication style. Onboarding starts with approved access and a short, observable first-week plan.

Review the rhythm

At the first review, we inspect response times, calendar control, handoff quality, and the issues that still reach the leader unnecessarily.

Quality controls

How we know the work is holding.

Work is checked against the written scope rather than an informal understanding of helpfulness.

Calendar and inbox decisions follow documented rules, with exceptions escalated rather than improvised.

The first month includes explicit review points so small mismatches are corrected before they become habits.

Human boundaries

What remains a human decision.

  • The assistant does not approve contracts, spending, personnel decisions, or legal positions.
  • Sensitive stakeholder communication follows the escalation path your organization defines.
  • Access is granted by your team, limited to the role, and reviewed as the engagement develops.

Starting scenarios

What this looks like in practice.

These are common entry points, not promises about a specific outcome. The consultation tests which one matches your team.

The calendar is full but the priorities are not

The assistant rebuilds the week around the commitments that carry decisions, adds preparation time, and gives the leader a defensible way to decline or defer the rest.

The inbox has become the operating system

The assistant separates requests that need the leader from work that can be drafted, routed, or closed, then reports the pattern so the underlying volume can be addressed.

Common questions

Questions about executive assistant.

Is this the same as an administrative assistant?
The scope can include administrative work, but an executive assistant is assessed for judgment, communication discipline, and ownership of leader-facing work. The written scope makes the difference explicit.
Can the assistant work part time?
Yes. Coverage is defined by the work pattern. Some leaders need a few focused hours each day, while others need full-day coverage across time zones.
How do you protect confidential information?
Access is approved by your organization, limited to the role, and paired with escalation rules. Confidential decisions remain with authorized leaders.

Tell us what keeps landing on the wrong desk.

We will help define the scope, the coverage, and the next sensible step without pressure to commit.