Is this a normal price?

The four questions that settle it

You do not need technical knowledge to ask these, and the answers are more informative than any benchmark table.

• What does this price assume about our existing systems and our data?
• What is deliberately not included?
• Who specifically will write the code, and what have they built before?
• What happens, in money and in time, if something takes longer than estimated?

Why the same brief gets a threefold spread

Almost all of it is scope, not greed. A quote for 'a members area' can legitimately mean a login page and a static account view, or it can mean roles, permissions, billing changes, email notifications, an audit trail and a support process.

The rest is seniority and location. An experienced engineer costs more per hour and frequently less per outcome, because the estimate is not padded to cover uncertainty they do not have.

Signs the price is genuinely too high

There are patterns that suggest a number inflated for reasons unrelated to your project.

• A large fixed price offered before anyone examined your existing system.
• Effort on setup and infrastructure comparable to effort on features.
• A rewrite of working software recommended without an audit.
• Refusal to break the total into items with days against them.
• Project management priced as a large share of the total on a small project.

Signs it is too low

The cheap quote is usually the expensive one, and the tells are consistent.

• No testing anywhere in the breakdown.
• Integrations priced in hours when nobody has checked whether an API exists.
• No mention of data migration on a project that replaces an existing system.
• A timeline with no client dependencies, implying nothing is expected from you.
• Nothing about what happens after launch.