Don't make the veteran fall in love with Accio (2026)

Bottom line:

Veterans usually resist visibility, version locks, and the end of oral night discounts—not the Accio UI.
Handover the shared pool, scripts, quote rights, and send key first. Software practice can wait a week.
Day 30 accepts behaviour, not affection. Time-in-product, login counts, and training likes are not gates.

Failed Accio rollouts are often motivational meetings. Management says AI is the trend. The veteran says buyers know their name. Both can be true. The meeting you needed was a handover: where inquiries live, who may change price, who presses send, and whether the buyer still exists at the company on the day someone resigns.

What Accio can do lives on the overview and the tutorial hub. Who speaks across time zones is on the 2 a.m. inquiry from Stuttgart. This page is how the system enters the day without requiring anyone to fall in love.

1. Admit what they are protecting

After eight years, buyers sit in a personal WhatsApp, prices sit in a private workbook, lead times sit in a head. Asking them to log into Accio is asking those three objects into a place colleagues and a model can see. Resistance is rational. “You are behind the times” only hides the buyers deeper.

The usable sentence is: buyers belong to the company, prices have versions, you still sign what the buyer sees. Accio drafts; you send. Without the last half, they hear “the robot replaces me.”

2. Minimum loop: four items before software training

Handover	Done looks like	Not done looks like
Shared pool	New inquiry main thread on Alibaba.com or a company number	Only on personal WhatsApp; the company cannot search it
Script versions	Received, sample, and lead-time macros carry a version	Each person has “my usual English”
Quote rights	Named people lock price; others only draft	Whoever replies first sets the number
Send key	Accio stops at draft; a person sends	Auto-send, wrong price found on Monday

Terms agreed off-platform must be written back on-platform or Trade Assurance stays on the old page. Finish the four items, then open skill packs. Training before the four items produces people who can click and still hide buyers in a phone.

3. Accio’s first week does three jobs

One: pull drawings and RFQ attachments into a seen/unseen table. Veterans hate filling fields at night. This reduces load and rarely insults anyone.

Two: draft an eight-line received note under the stop rules on night triage. No “fully feasible.”

Three: push inquiries into the shared pool by arrival time. Day shift’s first hour works the queue. This hits the “familiar account first” habit, so a manager must run it in the morning meeting for a week. A memo will not.

Do not, in week one: auto-lock DDP, auto-edit listings, score time-in-product, or compare “the AI is faster than you” in public. The last two reopen the motivational meeting.

4. Access: master, sub-account, managed ops

The master account stays with a director or a named ops owner. Veterans get sub-accounts through inquiry and draft, not payment-profile edits, not a full buyer export on the way out. Managed-ops vendors do not hold the master. Corpable does not hold it either.

Exit day is the exam: revoke the sub-account, transfer the company WhatsApp, write unfinished personal-number orders back on-platform. Fail the exam and Accio is only another unused login.

5. Day 30 accepts behaviour, not mood

Share of new inquiries in the company pool (indicative gate: 100% of new inquiries; personal numbers may book calls).
Full night quotes retracted by day shift—if this rises, take the send key back.
Listing, macros, and quotations share one lead-time version.
Leave drill: one day the veteran is offline; colleagues can still take the thread.

You may survey how people feel. Feelings are not a gate. Someone who dislikes the UI and passes the four behaviours has rolled out. Someone who logs in daily and still hides buyers has failed.

If day 30 fails item 4, check whether a second person can open a drawing, then return to move the shop floor first. Software does not fill a headcount gap. Neither does the veteran—unless you were using Accio to hide the gap. That is not a rollout. That is a drawdown.

Questions teams actually ask

The veteran will not log into Accio. Should we score “time in product”?

No. Time-in-product measures a window, not whether the shared pool exists or quotes share a version. Day-30 accepts behaviour: new inquiries in the company pool, nights sending only received notes, send key still human.

Can we let Accio auto-reply everything and tighten rules later?

No. Auto first, rules later trains the new system on the old wrong macros. Freeze scripts and quote rights, then let Accio draft. The send key is human from day one.

Clients live in the veteran’s personal WhatsApp. Is that a completed handover?

No. Personal-number clients vanish on leave or exit. Done means the main thread is on Alibaba.com or a company number, the personal number only books calls, and key terms are written back on-platform.

What should Accio do in week one so it is least resisted?

Three jobs: extract drawing fields, draft an eight-line received note, and push inquiries into the shared pool by arrival time. Do not ask it to lock DDP or replace the veteran’s relationships in week one.

Should a managed-ops vendor hold the master account?

No. Open sub-accounts on least privilege and revoke on exit day. Master-account and shared-pool red lines live on the sub-account security page. Corpable does not hold master accounts or collect membership fees.

Day 30 still fails. Does that mean Accio does not fit us?

Look first at whether a second person can open a drawing and confirm price. Software does not fill a line gap. Pushing Accio before the floor moves is what the veteran is resisting—they will not let a system force them to invent lead time.

Don't make the veteran fall in love with Accio