AI personal assistant for a founder's workday

An AI personal assistant can take routine work off a founder's plate: organise calendar details, prepare reminders, research travel options, collect receipts and draft the messages that keep a day moving. The useful distinction is between work that ends with information or a draft and work that changes something outside your workspace. An assistant can research a flight without booking it, prepare a payment record without moving money, and draft a reply without sending it.

The aim is to stop making the same small decisions every morning. Set clear rules for routine work, give the assistant a defined budget and a deadline, and decide which actions always need your approval. That gives an AI personal assistant room to finish ordinary errands without giving it permission to commit you to a purchase, promise a meeting time or send a message in your name.

Start with the errands that end in a deliverable

The safest first tasks are those that produce something you can inspect. A calendar review can identify conflicts and suggest a better order for meetings. Travel research can compare departure times, transfer lengths and cancellation terms. Receipt handling can collect files, extract dates and totals, and flag expenses that need clarification. None of these tasks requires the assistant to make a commitment on your behalf.

For example, a founder might ask for a travel brief for a two day visit to Berlin. The assistant can compare suitable trains and flights, estimate the time needed to reach each meeting, identify hotel options near the venue and prepare a shortlist. The finished brief should state the assumptions behind the comparison, including the dates, departure location and whether a changeable ticket matters.

That is a complete piece of work, even though nobody has booked anything. You can make the decision with the relevant information in front of you rather than spending an hour collecting it yourself.

Draw the line between preparation and commitment

A useful rule is to let the assistant gather, organise, compare and draft within an agreed scope. Pause when the next step would spend money, contact somebody, publish information or change a record that other people rely on. The exact boundary depends on the task, but it should be written down before the assistant starts.

The important detail is that approval should apply to the actual action, not to a vague intention. You might approve research into a trip without approving a booking. You might ask for a calendar change proposal without authorising invitations to be sent. A task brief should make that distinction explicit.

Write the rules once, then reuse them

If you have to explain every boundary in every request, delegation soon becomes another job. Write a short standing brief for the errands that recur, then change only the details that differ each time.

A calendar brief might say: review the next seven days each weekday morning, identify meetings with no preparation time, suggest changes that preserve existing commitments, and prepare a revised schedule. Do not move meetings or send invitations without approval. If a conflict cannot be resolved without changing somebody else's plans, explain the options and stop.

A receipt brief needs different instructions. Specify which expense categories to check, which fields to extract, how to flag missing receipts and what evidence is needed before matching an expense to a transaction. Tell the assistant to leave uncertain matches unresolved rather than inventing a category or treating a plausible match as a confirmed one.

Good standing rules answer four practical questions: what the assistant should do, what information it may use, what it must leave untouched, and what it should return when it cannot finish. The last point matters. A useful assistant should report a missing booking reference or an ambiguous calendar request instead of silently filling the gap.

Make the approval small enough to answer quickly

An approval process fails when the person reviewing it has to repeat the research. A request to approve a travel booking should show the chosen itinerary, the total cost, the cancellation terms and the reason the option fits the brief. A request to send an email should show the exact recipient and message. A request to change a calendar entry should show the current time, the proposed time and who will be affected.

The reviewer needs enough context to make a decision, but not another pile of raw material to sort through. If the assistant cannot explain why it selected an option, the work is not ready for approval.

We designed Delagents around this separation between delegated work and actions that need a person's sign off. Its approvals inbox presents an action as a card with the exact proposed action, the cost so far and a deadline. A person can approve it, change it or reject it. Each delegation also has a hard budget cap, and an append only activity log records tool calls, approvals and policy changes.

Some actions should remain approval only regardless of how routine they seem. In Delagents, these include first contact with someone outside the workspace, moving money or issuing refunds, deleting or overwriting records the agent did not create, changing roles or its own policy, connecting an integration or widening its access, accepting terms or signing, publishing publicly, and acting in another workspace. These boundaries prevent a routine errand from quietly turning into a broader authority.

Keep exceptions visible instead of adding more rules

A standing brief cannot predict every situation. A train may be cancelled, a meeting organiser may offer a new time, or a receipt may show a total that does not match the card transaction. These are not reasons to give the assistant wider permission. They are reasons to stop and present the problem clearly.

Ask for the original plan, the new information and the available choices. If a hotel is sold out, the assistant might return two alternatives with their prices and cancellation terms. It should not silently select a more expensive room because it appears convenient. If a receipt is missing, it should mark the expense as incomplete and tell you what evidence is needed.

Review exceptions periodically. If the same harmless question keeps returning, clarify the standing brief. If an exception involves money, an external commitment or access to sensitive records, keep the approval requirement. The point is to remove repeated judgement calls about routine work, not to remove judgement from decisions that can cause trouble.

Choose one daily errand and test the boundary

For a founder, the best first delegation is often a task that repeats, has a clear finish line and does not require a new commitment every time. A morning calendar review or a weekly receipt collection is a better starting point than handing over the entire inbox or giving an assistant permission to arrange travel without limits.

Write a brief that names the expected deliverable, the information the assistant may use, the budget limit if there is one, and the actions that must wait for you. Run it against a real task. Check whether the result is complete, whether uncertainty was reported honestly, and whether the assistant stopped at the right boundary.

If you are setting up this process for your own company, start with Delagents for founders and choose one recurring errand to delegate. Keep the first run narrow. Once the deliverable and approval boundary work as intended, reuse the brief for the next run instead of rebuilding the instructions from scratch.