An engagement is a promise about time. Executives told us what the last promise cost them: six months of many people’s time to verify what the team already knew, and a deck built to get a project approved. So the first question is rarely the price. It is the shape — what lands in writing, in what order, and when.
Scope, Phases & Duration
What Does an AI Consulting Engagement
Actually Look Like?
The two movements buyers accept, where the money lands phase by phase, and the point at which the numbers are still a range.
Built from real buyer questions in our sales meetings
Direct Answer
Short, output-first, and scoped before the invoice. The shape buyers accept has two movements: a structured discovery that produces written deliverables, then an implementation phase built against them, with a stated time to a real outcome instead of an open-ended retainer. The discovery output — architecture, cost model, project charter — is what the build is priced and staffed from.
The limit: what discovery produces is directional. Iternal says so plainly. The cost scoping is never definitive: it returns a range at low, medium and high, so it scopes rather than quotes, and delivery partners are expected to adjust or remove those figures. Iternal also states it may have little to nothing to contribute to some of the deployment plans its own discovery recommends. Treat the deliverables as a scoped starting point that still has to be priced and staffed, not a fixed-price statement of work.
Read the two eight-week clocks separately. Iternal’s own figures run four to eight weeks to a production-ready pilot, to tangible value, or to a production-scale deployment, and six to eight weeks from first call to a production version of a smaller use case — or to a production-ready scalable solution once you supply sample data. Weeks instead of months is the target it sets, and the shortest numbers are goals. Six to eight weeks is also what a consulting firm would take to write the comparable strategy: the baseline being replaced, not a delivery commitment. Ask for your own dates in writing.
Discovery and implementation are bought differently. The exploratory session carries no charge, the detailed deliverables are the paid step, and the build is scoped from the charter. For more information on picking which problem goes first, visit the choosing your first use case page. For more information on running the work without AI specialists, visit the starting without in-house AI skills page.
Two Different Clocks Both Called Eight Weeks
The same number describes two opposite things. One eight-week figure measures what a consulting firm would take to write an AI strategy; the other measures Iternal reaching an outcome. Unlabeled, the first flatters the second:
| What the figure measures | Stated as | How to read it |
|---|---|---|
| The consulting baseline — a consulting firm producing the equivalent written deliverable | six to eight weeks | A claim about your alternative. It belongs in a business case, never a schedule. |
| First call to a working use case — a production version of a smaller use case, or a production-ready scalable solution once sample data is supplied | six to eight weeks | Iternal’s own figure. One version starts at the first call, another when your data lands. |
| Pilot, value or scale — a production-ready pilot, tangible value, or a production-scale deployment | four to eight weeks | Iternal’s own figure, stated with hedging. Plan on the upper bound. |
| The stated ambition — the time to value Iternal aims for | weeks instead of months | A goal the company sets itself, not a number to sign against. |
The spread is a spread on purpose. Four weeks and eight weeks describe different use cases, different data, and different amounts of your own people’s attention. Neither end is a schedule until somebody writes dates down.
Pin it down: questions for your evaluation
-
Which outcome does the clock stop on for our use case: a working pilot, a production deployment, or the written plan?Whether a published timeline and your definition of done describe the same finish line.
-
What dated schedule will you commit to in writing once we supply sample data and name our stakeholders?Turns a published range into dates, and names who owns a slip.
Nobody Funds an Advisory Step Before They See Something
Buyers said it bluntly. Asking ownership for a large sum for AI without showing what it does is not a good answer, and not everybody will invest an hour up front without seeing something first.
The structure answers the objection instead of arguing with it. The exploratory session carries no charge and returns output before anything is invoiced; the detailed session is the paid step, producing the architecture, the cost model and the charter. Iternal also runs the sequence backwards when it should — a company that can already articulate its problem skips the exploration entirely, because paying to be walked to a decision you have already made is the waste buyers were objecting to.
Where the Money Lands, Phase by Phase
An engagement is easiest to judge when you can see what each phase asks of you and what it hands back. Iternal argues for a staged rollout, not a day-one transformation:
| Phase | What it needs from you | What you get | What ends it |
|---|---|---|---|
| Exploration no charge |
About fifteen minutes with somebody who can describe the business and where it hurts. | A written report that stack-ranks candidate use cases and scores each for complexity. | Leadership picks one use case to take further. |
| Detailed scoping paid |
The chosen use case, the stakeholders and their roles, and sample data or examples of the outcome done manually before. An hour or two, or a workshop. | Executive summary; current- and future-state architecture; model recommendations; ROI and cost model at low, medium and high; governance and risk; change management; a pilot charter that skeletons a statement of work. | A scoped opportunity carrying a directional number finance can react to. |
| Pilot | A statement of work priced from the charter, plus a sample of real documents. Write it in detail: anything not in the document is not something you agreed. | The use case built and tested against your sample, with the return measured rather than asserted. | A decision on the return, the license cost, the integration work and the time to production. |
| Production and expansion | The pilot outcome accepted, and a named owner for the rollout. | A staged rollout with the timing of each stage, then the next use case. | Open-ended by design: each stage is a decision, not an obligation. |
Two rows deserve an argument before you sign. The recommendation is a recommendation: it can be bought in modules, and a plan that only works if you buy every module is a plan to renegotiate. Most of the money lands in the third row, priced off the second.
Pin it down: questions for your evaluation
-
Which numbers in the cost model are ranges you will stand behind, and what would convert them into a fixed price?Where directional scoping ends and a quote begins.
-
Which parts of the recommended plan will Iternal deliver, and which are for our team or an implementation partner?The delivery split in writing, since a discovery can recommend work its author does not perform.
Do You Need an NDA First, and Who Does It Cover?
Nothing has to be signed to start looking. Iternal’s security architecture and deployment documentation can be shared without an NDA, and a demonstration needs only representative sample material, which can be public information. Paper becomes load-bearing when your own material moves: data you cannot publish, technical manuals, a code base. Iternal signs a mutual NDA on either party’s paper, including your standard form.
Coverage is the question worth asking early. Where a distributor or a channel partner sits in between, the mutual NDA usually flows down through their agreements — usually is doing real work in that sentence, and Iternal treats it as something to verify rather than assume. Some organizations accept the pass-through; others require a direct mutual NDA, and Iternal has worked both ways. A confidential disclosure agreement takes longer: a CDA is written one-to-one and needs tailoring on how much may be disseminated, so start it early.
What an Engagement Is Not: Six Months to Be Told What You Knew
The complaint came back in the same shape from very different companies. A large engagement consumed six months of many people’s time and verified what the team already knew. Discovery produced a statement of work for the wrong thing. Bodies arrived, staffed with junior associates who needed constant explanation.
The same failure is available here. Iternal has seen one of its own reports largely restate what the client already knew, with a few good recommendations inside it. Price that risk. The defense is structural: make the first step cheap enough that being told what you know costs an afternoon instead of a quarter; insist the deliverable be specific enough to argue with, an architecture and a cost model rather than a narrative; and stop the clock on something running rather than on something bound.
Answered elsewhere
- Which problem to put first — see choosing your first use case.
- How the discovery tool itself works — see the AI Blueprint Builder page.
- Whether to move now or wait — see acting now versus waiting.
- Who staffs the build — see who delivers the work.
- For more information on the software license — see what it costs.
FAQ
FAQ: Scoping, Timing and Paperwork
Iternal states four to eight weeks to a production-ready pilot, to tangible value, or to a production-scale deployment, and six to eight weeks from first call to a production version of a smaller use case. Its shortest numbers are goals. A separate six-to-eight-week figure describes what a consulting firm would take to write the comparable strategy — the baseline being replaced, not a delivery commitment.
They are not one size. Iternal has run a pharmaceutical program still progressing after three pilots, well into its second year, and has also gone from first call to a production version of a smaller use case in six to eight weeks. One use case reaching production is a weeks-scale exercise; a multi-pilot enterprise program is a multi-year one.
Not to start. Iternal’s security architecture and deployment documentation can be shared without one, and a demonstration needs only representative sample material. An NDA becomes necessary before your own material moves, and Iternal signs a mutual NDA on either party’s paper. Where a distributor or channel partner sits in between, the pass-through usually flows down through their agreements — confirm that in writing, since some organizations require a direct mutual NDA instead.
Yes — that is the input the detailed session is built around. Sample data, plus the outcome you want or examples of the same work done manually before, produces scope, level of effort, complexity and the financial case. It has to look like the work, not be perfect.
No. The exploratory session carries no charge and returns a written report that stack-ranks your candidate use cases and scores each for complexity, so you see output before anything is invoiced. The detailed session is the paid step: architecture, ROI and cost model, governance, and the pilot charter.
Ask for the Charter, Then Ask for the Price
A good engagement is legible from the outside: you can name what each phase costs you and what it hands back. Start with the session that costs nothing, judge the output on whether you could argue with it, and hold the timeline to dates rather than ranges.