Most engineering roadmap tools treat the roadmap as a report: a read-only artifact generated from data you edit somewhere else. Veflow's roadmap is the opposite — it's a live timeline you plan directly on, by dragging project bars rather than filling in forms.
What it is
Every project with dates appears as a bar in its own lane on a timeline. The interactions are the ones your hands expect:
- Drag a bar to move the whole project. Drag either edge to pull the start or end date in or out.
- Ctrl+scroll to zoom, from a dense quarter-at-a-glance down to day-level detail.
- Drag empty space to pan. The timeline extends itself as you approach the edge — there's no "end" of the view, the horizon just keeps growing.
- A today line runs down the whole view, and any project whose dates straddle it gets an Active highlight — what's in flight right now is visually obvious from across the room.
- Click a project's name to jump into it.
Your zoom level, row height, and team filters persist between visits, so the roadmap opens the way you left it.
Resizing a project is a drag, not a form.
Why this roadmap tool skips task-level Gantt charts
The roadmap plots projects, not tasks. That's a choice, not a gap.
Task-level Gantt charts have a long history of becoming fiction: hundreds of bars, dependencies nobody maintains, dates that stopped being true the week after they were drawn. The failure mode is so common it has a smell — the chart that everyone updates before the planning meeting and ignores after it.
Projects are the altitude where timeline planning is honest. A team can genuinely commit to "search ships in the back half of June." It cannot genuinely commit to which Tuesday a specific task lands — especially when agents are doing the writing and a task's wall-clock time is measured in minutes of review, not days of work. The tasks live on the board; the roadmap stays at the level where dates mean something.
Filtered by team
The roadmap filters by team, so "what is Platform doing this quarter?" is one chip-click. Projects that span several teams show up for each of them — cross-cutting work doesn't fall in the gap between lanes.
Plan a quarter, then go to work
The loop we built it for: zoom out, sequence the quarter by dragging bars until it stops looking like a lie, then click into whichever project is Active and start writing tasks. The roadmap is where you decide when; the tasks and the agents are where the what gets done.