The brief a client arrives with is rarely the problem they actually have. Discovery is where that gets sorted out — cheaply, before it becomes a build decision that costs money to reverse.

We sit with the people who will use the thing, map how the work happens now including the parts nobody has written down, and come back with a specification you can hold us to. Sometimes the answer is a much smaller system than you expected. Occasionally it is that you do not need software at all, and we will say so.

What this covers

Stakeholder and end-user interviews
Current-state process mapping, including the undocumented workarounds
Written functional specification with fixed scope
Wireframes and clickable prototypes before development starts
Technical feasibility and integration assessment
Honest estimates, with the assumptions stated

How engagements work

Interviews

Time with the people who will actually use it, not only the people buying it.
Mapping

How the work happens today, written down properly for the first time.
Prototype

Something clickable, so disagreements surface now rather than at delivery.
Specification

A scoped document with an estimate you can take to a board.