Our approach
We don't start with what to build. We start with what matters.
Our approach connects business understanding with practical implementation. Before recommending a system, we seek to understand the objective, examine the current process and establish what a successful improvement would actually mean.
The framework
Understanding is part of the work.
Four connected stages describe how we intend to join commercial reasoning with delivery. The depth of each stage, its outputs and its review points are agreed for the particular engagement.
What is happening, and why does it matter?
Stage 01: Understand & Diagnose
Start with the business objective. Map the current process, the people involved and the points where an enquiry, decision or handoff becomes difficult. Examine available records, recurring questions and previous attempts to improve the situation. Discuss the consequences of leaving it unchanged, identifying estimates as estimates.
A client's account, an observed fact and an explanation we want to test are different kinds of information. Keep them separate. Where evidence is missing, record the gap and agree what would help resolve it before recommending an intervention.
- Potential output
- A documented understanding of the agreed problem, relevant constraints and evidence gaps.
- Decision point
- Confirm the objective and what is known. Decide whether there is enough evidence to recommend work or whether further investigation is needed.
What is justified, and what will it take to deliver?
Stage 02: Design & Implement
Choose an intervention that fits the problem and our capabilities. It might be a website, a digital showroom, a clearer enquiry process or an improvement to an existing workflow. Consider how it will fit the people, information and tools already in use.
Before production, agree the scope, exclusions, responsibilities, technical requirements, milestones, payment terms and acceptance criteria. Use working previews and relevant tests to review the implementation. Changes to scope need an agreed effect on cost and timing before additional work begins.
- Potential output
- A tested deliverable addressing the agreed scope, with the documentation and access needed for its handover.
- Decision point
- Review against the agreed criteria. Record approval, resolve in-scope issues and confirm the payment and launch conditions before going live.
What changed, and what can the evidence support?
Stage 03: Measure & Evaluate
Define success before describing something as an improvement. Where measurement is appropriate and agreed, establish the indicator, its definition, the source and the observation period. A qualified enquiry, a substantive reply, an attended inspection and a completed process each tell a different story.
Use a baseline where one exists and report its limits. Changes in stock, pricing, campaigns, seasonality or staff availability may also affect the result. A contact-button click does not establish a sale. When evidence is qualitative, client-reported or insufficient, identify it clearly.
- Potential output
- An evidence-based assessment of the agreed outcomes, including what remains uncertain or has not been measured.
- Decision point
- Review the evidence together. Separate observed changes from assumptions about their cause before deciding what deserves attention next.
Is another intervention worth making?
Stage 04: Improve & Evolve
Use what has been learned to decide whether further work is justified. Prioritise an opportunity by its likely value, evidence, effort and operational demands. A useful next step may be a small adjustment, a separate project or allowing more time to observe the existing change.
Some engagements end with a complete handover. Others may warrant continued support or a focused round of improvement, agreed separately. Confirm ownership, access, responsibilities and any support limits so the client understands how to operate the system after delivery.
- Potential output
- A prioritised, commercially justified next step where needed, or a clear handover when the agreed work is complete.
- Decision point
- Choose whether to hand over, observe or commission further work. Ongoing support is an option, not a condition of a successful engagement.
The decision criteria
A recommendation has to earn its place.
These are the questions we intend to hold a recommendation against. A proposal should explain the reason to act as clearly as the work itself.
A problem the client recognises.
Management agrees that the issue occurs and deserves attention. An interesting technical possibility alone is not a reason to begin a project.
Commercially meaningful value.
The likely benefit should justify the cost, time and disruption involved. Where that value is uncertain, make the uncertainty part of the decision.
A proportionate solution.
Consider a process adjustment, clearer information and better use of existing tools alongside new software. The complexity needs a business reason.
A feasible implementation.
Technical feasibility sits alongside staff capacity, content, access, maintenance and ownership. The business needs to be able to use what is delivered.
An appropriate standard of evaluation.
Agree what can be observed, over which period and with what limitations. The available evidence should support the claims made about the work.
The competence to deliver.
Check that the agreed work fits our capabilities and capacity. Identify where specialist advice or a different provider is needed before committing.
Professional discipline
Clear standards. Credible promises.
Confidence in the work begins with being precise about what we can take responsibility for.
- Honest commercial expectations
- Agree the objective and the work we can take responsibility for. Arbitrary percentage increases in sales are not something we guarantee.
- Technology with a reason
- A new system needs to serve the agreed problem. Technical novelty is not, on its own, a recommendation.
- Clear professional boundaries
- We do not claim expertise in every part of a company. Questions beyond our remit need the appropriate specialist.
- A handover that stands on its own
- Clarify ownership and ongoing responsibilities. A clean handover is a valid endpoint; a long-term retainer is not compulsory.
- Evidence before claims
- Distinguish observations, client reports and working assumptions. A proposed benefit becomes a reported result only when evidence supports it.
How clients work with us
A clear route from conversation to handover.
The agreement makes the work concrete. Scope, dates, review responsibilities, payment terms and support are established for the engagement.
Initial conversation
Describe the business objective, the current situation and the change you are considering. Establish whether there is a useful conversation to continue.
Qualification
Clarify the problem, decision-maker, fit, likely budget, timing and practical constraints before committing to custom work.
Agreed scope
Set the proposed boundaries: what is included, what is excluded, the dependencies and how the work will be reviewed.
Proposal
Document fees, responsibilities, milestones and payment terms. Production begins after written agreement, the agreed initial payment and the necessary inputs.
Implementation
Work through the agreed milestones with previews, concise progress updates and review points. Record decisions and agree scope changes in writing.
Acceptance
Check the deliverable against the agreed criteria, record approval and complete the payment and handover arrangements. Distinguish an in-scope fix from a new request.
Optional further improvement
Use the available evidence to decide whether separate support or another focused intervention makes sense. The engagement can also end with handover.
Separately agreed, where justified
The value of learning
A method that should get better with the work.
We are building the habit of documenting the problem, the alternatives considered, the reasons for a decision and what the evidence later shows. The aim is to improve our judgement and delivery methods as experience accumulates.
Over time, we want that discipline to become institutional knowledge: practical lessons that help us recognise recurring problems and make better decisions in future engagements. That expertise has to be earned through the work.
Client information stays private. Public names, screenshots and outcome claims require separate permission. Learning from an engagement should respect those boundaries.
Explore the thinking in context
See where we fitWhat we examine
Recognise the friction.
Explore the commercial questions that can sit behind a request for a new website or system.
What we can implement
Explore our capabilities.
See how websites, digital experiences and practical systems can support an agreed objective.
How we document the work
Read the context.
Look at selected work and clearly labelled studies, with their decisions, status and limitations.
Begin with the objective
The objective comes first. The solution follows.
Tell us what your business is trying to improve, how the process works today and where the uncertainty lies. That is a useful place to start.