Meru AI

Implementation guide

The first 100 days of AI implementation in a portfolio company.

Use the first 100 days to establish one working implementation and a credible decision about what comes next. The calendar is a planning structure; access, evidence, and readiness determine when the work advances.

For
Operating partners and portfolio leaders
Purpose
Sequence the work and set release gates
Prepared by
Meru AI
Last Updated
October 20, 2026

A planning horizon, not a delivery guarantee.

The first 100 days should produce an informed operating decision: a bounded system ready for supported use, a narrower scope, or evidence that the proposed work should wait. It is not a promise to transform a company on a fixed date.

Before starting the implementation clock, confirm a sponsor, a business owner, access to the relevant people and systems, and authority to approve changes. Procurement, data remediation, security review, and integration constraints may extend the sequence.

This plan applies the five Meru stages to one complete workflow: understand the operation, define the priority, design the solution, implement the system, and support and improve. Passing a readiness gate matters more than keeping a calendar milestone.

Understand the work and select the priority.

Observe the workflow with the people who perform it. Follow representative records from the initial trigger through completion, including escalation, handoffs, and failures. Establish which system holds the authoritative record.

  • Document inputs, decisions, outputs, users, systems, and exceptions.
  • Measure a representative baseline, with its period, source, and limitations.
  • Confirm approved data use, vendor constraints, account access, and decision rights.
  • Compare AI with process repair, existing features, and rules-based alternatives.
  • Choose one priority and agree quality, cost, adoption, and business acceptance criteria.

Gate: Management can explain the problem, the owner, the expected operating change, and what would disprove the proposal. Do not move into a build with unresolved data rights or no route into the core system.

Design the controls and build against real conditions.

Agree the design before scope expands. Specify permitted inputs, where outputs land, required review, integration behavior, and the fallback when a dependency or model fails. Establish an evaluation set from authorized, representative examples.

  • Test missing, contradictory, stale, and malformed information, not just ideal records.
  • Test permission boundaries and isolation between accounts or companies.
  • Confirm retries cannot create duplicate writes or unapproved downstream actions.
  • Measure the cost and latency of the full workflow, including review and rework.
  • Prepare operating instructions, support ownership, logging, and rollback.

Gate: The business and technical owners have evidence against the agreed tests and understand remaining limitations. Use shadow mode or a restricted group where appropriate; do not turn a test result into permission for unrestricted deployment.

Introduce live use and make the next decision.

Roll out to a defined group with trained reviewers and a named escalation route. Compare actual work with the baseline, retaining enough context to explain changes in workload, staffing, or business mix.

  • Inspect use, abandonment, overrides, exceptions, and completed work.
  • Review output quality and permission behavior during representative live demand.
  • Track recurring costs, review effort, and support burden.
  • Have someone other than the builder demonstrate routine operation and recovery.
  • Keep an improvement backlog and decide what merits further investment.

Gate: The owner can accept supported production use against the agreed criteria. If volume is too low or performance remains uncertain, extend controlled use. A calendar date is not evidence.

Use a release record, not a launch announcement.

Evidence to record for the release decision.
AreaEvidence requiredWho accepts it
Operating resultBaseline, live comparison, workload context, and limitations.Business owner; finance for claimed financial benefits.
QualityRepresentative evaluations, error severity, review coverage, and exception handling.Business owner and relevant domain reviewer.
Access and dataApproved permissions, retention, vendor use, and boundary tests.Company security or data owner, with legal review where required.
IntegrationFailure, retry, duplicate prevention, logging, and rollback tests.Technical owner.
Adoption and supportActual usage, handover test, runbook, escalation route, and change process.Operating manager and support owner.

Set acceptance thresholds before testing and justify them for the workflow’s risk. There is no universal accuracy percentage or sample size that makes every AI system safe.

Stop conditions protect the implementation.

Access or ownership is still unresolved.

The build depends on accounts, data, or decisions nobody can legitimately authorize.

What to do: Pause the dependent work and resolve permissions or scope. Do not work around controls with personal credentials.

The baseline keeps changing to justify the result.

The program has no agreed comparison method or ignores shifts in workload.

What to do: Freeze definitions, document changed conditions, and separate observed results from estimates.

