Open with the reason this custom software development company should exist, not a list of screens. What kind of user will use it day to day, with what frequency, and how is the job done today? An experienced team who understands the goal can propose an alternative that costs less; a team that receives only the requirements as given will price exactly what you asked for.
Set out the scope as user stories or scenarios: ecommerce software development company what the user does and what the system does in response. Every bit as useful, write down what you are not building. A written out-of-scope list prevents more argument later than the rest of the brief combined. Mark too which parts are firm and which are still open — the difference between livewire and vue changes the price, and pretending everything is fixed helps nobody.
List the constraints. These include existing systems the software has to talk to, the data you have and where it lives, security and compliance rules, expected load, which devices matter and infrastructure that is already decided. If a deadline is real, say what depends on it: a team can often cut the right scope to protect it, but only if they know it exists.
Write down what the word done means for each item. Acceptance criteria do not need formal language: a short list setting out the expected behaviour is sufficient. That one addition compresses acceptance testing by a surprising margin and removes the most common source of disputes.
To close, ask for a specific format. Require a task-level breakdown, the assumptions behind each number, the risks the team sees and a range rather than a single figure. Take a broad range as information, not evasion: it tells you exactly which requirement is unclear. At that point clarify that area and request a revised number — the revised figure tends to be the one worth planning around.