Durward builds practical AI workflows around work your business already does
We design and implement focused systems for sales, service and operations. Every offer names the buyer, repeated job, source records, useful output and decisions that remain with people.
What we are, and what we're not
Durward is a specialist implementation practice, but specialism here means narrow products for defined situations, not a permanent restriction to one or two industries. The current public portfolio groups its concrete products under B2B Lead Generation, Quote & Service Recovery, Research & Evidence Workflows, and Front Desk & Enquiry Handling.
The people building this. This page does not publish founder biographies yet. When it does, real names and real backgrounds will appear here; nothing placeholder or invented in the meantime.
Before an engagement begins, its scope is written down. Where the agreed architecture permits, client accounts, subscriptions and API keys stay in the client’s name. Any referral or reseller commission is disclosed before a recommendation. The client protection page sets out the commitments in full.
Durward has not launched publicly and the company is not yet registered, which is why registration details do not appear on the site. Client work is still bounded by a written scope and designed in client-owned accounts where practical; the full approach is set out under client protection. The security and trust status we have, and what is still planned or in progress, is stated plainly rather than left implied.
We are not loyal to any vendor — we are loyal to the client’s requirements, economics, data and operational outcome. What that means in practice, from source traceability and freedom to leave to the things we will refuse to automate, is written down on the client protection page.
Human-in-the-loop on every workflow Confirmed
Confirmed by design: every automated workflow has a defined escalation and review point; no fully unattended client-facing action.
Client account ownership Confirmed
Confirmed by design: client-specific subscriptions and integrations run in the client's own accounts, never ours (product-specs/00 §4.5).
ICO registration Planned
Registration deliberately deferred until the company itself is registered.
How we think about this
Why segments and use cases lead
A fleet supplier, trade merchant and external transport manager do not buy the same outcome. The public offer starts with their actual workflow rather than hiding the difference behind a generic AI service.
Why the source stays visible
An official change, historic quote or missing document can justify review, but it cannot prove intent, urgency or a professional conclusion. We retain the source and label any inference.
Why a named person, always
The salesperson, service owner or qualified professional keeps the commercial, technical and regulated decision. The workflow prepares context and exceptions for that owner.
Why we inspect the current system first
Buying, enabling or configuring an existing product can be better than another integration. A project starts only where a real residual gap remains.
Questions about where we are
Are you still focused only on appointment-based businesses? No.
No. Front Desk & Enquiry Handling remains a core offer, alongside focused sales, revenue-recovery and operational-evidence products for other UK segments.
Why isn't there a company number or registered office here yet? Because the company has not registered yet.
Because the company has not registered yet. Registration details will appear here once that is complete; the current trust statuses are published separately rather than implied.
Do you sell one proprietary AI platform? No.
No. We compare buying, enabling, configuring, integrating and building, and recommend the smallest option that can reliably solve the named workflow.
Talk to the people doing the work
Twenty minutes, no charge, and a plain answer on whether this is a fit before anything is proposed.