What Businesses Should Know Before Building an App

A mobile app can be a powerful addition to a business — or an expensive disappointment. These questions help you tell the difference.

1. What problem does the app solve?

Be specific. “We need an app” is not a goal. “Customers should be able to book without phoning” is.

2. Do you need an app, or would a mobile-friendly website do?

Many needs are met well by a good mobile website or web application, which can be quicker and cheaper to build. An app makes most sense when you need features such as push notifications, offline use, or frequent repeat use.

3. Who will use it, and how often?

An app people open daily — staff tools, regular bookings — justifies more investment than something used once a year.

4. What is the smallest useful first version?

Start with the core features that deliver value, launch, and learn from real users. Adding everything at once increases cost and delays feedback.

5. What does it need to connect to?

Most apps need a backend: user accounts, a database, payments, notifications. This hidden part is often the larger share of the work.

6. How will you keep it running?

Apps need updates when phone systems change, bug fixes and ongoing support. Plan for this, not just the launch.

7. How will people find and install it?

An app does not attract users on its own. Think about how you will tell customers it exists and why they should install it.

8. What will it cost?

Costs depend on features, platforms, design and integration. A clear scope leads to a clear quote.

A sensible way to start

Write down who the users are, the three things the app must do and what success looks like. Then talk it through with a developer who will give you honest advice, including if an app is not the answer. Start a conversation or read about our mobile app services.