A Quick Test to See if your Quote is Missing Money.
If you are building a React Native app in the USA, a quote can look fine and still be missing big items.
Missing items do not stay missing.
They show up later as extra invoices, delays, and stress.
This post is a simple quote audit.
You can use it in 10 minutes before you sign.
Download the printable checklist PDF
React Native Budget Checklist USA 2026
Use it while reading the quote. Use it again during kickoff.
Section 1
---------
A Quick Test
Is your quote missing money?
Answer yes or no.
- Does the quote show a clear list of what is included
- Does it show what is not included
- Does it include testing time and bug fixing time
- Does it include store release work for iOS and Android
- Does it include payment failure cases and double order prevention
- Does it include device testing on more than two phones
- Does it include who owns accounts, code, and access
- Does it include change request rules and pricing
If you said no to three or more, the quote is likely missing money.
Section 2
---------
The 5 line items that are usually missing from quotes
These five items are where cost and time jump.
1. Testing and bug fixing
Many quotes say development, but they hide testing.
What this should include
QA testing time
Bug fixing time
Retesting time
Basic regression testing before release
If it is missing, you will pay later.
2. Device list and device testing
Testing on one iPhone and one Android is not real testing.
What this should include
A short device list
At least one mid range Android phone
A plan for bugs that happen on one device only
3. Store release work
Many quotes end at build ready.
Real work still remains.
What this should include
Signing and build setup
Store listing details
Screenshots
Privacy forms
Review notes
Buffer time for rejection and resubmission
4. Payments and failure cases
If your app has payments, the happy path is not enough.
What this should include
Payment failed handling
Payment success but order not confirmed
User taps pay again
Status checks to stop duplicate orders
5. Upload failure handling
If your app has uploads, failures will happen.
What this should include
Slow internet handling
Retry steps
Clear error messages
Safe continue steps so users do not get stuck
Section 3
---------
Questions to ask your developer before you sign
Ask these questions in a call.
If answers are vague, expect trouble.
Scope and plan
- What is out of scope for version one
- What are the hard screens in this app
- Which parts have the most risk
QA and devices
- What is your test device list
- How many rounds of QA are included
- Is bug fixing included or billed extra
- What happens when a bug only happens on one Android model
Payments and uploads
- How will you stop duplicate orders if payment is slow
- How will you handle payment success but order not updated
- How will uploads work on slow internet
- What happens when users deny camera or photo access
Release and ownership
- Who owns the Apple and Google store accounts
- Who owns the code repo
- Will you hand over all keys and access at the end
- How many days do you keep for store review and fixes
Change control
- How do you price a change request
- What counts as a change
- Who approves changes and how fast
If the team cannot answer these clearly, the quote is not ready.
Section 4
---------
Red flags checklist
Here are the red flags. If you see these, pause.
Red flag 1
One total number with no phases
Red flag 2
No QA time mentioned
Red flag 3
No device list mentioned
Red flag 4
No store release work mentioned
Red flag 5
Payments included but no talk about failure cases
Red flag 6
Uploads included but no talk about slow internet failures
Red flag 7
No clear list of what is included and not included
Red flag 8
No mention of who owns the repo and accounts
Red flag 9
No change request rules
Section 5
---------
Example
Medicine delivery app quote audit
Example app
A healthcare shopping app that sells medicines and daily use products.
Core features
Product list
Product page
Cart
Checkout
Order tracking
Prescription upload for some medicines
Notifications for order updates
Now the audit.
What many quotes cover
Screens and basic flows
Basic backend endpoints
Basic login
Basic checkout screen
What many quotes miss
Prescription upload details
Camera and photo permissions
Users deny access
Slow internet upload failures
Retry steps and clear messages
Payment edge cases
Payment success but order status not updated
Users retry and create duplicate orders
Need status checks and duplicate order prevention
Device testing
Android device differences
Notifications blocked by battery settings
Camera issues on certain models
Store release
Privacy forms
Permission text
Store review changes
Resubmission buffer
If the quote does not mention these items, the quote is missing money.
This is why a simple app can move from 8 weeks to 14 weeks.
Not because of new screens.
Because missing items show up late.
Section 6
---------
What a good quote looks like
A good quote is split into clear parts. Each part has a line item and a clear output.
1. Discovery
What it should include
Requirements list
User flows
Out of scope list
Hard screens list
Risk list
What you should receive
A written scope document
A clear list of what is included and not included
2. Design
What it should include
Key screens
All states for key screens
Error messages
Permission screens
What you should receive
Final screen designs
A simple flow for each key feature
3. Development
What it should include
App build work
Backend work
Admin work if needed
What you should receive
Working builds you can test
Access to the code repo
4. Integrations
What it should include
Payments
Push notifications
Analytics
Uploads
Maps or other tools
What you should receive
A list of all tools used
Proof that each tool works on iOS and Android
5. QA
What it should include
Device list
Test plan for key flows
Bug fixing time
Retesting time
What you should receive
A test report or bug list
A stable build before release
6. Release
What it should include
Signing and build setup
Store listing tasks
Screenshots
Privacy forms
Time buffer for review and resubmission
What you should receive
Store ready builds
A release checklist
7. Handover
What it should include
Repo access
Accounts access
Keys
Basic documentation
What you should receive
Full ownership and access
A handover checklist
8. Change rules
What it should include
What counts as a change
How changes are priced
Who approves changes
What you should receive
Clear change request rules in writing
If your quote does not look like this, ask for a rewrite.