You accept the scope
USD 500, fixed. 50% now, 50% on delivery. Fixed date, written scope, no discovery call needed to start.
Every finding cites what I read. Every item is ranked by hours recovered and priced in money. It ends in a build plan, or a written reason there is not one, which is a real answer and happens.
50% on acceptance, 50% on delivery. Fixed scope, fixed date, no retainer required. If it says do not build, you keep the rest.
Written and asynchronous, because you are probably in a different timezone and a status call is not work.
USD 500, fixed. 50% now, 50% on delivery. Fixed date, written scope, no discovery call needed to start.
Site, funnel, inbox, repo, whatever the scope names. Nothing is changed, nothing is sent, nothing is installed.
A ranked list of where the hours go, each finding citing what I read, each item priced in hours and money.
Build it yourself, take the sprint, or stop. A written 'do not build this' is a valid deliverable and it costs you nothing further.
The sprint is only offered after an audit, because building the wrong module fast is the most expensive way to be wrong.
Where the hours actually go, ranked, with the evidence attached. Ends in a map of the modules your business needs, or a written 'do not build this'.
The top modules from the audit, built, gated and shipped. You get the working thing, the procedure that drives it, and a wiki so it runs without me.
The systems we built stay running: monitoring, fixes and small changes. Nothing new, because a new build is a sprint. Capped hours, so it stays infrastructure and not a job.
The rest is on the main FAQ.
Fixed scope, fixed date, half now and half on delivery.
Not ready for the whole workflow? is credited against the audit if you go ahead.