How I analyse a client’s new idea

A client often begins the conversation with a simple phrase: “I need a website,” “I want an app,” or “We need to build a platform.” Starting development immediately after such a statement is risky. First, I try to understand not what kind of product the client wants to see, but which real problem that product must solve.

I study who will use the system, which problem these people face today, and what the outcome should be after launch. I then examine the existing business processes: how enquiries arrive, where data is stored, who is responsible for the client, which actions are performed manually, and at which stages the company loses time or money.

Next, we define user roles, core scenarios, required sections, integrations, payment methods, notifications, analytics, and security requirements. Every feature is divided into what is essential for the first launch and what can be added later. This approach prevents the product from becoming overloaded and directs the budget towards genuinely important tasks.

The analysis results in a clear project structure: exactly what we are building, who it is for, in which sequence it will be created, and which metrics will be used to evaluate the result. A good brief is not a formality; it is a foundation that protects the client’s budget, reduces rework, and gives the entire team a shared understanding of the future product.