From signing, how long until your team sends a real quote?

Partly because the destination is the nice part. Mostly because the journey is not entirely theirs.

A vendor can promise what their software will do. They cannot promise when your IT provider will answer an email, or when somebody in your office decides which of four rate spreadsheets is the real one. So the safe move is to describe the finished state warmly and leave the middle grey.

That is understandable and still not good enough. A supplier who has done this in a forwarding company knows exactly which of your things they will end up waiting for. They have waited at every other customer. Asking them to say so out loud is the point of B3.

Notice what the question asks for. Not a promise. A date, and the things that would push it. The second half is the honest half, and a vendor who gives the first without the second has given you a wish.

The answer also tells you who they think will do the work. If every milestone in their plan belongs to them, they have not thought about your side. If every milestone belongs to you, you are buying a licence rather than a supplier.

Milestones, in order, each with one owner and a plain definition of done.

A date on its own is a number somebody said in a room. A date with milestones behind it can be checked while it is still fixable, which is the only kind worth having.

Three of those eight are shaded because they are yours. That is not a supplier dodging responsibility, it is the shape of the work, and a plan that hides it fails quietly. Ask for the shaded ones by name in the first meeting. They are the ones with your calendar in them.

Define the last step in writing. A quote that went to a colleague is not a first quote. The milestone is a real price, on a real enquiry, approved by your person, in a customer's inbox.

The outline puts it plainly: the slip is always the same two or three things. In a forwarding office they are these.

Slip one. Nobody owns the mailbox permission

The work arrives by email, so something has to be allowed to read the mailbox. That permission is not a switch anyone can flick. On Microsoft 365, granting an application scoped access to particular mailboxes is done through role assignments in Exchange Online, and Microsoft's own documentation is specific about who may do it: membership of the Organization Management role group, and the Exchange Administrator role in Entra ID. Consenting to an application across the whole organisation is described by Microsoft as “a sensitive operation”, restricted to a short list of administrator roles. On Google Workspace, the equivalent is domain-wide delegation, and Google's guidance is equally plain: “You must be signed in as a super administrator for this task”, and each scope you add “should be appropriately narrow”.

None of that is difficult. All of it needs one specific person with one specific role. In many forwarding companies that person works for an outside IT provider with other customers ahead of you. That is where the slip lives: a queue problem wearing a technical costume.

Slip two. Nobody has decided which rate card is the truth

The rate material is in four places. There is a master spreadsheet, a newer one somebody made for the ocean desk, an agent's tariff that only exists inside an email thread, and a surcharge sheet in a PDF that was current last month. Everyone knows which one they personally trust.

No supplier can settle that for you. It is not a data problem. It is a decision about who is allowed to say what a price is, and it usually falls to the busiest person in the firm. Left alone it quietly stops the plan, and the status call keeps saying “waiting on rates”.

Slip three. There is no named approver

Every one of these products ends at somebody approving something. If that person is not named at signing, the first real quote sits and waits. If they are named but they are also the owner, and the owner is at a conference, it waits anyway.

Name one person and a deputy, in the plan, in writing. An approval gate with nobody standing at it stops everything behind it, and the stopping is invisible until somebody asks why the number is still zero.

A fourth appears on nobody's plan: the security review. Between signing and switching on, a form arrives asking about certifications, where data sits and who can see it. Ask at the first meeting whether your side will run one, who owns it, and what the supplier normally produces. It is a short conversation before signing and a long one after.

Specific, slightly unflattering to both sides, and written down afterwards.

The dependency row separates experience from enthusiasm. A supplier who has run this in a forwarding company will tell you, before you ask, that they will be waiting on a mailbox permission and an agreed rate card.

Here is the only implementation wording we publish, and it is deliberately a method rather than a date.

• We scope the first workflow, integration requirements and implementation plan with your team.

Notice what it does not contain. A sentence like that is where an honest answer starts, not where it finishes. Ask us for the date too, and hold the answer against the same six rows you would use on anybody else.

Four ways a confident answer can still mean nothing.

Trap one. “It depends on the setup”

The sheet names this as the warning sign, and it earns the place. The setup is the thing you just asked about, so the sentence is a restatement wearing a suit. Push once: which part, and who does it? A supplier who has done this answers in specifics. One who has not reaches for the word again.

Trap two. The date that is really a demo date

Some plans describe the day the software is switched on, in a test environment, with sample data. That milestone is real and it is not the one you asked for. Write the definition of sent into the plan and the ambiguity disappears.

Trap three. The date that assumes your people are free

This is what the sheet's dodge question is for. How many of my people, for how many hours, and in which weeks? Ask it exactly like that, put the answer in the proposal, then hold it against your own calendar. A plan that lands on your peak season, or when your pricing head is on leave, has already moved.

Trap four. The plan with no owner on your side

Every good plan of this kind has two owners, one in each company, speaking on a fixed day. If nobody in your office owns the date it drifts, and nobody notices until somebody asks at the quarter end why no quote has gone out. That is not the supplier's fault and it is still your problem.

One line per vendor, written the same day, in their words. Dates are the first thing memory softens.

One more lever, and it is the reliable one. Start narrow. One trade lane, one approver, last week's real enquiries. A narrow first run needs less agreement, and agreement is what moves these dates. Widen it once a real quote has reached a real customer.

B2 asked whether you have to replace your system to start. B3 asks what starting involves. Together they turn the vaguest part of the purchase into two lists you can check, and lists are harder to argue with than confidence.