Tell the customer’s CTO that the integration will land three weeks late. Your account executive promised her this date.

A CTO hearing bad news needs the new date before anything else. Our method puts the news in your first two sentences and the story behind it last. Before the call, tell your account executive and your manager. Agree on the new date and who says it, so she hears one story. The account executive should not offer a date of his own. Say the news and the new date. “The integration will go live three weeks later than we committed, on the twenty-second.” No warm-up, no “so, a few things came up”. Say what it costs her, then stop. Name the effect on her side: which team waits, which process stays manual, what she can no longer tell her board. Then let her react before you give the plan. When the interviewer is playing the CTO, a plan delivered over her reaction reads as not listening. Give the new plan, one alternative, and how sure you are. What is done, what is left, and the one dependency the date rests on, in the form “this date holds if X happens by Y”. Then offer a partial go-live on the original date if one exists, and let her choose. Own it, including when you knew. “We committed to that date, and we missed it.” The account executive is part of “we”. Blaming sales, or her team’s data, tells her that nobody on your side is in charge. Say when you found out. If it was more than a few days ago, own the delay too. Give the cause in one or two sentences. Specific and technical, then stop. If she wants detail, she will ask. Ask for what you need. A name, an access grant, a decision, each with a date. Offer what she can show, and close in writing. Find a real thing she can put in front of her board, then promise the summary email today. Say “I” for what you will do next and give a date for each. When she pushes on the promise, acknowledge that the date came from your company and that she planned around it, before you say anything else. Don’t make her wait through a long explanation of the cause for the only sentence she needed.

Tell the CTO you will be three weeks late

A practice prompt we wrote. No company or candidate report names it, so it carries no company tag.

How to answer

A CTO hearing bad news needs the new date before anything else. Our method puts the news in your first two sentences and the story behind it last.

Before the call, tell your account executive and your manager. Agree on the new date and who says it, so she hears one story. The account executive should not offer a date of his own.
Say the news and the new date. “The integration will go live three weeks later than we committed, on the twenty-second.” No warm-up, no “so, a few things came up”.
Say what it costs her, then stop. Name the effect on her side: which team waits, which process stays manual, what she can no longer tell her board. Then let her react before you give the plan. When the interviewer is playing the CTO, a plan delivered over her reaction reads as not listening.
Give the new plan, one alternative, and how sure you are. What is done, what is left, and the one dependency the date rests on, in the form “this date holds if X happens by Y”. Then offer a partial go-live on the original date if one exists, and let her choose.
Own it, including when you knew. “We committed to that date, and we missed it.” The account executive is part of “we”. Blaming sales, or her team’s data, tells her that nobody on your side is in charge. Say when you found out. If it was more than a few days ago, own the delay too.
Give the cause in one or two sentences. Specific and technical, then stop. If she wants detail, she will ask.
Ask for what you need. A name, an access grant, a decision, each with a date.
Offer what she can show, and close in writing. Find a real thing she can put in front of her board, then promise the summary email today.

Say “I” for what you will do next and give a date for each. When she pushes on the promise, acknowledge that the date came from your company and that she planned around it, before you say anything else. Don’t make her wait through a long explanation of the cause for the only sentence she needed.

Follow-ups

What the interviewer may ask next, once your first answer is on the table.

She says: ‘Your salesperson promised me this date.’ What do you say?
She needs something for her board in two weeks. What can you show?
Write the first line of the follow-up email.

Where answers go wrong

Explains the cause for two minutes before stating the new date and plan.

Answer this in two minutes

Write the answer you would say out loud. The clock starts with your first word.

Compare with the model answer

Model answer

“Maria, I’ll start with the news. The order integration will go live three weeks later than we committed, on Monday the twenty-second instead of the first. That means your warehouse team keeps keying orders by hand until then, and I know that is what you planned around.”

Stop here, and let her react before you give the plan.

“Here is the new plan. The order sync and the error queue are built and tested against your staging system. What is left is moving from your ERP’s record-by-record API to its bulk export: two weeks of work, then one week running in parallel with the manual process before we switch. The twenty-second holds if the bulk export is turned on by next Wednesday. If it isn’t, the date moves a day for each day it’s late, and I’ll tell you the new date the same day. I’ll confirm on Wednesday either way.

“There’s a second option. On the first, we can go live on the record-by-record API for next-day orders only: they sync overnight, inside the throttle. Same-day orders stay manual until the twenty-second. That takes next-day orders off your warehouse on the original date, at the cost of running two paths for three weeks. I’d recommend it if the manual keying is what hurts most. If a clean single cutover matters more to your team, take the twenty-second.

“This is on us. We committed to the first before we had tested at your real volume, and that was our mistake, not your team’s. We found this on Tuesday, when we ran last month’s full order volume through staging for the first time. I’m telling you two days later, once I had a plan to bring with it.

“The cause, briefly: the record-by-record API throttles us, so a full day of orders takes longer than a day to sync. More servers won’t fix that. The bulk export will.

“What I need from you is one person on your ERP team who can enable the bulk export, named by Friday, and an hour of their time next week. I’ll send you all of this in writing today: the date, the one dependency, the option and my ask.”

If she says, “Your salesperson promised me this date”: “You’re right, he did, and he was speaking for us. You planned your quarter around it. He knows about this and agrees with the new date; you’ll hear the same thing from him. The new date is one I’m making myself, after running your real volume through it, and I’ll tell you on Wednesday if it’s at risk.”

If she needs something for her board in two weeks: “The sync is running today against your staging system with last month’s real orders. I can have a short recording of an order flowing from your storefront into the ERP, with the error queue catching the bad ones, by the end of next week. It’s real software on your data, not slides, and it’s the same code that goes live. I’ll also write three sentences you can read out: what works, what’s left and the date.”

The first line of the follow-up email: “Subject: Order integration moves to Monday the twenty-second: plan, one option and one request. Maria, as we discussed today, go-live moves three weeks to the twenty-second because of the ERP API limit, and the plan below needs one ERP contact from your team by Friday.”

Why this order. She hears the date in the second sentence and the cost to her in the third, so the rest of the call is about the plan and her choice, not about suspense. Owning it before the cause stops the cause from sounding like an excuse.