Ten real, anonymised examples of work executive assistants handled without being asked, from auditing a €24,000 vendor contract to answering national press.
Founders delegate inbox, calendar and travel first. The work that changes the relationship is everything after that: auditing a supplier nobody was checking, drafting answers for a national newspaper, turning an offhand remark into a decision-ready plan. In one case an executive assistant reviewed a year of agency performance and found that €24,000 of annual spend had produced 11,000 contacts and one paying client. Below are ten real, anonymised examples from working engagements.
The agency was not bad. The reports looked busy, the invoices ran on auto-renewal at €2,000 a month, and for twelve months nobody opened the file. When an executive assistant finally reviewed a year of performance data, €24,000 had produced 11,000 contacts and one paying client. The founder cancelled before the renewal date. The saving matters less than the reason it was available: nobody had been asked to look.
That is the pattern in every example here. These are not tasks founders chose to delegate. They are tasks founders did not recognise as tasks at all: the vendor nobody reviews, the deadline that lands while you are abroad with the wrong documents, the vague sense that something in the business is not working but no brief to go with it. An assistant close enough to see them, and senior enough to act, closes them without being asked. Our CEO delegation playbook covers how to build that level of trust deliberately.
There is research behind why this is hard. Porter and Nohria tracked 27 chief executives across more than 60,000 hours and found that the average works 62.5 hours per week, with 36% of that time spent in reactive mode (Porter & Nohria, “How CEOs Manage Time,” Harvard Business Review, 2018 (opens in a new tab)). Reactive time is exactly where this work lives, and it is the first thing that disappears when someone else is watching the same inbox.
The ten examples below are real. Names, companies and identifying details have been removed, but the numbers, the cities and the situations are unchanged. Each one began as something a founder was either doing themselves, putting off, or had never thought to hand over.
The situation: The contract in the introduction had run for a year on auto-renewal. Nobody had asked for it to be reviewed, and no review was scheduled.
What the EA did: Went through the agency’s own performance reporting and traced output against spend: roughly 11,000 contacts across the year, one of which became a paying client. The findings were put in front of the founder before the auto-renewal date, which is the detail that made the work worth anything. A month later, the same analysis would have cost another year of fees.
The result: The founder cancelled. The agency was not the problem, and the EA was never asked to investigate it. The trigger was simply a recurring payment that nobody owned. The same logic drives the CEO buyback audit.
The situation: A CEO told their EA that something felt wrong with how the business was running. There was no specific brief, just a sense of disconnect and a lack of accountability across teams.
What the EA did: Took that vague observation and built a concrete planning framework: a structured template with named owners for every workstream, clear accountability lines, and a new operational pillar the business had been missing entirely.
The result: The founder did not need to write the brief. The EA translated an instinct into a system the business could operate from.
The situation: A founder was invited to respond to more than a dozen questions from a national journalist ahead of a major industry summit. The questions were technical, policy-heavy, and due on a tight deadline.
What the EA did: Researched and drafted every answer, sourcing data from official agencies and published reports. Where questions fell outside the founder’s direct expertise, the EA redirected them to more appropriate respondents rather than guessing.
The result: The founder reviewed the answers. The journalist received them on deadline. The EA had done the research, the writing, and the editorial judgement. It is a long way from the job description, and closer to what an executive assistant actually does.
The situation: A CEO sent event invitations to a group of VIP guests with the wrong dates.
What the EA did: Caught the error, drafted and sent correction messages in the CEO’s own name to the affected guests, then swept the rest of the guest list to prevent the same mistake reaching anyone else.
The result: The speed mattered more than the task itself. The EA did not wait for instructions or flag the problem and ask what to do. They fixed it and reported back.
The situation: A founder’s childcare provider quit with less than 24 hours’ notice.
What the EA did: Clarified the family’s requirements, posted in local community groups, screened the responses, and personally called the top five candidates.
The result: A new childcare provider was in place within days. This is not a traditional EA task, but it is a clear example of the principle: if it is operational, time-sensitive, and the founder does not need to be the one doing it, an EA can handle it. Our executive assistant services page sets out where that scope begins and ends.
The situation: A founder had been running their entire WhatsApp sales process from memory. Nothing was documented. If they were unavailable, the process stopped.
What the EA did: Observed the process, asked clarifying questions, and built a step-by-step playbook that any team member could follow.
The result: What had been a one-person, undocumented method became a repeatable system. The process now existed outside the founder’s head, which meant it could be delegated, trained, and improved. The method is covered in how to build SOPs to delegate.
The situation: A founder was drowning in repetitive operational tasks: the same questions, the same updates, the same status checks from multiple people.
What the EA did: Designed a concept for a centralised knowledge and operations system, structured it into a clear proposal, and presented it to the founder.
The result: The founder was impressed enough to hire a developer to build it. The EA did not write the code. But they identified the problem, designed the solution, and created something the founder could act on immediately.
The situation: A founder needed to complete an identity verification process but was travelling abroad with an expired passport.
What the EA did: Researched verification providers, found one that accepted a national identity card instead of a passport, and guided the founder through the process.
The result: The founder was verified within approximately ten minutes. Without the EA’s research, they would have missed the deadline or spent hours searching for alternatives between meetings in a different time zone.
The situation: A founder needed a housekeeper and had no time to search.
What the EA did: Posted in local Facebook groups, built a spreadsheet of candidates with relevant details (availability, experience, comfort with pets), and presented a shortlist.
The result: The founder chose from the list. A year later, when the housekeeper fell ill, the EA pulled up the same spreadsheet and contacted the next candidates, resolving the replacement in a fraction of the time. The reusable system was more valuable than the initial hire. The same instinct shows up in day-to-day inbox, calendar and travel management.
The situation: A founder mentioned in passing that the business should attend more industry events in 2027.
What the EA did: Took that single comment and built a master spreadsheet: every relevant event for the year, with dates, locations, speaker application deadlines, registration costs, and travel requirements.
The result: What had been a vague intention became a calendar the founder could approve, reject, or delegate in one sitting. The difference between a founder who attends three events a year and one who attends twelve is rarely ambition. It is whether someone turned the ambition into a plan.
None of the ten tasks above appears on a standard executive assistant job description. None was assigned. In most cases the founder had not framed them as work at all, which is exactly why they sat undone.
That is the difference between an assistant who executes a list and one who reads a business. The first needs you to spot the problem before anything happens. The second spots it for you, which is the only version that returns your time rather than redistributing it.
The commercial case is well established. Gallup studied more than 1,400 entrepreneurs and found that CEOs with strong delegation ability generated 33% more revenue than those without it (Gallup, “Delegating: A Huge Management Challenge for Entrepreneurs,” 2015 (opens in a new tab)). The founders in this article are not better organised than their peers. They simply stopped being the only person who could see what needed doing.
A managed executive assistant at €2,700 per month works the way the examples above describe: embedded enough to see the gap, senior enough to close it, and backed by a team that keeps the standard consistent. Full plan details are on the pricing page.
Book an Introductory Call
Checked for accuracy against how DonnaPro actually works before publication.
The examples in this article are drawn from real engagements between DonnaPro executive assistants and the founders they support. All identifying details, including company names, EA names, and specific business details, have been removed. The delegation and time management research is drawn from published academic and survey studies cited in full below.
Sources reviewed
Explore more guides to help you hire, work with, and get the most from your executive assistant.
