Skip to content
fidelic.ai®®
Hire

Coming up next · Meet ALEK · Executive Operations Chief of Staff

The founder starts with the decisions, not the inbox

Meet ALEK, an executive operations employee. ALEK turns the founder’s calendar, email, Slack, goals, meetings, and open promises into a current decision record. Strategy, sensitive judgment, and representing the founder stay with a human chief of staff.

First useful file
A morning priorities and decisions brief tied to current company records
Planned first delivery
The first morning after approved systems connect
Best for
Founders whose calendar, inbox, projects, and company goals no longer fit in one mental picture

Expert tier · In formation. See how the tiers work.

The workflows ALEK owns

One employee carries the work from the first fact through the next decision. The files below belong together because they use the same business record and improve one another.

  1. 01

    Daily executive brief

    Builds the morning view from current goals, due commitments, changed risks, calendar context, messages, and decisions only the founder can make.

    • Morning priorities brief
    • Decision queue
    • Calendar context note
    • At-risk commitment list

    Each workday morning with material updates

  2. 02

    Correspondence and calendar

    Prepares truthful drafts, agendas, scheduling choices, and context while the founder retains voice, send authority, and relationship judgment.

    • Correspondence draft queue
    • Scheduling decision brief
    • Meeting context card
    • Response and follow-up log

    Continuous within approved channels

  3. 03

    Meeting operations

    Carries each material meeting from purpose and pre-read through notes, decisions, commitments, unresolved questions, and follow-up.

    • Agenda and pre-read
    • Meeting record
    • Decision log update
    • Commitment and follow-up queue

    Before and after each material meeting

  4. 04

    Company priorities and projects

    Connects company goals to owned work, dependencies, evidence, due dates, risks, and decisions across functions.

    • Company priority map
    • Cross-functional dependency record
    • Risk and blocker brief
    • Owner review packet

    Weekly with daily exception watch

  5. 05

    Executive reporting and memory

    Preserves why a decision was made and reports what moved, what slipped, what changed, and what the founder must decide next.

    • Weekly executive report
    • Decision history
    • Commitment ledger
    • Monthly operating review

    Weekly and monthly

Illustrative work product

A file you can inspect before ALEK ships

This is not customer work. It is the first-file test: a concrete packet that shows the facts, open decisions, boundaries, and next action the employee must carry.

  • The illustrative company, people, commitments, and figures are fictional and are not customer work.
  • Executive decisions, consequential communications, personnel judgments, and company commitments remain outside the role.
  • Priority and status claims are tied to current records, named owners, and explicit company goals.

ALEK-01 · formation file

A morning priorities and decisions brief tied to current company records

Illustrative

Illustrative sample · not customer work

Monday morning priorities and decision brief

Illustrative file for the founder of a ten-person services company. The company is renewing two customer agreements, hiring an operations manager, collecting a late invoice, and preparing a product announcement. The brief organizes current records. It does not make executive decisions or infer that a person failed because a task is late.

Today’s three founder decisions

First, approve or change the customer renewal position before PRAX prepares the response due Tuesday. Second, decide whether the operations-manager opening remains active after ZEFA’s downside cash view moved the preferred start date. Third, approve the factual claims in the announcement brief before editorial work continues. Each decision includes the source packet, owner recommendation where one exists, consequence of delay, and latest useful decision time.

Commitments at risk

The late customer invoice has an owner-approved follow-up due at 10:00 a.m.; no reply has been recorded. A security questionnaire promised for Wednesday lacks one data-retention answer. The product announcement depends on a customer example that is not approved for public use. ALEK reports the missing evidence and dependency. It does not describe an accountable person as careless or replace the person’s status with a guess.

  • 10:00 a.m.: founder review of the collections draft and current account history.
  • 11:30 a.m.: customer renewal decision with PRAX brief attached.
  • 2:00 p.m.: hiring timing decision with ZEFA cash scenarios and LILA opening status.
  • 4:00 p.m.: announcement claims review; remove the customer example unless written approval arrives.

Meeting preparation

The weekly company review has one purpose: resolve work that crosses functions. The pre-read contains seven commitments, three changed dates, two decisions, and one new risk. Routine status items remain in the written record. The meeting agenda reserves time for the renewal, hiring timing, and security dependency rather than reading every project aloud.

End-of-day close

At day end, ALEK will report decisions made, changed commitments, unresolved questions, and tomorrow’s first dependency. Draft correspondence remains unsent until approved. Any disagreement between meeting notes, system records, and an accountable owner stays visible and is routed for confirmation rather than silently resolved.

ALEK next to the tool and human paths

Motion plans calendars, tasks, projects, meetings, notes, and reports inside its work system. ALEK connects the founder’s calendar, email, Slack, goals, projects, and commitments into a current executive record. A human chief of staff remains the right choice for strategy, political judgment, and representing the founder.

What ALEK, Motion, and a Human chief of staff each do.
ResponsibilityALEKMotionHuman chief of staff
Schedule tasks, projects, and calendar timeYesYesYes
Capture meetings and action itemsYesYesYes
Prepare a morning decision briefYesLimitedYes
Keep promises, decisions, and slippage connectedYesLimitedYes
Set company strategy or prioritiesNoNoYes
Represent the founder’s judgmentNoNoYes

Tool column checked against the official Motion product page on August 6, 2026. Features vary by plan. “Limited” means the option covers part of the row or still needs someone to operate it.

What forms ALEK

These are the primary sources that establish the work, current requirements, and professional boundaries. The live employee will check current sources again when the work begins.

The first month with ALEK

By day 30, every material company commitment and open decision has a reason, accountable owner, current evidence, due date, and visible next action.

  1. 01 · Day 1

    I map company goals, current commitments, decision rights, projects, meetings, systems, and the founder’s preferred brief.

  2. 02 · Week 1

    I deliver daily briefs, meeting records, the first commitment ledger, and a cross-functional risk and decision queue.

  3. 03 · Month 1

    I maintain the company operating view and deliver the first monthly review with decisions, movement, drift, risks, and next commitments.

Works with your existing systems

  • Slack
  • Email
  • Calendar
  • Notion
  • Asana
  • Linear
  • CRM
  • Google Drive
  • Microsoft SharePoint

What ALEK does not do

I do not impersonate the founder, conceal machine authorship where disclosure is required, or send consequential correspondence without approval.

I do not make strategy, hiring, firing, spending, legal, financial, customer, or partnership decisions.

I do not rank employee worth, infer motivation, or turn missing updates into performance judgments.

I do not label a commitment complete without the agreed evidence or accountable owner confirmation.

The line that does not move

I will not impersonate the founder, make an executive decision, conceal uncertainty, or assign blame from incomplete records.

When the record conflicts

If systems, notes, owners, or founder instructions disagree, I preserve the conflict, lower confidence in the affected brief, and ask for the smallest decision needed to proceed.

Functional adjacency

The employees ALEK hands work to

Put ALEK next in line

Tell us which part of the function is still sitting with you. We will use that work to set the release priority and the test this employee has to pass.

Tell us you need ALEK