Name the two service contexts
Founder support can include company administration and explicitly authorized personal logistics, but convenience does not erase the boundary between them. Write two service contexts with separate accountable owners, permitted tasks, systems, funding, records, working windows, and exclusions. State whether personal assistance is part of employment or provider scope and obtain qualified employment, tax, privacy, security, finance, and legal review where applicable. The assistant should not infer permission from trust or long service. A clear design protects the founder, company, assistant, family, and vendors by making it possible to identify which authority governs before information is shared or money is spent.
Classify requests before action
Give every incoming request a simple classification: company, authorized personal, mixed, or unresolved. Use the purpose, beneficiary, source of funds, record owner, systems involved, and decision authority rather than the requester's preferred label. A dinner reservation may be personal; a customer dinner may be company work; a trip combining both requires separation. When facts are missing, hold the request and ask the designated owner. Do not place the assistant in the position of deciding a tax or legal characterization. Record the accepted classification for recurring cases so the same ambiguity does not return through a different channel.
Keep money and approvals separate
Use distinct payment methods, budgets, approvers, receipts, reimbursement routes, and accounting records. Company purchasing authority should not become a general personal wallet, and a founder's personal card should not obscure a company commitment. State thresholds and prohibited categories for each scope. If one transaction combines purposes, obtain an approved allocation before purchase or route it to finance. The assistant can prepare options and evidence but should not determine deductibility, compensation treatment, or beneficial ownership. Never copy full card details into a task tracker. Reconcile refunds, credits, deposits, subscriptions, and disputed charges to the correct owner.
Control identities and records
Prefer company identities for company work and designated personal identities for personal work. Map mailboxes, calendars, contacts, documents, travel profiles, vendor portals, devices, password managers, forwarding, and recovery methods. Avoid syncing an entire personal account into a company system for one workflow. Company records should remain accessible to authorized business owners during absence or transition; personal records should not become broadly available because the assistant changes roles. Name who can revoke each access and how urgent continuity works. Technical permission to view both contexts never authorizes information to move between them.
Handle family and household requests
Define whether and how a spouse, family member, household employee, adviser, or personal vendor can request work. A relationship to the founder is not automatically delegated company authority. List the people allowed to initiate personal tasks, the categories they may request, spending limits, confirmation rules, and escalation owner. Company staff, customer, candidate, board, and employee information should not be disclosed to family without a valid authorized basis. Likewise, family preferences should not silently change a business calendar commitment. The assistant needs a respectful holding response for requests that cross or exceed the written boundary.
Protect personal and company privacy
Apply minimum necessary access in both contexts. Personal work may involve home addresses, identity documents, family schedules, health-related information, or private financial details; company work may involve employees, customers, transactions, security, or board matters. Store each in its approved system and share only with the audience needed for the task. Do not use a common spreadsheet as a shortcut across domains. Set retention and deletion rules and record wrong-recipient incidents. Privacy language should not claim absolute secrecy: the assistant must know when safety, security, legal, or authorized specialist escalation applies.
Plan travel with two scopes
For blended travel, separate business itinerary requirements, personal companions, upgrades, leisure segments, payment, insurance, loyalty information, ground transport, and calendar disclosure. Confirm which changes support may make and who accepts extra cost. A company itinerary may need continuity evidence without exposing a companion's identity or private plans to a wide team. Personal extensions should not alter customer promises or business expense records silently. During disruption, present options that show the consequence for each scope. Route immigration, tax, medical, security, and duty-of-care questions to qualified owners instead of resolving them as booking preferences.
Set conflict and escalation rules
Identify conflicts such as a personal vendor seeking company work, a family request competing with a board commitment, company staff asked to perform household tasks, or private information influencing a company decision. Give support a confidential route to pause and disclose the facts to an authorized reviewer. The solution may be separate ownership, recusal, a different vendor, explicit approval, or declining the request. Avoid asking the assistant to balance founder loyalty against company duty privately. Urgency is not authority. Record the decision and controls while limiting personal detail to people who need it.
Review a mixed request
Suppose a founder asks an assistant to arrange a family celebration during a company offsite week using the same venue. The assistant should classify attendees, contracts, payments, calendar blocks, vendor communications, data, and cancellation terms separately. Company negotiation information should not subsidize or influence the personal event without authorized review. The founder decides personal preferences; the company event owner protects business requirements; finance classifies costs. A combined logistics plan can show dependencies, but its records and approvals stay distinct. This method keeps a convenient shared venue from creating an unrecorded company benefit or exposing private guest details.
Recertify the boundary
Review the boundary when the founder's role, family authorization, assistant scope, provider relationship, systems, travel pattern, or company governance changes. Sample mixed requests, reimbursements, access groups, and records. Remove permissions no longer used and update examples that produced repeated questions. HireExecutiveTeam founder operations support can coordinate approved workflows inside a written model, but the founder and company owners retain their respective decisions. The immediate next step is to list ten recent requests, classify them with the proposed rule, and resolve every disagreement before granting wider access or treating the pattern as routine.
Related resources
Read also: Founder operations support and Founder assistant role scope.
Frequently asked questions
Can one assistant handle both company and personal work?
Sometimes, when both scopes, systems, funding, authority, privacy, capacity, and escalation paths are explicit.
Can a founder's family member direct company work?
Only when a valid delegation defines that authority; the relationship alone is not enough.
Ready to define the role?
Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.
Book a consultation