KelderbyA launch already promised

The launch can't wait for the roadmap.

Seven warehouses go live on 2 November. The new capability will not ship before the first cutover. Ana separates what the customer can use now from what depends on a release, asks Tom where the product decision is being made, and gives the agent a standing Friday check.

AnaCustomer success
TomSales

ACME is a fictional software company using Emargen.

01Topics & Initiatives · Keep commitments clear

First seven now. Next eighteen after the release.

The existing rollout switches warehouses individually over two weekends, rehearsing each one first. The new initiative proposes one setup and a controlled switch for every tested site. Those are different commitments. Ana keeps the first seven on the existing plan while checking whether the next eighteen can use the planned capability. A promising approach does not become an available feature.

Ana · Customer successChecks what the customer can use now and what depends on a release.

EmargenCurrent plan & planned capability · ACM-214 · ACM-293

One customer. Two different promises.

First 7

Existing setup, warehouse by warehouse. Launch: 2 November.

Current launch plan

Next 18

One shared setup, once the new capability ships.

Depends on release

The first rollout retains its own dates, rehearsals and fallback.

02Inbox · A question answered at its source

Ask where the product decision is being made.

Ana asks Tom in the initiative whether the next eighteen can switch together after go-live. He confirms the intent and states the boundary: until it ships, the first seven still go warehouse by warehouse. His reply reaches Ana's Inbox with her question attached. She can return to the initiative discussion, where the answer stays beside the plan it qualifies.

Tom · SalesConfirms the future capability without changing the current launch promise.

EmargenInbox · Initiative discussion · ACM-293

The answer keeps its condition.

Ana asks Tom

Can the next eighteen switch together after go-live?

Tom replies

Yes, once it ships. Until then, the first seven use the existing plan.

The reply opens its source in the initiative.

03Topics · Plan toward the date

Make the unanswered questions part of the plan.

In a rollout topic, Ana asks the agent to plan toward 2 November using the earlier customer information. It lays out the two weekends, test sign-ins, what Kelderby must supply and what happens if sign-in fails. The plan also exposes a human question: who approves each warehouse's switch? It marks that as unknown and identifies Tom as someone who may know.

Ana · Customer successUses the plan to see what still needs a person's answer.

EmargenTopic · Rollout plan · ACM-319

Dates, responsibilities and gaps.

Before
Rehearse each warehouse with a test account.
At switch
Follow the plan, including what to do if sign-in fails.
Open
Who approves each site's switch? Tom may know.

The topic keeps the rollout and the questions for Kelderby together.

04Recurring work · A standing job for the agent

Give the Friday readiness check a schedule.

Ana configures a weekly agent task: list warehouses still to switch, open questions in the rollout and product initiative, and anything Priti asked that week. Each run can produce a topic and bring it to Ana's Inbox, keeping the findings available for follow-up. The recorded task has not run yet; the instruction and Friday schedule are in place.

Ana · Customer successDefines what the agent should check and when it should report.

EmargenCalendar · Agent task · Weekly · Friday

Kelderby go-live: what's left

Every Friday09:00

Warehouses: Which have not switched yet?
Open questions: What remains on ACM-214 and ACM-293?
Customer: What did Priti ask this week?

Task configured · It has not run yet. Future findings are written into a topic.

Try it on a promised launch.

Bring a date your team has to meet. See what the customer can use now, what depends on a release and what still needs a person's answer.

Plan your first rollout →

Early access · We reply by email.