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

Do You Need to Build an App to Test Your Idea?

Choose one result to test with a customer, learn from the attempt and decide what to do before investing in an app.

João Dezembro · 4 min

More in Business

You have an idea for an app and can see how it might help people. Before asking a team to build it, though, you want to know whether anyone would use it and whether the problem is important enough for them to change how they work.

You may be able to learn part of that without building the app first. I would start with one person you want to help and a result they need, then find a simple way to help them reach it. What happens during that attempt can tell you what to explore before deciding what to build.

Start with a real task

Suppose you want to build an app that helps photographers collect clients’ choices after a photo session. You imagine a gallery where clients select their favorite pictures and the photographer receives a final list. Before commissioning the app, you want to know whether collecting those choices is actually difficult for photographers.

Speak with a photographer about a recent session. They might explain that clients send numbers through several messages, making it hard to know which pictures were finally selected. Or they may already have a gallery that handles the work comfortably. Those answers will help you decide what is worth trying.

If the photographer wants help with an upcoming session, you could offer to collect the client’s choices through an existing shared document and send the photographer one final list. The photographer and client should know that you are handling this step manually, who can see the pictures and when to expect the result.

You are not asking them to pretend an app exists. You are offering to help with the work and finding out whether the result makes their next step easier.

Choose what you want to learn

Before trying it, ask the photographer how much effort went into collecting the choices from a recent session. Then pay attention to what happens during this one: did the client send a final selection, did the photographer still need to chase them and was the list clear enough to start preparing the pictures?

If the photographer still spends time asking the client to choose, sending a better list may not address the hardest part of the work. You can ask what would have helped and use that answer to decide what to try next.

Perhaps the photographer likes the idea but does not have a session coming up. The conversation can help you understand their work, but it cannot show you what they would do when a client needs to choose. You might agree to return when that situation arises, or speak with another photographer who has a selection to collect now.

Even if one session goes well, you still need to understand whether other photographers have a similar problem and whether anyone would pay for a solution. The trial gives you a reason to continue that conversation, not a guaranteed answer.

Make the manual service workable

Running the process manually can reveal work an app would eventually need to support. Perhaps clients change their choices after sending the list, or the photographer needs to know which selection is final. You may be able to manage that with a conversation for a few sessions, but you need to be clear about who is responsible and how long a client should wait for an answer.

If the work involves private photographs or personal information, use an appropriate way to handle them and agree on access with the people involved. If you cannot provide the service responsibly, narrow the trial or wait until you have a suitable way to do it.

Decide what to do with the result

After the trial, return to the question you started with: did the photographer receive a usable list with less effort? If they did, ask whether they would want the same help for the next session and what would have to change before they could rely on it regularly. You may learn that a manual service is enough for now, or that handling changes to the selection is the first part worth building.

If the list did not help, follow the part of the work that still took time. You might try a different way to help clients make their choices before deciding that an app is the answer.

Suppose the photographer uses the list but still has to chase the client for a decision. You now know that collecting the final choices is only part of the work. Before paying to build a gallery, you can explore what would help the client choose and try that with another session.

If the trial instead makes the photographer’s work easier and they want to repeat it, you can look at what you handled manually and decide which step an app needs to support first. In both cases, the next decision comes from work you have seen rather than a feature list alone.

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 20, 2026

4 min

Filed under

Categories