01
Runs discovery with your people
Sessions with founders, ops staff and real users, so the requirements come from the people doing the work.
02
Maps the process before the screens
Current and future workflows, written down, so everyone agrees what the software should change.
03
Writes stories engineers can build
User stories with acceptance criteria, edge cases and the data each screen needs.
04
Checks feasibility with the engineers
Every story is reviewed with the people who'll build it before it reaches a sprint.
05
Settles conflicting requirements
When sales, ops and finance want different things, the analyst writes the options down and gets a decision.
06
Keeps the backlog honest
Priorities, dependencies and open questions tracked in one place you can read.