Agency, Software Vendor, or System Builder?
We are not a marketing or web agency, a software vendor or a traditional consultancy. We diagnose one workflow, build a system around it, deliver it with documentation and an exit path and, if you want, operate it. We are accountable for a working system in production.
If someone forwarded you this site without much context, the first honest question is probably “what kind of company is this?”. It is a fair question, because the shape of the engagement does not map neatly onto the categories most people already have in mind. This article compares the four closest ones, and says plainly where we differ.
01. Four categories at a glance
| Agency | Software vendor | Consultancy | System builder (us) | |
|---|---|---|---|---|
| Typically paid for | Output: content, campaigns, a website | A licence to a product built for many customers | Advice, a strategy, recommendations | One workflow built, tested and handed over |
| Usually structured as | A retainer or project tied to output | A subscription or licence | A project or day rate | Three sequential engagements, fixed price against written scope |
| What you end up with | The output | Access to the product | A document | A working system in production |
| Who implements | The agency | You | Someone else | Us |
02. Not a marketing or web agency
An agency is typically engaged around output volume: content produced, campaigns run, a website designed. It is paid on a retainer or project tied to that output. We do not produce marketing output, and an engagement with us is not measured by the volume of anything produced. It is measured against acceptance criteria for a specific workflow, written down before the work starts.
03. Not a software vendor
A software vendor sells a licence to a product built for many customers, configured to your use case as far as the product allows. We do not sell a licence to a standing product. That is the most common assumption people bring to a first conversation with us, so it is worth being direct about.
What we build is specific to one workflow. You own your data, your content and the bespoke outputs built for you. We keep our frameworks, methods, reusable components and the underlying architecture. For why a licence alone rarely fixes a workflow, see a new SaaS tool won’t fix a broken workflow.
04. Not a traditional consultancy
A consultancy typically delivers advice, a strategy document or recommendations, and someone else, usually your own team or another supplier, implements them. We do not stop at the recommendation. The Diagnostic produces a decision document that you own, but the engagement continues through design, build, testing, implementation and handover if you choose to proceed, and optionally into ongoing operation afterwards.
05. What we actually are
Diagnose, build, deliver and, if you want it, operate. Every stage states what happens, what you receive and the gate where you can stop. Continuing is never automatic.
| Phase | Stages | Notes |
|---|---|---|
| Diagnose | Fit call (free), then the Workflow Diagnostic (paid) | The fit call decides whether a Diagnostic is justified |
| Build | Design specification, build and testing, implementation and training | Built and tested against written acceptance criteria |
| Deliver | Handover and acceptance, then stabilisation (included) | Documentation and an exit path are part of handover |
| Operate | Managed operations (optional) | Monthly cancellation |
Four roles carry every engagement: commercial terms, delivery, technical architecture and data protection. They are introduced to you directly during the fit call and contracting, rather than left as anonymous functions inside an organisation. The closest honest label is a delivery system builder: we are accountable for a working system in production, not for a report or a piece of software sitting on a shelf.
06. Why the distinction matters to you
It changes what you should expect from the relationship.
- You should not expect ongoing content or campaign output. That is not what is being delivered.
- You should not expect a product roadmap or feature releases. Nothing is sold as a standing product.
- You should expect a specific system, built around one workflow’s acceptance criteria, tested against them, and handed over with documentation and an exit path, whether or not you continue with us afterwards.
07. If you are briefing someone else
If you found this site and need to explain it to a colleague, the shortest accurate version is: not an agency, not a software subscription, not advice without implementation. It is a system that gets built, tested and handed over, and that can be run by us or by you afterwards.
08. Frequently asked questions
Are you a marketing or web agency?
No. We do not produce marketing output, and our work is measured against written acceptance criteria for a specific workflow, not volume of output.
Do you sell software?
No. We do not sell a licence to a standing product. We build a system around one workflow. You own your data, your content and the bespoke outputs; we keep our frameworks, methods, reusable components and underlying architecture.
Are you a consultancy?
Not a traditional one. The Diagnostic produces a decision document, but we also design, build, test, implement and hand over the system, and optionally operate it.
What does an engagement look like?
A free fit call about one workflow, then a paid Diagnostic, design, build and testing, implementation and training, handover and acceptance, stabilisation, and optional managed operations. You decide at each stage whether to continue.
Do I have to keep working with you after handover?
No. Handover includes documentation and an exit path, and managed operations is optional with monthly cancellation.
09. Next step
See the eight stages, from the free fit call to handover. How it works →
