Help for owners
I have a quote for my app and I want a second opinion
Short answer
A quote is easier to judge when you can see what is in it. Ask for the work split into parts, what is not included, who owns the code and accounts at the end, and how changes are handled. An independent engineer can read the quote against your idea and say whether the scope, the approach and the exclusions make sense.
Does this sound like your situation?
- Two quotes for the same app are very far apart.
- The quote is one line or a single number.
- I do not understand the technical words in it.
- I was told I need a complete rewrite and do not know if it is true.
- I feel pressured to sign this week.
Why does this happen?
Quotes are for different things
One bidder prices a simple first version, another a full product with admin tools, support and tests. The gap often comes from what is included, not from skill or greed.
Important items are left out
Store accounts, hosting, security, testing, bug fixing after launch and handover are the lines most often missing, and each can add real cost later.
Ownership can hide in the terms
Some quotes keep the code or the store accounts in the developer's name. The transfer page explains why this causes trouble later.
Vague scope turns into change requests
A quote that does not say what each screen does leaves room for disputes about what counts as extra work.
What can I do about it today?
- Do not sign under time pressureA real offer will survive a few days of checking.
- Ask for the quote in partsDesign, app, back end, testing, store release, hosting and handover, each described in plain words.
- Ask what is not includedA good quote lists exclusions. If it does not, ask for them.
- Ask who owns everything at the endCode, designs, store accounts, servers and keys. Get the answer in writing and have a lawyer read the contract.
- Send me the quote and what you want builtRemove names and prices if you like. I need the scope and your idea.
When should I bring someone in?
- You are about to commit a large sum to one bidder.
- The quote and your needs do not seem to match.
- The developer says a rewrite is unavoidable.
How do I handle it?
- Read the quote against your goalI check that what is described is what you need, and I note anything missing or unnecessary.
- Check the approachWhether the technology and the architecture suit your product, or whether they favour the bidder.
- List the questions to askA short list to send to the bidder, so their answers show how solid the quote is.
- Say what I would do differentlyIf a simpler route exists, I describe it. I do not give a price judgement without the scope.
- Keep it independentIf you want me to do the work, I quote it separately after the review. The review is not a sales step.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can you tell me whether the price is fair?
I can tell you whether the scope supports the number and what looks missing. I do not name a fair price without a defined scope.
Do I have to hire you after the review?
No. The review stands alone. If you ask me to do the work, it is a separate written scope.
What if I have no written scope of my own?
Then I start with a short description of what the app must do for customers. That is enough to compare quotes.
Do you review quotes from agencies as well as freelancers?
Yes. I read the scope and the terms the same way.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.