The system produces consequential outputs without review.

The release scope moved beyond tested decisions and acceptable risk.

What to do: Restrict usage, restore the approved review path, and retest before expansion.

Everyone is waiting for a portfolio-wide launch.

Too many companies and dependencies were tied to one deadline.

What to do: Separate company readiness gates and complete one operating implementation before replication.

Make each review end in a decision.

During delivery, use a regular working review for blockers and a separate sponsor review for scope, investment, and risk decisions. Agree the frequency around the work rather than adding meetings by default.

Keep one decision log with the issue, evidence, owner, due date, and consequence of delay. At the end of controlled live use, choose explicitly: expand, improve within scope, maintain, defer, or stop. Record why.

Released time should be reported as capacity until management can show how it was redeployed or converted into realized savings. Do not turn an estimated time saving into a financial result by multiplying it by payroll alone.

Further reference. The NIST AI Risk Management Framework is a useful reference for organizing governance, evaluation, and risk controls. The sequences and checklists on this page are Meru’s practical recommendations, not a NIST certification or prescribed implementation method.

Leave the kickoff with seven answers.

Use these seven fields in an operating review. Unknowns are part of the brief, not blanks to fill with an optimistic estimate.

01Workflow and boundary
What work are we improving? Name its trigger, end state, current bottleneck, and what remains outside scope.
02Owner and decision rights
Who owns the operating result, system access, review, and release decision?
03Baseline and unknowns
Define the unit of work, measurement period, source records, and comparison method. Label missing evidence.
04Systems and dependencies
Identify source documents, authoritative records, permissions, integrations, and people needed.
05Proposed change and acceptance
Describe the smallest complete change. Agree quality, review, adoption, and total operating-cost criteria before testing.
06Exceptions and fallback
What is held for review, who resolves it, and how do staff continue if the system fails?
07Next decision and evidence
Request a bounded decision. State the evidence, owner, and unresolved conditions required for the next stage.

Includes a blank worksheet and the fictional example below. Use your browser's Print command to print or save a PDF. Nothing is submitted to Meru.

Read a fictional completed brief

An illustrative planning exercise, not a Meru client engagement, measured outcome, or deployment recommendation. Example Co. and its circumstances are invented.

Workflow and boundary
Example Co., a fictional distributor: from a supplier invoice received in the shared inbox to a reviewed accounts-payable entry. Staff currently reconcile invoice lines with purchase orders and receiving records. Payment authorization and supplier master changes remain outside scope.
Owner and decision rights
The operations manager owns the workflow. IT approves access and integration. An accounts-payable reviewer checks each prepared entry; the finance lead accepts financial controls and any later release proposal.
Baseline and unknowns
No baseline has been measured yet. Before testing, the owner will agree a representative period and record received invoices, completed entries, review and rework time, and exceptions. Invoice mix and review effort must remain visible in comparisons. No savings estimate is approved.
Systems and dependencies
Inputs: invoice, purchase order, receiving record, and supplier master. The accounting system remains authoritative. Inbox access, document retention, API permissions, and source completeness need confirmation before a build is approved.
Proposed change and acceptance
Prepare a source-linked entry for a reviewer, matching supplier, order, quantity, and amount to the records. Every proposed value must have a traceable source. Test missing records, mismatches, duplicates, and ordinary work. The owners must set justified pass criteria and a cost ceiling before evaluation; they are not yet agreed.
Exceptions and fallback
Hold discrepancies and missing originals. Check the records already received before requesting information again. Ask for genuinely missing or stale information. Never guess a quantity, approve a payment, or create a second entry on retry. Staff retain the existing manual process.
Next decision and evidence
Request authorization for bounded discovery only, not production. The next review needs an approved access plan, baseline definition, representative evaluation records, and cost and acceptance criteria. Proceed, narrow, or defer based on that evidence.

Bring one workflow, the business problem it creates, and the decision you need to make. There is no need to prepare a technical specification.

Start a conversation

Do not share passwords, confidential client records, or regulated information in an initial inquiry.

These guides draw on our implementation and consulting work. Adapt the sequence to the company's systems, risk, and responsibilities, and assess outcomes against its own baseline. They are operating recommendations, not a forecast of financial results.