A2A F26 | Week #1: Think Like an AI Architect: Build Your First AI Employees Workshop

Okay so here is the thing that drives me crazy. I send like three to five follow up emails every single day after meetings, and by the evening I cannot remember who said they would do what. So I sit there for about thirty minutes rebuilding it from my notes, and half the time I am guessing. Everybody is waiting on me for the decisions and who owns what and by when.

What I want is to paste in a transcript and get back the follow up email, written the way I would send it. And I am a little obsessed with my template, it has to look exactly the same every time so my team knows where to look.

So the subject line has the project name and then says decisions, owners, and what I need by Friday. Then "Hi team," and one line that says this is a quick recap so we are all working off the same page. Then what we decided, each decision with one line of context. Then what is still open, so the question, who owns getting us an answer, and by when. Then the action items, each one as the owner, the specific thing they are delivering, and the date. Then what I need from each person this week, just the one thing next to each name. Then the risks I am watching, with the trigger that would make me escalate.

And at the bottom I always say that if anything here does not match your understanding, push back today, because silence means agreement and I will move on it Monday. Then thanks.

A few rules. Same format every time, no extra sections, and do not make it wordy. Plain English, like a sixth grader could read it. If something is unclear, flag it with needs confirmation in brackets. If nobody got named for a task, put owner needed in brackets, please do not guess. If there are no risks, just say none right now. And no long summary of the meeting, I was in the meeting.

Before you start, ask me any clarifying questions you need.

ROLE: You are David Allen, creator of Getting Things Done and the world's foremost expert on capturing commitments, clarifying ownership, and closing the loop after high-stakes conversations—so nothing falls through the cracks and everyone knows exactly what they own.

CONTEXT: I run [NUMBER] meetings per day and send [NUMBER] follow-up emails every evening. My team depends on my follow-up emails to know what was decided, what they own, and what I need by end of week. I have a strict template I use every time—my team has learned where to look, and I never deviate from it. I will paste a raw meeting transcript below. Your only job is to extract the relevant information and populate my exact template. Do not summarize the meeting. Do not add sections. Do not editorialize. Write at a sixth-grade reading level—short sentences, plain English, no jargon.

REQUEST: Read the transcript I paste and produce one complete follow-up email using this exact structure, in this exact order, with no additions or omissions:

**SUBJECT:** [PROJECT NAME] — Decisions, Owners & What I Need by Friday

Hi team,

Quick recap so we're all working off the same page.

**WHAT WE DECIDED**
— [Decision]. [One line of context.]
— [Repeat for each decision.]

**WHAT'S STILL OPEN**
— Question: [Open question] | Owner: [Name or [OWNER NEEDED]] | Due: [Date or [NEEDS CONFIRMATION]]

**ACTION ITEMS**
— [Owner] → [Specific deliverable] → [Date]

**WHAT I NEED FROM YOU THIS WEEK**
— [Name]: [The one thing]

**RISKS I'M WATCHING**
— [Risk] | Trigger: [What would make me escalate]
— (If none: "None right now.")

If anything here doesn't match your understanding, push back today. Silence means agreement and I'll move on it Monday.

Thanks,
[MY NAME]

RULES YOU MUST FOLLOW:
- Use [NEEDS CONFIRMATION] for anything unclear or ambiguous in the transcript
- Use [OWNER NEEDED] if no one was named for a task—do not guess
- Never add sections, headers, or commentary outside this template
- No long sentences. Plain English only.
- Do not reference or summarize the meeting itself

QUESTION: Before proceeding, paste your transcript below and I'll return your email ready to send. If you'd like me to ask clarifying questions first, say so now.

SUBJECT: Atlas Insights — Decisions, Owners & What I Need by Friday

Hi team,

Quick recap so we're all working off the same page.

WHAT WE DECIDED
— Atlas launches as a small pilot, not a full release. We want to find problems with a few customers first.
— The pilot is capped at 12 customers. Support can't handle more than that yet.
— We will not share a general release date with customers. We'll set it after the pilot.

WHAT'S STILL OPEN
— Question: Do pilot customers pay, or is it free? | Owner: Rafael | Due: Thursday, Oct 8
— Question: Who writes the pilot welcome guide? | Owner: [OWNER NEEDED] | Due: [NEEDS CONFIRMATION]

ACTION ITEMS
— Elise → List of 15 possible pilot customers → Wednesday, Oct 7
— Priya → Ask account leads which customers would say yes → Thursday, Oct 8
— Jonah → Support plan for pilot questions → Friday, Oct 9

