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

Should You Fix Your App or Start Again?

Compare what a repair and a new version will deliver before committing more money to your app.

João Dezembro · 5 min

More in Business

You paid to build your app, but it is not doing what your business needs. When you ask for help, one person says it can be fixed and another says you should start again. Both options mean spending more, and it can be difficult to know which advice to trust.

Before choosing a direction, I would want to understand what is going wrong and whether the parts the app depends on can support what the business needs. Once someone has looked at the app, you can compare the work needed to get from where it is today to a result your customers can use.

What do you need the app to do?

Start with the task your customers or your team cannot complete. Show the team what happens now and explain what you need to happen instead. You do not have to know what caused the problem, but the people proposing the work should be able to explain what they find in a way you can follow.

Imagine a customer uses your app to request a service and then tries to pay, but the payment fails. The customer needs to know whether the request went through, and your team needs to know whether it has been paid. A useful first step is to follow that request through the app and see what was saved, what happened to the payment and where the process stopped.

When could you fix the app?

Suppose the request and customer details are saved correctly, and the team finds that the payment problem can be corrected without changing the rest of the app. In that situation, fixing the affected part may be enough. Ask the team to explain what it would change and how it would check the full request and payment process afterward.

I would also want to understand whether the parts underneath that process can be relied on. Can the app keep the information the business needs, make it available to the right people and support the changes you need to make? If those things work and the problem is contained, there may be a lot you can keep. A screen that looks right on its own does not answer those questions, so ask the team what it checked.

When could starting again make sense?

Now imagine the same app was built for one business, but you need several businesses to use it, each with its own customers and private information. The team may find that supporting this safely requires changes to parts of the app that many other features depend on. It may also find a way to adapt what is already there.

If someone recommends starting again, ask them to explain why changing the existing app would not be a reasonable way to meet that need. You should understand what would need to be rebuilt, what could still be kept and how the work would compare with changing the current product. Starting again can make sense when the necessary changes are extensive, but the recommendation should be based on what the team found in your app.

There may also be a way to keep some parts and change others. Perhaps the team can replace the part that manages access while keeping the screens or information that already work. Ask what that approach would deliver and what would still need attention afterward, especially if the first stage solves only the most urgent problem.

How do you compare the proposals?

Once you understand the options, give each team the same result to work toward. If one proposal gets customers through the request and payment process while another includes a wider set of changes, the prices are covering different work. Ask what each team will keep, what it will change and what customers or your staff will be able to do when it is finished.

You also need to know how much more you will pay, how long the work will take and what is not included. If nobody has examined the app yet, a team may need a limited review before it can answer. Agree on what that review will cover, what you will receive and whether you are committing to any further work afterward.

If customers already use the app, include them in that comparison. They may have accounts, subscriptions or information they expect to find when they return, so ask who will keep the current app running while the work is underway. If information needs to move to a new version, find out whether that work is included and how the team will check that customers can still access what they need.

There may also be screens, account settings or working features worth keeping if you have not launched yet. In either case, make sure the proposal explains what happens to the parts you are relying on while the changes are made.

You have already paid to build the app, and it is understandable to want that work to count. The decision in front of you is what the next investment will deliver. Once the team can explain what it found and what each option involves, you can choose the work that gets your business to the result it needs, whether that means a repair, a change to part of the app or a new version.

If an important question is still unanswered, agree on how it will be investigated before committing to a larger project. You should know what the next stage is meant to solve and what, if anything, it will leave for later.

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

5 min

Filed under

Categories