Company

We engineer clarity into complexity.

ANOVA PROJECTS exists to solve business problems that cost time, money, customers or unnecessary stress — by understanding how a business creates value, finding the friction around it, and building something practical that improves it.

Purpose

Every business has one activity that actually creates value.

A salon delivers a service people come back for. An agency gets attention for its clients. A studio helps people feel better.

Everything else — the admin, the repeated messages, the disconnected tools, the enquiries that quietly go cold, the not-quite-knowing how the month is going — is work that surrounds the valuable part without adding to it.

We reduce that surrounding work first. It is usually the cheapest thing to fix and the fastest thing to feel. Once it is gone, the core of the business can be improved, scaled, delegated or sold more effectively — and that is where the larger money is.

Which technology gets used to do it is our problem, not yours. AI, automation, software, a website, a better process: whatever the situation actually calls for. The technology is not the product. The business outcome is.

The company in one paragraph

We find problems that cost businesses money, time or customers, and build digital systems to solve them. Using AI, automation, software and growth systems, we help companies grow, operate more efficiently, and build better infrastructure around the work that actually creates value.

Principles

How we prefer to work.

Diagnose before prescribing

The solution a client asks for and the problem they have are often different things. We look for the bottleneck first, even when it makes the project smaller.

The simplest thing that works

Impressive systems that nobody uses are a failure. We build the smallest version that changes something real, put it in front of people, and grow it from there.

Plain language

You should never have to nod along to a word you do not know. If we cannot explain what something does and why it is worth paying for, it probably is not.

Measure, then say so

We agree what should change before building, and check afterwards. If it did not work, you hear that from us first.

You own what we build

Your data, your accounts, your system. We are happy to keep running it because it is genuinely easier for you — not because you are locked in.

Then find the next bottleneck

One solved problem tends to reveal the next one. Good clients keep going for years precisely because each step pays for the following one.

Delivery process

Seven steps, every time.

The same framework runs behind every project, whatever is being built. It is what lets you always know where things stand — and what lets us hand work to other people without the quality changing.

  1. 01

    Understand

    How the business makes money, who the customers are, what the goal is this year, and what is genuinely in the way.

  2. 02

    Diagnose

    Find the actual bottleneck rather than accepting the first proposed solution. This is where projects get smaller and better.

  3. 03

    Design

    Specify the simplest system that meaningfully solves it — what it does, what it will not do, what it costs, and how we will know it worked.

  4. 04

    Build

    Implement it with whichever technology fits the problem. You see progress rather than silence.

  5. 05

    Launch

    Put it into the real workflow with the people who have to use it, and stay close while it settles in.

  6. 06

    Measure

    Check whether the expected result is happening. The uncomfortable version of this step is the one that makes the next step worth anything.

  7. 07

    Improve

    Optimise what exists, then identify the next thing worth fixing. Most relationships continue here.

Working together

You describe the problem. We work out the answer.

You should not have to know whether your situation needs an integration, an automation, an application or a better landing page.

That is the relationship we are built for: you describe what is not working, we investigate it, we propose something specific, and then we build it. Early on we will explain more than strictly necessary, because trust is built by understanding. Over time, most clients simply say what they want to be true and let us handle the rest.

  1. 1

    You describe the problem

    In your own words. Symptoms are fine — "we keep losing enquiries" is a perfect brief.

  2. 2

    We investigate

    We ask about how the business runs and look for where the money and time are going.

  3. 3

    We propose something specific

    What we would build, what it should change, what it costs. Including when the answer is "not much".

  4. 4

    We implement it

    And keep it running, if that is genuinely more useful to you than handing over the keys.

Clarity at the start. Certainty at the finish.

ANOVA principle

From the founder

ANOVA PROJECTS started from a simple observation: most small and mid-sized businesses are not held back by a lack of tools. They are held back by tools that do not fit, work nobody should be doing by hand, and information that is hard to reach at the moment it matters.

I would rather build a company that solves that properly than sell whichever technology happens to be fashionable. That means saying no to work we should not take, being honest about what we have proven so far, and building systems we would be happy to inherit.

Michael — Founder, ANOVA PROJECTS

Direction

Where the company is going.

We would rather tell you this openly than imply we are further along than we are.

NOW

Real projects, real clients

Concrete work we can already deliver well: growth systems, automation, AI setups, websites and small business tools. Early clients get disproportionate attention.

NEXT

Systems that keep working

Hosting, monitoring, maintenance and continuous improvement — relationships that continue because the system keeps earning its place, not because of a contract.

LATER

The operating layer

Larger integrated business systems: one place a company can see and run itself from. Everything we build now is designed to become part of that.

What would you like your business to do better?

Describe it in your own words — the symptom is enough. Working out what it actually needs is our job, and the first conversation costs nothing.