Start by describing the problem in one sentence
“We want an app” is a starting point, but on its own it doesn’t explain what the app needs to change. Write down which task takes time, who struggles with it and how it is handled today.
For example, “Dealers send their orders by message and the team re-enters them into the system” gives concrete information about the flow to be designed. Bringing one example from your current process to the first meeting is enough.
Define your first user
A customer, a dealer and an operations employee may use the same system for different purposes. Identify the most important action for each user group. Placing an order, approving it and tracking delivery are separate needs.
Instead of describing every screen from scratch, think about which steps the user will complete from start to finish. That way we can discuss the necessary functions before any unnecessary screens.
Draw the boundaries of the first version
Not every idea needs to be built at once. Choose the main problem the first version has to solve. Keep the functions that can wait for a later phase in a separate list.
Also define how you will measure success: less duplicate data entry, orders that can be tracked, or a task completed in fewer steps.
Bring three things to the first meeting
A short description of your current workflow, your user groups and your priority list make a good start to the conversation. The tools you use and the connections you need also help us understand the scope.
You can gather this information by preparing your project brief with CM Apps. We then define the scope, the development phases and the technical requirements together.