How Wevit works
Wevit follows one path from an idea to delivered work: describe it, break it down, order the work, plan it, deliver it and measure it. You do not have to go in order, and you can come back to any step. Which tabs you see depends on your plan and your role in the project.
1Describe it
Write down the idea. Wevit can draft the PRD from a short description.
Start by writing down what you want to build. In the PRD tab you describe your idea in a box and Wevit drafts every section of the product requirements document for you; you can also write the sections yourself. You do not need to fill anything in first.
If ideas arrive from your team or customers before there is a PRD, collect them in the Ideas tab, where each one moves from Submitted through Under Review and Planned to Completed or Declined.
2Break it down
Turn the PRD into features, epics and stories in the backlog.
The backlog is where the PRD becomes work. It is a hierarchy of features, epics and stories (the level names depend on how the project was set up), with room for estimates. You can import an existing backlog from Excel and group work into streams.
Stories carry the detail the team builds from. The backlog is the core of the project, so most of the later steps read from it.
3Order the work
Map what depends on what, and decide what matters most.
Once the work exists, decide what comes first. The Dependencies tab records which items cannot start or finish until another does, including work that relies on another team, and shows the links as a graph or a table.
The Prioritization tab scores and ranks your features using frameworks such as Now/Next/Later, MoSCoW, WSJF, RICE, ICE or a Value vs Effort chart. It needs features in the backlog first.
4Plan it
Allocate the work across sprints and see the timeline.
Planning turns the ordered backlog into dates. The Planning tab spreads the work across sprints using your team's capacity, either generated by Wevit or built by hand, and shows a timeline. It works best when the backlog has estimates and the team members have been added in the Costing tab.
The Roadmap tab shows what is coming and in what order, built from your features, goals and initiatives, which is useful for stakeholders who do not need the sprint detail.
5Deliver it
Move stories across the board and log the time spent.
While the team builds, the Kanban board shows your stories in columns from Backlog to Done, and you move cards as work progresses.
The Time Tracking tab has a timer and timesheets for logging the hours spent, which can then be submitted and approved.
6Measure it
Track progress, velocity and cost against the plan.
Check progress against the plan. The Reports tab shows sprint velocity, burndown and cost analysis, with Excel exports. The Velocity tab tracks how much work the team finishes per sprint so the next sprint can be planned realistically.
The Costing tab shows what the project costs, based on your team members and cost configuration. What you learn here feeds back into planning for the next round.
Last updated 4 October 2026