Second Opinion on a Developer's Quote
Got a quote for an app or an AI project and not sure it holds up? Email it to me. Within 48 hours I will tell you in writing, for free, what is solid, what is missing and what to ask before you sign.
What do you check?
- Whether the scope covers what you need, and what is vague or left out.
- Whether the price is fixed or open-ended, and where it is likely to grow.
- Who owns the code, the data and the accounts when the project ends.
- Assumptions that turn into extra invoices: data migration, integrations and "you will provide" lines.
- Whether you need a custom build at all, or whether a setting or a ready-made tool does the job.
- What happens after launch: who fixes bugs, who has the logins and what it costs to run.
What do you get back?
A short note written by me: whether the price looks reasonable for the scope, what is missing, and a list of specific questions to send your developer before you sign. If the quote is good, I will tell you to sign it.
What should you send?
The quote or proposal, plus two lines on what the software must do for your business. Please leave out passwords and card details.
What is the catch?
I sell a monthly development subscription, and this is how you see the way I think before you ever talk to me about it. You do not have to buy anything. I will not contact your developer, and I will not rubbish their work to win the job.
Who sees the quote?
Only me. It sits in my mailbox, hosted by Titan. I do not share it, and I delete it within 30 days of replying. See theprivacy page.