WHAT I NEED FROM YOU THIS WEEK
— Elise: The pilot customer list
— Priya: Account lead feedback
— Jonah: The support plan
— Rafael: The pricing answer

RISKS I'M WATCHING
— Data imports are still failing in testing | Trigger: Not fixed by Oct 30

If anything here doesn't match your understanding, push back today. Silence means agreement and I'll move on it Monday.

Thanks,
Maya
SUBJECT: Q3 Close & Q4 Forecast — Decisions, Owners & What I Need by Friday

Hi team,

Quick recap so we're all working off the same page.

WHAT WE DECIDED
— Q3 ARR is final at $23.6M. Finance closed the books and the number is locked.
— Finance owns the forecast from now on. One number, one owner.
— Deals only count once they're signed. A verbal yes doesn't count.

WHAT'S STILL OPEN
— Question: Will the cloud vendor give us a credit for the migration overrun? | Owner: Marcus | Due: [NEEDS CONFIRMATION]

ACTION ITEMS
— Rafael → Base, downside, and upside Q4 forecast → Thursday, Oct 15
— Priya → Q4 pipeline by deal stage → Wednesday, Oct 14
— Marcus → Cloud cost breakdown since the migration → Friday, Oct 16

WHAT I NEED FROM YOU THIS WEEK
— Rafael: The Q4 forecast
— Priya: The pipeline view
— Marcus: The cloud cost numbers

RISKS I'M WATCHING
— Gross margin is below plan | Trigger: Forecast drops under 72%
— Pipeline coverage is light | Trigger: Falls below 2.5x

If anything here doesn't match your understanding, push back today. Silence means agreement and I'll move on it Monday.

Thanks,
Maya

# Acme Co — Q4 Board Meeting Prep

**Meeting date:** Tuesday, October 27, 2026  
**Time:** 9:00–9:20 a.m. Central  
**Platform:** Zoom  
**Duration:** 20 minutes

**Participants:**
- Maya Chen — CEO
- Rafael Ortiz — CFO
- Priya Nair — VP of Sales
- Jonah Brooks — VP of Customer Success
- Elise Morgan — VP of Product
- Marcus Lee — COO

---

## Raw Meeting Transcript

**[00:00] Maya Chen:** Morning, everyone. Can you hear me? Rafael, you're muted. Yep, there we go. Okay, we've got twenty minutes, and I actually have to leave at 9:20. So let's stay focused. The Q4 board meeting is November 12, and the board packet needs to go out Friday, November 6, by five Central. I don't want us building slides the night before again.

**[00:23] Marcus Lee:** That was one time.

**[00:26] Maya:** Marcus, it was literally the last three meetings.

**[00:30] Priya Nair:** I was going to say, I remember at least two.

**[00:34] Marcus:** Okay, fine. Point taken.

**[00:38] Maya:** Here's what I want today. We need to agree on the numbers, the story we're telling, the decisions we want the board to make, and what each of you needs to deliver this week. Rafael, start us off.

**[00:54] Rafael Ortiz:** Yeah. So I've got the preliminary October numbers through yesterday. Just to be clear, October isn't closed. We won't have final actuals until November 3. But the picture is reasonably stable. We finished Q3 at $23.6 million in annual recurring revenue. Our current Q4 exit forecast is $25.4 million in the base case.

**[01:17] Priya:** Hang on. That's lower than the number we discussed yesterday. Sales has us at $25.7 million.

**[01:25] Rafael:** Right, and that's actually one of the things we need to settle. The $25.7 million includes the Northstar Health expansion. That contract hasn't been signed.

**[01:36] Priya:** It's in legal. They're not walking away. I talked to their VP yesterday.

**[01:43] Rafael:** I believe you. But it's a $300,000 annual contract that hasn't been countersigned. I can't put it in committed revenue yet.

**[01:55] Maya:** Okay, so the difference is one contract?

**[01:59] Rafael:** Exactly. Same starting point. Different treatment of Northstar.

**[02:05] Maya:** Initially, I was inclined to use the $25.7 million. But we can't walk into the board meeting with a number we can't defend. Rafael, what are your scenarios?

**[02:18] Rafael:** Base is $25.4 million. Downside is $24.8 million. Upside is $26 million. Those are projected year-end ARR figures, not recognized revenue. I want that labeled clearly on the slide.

**[02:35] Maya:** Agreed. Decision: finance owns the forecast. We use $25.4 million as the base, $24.8 million downside, and $26 million upside. Northstar stays out of the base until it's signed. Priya, I know that's frustrating.

**[02:54] Priya:** No, that's fair. I just don't want the board thinking Sales is sandbagging.

**[03:00] Maya:** Then explain the upside. But don't count a signature we don't have.

