The “How Much Does It Cost to Build a Mobile App?” tool was a microsite that estimated development cost for a mobile app idea based on a short sequence of questions.
The goal was not to give an exact quote, but to help people reason about scope, platform choices and complexity — and translate that into an approximate budget range.
Problem: Abstract Ideas, Fuzzy Budgets
Many individuals and organisations have app ideas, but struggle with one basic question:
“Roughly how much would it cost to build this?”
Traditional discovery calls often suffer from:
Unclear scope at the beginning,
Long email threads or meetings just to gather requirements,
A big gap between initial expectations and realistic costs.
There was room for a self‑service tool that helped idea owners think through key decisions before talking to a development team.
Solution: Question‑Driven Cost Estimation
The tool guided users through a series of visual questions, such as:
Which platforms do you target? (iOS, Android, both)
Will users log in? If yes, how?
Do you need user profiles?
How will the app generate revenue?
Is there rating / review functionality?
Do you need integration with an existing website or backend?
What level of UX and visual polish do you expect?
Do you need support for app icon design?
Behind the scenes:
Each answer had a weight or multiplier,
The base cost was adjusted according to complexity and integrations,
The result was presented as a range, not a fixed price.
Approach: Visual Choices, Lightweight Backend
On the frontend:
Each question was represented as a set of icon‑driven cards,
Short, non‑technical explanations described what each choice meant,
The flow was optimised for mobile and quick completion.
On the backend:
A small PHP application processed the answers,
The pricing model was kept in a configuration layer,
The result page summarised selected options and the estimated range.
The experience was designed as an expectation‑setting tool, not a replacement for detailed scoping.
Outcome
With this microsite:
Idea owners gained a more realistic sense of budget before any call,
Early conversations between client and agency could focus on the product,
The same flow could be reused and adjusted as pricing models evolved.
It is a good example of how an interactive content piece can support pre‑sales, discovery and education at the same time.