One of the first questions clients ask is "how much will this cost?" It's the right question, and one that too many agencies dodge with vague answers like "it depends." Of course it depends — but that doesn't mean we can't explain exactly what it depends on and give you a real number as early as possible.
Here's exactly how we estimate projects at DevTech, why the math works out the way it does, and what you can do before our first conversation to help us give you a more accurate number faster.
Step 1: Discovery call (free, 30–60 minutes)
Before any numbers, we need to understand what you're actually building. We'll ask about your business goals, who your users are, what the core features need to be, and what you already have (designs, content, existing systems). We also ask about your timeline and budget range — not to lock you in, but so we're building a realistic scope from the start, not quoting something that doesn't fit.
If we can already tell during the discovery call that the budget doesn't match the scope, we'll say so. It saves everyone time.
Step 2: Feature and screen breakdown
After the discovery call, we build a complete feature list — every screen, every interaction, every integration. For a mobile app, this might be 20–80 line items. For a website, it might be 10–30. We break every feature into three complexity categories:
- Simple — standard UI patterns, no custom logic, no integrations (a static content page, a contact form)
- Moderate — custom logic or one integration (a filtered product search, a booking form connected to a calendar)
- Complex — custom algorithms, multiple integrations, or real-time functionality (a GPS tracking system, payment processing with subscriptions, custom data dashboards)
Step 3: Time ranges per feature
Each feature gets a best-case and worst-case hour estimate. We use ranges because software always has unknowns — edge cases, API behavior you didn't expect, design iterations. We then sum the ranges across all features to get a total project range.
We also factor in:
- Design time — UI/UX work before a single line of code is written
- Testing time — QA across devices, browsers, and edge cases
- Integration and configuration time — setting up hosting, CI/CD, third-party services
- Content time — if you need us to write copy or source images
Step 4: Adding a realistic buffer
We add 15–20% to the total estimate for unexpected complexity, polish, and the inevitable "can we also add this small thing?" conversation. This isn't padding — it's honest planning. Projects that skip the buffer almost always run over. We'd rather quote a number with the buffer included than promise something and come back with a change order mid-project.
What drives the price up
The biggest factors that increase project cost:
- Number of unique screens or pages — every new screen is design + development + testing
- Third-party integrations — payment processing, maps, authentication, CRMs all take time to integrate and test
- Real-time features — live data, WebSockets, background processes add significant complexity
- Multi-platform — iOS + Android + web is 3x as much testing surface as just one platform (though React Native keeps it manageable)
- Custom design — fully custom UI takes more time but produces better results than slotting content into a template
- No defined scope — "we'll figure it out as we go" is the most expensive way to build software
What drives the price down
You can keep costs lower by coming prepared:
- Clear content — if you have your copy, images, and branding ready, we skip a lot of back-and-forth
- Defined scope — a well-thought-out feature list means we're estimating what you actually need, not a wishlist
- Phased approach — launching an MVP and adding features later is almost always cheaper than building everything at once
- Using our packages — for common project types, our service packages bundle the most common features at a predictable price
Why we'd rather lose a deal
We've turned down projects where the budget genuinely didn't match what the client needed. That might seem like bad business, but here's why it's the only way we operate:
- Underbidding leads to cut corners, which leads to a product neither of us is proud of
- Overpromising and underdelivering breaks trust — and trust is the most valuable thing in a service business
- Being upfront about costs, even when awkward, builds long-term relationships and referrals
If we think your project can be done for less with a different approach, we'll tell you. If we think your budget is unrealistic for what you want, we'll tell you that too — and often suggest a phased approach that gets you something real within your budget now.
Sample pricing reference
To give you a rough idea before we've even talked:
- Simple business website — $1,500–$3,000
- Full small business site with SEO — $3,000–$5,000
- E-commerce store (Shopify) — $3,000–$10,000+
- Mobile app MVP (React Native) — $3,000–$25,000+
- Custom web app — $5,000–$50,000+ depending on complexity
See our packages page for fixed-price options that cover the most common project types.
Get a real number
If you're curious about what your project might cost, fill out our quote form or reach out directly. We'll respond with a real estimate — not a sales pitch — usually within one business day.
Related resources
- Service packages & pricing — fixed-price options starting at $1,500
- Frequently asked questions — including common pricing questions
- React Native vs. Native — understanding the platform decision that affects mobile app cost