Two calendars that do not match
You need the workflow this quarter. The vendor needs a feature that sells to their market next year. Those are not the same schedule, even when the slide uses the word roadmap.
We already wrote about why context-right beats vibe-coded, and about the last mile after the demo. What off-the-shelf cannot see is the exception layer. This is different: order and timing. Who sets the sequence.
How this differs from “the tool can’t do it”
Sometimes the package literally cannot model the job. That is a missing object.
Sometimes the package will get there, on their calendar, for their average customer. That is a sequence problem. You are not blocked by capability forever. You are blocked by someone else’s backlog.
The SERP is full of essays about product strategy inside your own company. Fine. Those posts are about your backlog. This post is about living on someone else’s. A vendor ships what serves their market. Your close, dispatch, or quote does not get a vote.
Can you wait for the vendor?
Sometimes. Wait when the gap is annoying, the workaround is cheap, and the vendor’s date is real and near.
Do not wait when:
- The week already stops without the workflow
- The unofficial tracker is already load-bearing
- “Coming soon” has slipped once
- The feature, even if shipped, will still need your exception path
If the next thing you need is on their Q3 slide, it is not on your schedule.
Build around vs replace
You do not have to rip the suite out to stop waiting.
Buy the commodity. Build the layer that sits on your timeline: the exception, the handoff, the sequence the vendor will not prioritize. That is custom software that earns its keep. Consulting is how you decide what stays packaged and what you own so Friday no longer depends on a vendor slide.
Replacement is for when the package cannot see the work at all. Sequence control is for when it might, later, after your week has already burned.
Who owns the sequence after you customize
You do. That is the point.
Once the path that matters runs on software this company can change, the vendor’s roadmap becomes input, not a gate. You can still adopt their feature when it lands. You are no longer frozen until it does.
If you are already waiting on a slide for a workflow you run every week, talk to us about the sequence, not another demo of their roadmap.
Questions
How is this different from “the tool can’t do it”?
Missing capability is an object-model miss. A roadmap miss is timing: they may ship it for their market later. Your week still needs an owner now.
Can you wait for the vendor?
Yes when the gap is cheap and the date is credible. No when the unofficial tracker is already the system, or the week stops without the workflow.
What do you build around vs replace?
Build the path that must move on your calendar. Keep the commodity packaged. Replace only when the package cannot see the work even in principle.
Who owns the sequence after you customize?
This company. The vendor roadmap becomes optional input. It is no longer the gate on Friday.