The dossier arrives inside a week
A person replies within one business day, and the written findings follow inside a week. There is no discovery call to sit through first. The dossier is yours to keep whether or not you hire anyone, which is the whole point of it being free — a studio that will not write down what it found is asking you to take its word.
Then a slice, not a build
The first thing built is one workflow, all the way through: input, database, interface, notification, in production, with your own data. It is narrow on purpose and completely real.
Two things come out of it. You get something concrete to judge the work on before any budget is committed. And the integrations that are going to fight — the supplier feed with three formats, the accounting system with an undocumented field — surface in week two instead of month four.
Why the order is this way round
Architecture decided on a whiteboard survives contact with one real integration about half the time. A slice is the cheapest way to find out which half you are in, and it is cheaper still when the answer is "this approach is wrong" and only two weeks have been spent.
The plan is then revised against what the slice actually showed, with numbers that came from your systems rather than from an estimate.
If you hire someone else
The dossier is written to be useful to whoever does the work. That is deliberate. A scope specific enough to hand to another studio is also a scope specific enough to hold us to.