Home
Deep Insights| 2026-09-18

You Gave Sales a Date. Now You're Building Their Feature.

Jessica Tran
Staff Writer
You Gave Sales a Date. Now You're Building Their Feature.

It started in a Slack DM. The VP of Sales pings you: “Hey, quick question. Acme Corp is about to sign, but they’re asking about the new dashboard. Can you give me a rough date? Just a ballpark for Q3 is fine.”

You know the risks. But you want to be a team player. You check the backlog, mentally add some buffer, and type back: “Heavily caveated, but we’re targeting late Q3. Let’s say September.”

A week later, you’re in the deal review meeting. Your feature is on the slide. Not as a roadmap item, but as a contractual commitment. The deal is contingent on a September 30th delivery. Your ballpark estimate, full of caveats, has become a deadline. Your discovery-driven roadmap just became a project plan for one customer.

Why Giving a Date Is a Trap

When a sales leader asks for a date, they aren’t asking for an estimate. They’re asking for a commitment they can use to close a deal. It’s not malicious; it’s just how their world works. Their incentives are quarterly quotas and signed contracts.

Your world is different. You’re paid to solve the right problem for the entire market, not just the next big logo. Your currency is validated learning and de-risked bets.

When you give a date for an un-specced feature, you’re trading your currency for theirs.

  • It kills discovery. You can no longer ask, “Is this the right problem to solve?” The only question left is, “How do we ship this by September 30th?”
  • It creates a shadow backlog. The feature for Acme Corp now has an implicit #1 priority, regardless of what your strategy says. Your carefully planned sprint is one escalation away from being derailed.
  • It erodes trust. When you inevitably have to renegotiate the date because of unforeseen complexity (which you never had time to discover), you look like you can’t plan.

The Wrong Ways to Respond

Most product managers try to hedge, but these tactics usually backfire.

  • Adding massive buffers: You take the engineering estimate and triple it. This might buy you time, but it destroys credibility.

Generated by Reportify AI — Automate your team's status reports, standups, and weekly updates. Try free →

Stop Drowning in Reports

Turn your scattered meeting notes into executive-ready PPTs and Word docs in 30 seconds.

Get the App