The role that turns business needs into requirements developers can build from — mapping processes, resolving contradictions between departments, and writing down the rules nobody had written down.
Most requirement failures are not technical. They happen because two departments described the same process differently and nobody reconciled it before development started.
We involve analysis where the domain is genuinely complex — finance, logistics, regulated work — and skip the overhead where a founder can specify the product directly.