Start a digital product without building the wrong thing

“We need a website” starts a useful conversation, but it does not yet define the challenge. One company needs a persuasive introduction for major buyers. Another needs a catalogue that helps its sales team. A third needs an account area to replace orders scattered across messages. Similar requests can lead to very different products.

Start with a change in the business

Ask what should become easier after launch. A customer understands the offer. A manager receives an enquiry with useful context. An employee stops copying data between spreadsheets. This connects the investment with real work.

Then describe the main journey rather than a list of pages: someone arrives with a question, sees the relevant evidence, chooses an offer, sends a request and gets a next step. Beautiful screens only become a service when those transitions work.

A first release needs a complete journey

Reduce capabilities while keeping the journey intact. A catalogue can launch without online payments if buyers can select products and send a request, and the team can process it. An enquiry form without reliable delivery loses the point of the product.

For each part of the first release, define who uses it, what they receive and how readiness will be checked. This separates essentials from later improvements. The remaining ideas become a roadmap rather than hidden commitments.

What to bring to an estimate

• The process that needs to change and its current friction.
• The users and the important action.
• The data, materials and systems already available.
• The launch date and what makes it significant.

You do not need a detailed specification for a first conversation. A useful estimate follows an understanding of the context, with scope, sequence and boundaries proposed by the team. It is a discussion of your business challenge rather than a price for an arbitrary screen count.

Start with a few words about your project. We will clarify the journey and suggest a next step.