**[03:07] Priya:** Fine. I'll get an update from Northstar. They told us legal would finish this week.

**[03:14] Maya:** Can you confirm the signature status by Thursday at noon?

**[03:20] Priya:** Yes, Thursday the 29th, noon Central. I'll send you and Rafael the answer.

**[03:29] Rafael:** Great. And even if it gets signed, let's reconcile the numbers before changing the board deck.

**[03:37] Maya:** Absolutely. Nobody changes the headline number without Rafael signing off.

**[03:46] Marcus:** Sorry, one question. Is that forecast assuming the two open sales roles get filled?

**[03:53] Rafael:** No. It's based on current headcount.

**[03:57] Priya:** Which is part of my concern, but let's get to that.

**[04:03] Maya:** We will. How's the pipeline looking?

**[04:08] Priya:** Mixed. October new bookings are tracking around $720,000 against an $850,000 target. We're at 2.6 times pipeline coverage for Q4, where we really want to be at three times. The good news is deal quality is better than last quarter. The bad news is that three larger deals are moving slower than expected.

**[04:34] Maya:** Which three?

**[04:37] Priya:** Northstar, Westbridge Manufacturing, and Summit Financial. Northstar is paperwork. Westbridge is waiting on their security review. Summit is a budget issue.

**[04:51] Jonah Brooks:** Sorry, is Summit the one that asked for the customer reference?

**[04:55] Priya:** Yeah. We gave them two options on Friday.

**[05:00] Jonah:** Okay. I know one of those customers. I can call them if that's holding things up.

**[05:06] Priya:** Thanks, but I don't think references are the blocker right now. Their CFO froze new software purchases until November.

**[05:15] Maya:** All right. Priya, I don't want just a list of deals. I want to know what we're doing to close the gap. Can you give me a recovery plan for our top ten late-stage opportunities, including the owner, next step, expected close date, and what needs executive help?

**[05:35] Priya:** Yes. Friday at two?

**[05:39] Maya:** Friday, October 30, two Central works. Also, if two of our top five deals slip past December 31, I need to know the same day. Don't save that news for the board deck.

**[05:52] Priya:** Got it.

**[05:56] Maya:** Jonah, let's talk retention. This is the other big issue.

**[06:01] Jonah:** Yeah. And I'm going to be upfront. The renewal number isn't where we want it. We're currently at 91% gross revenue retention for the preliminary October view. Our plan was 94%.

**[06:17] Rafael:** And that's the three-point gap that shows up in the finance bridge.

**[06:22] Jonah:** Right. We've had two notable customer losses. Pinecrest Foods left after a difficult onboarding. Harbor Logistics consolidated vendors during a procurement review. Together they represent about $410,000 in annual contract value.

**[06:41] Maya:** Are we sure Pinecrest was an onboarding issue and not a product issue?

**[06:46] Jonah:** Mostly onboarding. Their first implementation took eleven weeks against a six-week commitment. But there were also some reporting gaps. So, honestly, it's both.

**[06:59] Elise Morgan:** Yeah, I want to jump in there. The reporting gap was real, but it wasn't a missing feature. It was a configuration issue that took us too long to diagnose. That's a shared problem between Product and Customer Success.

**[07:15] Jonah:** Agreed. I don't want us pointing fingers. The customer doesn't care which team owns the issue.

**[07:22] Maya:** Good. We need that attitude in the board materials. I'm not interested in a slide that explains why every problem belongs to someone else.

**[07:34] Rafael:** We could probably bury the churn detail in the appendix and focus on the overall retention trend.

**[07:41] Maya:** No. Actually, that's exactly what I don't want. If we miss retention and hide it, the board will find it in five minutes. Let's lead with it.

**[07:56] Marcus:** Are you saying a full slide on the two losses?

**[08:00] Maya:** One slide on retention. Show the gap, the main causes, and what we're doing over the next thirty days. We should use customer examples, but no customer names without permission.

**[08:16] Jonah:** We may be able to use a quote from Cedarline Systems. Their COO gave us some really good feedback about the onboarding changes. I just don't know whether they've approved us using it externally.

**[08:32] Maya:** Can you check?

**[08:35] Jonah:** Yes. I'll contact their COO and our account lead. I should know by Thursday at four.

**[08:42] Maya:** Good. If we don't have written permission by then, make it anonymous. That's the rule. We don't hold up the packet over a quote.

**[08:56] Jonah:** Makes sense.

**[08:59] Maya:** And what does the thirty-day recovery plan actually look like?

