Skip to content
AIMAI

Our thinking

Why we built our own business software

We used Asana for years, then moved Everpro into a project and client system we built ourselves. Here is the assumption that decision challenged, and the questions it raises.

Jonathan BradleyPublished

We used Asana for years. Then we built our own project and client system and moved the whole of Everpro into it.

A few years ago, I would have questioned the sense of that. There are hundreds of perfectly good systems already. Why take on the work of building another one?

An assumption worth revisiting

For a long time, bespoke software felt like a decision for a larger business with a substantial budget and the patience for a long development project.

Most smaller businesses bought something established and worked out how to make it fit. That was often a sensible decision. It still can be.

What has changed is the effort involved in designing and developing software. AI-assisted development has made it possible to explore a different approach: start with the way the business needs to work, then shape an application around it.

That opens up a choice which previously might not have felt worth considering.

Our decision at Everpro was to try that choice for ourselves. The result was our own project and client system, replacing the tool we had used for years.

The question is bigger than the software

I would be careful about treating that as an argument for rebuilding every application a business uses.

A familiar tool can have a great deal going for it. People know how to use it. It has established features and a team maintaining it. Replacing it creates work of its own.

The useful starting point is the work the business needs to do.

Where does the current system fit well? Where are people working around it? Is information being copied between places? Does a process depend on someone remembering a step that the system does not handle?

Those are useful questions whether the answer turns out to be better use of an existing product, a connection between systems or something custom.

A different interface is not much of a reason to build. A worthwhile improvement to how the business operates can be.

Building it is only part of the decision

The ability to create an application quickly makes it tempting to focus on the first working version. Seeing your own idea on a screen is exciting.

Then it has to become something people can depend on.

Who should be able to see or change each record? What happens when information is missing or wrong? How will it connect with the other systems the team uses? Who takes responsibility for problems, changes and ongoing support?

There is also the everyday reality of introducing it. People need to understand how the work moves through the system and what they should do when something unusual happens.

Those questions do not disappear because development becomes faster. They become part of deciding whether the application is ready to use.

A working system has to earn its place

The test of a custom application is what happens in normal use.

Can the team follow the work? Is the right information available when somebody needs it? Are important steps being handled consistently? Can the system adapt as the business changes?

That is where the value has to show up. A convincing demonstration is a useful start, but it is only a start.

The same standard applies to an established product. Being custom does not make software better by itself. Its value comes from how well it supports the people and the work.

The choice has changed

I would not take our decision at Everpro as a recommendation that every business should replace Asana.

I would take it as a reason to question the old assumption that software built around your business is automatically out of reach.

Buying a product, improving what you already have, connecting existing systems and building something new are all options worth considering. The right choice depends on the problem and the responsibility involved in keeping the solution useful.

For us, that meant saying goodbye to Asana.

For another business, it might mean keeping most of its systems and creating one application that joins an important workflow together.

The interesting part is being able to start with the business and consider the possibilities.