Process and collaboration
What happens in which order, who owns what and when you take over — the process, before the first meeting takes place.
An AI project at Davies Meyer runs in four phases: assessment, prioritisation with a business case, a pilot taken into production, and finally scaling with handover to your team. On your side it needs one subject-matter contact, one decision-maker for approvals and, depending on scope, IT-side access to systems and data. The first dependable results appear in the pilot, not in the concept phase.
Our approach: creative engineering
We work neither as tool consultancy nor as a classic production agency, but in between: creative engineering means building the production chain behind the creative work — templates, generative modules, checkable brand rules and delivery as one system. The creative judgement stays with the team, the multiplication becomes an engineering task.
The concept stays human
Idea, visual language and tone are created as before. What follows is what gets automated: variants, formats, language versions, delivery.
Brand rules the machine can check
Colour, typography, logo usage, forbidden claims — stored as rules that apply automatically before approval instead of sitting in a PDF guideline.
Production as a chain, not a tool
Template, generative module, validation step, approval and delivery interlock. A single tool without that chain only moves the manual work elsewhere.
Impact measurable at creative level
We evaluate not only the campaign but the individual attribute: hook, composition, colour world, length. That feeds the next production round.
What we take on
Roles on both sides
At project start we name the contact, decision-maker and technical contacts on both sides in writing. Unclear responsibilities are the most common cause of delay — not technology.
Approvals and quality assurance
For every automated step we define whether it runs fully automatically, is sampled, or always requires sign-off. These levels are fixed before implementation and can be adjusted later.
Documentation and handover
Every engagement ends with documentation, a runbook and training. The goal is that your team can take over operations — continued operation by us stays an option, not a prerequisite.
Communication during the project
A fixed weekly meeting, one shared channel for quick questions and a written status listing open decisions. No status decks that take longer to build than to discuss.
How the engagement runs
- 01
Assessment
We review your processes, data situation and existing stack, and document where AI realistically creates impact today — and where it does not.
- 02
Prioritisation & business case
Use cases are ranked by effort, impact and risk. Every candidate gets a transparent calculation instead of a gut estimate.
- 03
Pilot in production
We build the first use case all the way into real operations — including system integration, approval flow and measurement points.
- 04
Scaling & enablement
What works gets rolled out and handed over: playbooks, training and governance, so you do not stay dependent on us.
Frequently asked questions
30 minutes, a concrete assessment
Describe your use case briefly — we will say plainly whether and how it pays off.