**[09:05] Jonah:** Three pieces. First, we assign executive sponsors to the eight renewal accounts flagged red. Second, we put a tighter handoff between Sales and implementation. Third, we run a weekly review of any onboarding that's more than seven days behind.

**[09:28] Marcus:** On the second point, we already have a handoff checklist.

**[09:32] Jonah:** We have a checklist, yes. But not everyone uses it.

**[09:39] Marcus:** That's fair. We can make it a required step in the workflow.

**[09:45] Maya:** Okay. Decision: we're launching the thirty-day retention recovery sprint. No new headcount for it. Jonah leads the customer work, Marcus fixes the operating handoff, and Elise supports the reporting fixes.

**[10:04] Elise:** That's fine. I just want to be careful about promising every reporting issue will be fixed in thirty days.

**[10:13] Maya:** We're not promising that. We're promising a plan and visible progress.

**[10:19] Jonah:** I can get you the retention slide by Friday at three. It'll include the three main causes, the eight at-risk accounts, the recovery steps, and who owns the outreach.

**[10:33] Maya:** Perfect. One other question: can we show retention by customer cohort? I'm worried the blended rate hides what happens with newer accounts.

**[10:43] Jonah:** Probably. The data exists, but I haven't checked whether the account start dates are clean enough to use. I need to look at it.

**[10:54] Maya:** Okay. Keep that as an open question. Don't put an unverified cohort chart in the deck. Let me know what the data can support.

**[11:05] Rafael:** On a related note, our gross margin is at 72% in the preliminary view, against a 74% plan.

**[11:14] Maya:** That's the next problem. Marcus?

**[11:18] Marcus:** Yeah. Most of that gap is higher cloud infrastructure cost from the migration. We spent about $140,000 more than planned. We have a vendor credit request outstanding, but I don't want to count the credit until they approve it.

**[11:37] Rafael:** Thank you. That's the correct accounting answer.

**[11:41] Marcus:** I knew you'd like that.

**[11:45] Maya:** What's the current status?

**[11:48] Marcus:** Their account team says they'll get back to us by Thursday morning. I'll confirm by Thursday at eleven and send Rafael the result.

**[12:00] Rafael:** And if there's no credit, my margin forecast stays where it is.

**[12:05] Maya:** Right. If the credit isn't approved by Thursday at eleven, Marcus, tell me directly. We shouldn't be suggesting that margin will bounce back based on a verbal promise. And if the updated margin outlook falls below 71.5%, I want an immediate escalation.

**[12:25] Marcus:** Understood.

**[12:28] Priya:** Can we talk about those two sales hires now? Because if we're expecting pipeline coverage to improve—

**[12:36] Maya:** Yes. Go ahead.

**[12:39] Priya:** We have two open SDR roles. I've been interviewing for both. If we pause them, we might save money in Q4, but we'll pay for it in pipeline generation next quarter.

**[12:56] Rafael:** I understand that. But we're below our margin plan, and the forecast assumes current headcount. I don't think it's the right time to add fixed cost.

**[13:09] Priya:** Could we at least fill one?

**[13:13] Marcus:** Maybe, but we're also looking at moving budget from events into retention. We can't do everything at once.

**[13:22] Maya:** Here's where I land. We pause both open SDR hires through December 31 and revisit the decision in the January planning cycle. Priya, we can still build the candidate pipeline, but no offers until the hiring plan is reviewed.

**[13:39] Priya:** Okay. I don't love it, but I understand the constraint.

**[13:45] Maya:** I know. Let's make sure the pipeline recovery plan reflects that we're working with the team we have.

**[13:56] Marcus:** On budget, I've confirmed there's $120,000 available from Q4 field events that we canceled. I think we should move that into customer onboarding and retention.

**[14:09] Rafael:** That is within the current operating plan. We can reallocate it without asking for incremental spending.

**[14:18] Maya:** Let's do it. Decision: reallocate the $120,000 from canceled field events to retention recovery. No net new budget. Marcus, I want a breakdown of where the money goes, and Rafael needs to validate it before we show it to the board.

**[14:40] Marcus:** I can have the allocation plan Friday by four. It will cover implementation support, training, and customer outreach.

**[14:51] Rafael:** Send it to me when ready. I can review the finance treatment before Monday's dry run.

**[14:59] Maya:** Great. Elise, we need to cover Atlas Insights. I don't want the board thinking we forgot about the product launch.

**[15:08] Elise:** Right. So Atlas is still targeting November 16 for early access with twelve customers. Six have confirmed. Four have expressed interest but haven't signed the pilot terms, and two haven't responded. The core reporting experience is working, but we're still testing data imports.

**[15:30] Maya:** How serious is the import issue?

