Your AE Promised a Ship Date You Cannot Hit [2026]
The closed-won lie
CRM celebrates closed-won. Customers celebrate delivery. When those dates diverge, you do not have a CRM problem — you have a trust problem that shows up at renewal as churn, chargebacks, and angry champions who will not take your call.
Product-led companies selling hardware, kits, samples, or bundled physical goods hit this wall earlier than pure SaaS. The fix is not “sales should communicate better.” The fix is one place for pipeline and inventory truth.
Before the AE says yes — checklist
- SKU and quantity on the opportunity — not “~500 units.”
- Available stock or documented backorder with date range.
- Vendor lead time if you drop-ship or assemble.
- Shipping constraints — regions, carriers, hazmat, signature required.
- Fulfillment owner named before signature.
If the rep cannot check stock in under two minutes, they should not quote a ship date. Use Flow (Beta) from the launcher — supply chain on the same graph as Momentum. See Flow supply chain starters.
What to log when the customer asks "can you ship by…?"
| Field | Why it matters |
|---|---|
| Requested date | What sales promised — auditable |
| Committed date | What ops confirmed — may differ |
| Inventory snapshot | Count at time of promise |
| Exception reason | Backorder, partial, substitute SKU |
When committed ≠ requested, update the customer in Mail on the opportunity before they ask. Proactive bad news beats reactive tickets in Resolve.
Post-close handoff that does not fail
- Closed-won triggers fulfillment task with SKU, qty, ship-to, committed date.
- Ops updates status — picked, packed, shipped, tracking — on the account.
- CS sees shipment context before the welcome call.
- Finance matches invoice timing to ship event in Ledger.
Read sales-to-CS handoff — add physical fulfillment as a required row, not an ops afterthought.
When sales must say no
Say no when: stock is zero with no credible inbound, vendor lead time exceeds the deal’s business reason, or customs/compliance blocks the region. A lost deal beats a lied-to customer. Offer alternatives — partial ship, later date, substitute SKU — on the record, not verbally.
Founders hate hearing no from sales. Customers hate hearing maybe when they paid yes. Pick the customer.
Connect and Mail on delivery exceptions
When ship dates slip, do not hide behind a tracking email from the carrier. Schedule a five-minute Connect call with the champion, send a written summary in Mail on the opportunity, and log the new committed date on the account. Buyers forgive delays they were told about early; they churn on surprises discovered in their warehouse.
Renewal and expansion depend on delivery
You cannot land-and-expand on an account that never received order one. Ship-date discipline is renewal insurance. Track delivery SLA on the account; review misses in weekly pipeline alongside commit. Ops and revenue in one login is not branding — it is how you stop promising inventory you do not have.
Weekly ops-revenue standup (fifteen minutes)
Product-led teams skip this until a board member asks why NPS dropped. Run weekly:
- Open opportunities with ship dates in the next 14 days — confirm stock.
- Closed-won last week without fulfillment task — fix today.
- Backorders with no customer update — draft Mail before standup ends.
- Vendor delays affecting commit forecast — log on the account, adjust pipeline.
Use weekly pipeline review rhythm — add one ops row. Sales-only reviews miss the deliveries that kill renewals.
SKU complexity without a WMS
You do not need enterprise warehouse software on day one. You need honest counts for what you sell and a rule that sales cannot promise outside those counts. Start in Flow with top SKUs, tie them to active opportunities, and expand catalog discipline as volume grows. Teams that wait for perfect inventory data never ship; teams that guess ship apologies.