Founder Assistant vs Executive Assistant: How to Scope the Role

The label hides three different choices

Founder assistant can mean business executive support, personal support, or a deliberately blended role. Executive assistant usually signals company-focused work, but titles vary widely. The practical task is to identify who benefits from each workflow, who pays, which system holds the record, and who may authorize the action. A founder should not use a flexible title to postpone decisions about privacy, employment scope, reimbursement, working hours, or conflicts between company and personal priorities.

Inventory requests by beneficiary

Review a representative month and classify every request as company, personal, mixed, or out of scope. Investor scheduling, leadership meeting preparation, and company travel serve business outcomes. A family itinerary or household appointment may be personal even when it protects the founder's time. Mixed requests need an explicit treatment. Record frequency, sensitivity, required tools, expense source, after-hours demand, and the decision maker. The resulting inventory is more useful than a list of generic assistant skills.

Draw the company-work boundary

Company work belongs in approved company identities and systems. The role can coordinate executive access, prepare business meetings, maintain commitments, route correspondence, and organize company travel under written authority. It should preserve records the company owns and support continuity when personnel change. The founder remains accountable for strategic, legal, people, financial, and governance decisions. A close working relationship does not allow the assistant to treat company assets or information as the founder's personal property.

Design personal support on purpose

If personal work is included, describe permitted categories, employer or contracting entity, tools, reimbursement, insurance, record ownership, confidentiality, backup, and working-time expectations. Some personal information should never enter a company task system. Health, identity, household, financial, and family details require especially narrow handling. Obtain appropriate professional guidance for the arrangement rather than assuming that a company job description, general confidentiality clause, or founder approval resolves every obligation.

Handle the awkward mixed request

Imagine a business trip extended for a family event. The company portion may include approved flights, customer meetings, and business accommodation; the personal extension may require separate payment, records, and approval. The assistant needs a rule for allocating changes and credits without exposing family information to unnecessary company viewers. The same discipline applies when a personal relationship requests company access or a business contact sends a private invitation. Mixed does not mean ungoverned.

Make priority collisions visible

A board deadline and a household disruption can both be urgent. The assistant should not invent which one wins. Define who can resolve collisions, what minimum context they receive, and how affected stakeholders are informed. State any emergency categories in advance and distinguish immediate safety from convenience. Track after-hours demand and personal work that displaces business commitments. Without that evidence, the founder may believe one blended role has spare capacity while the assistant is quietly making high-consequence tradeoffs.

Use separate identities and least privilege

Do not share the founder's passwords to simplify a blended scope. Use individual identities, delegated permissions, multifactor authentication, and approved storage. Personal and company accounts should remain separate where ownership and retention differ. Access to a calendar does not imply authority to disclose details or accept every invitation. Maintain an inventory showing purpose, approver, review date, and revocation owner. Remove permissions when a workflow or relationship ends.

Tell close stakeholders how the role works

Family members, investors, employees, and long-standing contacts may each assume a different relationship with the assistant. The founder should communicate the approved routing and limits rather than leaving the assistant to negotiate status alone. Provide a respectful refusal and escalation path. A message such as I can route that request but cannot share the calendar detail protects both service and boundary. Repeated attempts to bypass the rule should reach the founder or named company owner.

Recruit with the real scope

Candidates should see the proportion of company, personal, mixed, travel, and after-hours work before accepting the role. Use scenarios that reflect those categories without exposing real private information. Ask how the candidate would separate records, clarify payment, respond to a family request for company information, and surface a collision. Do not advertise an executive role and reveal household duties after hire. Consent to the actual scope supports better selection and retention.

Measure the two systems separately

For company work, review meeting readiness, commitment closure, calendar rework, and accepted business records. For personal work, use only appropriate service measures agreed under that arrangement. Across both, monitor priority collisions, access exceptions, reimbursement problems, after-hours load, and work stored in the wrong system. Avoid a single productivity score that encourages sensitive overcollection. The purpose is to see whether the blend remains controlled and sustainable.

Know when to split the role

Split ownership when personal volume regularly displaces company outcomes, company reviewers gain unnecessary access to personal records, one employment arrangement cannot support both scopes cleanly, or coverage becomes unsafe. Separate roles may also be appropriate when business complexity requires specialized executive support. A split does not need to create duplicate coordination: the founder can define one small handoff for genuine calendar conflicts while keeping records, budgets, and authority distinct.

Plan the exit before trust is tested

Document which company records must be returned, which personal records belong to the founder, how open commitments transfer, and who removes every permission. Avoid copying one domain into the other during handoff. The receiving person should accept time-sensitive work from a controlled register, while security confirms revocation for company systems. Clear exit rules protect a good relationship and reduce the temptation to leave broad access active because nobody can locate the current instructions.

Review the arrangement after a bounded cycle

Pilot only the approved categories, then review a normal period and a peak. Ask whether the assistant could identify the right system, payer, owner, boundary, and evidence without relying on private memory. Correct unclear routing and remove unused access. Publish the accepted version where relevant people can find it. A successful founder-support design protects the founder's time while keeping company obligations, personal privacy, and the assistant's sustainable scope visible.

Related resources

• Founder operations support
• Executive assistant support
• Founder support role scope checklist