How a fractional AI and technology engagement works.
Indicative schedule for Lead + delivery. Access, data quality and integration complexity set the agreed timeline, and you approve the scope before any work starts.
The 30-minute conversation
You describe one expensive recurring workflow. We ask what it costs, who touches it and what has been tried. If there is no credible case, we say so.
A written scope
If there is a case, you get a short scope: the problem, the baseline we will measure, acceptance criteria, what is out of scope, the plan and the price.
Days 1–30: Diagnose
We map the workflow with the people who do it, measure the baseline, rank opportunities and agree one pilot with acceptance criteria.
Days 31–60: Deliver
We build and test the improvement with real examples, starting with tools you already own. Your team reviews outputs before anything goes live.
Days 61–90: Measure
We support adoption, compare results with the baseline and recommend what deserves investment next, including whether to stop.
After day 90
Continue with the next priority, change plans, step down to Advisory or stop. You keep everything we built and documented.
From sales call to a reviewed proposal.
Approved tools prepare the draft from structured inputs. A person reviews scope and price before it is sent. We measure three things before and after.
Staff minutes per proposal
Timed on real proposals, before and after.
Turnaround
Hours from the sales call to the proposal sent.
Correction rate
How often the reviewer changes the draft, tracked weekly.
Bring one expensive workflow. Leave with a clear next step.
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.