Agencies that build AI automations, RAG systems, and agent workflows usually do not lose margin because the first demo was hard.
They lose margin earlier:
The expensive part is not always implementation. Sometimes it is realizing, too late, that the project should have been narrowed before anyone touched the build.
Before an AI automation or RAG build starts, I like to reduce the scope to four written questions.
Not the whole product. Not the full system. The first paid milestone.
A good milestone has:
If a team cannot describe that milestone in plain language, implementation will probably absorb the ambiguity. AI projects often fail because the team only lists what should be automated.
For scoping, the more useful question is: What should not be automated yet?
Examples:
This is not anti-automation. It is how a workflow becomes shippable.
For RAG projects, weak source readiness shows up as model problems later. Before building, check whether the source set has:
If the documents are not ready, the correct first milestone may be source cleanup, not retrieval. Some failure modes are tolerable. Some change the delivery plan.
Examples that should affect scope:
Those are not reasons to reject every project. They are reasons to price, sequence, or narrow it differently.
For agencies, a useful second pass can stay small: It does not need calls, production access, or client credentials. A redacted brief is usually enough to catch the big mistakes before a team commits build time.
I put together a page for this exact use case:
https://mindtrovertlabs-sketch.github.io/scopegrade-storefront/agency-partner-review.html There is also a free preview of the checklist style here:
https://mindtrovertlabs-sketch.github.io/scopegrade-storefront/preview.html The main point: AI agencies do not need more enthusiasm in the scoping stage. They need a written way to decide what is safe to fund first.