The AI executive assistant: your digital chief of staff
A managing director opens the inbox before everyone else and closes it after everyone else. In between, what matters is buried under what does not. Your agent reads overnight, sorts, matches deadlines to their clauses and hands you, at a fixed time, a briefing that fits on one screen: what needs a decision today, what can wait, what is already written. It reaches you where you already are — Teams, WhatsApp or your inbox. Hosted in France, on local inference or an isolated resource. You approve every message sent.
Updated on
4 decisions are waiting today, one of them before noon: the Nancy site needs a delivery date your ERP already provides.
3 deadlines fall this week, each with the contract clause behind it.
Five replies are written and waiting for your word.
⛓ Sourced · executive inbox, calendar, ERP, live contracts
The reply is written, four lines, with the date and the lot reference. It goes as soon as you say so — or right now, if you give me the mandate to confirm the lead times your ERP already covers.
✎ Framework · nothing goes without your word, or a written mandate you withdraw with a word
A Blue Lemon Agent executive assistant reads your inbox and calendar before you do, sorts what calls for a decision, matches every deadline to the clause behind it and hands you a daily briefing at a fixed time on Teams, WhatsApp or your inbox. It writes the routine replies, prepares the files for the day's meetings and keeps the list of what is pending. Hosted in France, on local inference or an isolated resource, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity. You approve every message sent — and the day you want it to send one precise category on its own, that is written into a named, capped, dated mandate you withdraw with a word. Live in two to four weeks.
Benchmarks describing our offer, not results measured at a client. How much you gain on your own day is confirmed by a pilot on your own inbox.
Why the director's inbox is the bottleneck of the company
A pending decision from the director usually blocks several people downstream. Yet those decisions arrive mixed with hundreds of messages that call for none — and nothing in an inbox tells them apart.
! The stake
The head of an SME is the crossing point of a flow that no tool ranks: client messages, internal chasers, contractual deadlines, meeting invitations, copies for information. They read early, reread late, and the single most expensive item — the one that called for a dated decision — is the easiest to lose. Handing that inbox to a consumer tool would expose executive correspondence, commercial terms and live negotiations to a third party, often hosted outside Europe and subject to the Cloud Act.
✓ Our answer
An executive assistant is only worth having if it is sovereign and confidential by design. Local inference or an isolated resource hosted in France, an overnight reading of inbox and calendar, deadlines matched to contracts and to the ERP, a briefing at a fixed time on the channel you choose, routine replies already written, files for the day's meetings prepared. You approve every message sent: the agent prepares and quantifies, you decide. And when you want it to send one precise category on its own, that is not guessed — it is written into a named, capped, dated, logged mandate you withdraw with a word.
An executive inbox is the most sensitive in the company: sovereignty & compliance
Commercial terms, live negotiations, employment matters, correspondence with counsel: the director's inbox concentrates the most confidential material the company holds. Here is how our architecture protects it.
Local inference
The agent can run on a machine inside the company: no message, no attachment, no calendar entry leaves the network.
Hosting in France
Otherwise, a dedicated, isolated resource hosted in France under French law — your executive correspondence: processing and access within the European Union targeted by the architecture.
Reduced extraterritorial exposure
Architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity: the analysis of your inbox depends on a subcontracting chain and remote access documented for the configuration chosen.
One inbox, yours
The agent serves the person who employs it, on their own inbox and their own calendar. It produces no indicator about colleagues from what it reads there.
Short briefing outside EU messengers
On WhatsApp the message travels through an operator outside the European Union: the briefing goes there in short form, with no client name, no amount and no file reference. The full version stays in Teams or in your inbox.
AI Act: governed deployment
Strictly a support agent; no message sent without your word or a written mandate; a full decision log and human supervision end to end.
What depends on the architecture chosen These points are not general guarantees: they are settled deployment by deployment, in the quotation.
- The applicable location is that of the architecture set out in the quotation and verified before commissioning.
- Local execution is announced only for the configuration explicitly described and accepted in the quotation.
- The applicable isolation depends on the deployment mode set out in the quotation; no dedicated isolation is presumed.
- The events logged, their content, their retention period and who may access them are defined for the deployment chosen.
See the agent at work
4 real situations, taken from those that come up most often. Pick one: the exchange unfolds as it would in your organisation.
A scripted demonstration. These exchanges show how the agent behaves — its sources, its refusals, what it leaves to your teams. Nothing is sent from this page, no model is queried here, and the matters named are fictional. That is precisely what we promise your data.
The behaviours shown here — monitoring, automation rules, routing and reminders — are configured with you during deployment, from your tools, your rules and your thresholds.
The architecture points named in these exchanges — location, local execution, isolation, encryption, role-based access, logging — are not a guarantee attached to the demonstration: they are those of the architecture set out in your quotation, and verified before commissioning.
The company in this demonstration
Fictional companySorel Menuiseries — maker of bespoke aluminium windows and doors, private and public contracts
- Sector
- Manufacture and installation of aluminium joinery, as finishing-trade lots
- Headcount
- 62 staff, including 1 managing director and 1 part-time executive assistant shared with accounts
- Market served
- Builders, architects and public buyers in the north-east of France
- Order of magnitude
- 128 messages a day in the director's inbox, 11 meetings a week, 34 live sites
- Tools in place
- Microsoft 365 mail and calendar, Teams, a production ERP, a CRM, site contracts in the document store
- Who decides
- The managing director approves every message sent; the executive assistant keeps the shared calendar
- Room for improvement
- 1 h 50 a day spent in the inbox, and 3 contractual deadlines missed over the last half-year
Sorel Menuiseries has doubled in size in six years without changing how it decides: everything comes up to the managing director, and the inbox has become the company's compulsory crossing point. The executive assistant keeps the calendar but has no access to site files, and nobody rereads the contracts before the deadline. The agent is connected to the mailbox, the calendar, the production ERP and the contract store; it reads overnight and delivers a briefing in the morning. Nothing goes without the director's word, except what a written mandate entrusts to it.
This company, its figures and the exchanges that follow were invented for the demonstration. They illustrate a common situation; they describe no real client.
What I counted: 11,520 messages received — 128 a day — of which 806 called for a reply from you, that is 7 %. Your read timestamps give 1 h 50 a day spent in the inbox.
And here is the gap that explains everything. Your 806 replies fall into two very unequal populations:
· 141 went out in under 2 hours. Every one is about a live site, and every one comes from a correspondent you know.
· 665 waited more than 24 hours, of which 203 more than four days.
All three of your missed deadlines are in the second group. Each was announced in a message that stayed 4, 6 and 11 days unopened — and in all three cases the subject line carried no word of urgency. It was not your attention that failed, it was the sorting: nothing in an inbox tells a routine chaser from a contractual formal notice.
My proposal: a briefing at 7:15, fourteen lines, separating what calls for a dated decision from what calls for none — and matching every announced date to the contract clause behind it. Approve it for a week, we measure it, and you change it as much as you like. diagnostic_90-days-of-inbox.pdf141 replies within 2 h against 665 beyond 24 h
⛓ Sourced · executive inbox (90 days), calendar, read timestamps, contracts in the document store
The three questions:
· Is someone waiting on you to move forward? I see it from an explicit request and from the absence of a third-party reply in the thread.
· Does a date commit the company? I then match the message to the site contract in the document store and display the article. A date without its clause cannot be ranked.
· Does the information already exist elsewhere? If the ERP gives the workshop availability being asked for, the reply is written before you open the message.
Here is this morning's briefing, exactly as it went out: 128 messages since 6 p.m. yesterday, 96 filed with no action needed, 32 concern you, 4 decisions today including one before noon, 3 deadlines this week, 5 replies written.
And the figure I owe you: replayed over the 90 days, my sorting would have been wrong 41 times — 29 messages filed as « no action » that you had in fact handled, 12 raised as decisions that were not. That is 0.36 % of messages, and I would rather tell you before you find it. All 29 misses come from new correspondents: I propose raising every first message from an unknown correspondent for a month, then measuring again. briefing_of-the-day_07-15.pdf14 lines, 4 decisions, 3 deadlines
⛓ Sourced · sorting rules replayed over 90 days, site contracts, production ERP
The hour: over 90 days, your first action of the day is at 7:22 in median, and it happens on your phone 6 days out of 7. A briefing at 7:15 arrives just before, not during.
You asked me last week to move it to 6:30: I advise against it, and here is the arithmetic. 4 of the 14 lines in yesterday's briefing came from messages that arrived between 6:30 and 7:10 — two site managers write before leaving for the site. At 6:30 you would have read a briefing already a quarter wrong.
The channel, and what travels on it: all three work, but they are not equivalent. On WhatsApp the message travels through an operator located outside the European Union. On that channel I therefore propose the short briefing: « 4 decisions, 1 before noon, 3 deadlines, 5 replies ready » — no client name, no amount, no site reference. One word from you and the full version opens in Teams or in your inbox, where it has never left your perimeter.
What you gain concretely: you see in three seconds whether to open it, and the information that would be worth something to a competitor does not travel on a consumer network. Convenience and confidentiality are not traded off here, they add up. briefing_three-channels-compared.pdfFull in Teams, short on WhatsApp
⛓ Sourced · first-consultation timestamps (90 days), message arrival times, data egress policy
· 1. Nancy site, joinery lot — before noon. Yann Delaunay is asking you to confirm the 14 October installation. Your ERP shows the workshop free from the 9th, the contract sets a penalty beyond the 20th. Four lines, the date and the lot reference. It unblocks four fitters and a scaffold already on hire.
· 2. Verrier architects — awaiting a reply for 6 days. They are asking again for the technical sheet of the RT-88 profile, which you sent them on 3 July. I attach the same version and say so.
· 3. Val-d'Ornain local authority. Request for an additional document on the live contract, filing deadline Friday 5 p.m., article 6.2 of the terms. The document exists, it is in the store, it is attached to the draft.
· 4. Unsolicited application from a quantity surveyor. An acknowledgement, with your HR team's real turnaround.
· 5. Chaser from an ironmongery supplier. Invoice settled on 28 August, payment reference in the draft.
What I have not written, and why it is useful to know: a sixth request asks for an exceptional discount. A price is not information, it is a commercial decision — I have prepared the file (client history, margin on the last lot, three comparable precedents) and the price line is left blank. You fill it in ten seconds, with everything in front of you. drafts_five-replies-ready.pdf5 sourced replies, one price line left blank
⛓ Sourced · production ERP, contract store, CRM, inbox history
What I measured on your 806 replies over 90 days: 412 commit neither a price, nor a contractual deadline, nor a person. They fall into three clear families:
· 187 acknowledgements — « received, I will come back to you before this date »;
· 149 forwardings of an already approved document, taken unchanged from the store;
· 76 confirmations of a slot already free in your calendar.
The mandate I propose writing covers exactly those three families and nothing else: named scope, a cap of 25 messages a day, a duration of three months, a log readable line by line, withdrawal with a word. Beyond the cap I stop and tell you — a cap reached is information, not an incident.
What stays under your signature, and I recommend leaving it there: anything touching a price, a contractual deadline, a person (hiring, discipline, leave) and every first exchange with an unknown correspondent. Over your 90 days that is 394 messages: fewer than five a working day.
The gain, quantified: 412 fewer acknowledgement reviews per quarter, and the reply time on those three families would go from 31 hours in median to under 10 minutes. Your clients will see it, not you. sending-mandate_scope-cap-duration.pdf3 families, 25 messages a day, withdrawn with a word
⛓ Sourced · classification of the 806 replies over 90 days, measured median delays
What guarantees it technically, and what you can check:
· The log. Every message sent under mandate appears with its timestamp, its recipient, its family and its full text. It is readable at any time, and I include an extract in Monday's briefing.
· The cap. 25 a day: at the 26th I stop and write to you.
· The exit rule. If a message in a mandated family contains an amount, a contractual date or a person's name, it leaves the mandate by itself and comes back as a draft. That is the rule that protects the mandate from its own drift.
· Withdrawal. One word — « stop mandate » — and everything reverts to drafts within the second, losing nothing in flight.
And one last thing, because it always ends up being asked: nothing I read in your inbox serves to describe anyone else. I produce no reply time per person, no volume per department, no individual habits. Your inbox serves your decisions, not the appraisal of your 62 staff — and the day the company wished to measure an activity, that would be a separate project, with the prior information of the people concerned and the consultation of the works council required by French employment law.
✎ Framework · log of messages sent under mandate, automatic exit rule, register of withdrawals
The three sending mandates I propose, named:
· “Acknowledgements” — 187 messages over 90 days. Cap of 15 a day.
· “Forwarding an already approved document” — 149 messages, and the document is taken verbatim from the document store, never rewritten.
· “Confirming a free slot” — 76 messages, only on a slot your calendar shows free at the second I write.
What “named” buys you in practice: you can withdraw one without touching the other two. A global mandate is withdrawn wholesale, so it never is — it is endured or deleted. Three named mandates are tuned finely: you closed “confirming a free slot” for the three weeks of your workshop move, and reopened it afterwards.
Withdrawable, and here is what that means technically: you write “withdraw the acknowledgements mandate”. The mandate ends immediately, messages of that family go back to drafts in the 7:15 briefing, and the log carries the date, the time and the mandate withdrawn. Nothing to undo, nothing to uninstall. And the reverse holds: a withdrawn mandate reopens on the same word, with its date.
The figure that does not flatter me: out of 1,044 messages sent under mandate in two months, 6 should have stayed as drafts — five acknowledgements sent into a thread a third party had already closed, and one slot confirmation on a meeting you had just cancelled by phone. What I did with it: the escape hatch now reads cancellations from the last hour and threads closed within 24 hours. Over the next 30 days: 0 out of 512.
✎ Framework · 3 named mandates, per-family caps, withdrawal recorded immediately
The file, on one page:
· Open point 1 — coating shop throughput. Set at 340 frames a week on 4 September. The ERP gives 291 on average over the last three weeks, and the whole of the drop is on non-standard colours: 19 % of frames against 11 % in the previous quarter.
· Open point 2 — supplier delay on ironmongery. Resolved since: delivery received on the 12th, the two blocked sites have restarted. I have taken it off the agenda and I am telling you rather than letting you discover it in the room.
· Open point 3 — hiring a fitter. No movement for three weeks; I have left it, with the date of the last action.
What I am adding to the agenda, and why: four sites whose contractual installation date falls within 30 days while the workshop has not yet opened a works order for them. That is exactly the configuration of your three missed deadlines this half-year. meeting-file_production-committee.pdf3 points open, 1 closed, 4 sites added
⛓ Sourced · minutes of the previous session, production ERP, calendar, contract store
· Friday 5 p.m. — additional document, Val-d'Ornain contract. Article 6.2 of the terms: the contracting authority may set the bid aside if the document is not produced in time. The document is in the store, attached to draft no. 3. All that remains is for you to send it.
· Saturday — automatic renewal of the vehicle fleet maintenance contract. Article 9: notice may be given up to 90 days before the anniversary, that is Saturday. After that date you are renewed for twelve months. I do not know whether you want to renew — what I do know is that the question arises today and not on Monday, and I have pulled the last three service reports so you can settle it in two minutes.
· Next Wednesday — annual price review, framework contract with the builder Ardennes Habitat. Article 4.3: indexation must be requested in writing before the anniversary date, failing which prices stay at last year's level. The letter is written, it is waiting for the index only you can choose.
And the comparison I owe you: your three missed deadlines this half-year were exactly of this kind — a notice clause, a document production deadline, a price review. None looked urgent when read; all three were urgent in the contract. That is the only reason a date without its clause is worth nothing. deadlines_dates-clauses-consequences.pdf3 dates this week, the article behind each
⛓ Sourced · contracts in the store (public-contract terms, maintenance contract, framework contract), calculated anniversary dates
Why I advise against 2 p.m.: two of the seven attendees — the workshop manager and the site manager for the southern sector — have been on site every Tuesday afternoon for eleven consecutive weeks. Of the six committees held in an afternoon over the last six months, they missed five, and three of the open points we have just picked up were deferred for want of them.
Tuesday 10 a.m., by contrast: all seven calendars are free, so is the room, and your 2 p.m. bank meeting stays untouched. One move instead of two.
What I do on your word: I send the seven invitations with the updated agenda and the file attached, and I tell the executive assistant for the shared calendar. If you still prefer 2 p.m., that is your decision and I carry it out as it stands — I will simply have given you the eleven weeks of data before, not after.
⛓ Sourced · shared calendars, site rotas, attendance of the last six committees
The figures I always report together:
· Decisions settled the same day: 61 % before, 88 % now.
· Median reply time across the whole inbox: 31 h → 6 h.
· Contractual deadlines missed: 3 in the previous half-year, 0 over these two months, out of 14 that fell due.
· Messages filed « no action » that you reopened: 11 out of 5,376.
And the figure that does not flatter me, because it counts as much as the others: of 214 drafts proposed, you rewrote 61 — 28 %.
What I looked at to understand: 54 of the 61 rewrites concern three correspondents — two architects and one public buyer. With them your replies are half as long and never close on an offer to meet. It is not my pen that is at fault, it is that I write to everyone the same way.
What I propose: I draw one template per regular correspondent from your 61 rewrites — you read them once — and I measure again next month. If the rewrite share does not fall below 20 %, then my grouping of correspondents is wrong and I redo it another way. You will get the figure in the first Monday briefing, whether it flatters me or not. review_two-months-of-briefing.pdf49 h returned, 28 % of drafts rewritten
⛓ Sourced · briefing log, read timestamps, rewrite log, contract deadline schedule
· Filing a message as « no action ». It is neither deleted nor moved out of your inbox: it changes label. You reopened 11 out of 5,376, and every reopening changes the rule from then on, dated and readable.
· Taking a point resolved since the last session off the agenda, telling you which and why. It goes back with a word — that happened once in two months, on the fitter vacancy.
· Sending the three families in your mandate, within the 25-a-day cap, with an automatic exit as soon as an amount, a contractual date or a person's name appears. 268 messages over the two months, 6 automatic exits, 0 cap breaches.
What stays entirely yours: a price, a discount, a contractual deadline, a decision touching a person, a first exchange with a stranger, and the arbitration of your calendar.
And the framework that holds it all: your inbox, your calendar, your contracts and I myself are hosted in France, on local inference or an isolated resource, with the deployment objective of processing and access operated within the European Union and an architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity. Your messages are not used to train a model. The short briefing on WhatsApp still carries no client name and no amount, and the log of messages sent under mandate is readable line by line — which is what lets you withdraw that mandate with a word, without having to take my word for anything. framework_what-goes-alone-and-what-waits.pdf3 reversible actions, 268 messages under mandate, 0 breach
⛓ Sourced · labelling log, log of messages sent under mandate, register of withdrawals, hosting policy
Your case is not here? That is exactly what a 15-minute conversation is for. Book the free audit →
What the executive assistant actually does
Each use corresponds to a capability we configure with you. All of them work in support: you approve every message sent.
Daily briefing at a fixed time
One screen, not a list: what needs a decision today, what can wait, what is already written.
On Teams, WhatsApp or in your inbox
The briefing arrives where you already are in the morning, in full or short form depending on the channel.
Drafted replies, ranked
Routine replies are written, sourced on your own documents and ranked by what they unblock.
The day's meetings prepared
One file per meeting: points left open, up-to-date figures, what has changed since the last session.
Deadlines matched to their clause
Every date carries its contract, its article and its consequence — a deadline without its clause cannot be ranked.
Named, withdrawable sending mandates
The day you want it to send one precise category on its own, the scope, the cap and the duration are written — and withdrawn with a word.
The company's memory
Instantly retrieve a contract, a term or the history of a file quoted in the briefing.
Need to go further?
These agents handle a different business process, with their own owner and their own price. They are added to this one.
Sorting and drafts on a shared inbox
For a shared address — contact@, sales@ — a dedicated agent handles the incoming flow.
Email assistant (sorting, drafts, replies) from 626 € excl. VAT / month Email assistant →Activity reports
To turn a meeting into a document you can circulate, a dedicated agent completes the set.
Activity report assistant from 574 € excl. VAT / month Activity reports →In 15 minutes we identify the most relevant agent — without oversizing the project.
How much of a director's day?
By taking on the reading, the sorting, the matching of deadlines and the writing of routine replies, the agent shifts the work towards the decision. Actual gains depend on your message volume and the number of your meetings.
The stages of your AI agent project
Audit & scoping
15 minutes to target the use case with the best return.
Quote or direct sign-up
A catalogue offer is bought online; a specific need gets a costed quote.
Design
We design the agent and its guardrails.
Integration & testing
We connect your tools to the agent, which is itself hosted in France.
Rollout
Going live and training your team.
Operation
Continuous supervision and improvement.
An executive assistant, installed and run for you
An agent connected to your mailbox and calendar, with the briefing channel of your choice, tuned to your files and your deadlines. Prices excluding VAT — annual subscription, the time it takes for the gains to settle.
Setup + controlled subscription
- Installation, configuration and training for your teams
- Operation, human oversight, updates and support
- Sovereign hosting in France, a dedicated and isolated resource
All inclusive, no setup fee
- Setup included (installation, configuration, training)
- Operation, human oversight, updates and support
- Sovereign hosting in France, managed end to end
On site, you own it
- Hardware installed on your premises (you own it)
- French / European AI models run locally
- Secure remote maintenance (Pro support included)
Four guarantees that matter for an executive inbox
Related resources
Your questions, our answers
How does it differ from the email assistant?
Which channel does the briefing arrive on?
Does the agent send messages in my name?
Does the agent measure my colleagues?
What if the agent gets a priority wrong?
Is our data protected?
How long does deployment take?
Other agents for the daily life of a management team
Let us size the potential on your day
15 minutes to scope your message volume, your deadlines and your briefing channel — hosted in France, supervised, no commitment.