A feature or integration in existing software
One defined outcome such as payments, a private area, an API, an internal panel, or a flow to finish.
Assumption: The project runs, access is available, and the change stays within one area.Choose what you are building and what the first release needs. The estimator shows a practical price range, delivery time, and the choices that affect both.
Live projects
Mappu is a live product. Preflight Scout has public code and packages.
Estimator
Choose the starting point and what the first release really needs.
Typical price ranges
Compare the likely cost and delivery time.
One defined outcome such as payments, a private area, an API, an internal panel, or a flow to finish.
Assumption: The project runs, access is available, and the change stays within one area.A usable web application with one main journey, the required backend, and deployment.
Assumption: One primary user, few integrations, and secondary features left for later.A first iOS and Android app with a backend, device testing, and a distributable build.
Assumption: The mobile flow is defined, without a full web app or large back office.The same journey works across web, iOS, and Android with shared backend and product logic.
Assumption: Release the core journey first, then add the remaining surfaces.Why the range moves
These four areas have the biggest effect on cost and timing.
Who uses it, what they complete, and what data the product needs to retain.
Working code and deployment reduce uncertainty; missing tests or access add it.
Permissions, recovery, payments, maps, email, and APIs add real states and failure cases.
Web, mobile, stores, monitoring, and support change both build and release work.
Scope
The range assumes one agreed release. Third-party fees and work added later are separate.
Frequently asked questions
Yes, by reducing the first release: one journey, one platform, fewer roles, and fewer integrations. A static prototype costs less, but it is not a working product.
Existing code can save time or add uncertainty. I check setup, the relevant code, tests, access, and deployment before pricing the change.
No. The main journey must work from start to finish. Secondary features wait; reliability and data ownership do not.
Next step
Send the estimate and anything that already exists. I will reply with the next practical step.