The person consequential leaders call when the infrastructure beneath them needs to match the size of their ambition.
Supporting my executives is never a single lane. It means holding the entire orbit from board relationships and investor communication to personal logistics, family coordination, and vendor management, without a single item dropping.
I was four years old when my family left Venezuela. My father was a hardware engineer, the kind of person who would tear apart a washing machine just to understand how it worked, then put it back together better than before.
My mom was a pediatric neuropsychologist. She spent her career decoding children that everyone else had given up on, finding the pattern underneath the behavior.
One who understood machines. One who understood people. But both of them were doing the same thing: thinking in systems.
Somewhere in that combination, an executive partner was born.
I'm drawn to companies where technology moves faster than the system around it. That's where I do my best work, because a place like that only needs one thing: someone who thinks in systems.
Every meeting auto-triggers a research pull 24 hours before it starts. LinkedIn activity, recent news, last email thread, relationship history, compiled into a one-page brief in the CEO inbox.
Every meeting gets auto-transcribed. An AI prompt extracts every commitment made, assigns owner and deadline, pushes it into a live tracker. A digest lands in the CEO inbox every Monday.
Every tier-1 relationship tracked against a last-contact date. The system flags anyone not touched in 30, 60, or 90 days and generates a suggested outreach in the CEO voice.
Every Friday the system assembles a complete week-in-review. CEO reads it over the weekend and walks into Monday already oriented. Built once. Runs forever.
A custom prompt system trained on the CEO's writing generates first drafts in their exact voice. Output sounds like the CEO on their best day. Consistent across every surface without them writing a word.
System sends templated input requests to each functional lead. AI assembles the narrative, flags inconsistencies, formats output into the board packet template. A week of chasing becomes a day of reviewing.
Each meeting tagged by mode. System flags incompatible back-to-back modes and proposes buffer time, resequencing, or a prep insert. CEO energy protected by design.
Every recurring internal communication runs through a workflow trained on CEO internal voice. EA inputs what happened, what matters, what the tone should be. The company experiences a CEO who communicates constantly. The CEO spent eight minutes on it.
Every significant decision captured in a single-line input. System expands it into a structured record: what was decided, why, who was in the room, what alternatives were considered. Searchable, timestamped, permanent.
Input assumptions across revenue, cost, and growth drivers. The agent runs scenarios, surfaces which levers matter most, and returns a structured output ready for executive review — without a single spreadsheet formula.
Reads calendar invites, pulls attendee context, recent email threads, and news. Generates a structured pre-read — who they are, what they want, what the CEO needs to know — in the CEO's inbox 30 minutes before every meeting.
Pulls live financials, runs them through a narrative generation layer, produces a first-draft board deck with charts, commentary, and talking points. The CEO reviews a near-finished document, not a blank slide.
Email me directly or use the scheduling link. I respond same day.
melissa@melissadevenish.comRegistro de cada decisión interfuncional tomada durante el tercer trimestre en la organización LATAM — quién propuso, quién disintió, qué se decidió, y cuál fue el resultado 90 días después. La atribución es el punto central. Un instrumento de rendición de cuentas que deja claro quién tomó qué decisión y con qué información.
Documento de alineación previo al lanzamiento que obligó a Producto, Legal, Finanzas y Ventas a comprometerse con una posición única antes de salir al mercado. Incluye el registro de qué área retrasó el lanzamiento y por qué. La claridad forzada como herramienta de ejecución.
Documento interno breve que define cuándo y cómo escalar algo a la oficina del CEO. No es un sistema de filtrado — es lo contrario. Les dijo a los VPs: "tráeme estas cinco cosas temprano y te facilito el trabajo." Las solicitudes entrantes aumentaron, no disminuyeron. La accesibilidad como ventaja operativa.
Portafolio de fin de año con los problemas interfuncionales que otros líderes me trajeron y sus resoluciones, organizados por área: Producto, Ingeniería, Finanzas y Comercial. El volumen es la evidencia. No es un resumen de logros — es un registro de trabajo.
Un tablero semanal de una sola página que combina economía del producto, pipeline comercial y salud operativa en una sola vista — la que el CEO realmente abría. Incluye el registro de acciones: qué decisiones se activaron a partir de qué señales. La visibilidad integrada que genera acción es lo que la mayoría de los candidatos finge con una captura de pantalla de Looker.
Three phases — Listen, Trust, Own — each with milestones, deliverables, and a built-in check-in structure. 12 to 15 pages. The document I hand an executive on Day 1 so Day 90 isn't a surprise.
Full audit of an executive's calendar against their stated priorities. Where time is going vs. where it should go, with a concrete action plan to close the gap.
End-to-end executive travel itinerary across multiple countries — flights, ground transport, hotels, visa requirements, local contacts, and emergency protocols. Everything in one doc.
The handoff document I built when transitioning out of a principal relationship — every system, preference, relationship context, and open loop documented so the next person doesn't lose 90 days figuring out how the office runs.
One page. Signal over noise. Business health, decisions needed this week, and what I'm watching. Written so the CEO can read it in under 10 minutes and act on it immediately.
The living doc that tracks every relationship that matters to the executive — board members, investors, key partners, and talent — with last contact, context, and what's needed next.
The complete pre-board checklist — materials coordination, pre-reads, attendee logistics, exec prep sessions, and post-meeting action log. Nothing left to chance.
The complete preferences doc — communication style, meeting structure, travel requirements, working hours, dietary needs, and non-negotiables. Built so any operator can support this principal without asking twice.
End-to-end production document for a company all-hands — run of show, speaker prep, slide coordination, Q&A logistics, and post-event follow-up. The doc that makes 500 people look seamless.
Full pre-event project plan with sprint structure, team assignments, and deliverable timelines — plus a post mortem capturing outcomes, blockers, and what gets built into the next cycle.
Ghost-written board narrative built from the CEO's raw thinking. Shows the before — fragmented notes, half-formed logic — and the after: a structured story with a clear arc and a single recommendation.
Pre-read written ahead of an executive offsite — not just the agenda, but the real agenda. Every session has the stated goal and the unstated tension. Dissenting views are named, not smoothed over.
A Slack and email thread where I stood in for the CEO with an external party. Shows tone calibration in real time — how the voice shifts depending on whether it's a board member, a prospective partner, or a founder.
The personal framework I run every week — the signals, the ratios, the conversations, and the silences I track across the org to know what's about to become a problem before it does.
A running log of things I caught before they became expensive. Each entry has context, what I did, and what it cost to fix vs. what it would have cost not to.
A list of introductions I engineered that closed — deals, hires, partnerships. Each one shows the context, why I connected those two people, how I framed it on both sides, and what happened after.
The calendar and communication protocol I run for executives with active relationships in the Gulf. Covers scheduling norms, decision-making pace shifts, the Hajj travel window, and how to maintain relationship momentum.
A unit economics analysis of Auth0's product built while I was at the company prior to the $6.5B Okta acquisition. Covers CAC, LTV, payback period, and the cohort dynamics that drove the valuation. Redacted.
A cohort analysis that surfaced retention dynamics no one on the team had connected. Shows the methodology, the initial hypothesis, what the data actually said, and what changed as a result.
A KPI tree that connects daily operational metrics to the financial outcomes the board actually cares about. Built so leadership can trace a number from the board deck back to the team that owns it.
The one-pager I send before a first meeting with a regional fund, government-linked entity, or distribution partner. One page. What we are, why now, what we're asking for, and what they get.
Written for a scenario where Product and GTM disagreed on prioritization. Lays out each position fairly, names the actual disagreement, and closes with a clear recommendation and a next step. The memo that gets the decision made without a meeting.
A weekly briefing format built for a family office principal — covering portfolio updates, relationship activity, board obligations, and personal priorities. Read-in-10 format.
The full scope of the Chief of Staff function for a family office — defining the operating rhythm, communication architecture, stakeholder map, and decision escalation framework.
The full meeting infrastructure for a family office with active board and investor relationships — pre-meeting prep package, agenda architecture, materials coordination, and post-meeting action log.
Coordinating a principal moving between primary residence, secondary home, and travel property. Staff handoffs, inventory tracking, vendor access management, and the 48-hour arrival prep protocol that means nothing is wrong when they land.
Working doc covering digital hygiene, physical security for travel, what the EA controls vs. what goes to the security team, and the communication blackout protocol for sensitive trips.
Concierge medicine providers, specialist relationships by city, medication management for international travel, and the protocol for a medical situation abroad. The EA who has this doc ready has already thought through something most principals haven't.
How the household runs when the principal is there, when they're not, and during a transition. Roles, access levels, communication norms, and the escalation path that doesn't require waking the principal at 2am.
The behind-the-scenes document for a private dinner at a principal's home — catering coordination, security sweep, seating by relationship dynamics, pre-brief on each guest, and the post-event debrief.
If the form isn't working, try refreshing the page or clearing your browser cache. You can also reach me directly at melissa@melissadevenish.com, just include which samples you're interested in and I'll get back to you.
Every CEO calendar I see before I touch it looks the same: random dark colors, no pattern, and grouped by reactivity. EA's assign categories like "interviews", "customer calls", "board meetings", each one gets its own color. That looks organized at a glance, but it's not strategic. It's color coding by what the meeting is called, not by what it actually demands from the executive. I zoomed out from the granular labels to find the pattern underneath. Interviews, customer visits, press, investor meetings: those are all External. The executive steps outside the organization and represents it outward, regardless of the specific format. Instead of 15 categories that look sorted but tell you nothing about how the executive is actually spending their energy, I collapsed them into the categories that matter for allocation.
A calm-looking calendar is a well-sequenced calendar. When the colors shift smoothly from cool to bridge to warm to neutral, the executive is moving through their day without cognitive whiplash.
This is not the executive's title. It is their cognitive state in the room. Are they walking in as a decision-maker, a listener, a relationship-builder, or a visionary? When an executive is operating in one mode, the EA can either deliver in another or close the gap before it costs anything.
The WHAT is whatever the executive needs to successfully arrive in the right mode. Sometimes that is a 3-line brief or five minutes of silence before the door opens. It can never be a static, one-size-fits-all workflow because every commitment requires a different cognitive state, and with that comes a different set of conditions to create it.
In order to ensure the right version walks through the door, there cannot be any dead zones. Every minute between commitments is either working for the executive or working against them. The car ride, the elevator, the 8 minutes in the lobby. None of it is neutral. It is either recovery or it is erosion. And if you have not decided which one it is, it is erosion. That is the default.
Most EAs inherit recurring obligations and protect them. What they never do is run a diagnostic against the executive's targets and ask: does this recurring commitment move us toward or away from where they want their time to go?
Before I audit the calendar, I run one formula:
Category hours per week ÷ Total working hours per week × 100 = % of week consumed by that category
The Intake Quiz gave us the target to measure against. Without it, we have no baseline — you're just looking at a list of meetings with nothing to compare them to, which becomes an opinion vs. a measurement.
For example, if the intake targets set external commitments at 30% but your schedule shows recurring commitments are already consuming 35% of that allocation, that's the first gap I surface before I've touched a single meeting. This is the difference between where your time is supposed to go vs. where your obligations are already sending it.
When a gap surfaces, it goes one of two ways depending on severity:
Once the 5% threshold is crossed on a minimum of one life category, I schedule a 20-minute session with the executive. The purpose of that meeting is not to figure out what to do — the thinking is already done. It exists to give my leader visibility into what I found, surface any context I'm missing, and leave with a confirmed action list.
To prepare for that session, I put together two documents:
There is a full library of proprietary frameworks covering every part of the job. Together we'll identify which frameworks your executive office actually needs and where the gaps are.
Live Notion workspace, AI workflow demos, calendar preset in action, relationship pulse system. Not a slide deck.
Full case studies are shared during active engagement processes. The summaries below reflect the scope and scale of real work.
I've called the Claude API directly, written production-grade prompts, built agentic workflows, and shipped functional tools. I don't use AI, I build with it. When a CEO wants to know what's real, I can show them something working, not a screenshot.