A confirmation email goes out immediately with your inquiry number in it. We read scope and size from what you wrote to produce an estimated range first, then a person checks whether that number matches reality. The quote goes out within one to three business days, and if the description is too short to price on we ask a few questions before that. Emails are not sent on weekends or public holidays; they go out together on the next business day.
It turns on the number of screens and features, which external services need integrating, whether an admin screen is required, and how often data comes in. Two projects both called "an online store" land a band apart once payment and settlement are involved. We sell at listed prices, so once the scope is fixed the price is fixed with it, and it does not go up mid-project unless the scope changes.
The difference is not length but whether "what, for whom, how often" is in there. The two sentences below describe the same job with very different pricing accuracy.
Please build me an online store.
A clothing store with around 200 products, card payment and bank transfer. The admin screen needs to show orders and stock and let us enter tracking numbers, and we want the courier API integrated.
Leave out anything you do not know. "Not sure yet" is an answer too, and it is usually faster if we propose a scope and a price first and adjust from there. Tell us the budget and we will decide together what comes out of it.
A document number and a validity date, the amount and VAT, the project overview and detailed scope, and the schedule. The amount is broken down by stage rather than given as one lump, so you can see what costs what. There is a validity date because labour and third-party service prices move; once it passes we simply issue a fresh one. If a line does not suit you, say so and we take it out — a smaller scope means a smaller price.

A spec, a sketch of the screens, a link to a competing service, an Excel template — any of these is enough. A hand drawing is often more precise than paragraphs. If you have a tender document or an RFP, just upload that and we will read it and work from it.
An admin tool of a few screens runs in weeks; a service with payment and settlement runs in months. What stretches a timeline is usually not development but decisions — a screen changes midway, or an approval is late. So we fix the screen list and the feature list before kickoff, and anything that changes is handled as a scope change.
Accept the quote and we send a contract; the amount is split into a kickoff payment, an interim payment and a balance. The contract states what has to be finished before each one is due. The balance comes after acceptance testing. Whether source code, accounts and server configuration are part of delivery is also settled in the contract up front.
This screen carries no ads and we do not pass on what you write. If you are unsure how much of the idea to reveal before a contract, ask for an NDA first. We do not make sales calls — we only reach you by email and in the inquiry thread.