A phrase that usually means nothing
Every dev shop says "production-ready." For most it means "it runs on my laptop and I deployed it once." Then the first real user hits an edge case, the thing falls over, and you discover that "production-ready" was marketing.
When we put "production-ready" or "deployed" on a quote, we mean a specific list. You should hold us to it, and you should hold any shop to it. Here it is.
The checklist
It is deployed on real infrastructure, not a demo host. The app lives on AWS, with HTTPS, a real domain, and the infrastructure defined as code (Terraform or CDK) so it can be rebuilt deterministically. "It works on Vercel's free tier" is a prototype, not production.
Auth is real. Not a hardcoded password. Actual authentication, sessions handled correctly, and access controls that hold up when someone pokes at them.
The data layer is durable and backed up. A database that survives a restart, with a backup story you can say out loud. Losing data on a deploy is not a production system.
Errors are handled, not just thrown. The app degrades gracefully. When a third-party service is down, the user sees a sensible message, not a stack trace. Failures are logged somewhere you can actually look.
It survives a basic security review. No secrets in the repo. Least-privilege access. The kind of posture that does not embarrass you when a customer sends a security questionnaire. We build to this by default because most of our work eventually meets one.
You get the code and the docs. The repo is yours. There is a handover doc that explains how to run it, deploy it, and change it. You are not hostage to us to keep the lights on.
Why this fits inside a fixed price
People assume "production-ready" means "expensive and open-ended." It does not, if the scope is honest. Our Web App engagements are fixed price, $6,000 to $25,000 depending on scope, delivered in 2 to 12 weeks. The fixed price is possible precisely because the production checklist is a known quantity, not a surprise we discover at the end.
What is excluded is also explicit: third-party costs like domains, Stripe fees, email sending, and model API usage are billed to you directly, not marked up through us. Honesty about exclusions is part of how a fixed price stays fixed.
How to use this
Next time a shop quotes you a "production-ready" build, send them this list and ask which items are included. The gaps in their answer are the gaps you will discover later, at the worst possible time.
If you want a build that clears every line on the list for a fixed number you see before work starts, book a 30-minute call. It ends with a written quote within a week.