How does the quote wizard work?
- You choose the platform: iOS, Android, both, or including a web panel.
- You tick the user roles and core screens (login, profile, list, detail, checkout, etc.).
- You add the integrations you need: payments, maps, push notifications, SMS, external APIs.
- You specify your admin panel and reporting needs.
- The wizard produces a scope summary and preliminary estimate from your choices.
The preliminary estimate is a starting point; the firm quote is given after we review the scope together. For a detailed look at what drives the cost, see the mobile app development cost page.
What is the estimate based on?
Every screen, role and integration corresponds to time spent on design, development and testing. The wizard adds these items up without counting shared parts, such as a common backend and admin panel, twice. The factors that move the estimate most are the number of user roles, features needing real-time data such as live location or real-time messaging, and integrations with external systems.
What should you prepare for a firm quote?
- Scope summary: The app's purpose, target user and the problem it solves.
- Screen list: The screens for each role and the actions on each screen; rough sketches on paper are enough.
- Reference apps: Apps you like and which feature you want to model.
- Integrations: The payment, shipping, accounting or map service you want to use.
- Priorities: What must be in the first release and what can come later.
The MVP approach: start small, grow the right way
An MVP is the smallest version that is enough to validate your idea with real users. In the wizard you can first pick only the must-have features to see the first release scope, then view the extra features separately. That way you see how much each feature affects the cost and make an informed decision.
An MVP still has to comply with store rules and offer real functionality; apps that merely wrap a website can be rejected on the App Store. You can find details on the App Store rejection fix page.
What I offer
Step-by-step wizard
Choose platform, screens, integrations
Preliminary estimate
Instant scope summary from your choices
MVP split
First release and later phases apart
Screen list
Role-based screen plan
Firm quote
Itemised after a scope call
Store compliance
Meets the minimum functionality rule
Technologies I use
Example projects
A selection of live projects serving real users.

Kassa — iPhone POS & Inventory App
Barcode sales, stock, customer credit and profit reports for grocery stores and kiosks; works offline.
View
Taxi, Fleet & POS Platform
Passenger, driver and fleet apps with live dispatch and POS.
View
Pingora — Number-Free Messaging
Secure messaging and video calls without sharing a phone number.
ViewHow we work
Free intro call
We clarify needs, existing systems and goals together.
Quote & roadmap
Scope, technology, timeline and budget within 24 hours.
Staged development
Weekly demos and a live test environment.
Launch & support
Go-live, training and ongoing maintenance.
Free pre-analysisThe first meeting and roadmap are completely free, with no obligation.
Staged delivery and approvalYou review each module on a test environment before we move on.
Written scope and rightsScope, delivery and source code rights are defined in the contract.
Frequently asked questions
Is the wizard's estimate a final price?
No. The wizard produces a preliminary scope and estimate based on your choices. The firm quote is given after the scope and screen list have been reviewed together.
How do I prepare a screen list?
For each user role, list the screens they will move through in order and describe in one sentence what happens on each. Rough sketches on paper are enough.
Why do reference apps matter?
A reference app communicates your expectations quickly and clearly. Saying which feature or flow you like prevents the scope from being misunderstood.
Is starting with an MVP right for every project?
It suits most projects where the idea needs market validation. For projects that digitise an existing business process, the first release may need to cover the process in full; that decision is made together during the scope call.