We Built a Tool to Find a Business. It Turned Out to Be the Business.

Together with my partners, I was working through a set of business opportunities. Not one idea pursued to the end, but several, evaluated deliberately, one after another, to find out which of them had a real market behind it.

That is where every test slowed down.

We moved between LinkedIn, company websites, event pages, news articles, job postings and spreadsheets. We collected information, verified it, cleaned lists and tried to work out which companies were genuinely relevant.

The problem was not a lack of information

The problem was turning all that information into a useful answer:

Who should we speak to, why should we speak to them and why now?

Every idea we wanted to evaluate ran into the same wall before we could evaluate it. So we built the thing that would let us get past it. Software that could identify relevant sales signals, research and qualify potential leads, and reduce the repetitive work behind prospecting, while keeping people in control of the final decisions.

At that point it was not a product. It was infrastructure. It existed so that we could do the actual work of testing ideas.

Then the test returned an answer we had not expected

We did eventually reach a conclusion about which opportunity to pursue.

It was not on the list.

Of everything we were evaluating, the tool we had built to run the evaluation was the easiest thing to sell.

It generally means the buyer recognises the problem before you have finished describing it. You are not funding an education campaign. You are not explaining why the problem is worth attention, because the person across the table has already lived it, already built a workaround for it, and is quietly relieved that someone has taken it seriously.

So we stopped treating Signalist as internal tooling and started treating it as the product.

The most reliable signal was not enthusiasm for an idea.

It was how little explaining the idea required.

The best product ideas often begin inside the company

The experience reinforced something I had already seen repeatedly in software development:

Some of the best product ideas begin as internal operational problems.

Important knowledge is stored in spreadsheets, documents or the minds of a few experienced employees.

Employees create workarounds because the available software does not reflect how the company actually works.

But as the company grows, the workaround becomes part of the operating model.

At that point, the company does not necessarily need another general-purpose tool. It may need software designed around its own process.

And occasionally, which is the part worth paying attention to, that software turns out to be valuable to people outside the company as well.

We did not start by asking which category of software we wanted to enter. We started by building what we needed in order to work at all. The product came later, and it came from the tooling rather than from any of the ideas the tooling had been built to test.

Winning more clients is only one side of growth

But winning more clients does not automatically create a stronger business.

In fact, growth often exposes operational weaknesses that were less visible when the company was smaller.

A business may successfully generate demand but struggle to deliver its work efficiently. Each new client creates more spreadsheets, more reports, more coordination and greater dependence on individual employees.

This is especially common in consulting and professional services.

Many consultancies possess highly valuable specialist knowledge. They have developed methodologies, assessment models, processes and frameworks through years of client work.

But that knowledge is often delivered almost entirely through consultant hours. It remains inside workshops, presentations, questionnaires, spreadsheets and manually produced reports.

As a result, growing the business usually means adding more people. More clients require more consultants. More projects require more manual delivery. Revenue remains closely connected to available working hours.

This is where the connection between Signalist and Browserbite becomes clear.

One helps create opportunities.

The other helps companies scale what they deliver.

Two companies, two kinds of friction

Signalist and Browserbite are different companies solving different problems.

Signalist focuses on the process of identifying, researching and qualifying relevant B2B opportunities. It uses sales signals, automation and AI to reduce the manual effort behind lead generation and outreach preparation.

Browserbite works with consultancies that want to turn their specialist methodology into software under their own brand.

Signalist therefore addresses friction before a client relationship begins.

Browserbite addresses friction in the way specialist expertise is packaged, delivered and scaled.

One can help a company find the right opportunities. The other can help a consultancy build a more scalable way to serve them.

Software should strengthen expertise, not replace it

It is easy to misunderstand the purpose of automation. The objective is not to automate everything simply because the technology exists.

In sales, software can identify signals, organise information and support research. But a person still needs to understand the context, evaluate the opportunity and communicate with relevance.

In consulting, software can structure assessments, collect evidence, guide workflows and generate consistent outputs. But it does not replace specialist judgment, client understanding or strategic advice.

Good software removes the parts of a process that do not require the full attention of an expert.

It gives experts more time for the parts that do.

The starting point should never be:

Where can we add AI?

It should be:

Where is unnecessary friction preventing our people from doing their best work?

Technology comes after that question.

Your internal process may already contain a product

Consulting firms often think of their methodology as something they use to deliver a service.

But in some cases, that methodology can become more than an internal process. It can become a client-facing product.

Consider a consultancy that repeatedly conducts the same type of assessment. Its consultants ask similar questions, collect similar evidence, apply the same specialist logic and prepare a similar structure of recommendations for every client.

The expertise is valuable. The process is proven. Clients already pay for the outcome.

But the delivery remains almost entirely manual.

Turning the appropriate parts of that methodology into software can create several advantages. Clients receive a clearer and more consistent experience. Consultants spend less time on administration and repetitive preparation.

The consultancy can support more organisations without increasing its team at the same rate. The software can continue supporting clients after the initial project has ended.

And because the product carries the consultancy's own methodology and brand, it becomes considerably more difficult for competitors to reproduce.

This is not simply internal optimisation. It is productisation.

It can create stronger differentiation, longer client relationships and more predictable revenue.

Not every process should become software

Building Signalist also strengthened my belief that companies should not develop software simply because they can.

A frustrating process does not automatically justify a custom product.

Sometimes the right answer is to simplify the process. Sometimes an existing tool is sufficient. Sometimes the problem is unclear ownership rather than missing technology. And sometimes the potential value does not justify the cost and complexity of development.

A responsible technology partner should be willing to recommend not building when the business case is weak.

The goal is not to produce more software.

The goal is to solve the right problem.

Growth begins by removing the right constraints

When companies want to grow, they naturally look outward. They search for new clients, new markets, new channels and new partnerships.

That is necessary.

But growth is also shaped by what happens inside the company.

A business cannot scale sustainably when every new opportunity creates a disproportionate amount of manual work. A consultancy cannot fully benefit from increased demand when its most valuable knowledge remains difficult to reuse. A sales team cannot build meaningful relationships when most of its time is spent collecting and cleaning information.

The answer is not always to hire more people or work longer hours.

Sometimes the next stage of growth begins by redesigning the process. Sometimes it begins by turning that process into software.

Signalist began as the tool that allowed us to look for a business. It became the business. That is not a story about brilliant foresight. It is a story about building the thing you actually need in order to work, and then paying close attention to what the market does with it.

The most valuable software opportunity inside a company is not always a completely new idea. It may already exist in the work the company repeats, the knowledge it has developed and the problem its employees have quietly learned to tolerate.

So the question is not only which recurring part of your business could become a product.

It is also this:

Which of the tools you built for yourselves would somebody else pay for?

Andreas Wawer
CEO, Browserbite
Co-Founder & CTO, Signalist