Can We Price an Application Without Understanding the Product?

“Can you give me a quotation? We only need a basic app.”

This is a question many technology companies hear.

But here’s the challenge: how can we accurately price an application when we don't yet know what needs to be built?

Many customers expect a low-cost quotation based on a product outline. When we ask for more details, they may not respond—or later say they received a lower quotation elsewhere.

And sometimes, the negotiation comes down to:
“Why are you charging this much? AI can build it.”

I believe this is where we need to change the conversation.

A Real Product Needs More Than an Outline

Before building an application, we need to understand:
Business Requirements → BRD → Product Scope → User Journey → Technology → Development → Testing → Launch → Maintenance

We also need to understand the business model, target audience, growth plan and expected outcomes.

Without this clarity, a quotation is often just an estimate—not a reliable project plan.

What About AI?
AI is a powerful tool for developers. It can help with coding, debugging, documentation and many other tasks.

But building a real product is not simply generating code.

The application still needs to:
Work according to the business requirements
Integrate with the required systems
Handle real-world use cases
Be tested and maintained
Evolve as the business grows

Even when AI helps generate code, developer expertise is still needed to validate, fix, integrate and deliver the product properly.

My Takeaway
A low quotation is not always a low-cost solution.

The real question is:
“Are we comparing the same scope, the same quality and the same expected outcome?”

Before asking “How much does an app cost?”, let's first ask:
“What problem are we solving, and what does success look like?”

That is where a meaningful technology discussion begins.

Have you ever received a software quotation that looked low initially but changed significantly after the requirements became clear?