App planning guide · By Fawaz Alesayi
What will your app cost to build?
A feature list is a start, but it rarely tells the whole story. The estimate also needs to cover how the app works, the systems it connects to and the work required to release it. Here is how I price that work at Accelerate.
My rate and what it includes
Agreed work is billed at SAR 250/hour for actual time. That includes discovery, meetings, implementation, testing and deployment. Third-party costs are separate. No VAT is charged under the current service terms.
An estimate is a range based on the scope and assumptions, not a fixed-price promise. The AI conversation and initial estimate are free. I review the scope before we agree on any paid work.
What changes the number of hours?
A single customer journey is different from an app with several roles, payments, subscriptions, admin tools and integrations. Supporting more platforms or languages also adds work that needs estimating.
Existing code can help, but only after we check its condition. An undocumented integration, data migration or an uncertain requirement can change the estimate even when the screen looks simple.
Example arithmetic, not a typical app price
If an agreed scope took 100 hours, the development charge at my current rate would be SAR 25,000. At 200 hours, it would be SAR 50,000. These are arithmetic examples only, not packages or an estimate for your app.
Hosting, external APIs, store accounts and other services may add separate costs. We identify the services your project needs and check their pricing when preparing the estimate.
What to send before asking for an estimate
Describe who will use the app and the main thing they need to accomplish. Include the platforms and languages you need, any existing software it must connect to, and what you have already built.
Mention your budget and any real deadline, including why it matters. List what must be in the first version and what could wait. A sketch or a redacted example is useful; sensitive records are not.
Compare the scope, not just the total
Check whether each proposal includes testing, admin tools, integrations, deployment and handover. Ask who holds the accounts and what support covers after release.
To reduce the initial scope, choose one useful customer journey and postpone features that are not needed to test it. Keep the testing and data-handling work that journey requires.
Questions before starting
Is the AI estimate a final quote?
No. It helps outline the requirements and a likely range. I review the details before we agree on the work.
Can I discuss it without using AI?
Yes. Use the direct contact form to send me your project details.
Is this a Saudi market price survey?
No. This guide explains my own pricing and estimating approach. It does not claim an average price for agencies or developers in Saudi Arabia.
Get an estimate for your actual scope.
Start with the assistant, or send your idea directly to me if you would rather talk first.