**[15:34] Elise:** It's inconsistent. Most accounts are fine, but we have one test environment where records aren't mapping correctly. We have a fix in testing. I don't want to call it resolved until the test passes.

**[15:49] Jonah:** And we need to be careful with support. If those twelve customers all start asking questions at once, my team needs to know what we can promise.

**[15:59] Elise:** Agreed. That's why I want a small pilot rather than a full launch.

**[16:05] Maya:** So for the board, we say November 16 is the target for a controlled early-access pilot with up to twelve customers. We do not announce a general release date. Correct?

**[16:17] Elise:** Correct.

**[16:19] Maya:** Decision made. And if two or more critical issues are still open by November 6, we do not send the pilot invitations. Elise, flag that to me as soon as it looks likely.

**[16:34] Elise:** Yes. I'll have the readiness matrix by Friday at one. It'll show customer confirmations, import testing, support readiness, and the go-or-no-go criteria.

**[16:49] Jonah:** Can you send me the support section before you finalize it? I don't want my team surprised.

**[16:54] Elise:** Yep. I'll get that to you Thursday afternoon.

**[17:00] Maya:** Okay, we have about three minutes. Let's lock the board story. I want a simple structure: where we are against plan, what's putting the year-end outlook at risk, and what we're doing about it. We are not turning this into a thirty-slide product tour.

**[17:20] Priya:** Thank you. The last deck was forty-two slides.

**[17:24] Marcus:** Forty, technically. Two were appendix.

**[17:28] Maya:** That doesn't help your case, Marcus. We're targeting twelve core slides this time. Appendix is fine for backup detail.

**[17:38] Rafael:** Are we including the competitor comparison? The board asked about pricing pressure last quarter.

**[17:44] Priya:** We have some win-loss data, but I'm not sure it's clean enough to put actual competitor pricing in front of them.

**[17:54] Maya:** That's an open question. Someone needs to validate the competitive claims and decide whether the comparison is safe to use. I don't want unsupported pricing numbers in the packet.

**[18:07] Marcus:** Who's taking that?

**[18:10] Maya:** We need to sort that out. I'm not assigning it without knowing who has the source data. Let's flag it.

**[18:19] Rafael:** Also, who is handling the international revenue exposure footnote? We may need it because of the currency question from the last board session.

**[18:29] Maya:** Good catch. Is that you or Legal?

**[18:33] Rafael:** I need to check. I can identify the right person, but I'm not sure whether Legal needs to sign off.

**[18:42] Maya:** Okay. That stays open. Don't guess on the footnote.

**[18:49] Maya:** Before we wrap, here's what I need by Friday. Rafael, the reconciled forecast and scenario slide by noon. Priya, the top-ten deal recovery plan by two. Elise, the Atlas readiness matrix by one. Jonah, the retention recovery slide by three. Marcus, the $120,000 allocation plan by four. Those are my five must-haves.

**[19:12] Rafael:** All good. I'll also flag if the ARR forecast changes after the Northstar check.

**[19:18] Priya:** Good on my end. I'll send the Northstar signature update Thursday at noon, even if the answer is that it's still unsigned.

**[19:27] Jonah:** I'm good. One concern: two of the eight red renewal accounts still don't have confirmed executive outreach scheduled. If we can't get those booked by Friday afternoon, I think that's worth escalating.

**[19:40] Maya:** Yes. If two or more of those at-risk accounts still have no executive outreach booked by Friday at three, call me. Don't just put a red dot on a slide.

**[19:50] Marcus:** And I'm still waiting on that vendor credit. I'll send you the answer Thursday, either way.

**[19:56] Maya:** Perfect. I'll send the board deck outline by end of day Wednesday. We'll do our internal dry run Monday, November 2, at three Central. And please, if any of these dates are slipping, tell me before the deadline, not after. Thanks, everyone.

**[20:00] Recording ended.**

You are my Executive Assistant. Your job is to keep my follow-ups, calendar and inbox moving so nothing I promised slips.

Before every task, read executive-assistant-context.md in this project. It has my people, meetings, priorities and rules. If it's missing, tell me to run the EA interview first. If a name, owner or date isn't in that file, ask me instead of guessing.

How to work:
- Keep answers short. Bullets first, then one next step.
- Write follow-ups the way my file says, with my sign-off.
- Check new work against this quarter's priorities and tell me when something doesn't fit.

When I paste a meeting transcript or notes, use my meeting follow-up email skill to write the follow-up.

Do the "Do without asking" items on your own. For everything else, draft it, show me and wait for my yes. Never send, delete or accept anything for me without that yes.