Loading Gridfused0%
Back to Blog
Business|Analysis|November 18, 2026

What Happens When a Customer Tries Your App?

Follow a customer through a real task, understand what they expected and use what happens to choose your next step.

João Dezembro · 5 min

More in Business

Someone is ready to use your app for something they actually need to do. You have spent time getting it ready, so you might be wondering whether they will find it useful or whether something you missed will get in their way. The only way to begin answering that is to see what happens when they try it.

I would start by asking what they are trying to get done and how they handle it today. Then, as they use the app, you can follow what they do and ask about anything you do not understand. You may find something that needs fixing, but you may also discover that the result they need is different from the one you had in mind.

Start with the customer’s task

Let’s say you have built an app to help small shop owners order stock from suppliers. One owner usually checks a notebook to see what is running low, then sends a message to the supplier, and you want to make preparing that order easier.

When the owner opens your app, they look around and ask where they can find what they ordered last time. You expected them to start a new order and enter the products, so you could take that as a request to add previous orders. Before deciding that, though, I would ask how they use the old list and what they need from it.

They might tell you that they buy much the same products every week and only change a few quantities. Or perhaps the products change often, but the old list helps them remember which supplier had each item. In both cases they asked for the same thing, but what would make the next order easier is different.

You can also follow what happens after they prepare the list. If they need to copy it into a message, for example, ask them to show you how they would send it. The order may look complete in the app, but it still needs to be useful when they go back to work.

Let them try it

When you invite someone to try the app, give them a task that makes sense for them, such as preparing their next order. If they do not have one to make that day, you can use an example together and follow up when they do. Make sure they know whether it is a real order or a test, and get their agreement before sending anything to a supplier.

Give them room to decide where to start, and if they pause, ask what they were expecting to find. You do not need to leave them struggling to get an answer. Help them move on, make a note of where they needed you, and if the app cannot complete the task, agree on another way to help them continue.

Once you have seen where the owner needed help, you can look more closely at what happened. If they could not find where to add a product, ask where they expected to find it before deciding how to change that step. If they added the products but the order disappeared when they came back, you need to find out what happened to the information before asking them to rely on the app again.

The owner may also finish the order and still return to the notebook because it helps them decide what to buy. In that case, I would ask them to show you how they use it. The app may be doing what you built it to do, but you still need to understand whether that is enough for the work they want to get done.

Keep track of what happened

After the conversation, write down what happened while you still remember the details. You might note that the owner looked for a previous order, needed help adding a product and kept the notebook nearby, then write down what you still need to understand about each of those moments.

You can return to the same person when they prepare another order, or ask another shop owner to try the task. They may have a different way of working, so I would give them the same room to show you what they do rather than assuming the first explanation applies to everyone.

Choose what to do next

You do not have to act on every request at once. Start with what is preventing the customer from getting a result they can use. If the app loses an order, that needs attention before they can trust it with their next one. If the order is saved but they still need the notebook to choose products, spend some time understanding what the notebook gives them before deciding what to add.

After making a change, ask someone to try the task again and see whether it helped. If a customer took the time to show you the problem, let them know what you changed and invite them back when they have another order to prepare.

After that first attempt, you may know that the owner needed help adding a product and expected to find a previous order. You may still need to understand how they use that order before deciding what to build, and that is a useful outcome too: you now have a specific question to take back to the customer.

As more people try the app, keep looking at what happens after they reach the end of the task. If they can prepare an order but still cannot use it to contact their supplier, there is more work to do before the app is helping them in the way you intended.

João Dezembro

João Dezembro

Founder & Managing Director

Founder of Gridfused Technologies. Software architect and engineering leader focused on building reliable products, systems, and AI-enabled operations.

November 18, 2026

5 min

Filed under

Categories