First conversation
Thirty minutes on the problem, not a pitch. If we are not the right people for it, we say so and point you elsewhere.

Company
Every engagement starts with diagnosis rather than a proposal. We spend the first two weeks establishing which constraint is actually binding, because fixing the wrong one is the expensive mistake, and you keep those findings whether or not you continue with us.
What that means in practice
Why this order
A proposal is written before anyone understands the problem, work is delivered against that proposal, and six months later the commercial result has not moved because the original diagnosis was wrong. The work was done competently; it was simply the wrong work.
We run it in the other order. Diagnosis first, scoped proposal second. That means our first deliverable is usually a document telling you what is broken, including the parts we are not the right people to fix.
Process
Five stages. The first two are the ones most suppliers skip, and the reason most engagements miss.
Thirty minutes on the problem, not a pitch. If we are not the right people for it, we say so and point you elsewhere.
We establish what is actually wrong before proposing work. You keep the findings whether or not you continue.
What we will do, what we will not do, what it costs and how long it takes. Boundaries stated in writing.
Regular checkpoints against agreed commercial measures: enquiries, response times, hours removed. Not activity reports.
Documentation and training so your team can run what we built. Intellectual property is yours from day one.
Applied
The order does not change with the discipline. What changes is what the diagnosis is looking at.
We audit the current position: technical health, visibility, conversion, and where the process actually loses time. The output is a document telling you what is broken, including the parts we are not the right people to fix. You keep it either way.
Both, depending on the work. Search and automation programmes suit a retainer because they compound; a website build or a software project suits a defined scope. We will tell you which fits rather than defaulting to whichever is more profitable for us.
Then that is what the document says. It has happened, and it is a better outcome than six months of work against the wrong constraint.
The order above does not change with the discipline — what changes is what the diagnosis is looking at. Tell us what is not working and we will tell you which layer we would examine first.