Website, online store, or custom app: where should you start?

The right starting point depends on the task. Before choosing a platform, write down what someone should be able to do and what happens after they do it.

Choose a website when the next step is a conversation

A service business usually needs to explain its offer, show useful evidence, and make contact straightforward. A business website can handle that with a few focused pages. If you already confirm scope and availability by phone or WhatsApp, you may not need accounts or a checkout.

For example, a workshop can introduce its services, show completed work, and let visitors ask about a project. A clear enquiry path matters more than an extensive dashboard.

Choose a store when people can order a defined product

An online store makes sense when products have clear prices, stock rules, and fulfilment arrangements. A WhatsApp catalogue lets customers browse and then confirm the order in conversation. A Shopify store supports a more structured buying journey.

Before building, decide who updates stock, how you take payments, how delivery works, and how customers ask for help. Checkout design cannot settle operational questions that the business has not yet answered.

Choose custom software when the workflow is specific

If employees repeatedly copy information between systems, lose track of approvals, or need different access to shared data, an internal tool may be useful. Describe the current workflow with a real example. Identify the person responsible at each step, the information they need, and the outcome.

Start with one workflow you can test. Discuss data migration, backups, permissions, integrations, and who will support the tool after launch. A portal should earn its place by making a specific task easier.

Choose a mobile app for repeated use on a phone

A mobile app can suit frequent tasks and features that benefit from a device’s camera, notifications, or home screen. It also brings release, device testing, and update requirements that should be part of the scope.

Paycebo is our example of a focused app: savings goals, contributions, and everyday allowances. Its first version records information locally and does not connect to a bank. Clear product boundaries help users understand what it can do.

Define a useful first release

Write one sentence describing the user, their task, and a successful result. List the few features needed to achieve that result. Then separate ideas that can wait. Share your current process and budget when you enquire; we can help turn them into an agreed first scope.