If someone forwarded you this site without much context, the first honest question is probably “what kind of company is this, actually?” It is a fair question, because the shape of the engagement does not map cleanly onto the categories most people already have in their head.

01. Not a marketing or web agency

An agency is typically engaged around output volume — content produced, campaigns run, a website designed — and paid on a retainer or project basis tied to that output. We do not produce marketing output, and a Motive Journey engagement is not measured by volume of anything produced. It is measured against acceptance criteria for a specific workflow, written down before the work starts.

02. 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 — a point worth making on its own, because it is the single most common assumption people bring to a first conversation with us. What we build is specific to one workflow, owned by you at the end rather than rented indefinitely.

03. Not a traditional consultancy, either

A consultancy typically delivers advice, a strategy document, or a set of recommendations, and someone else — usually your own team, or another vendor — implements them. We do not stop at the recommendation. The Diagnostic produces a decision document, but the engagement continues through design, build, testing, implementation and handover if you choose to proceed, and optionally into ongoing operation afterwards.

04. What we actually are

Diagnose, build, deliver, and — if you want it — operate. Four roles carry every engagement: commercial terms, delivery, technical architecture, and data protection, introduced to you directly during fit 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.

05. Why the distinction actually matters to you

It changes what you should expect from the relationship. You should not expect ongoing content or campaign output, because that is not what is being delivered. You should not expect a product roadmap or feature releases, because nothing is being sold as a standing product. You should expect a specific system, built around one workflow’s acceptance criteria, tested against those criteria, and handed over with documentation and an exit path — whether or not you continue with us afterwards.

06. How to use this if you are briefing someone else

If you are the person who 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 — a system that gets built, tested, handed over, and can be run by us or by you afterwards.

See the eight stages this actually runs through, from the free fit call to handover — how it works →