Sessions 17–19 · Movement 03
Scoping the
Engagement
The engagement — scope it and lock the plan
Sessions 17–28 · The engagement

Twelve sessions. One real deliverable.

17–19

Scoping the Engagement

Scope with the business and lock the plan.

20–22

Building

Sprint the build; adjust as reality lands.

23–24

Training & Handoff

Test it, train them, and set it up in their accounts.

25–28

Buffer & Close

Held in reserve — then review, present and grade.

Sessions 17–19 · Visit one

Visit one is Day Zero.

Visit 1 — the run of show

Sponsor check-in (10 min) → access proven live at their desk (30) → interviews and shadowing (the rest). Delta drives access; Echo drives interviews. The sprint rule holds at semester scale: no access, no start — read-only credentials first (class 14’s rule).

The split: 1 maps, 2 decides

Visit 1 produces the findings report (systems, data, process — as observed) and the draft opportunity map. Visit 2 ranks it with the sponsor, picks the one demo target, and closes on the approval. Templates for every artifact live in the course repo — five teams, one skeleton. Firms charge $15–25K for this phase.

When Day Zero fails on-site

Dead credentials or an absent sponsor? Don’t burn the visit — switch to interviews and shadowing, log the gap, escalate to your instructor and the CTSBDC advisor the same day. And expect the memo (signed at Rotation Day, before anyone saw the systems) to be contradicted by the map — corrections go through the change order, in writing, before building.

Compendium Part II — the diagnostic sprint, applied at partner scale · visit mapping: research/notes/movement-m4.md
Sessions 17–19 · The deliverable

Audit, spec, build — it’s a ladder.

Auditwhat’s true, ranked
Specwhat to build, provable
Buildthe working thing
Retainerthe year-3 path

“Each stage de-risks the next for the client and raises your information advantage over anyone bidding cold.” Your team delivers exactly one rung — the ladder is why any rung is a complete deliverable: an audit team is doing stage one, properly. (Retainer is the year-3 path — nobody’s rung this semester.)

Where to aim: back-office first

Budgets chase sales-and-marketing AI, but measurable ROI concentrates in ops and finance: AP/AR, quoting, scheduling, reporting — the Tuesday chores from class 10, now with a P&L line.

Design for friction

Embed into the real workflow — the quote screen, the inbox, the sheet they already open — don’t perch a chatbot beside it. Adoption is designed, not hoped for.

Compendium Part II — “Starting the Firm” (the wedge) · the MIT method spine (back-office · friction)
Sessions 17–19 · The decision

Score the list. Commit to one.

With the sponsor, in the room

Put the long-list on the table and score it together — value × feasibility, the class-12 axis. Their ranking will surprise you; that surprise is data. Then commit to one and write the rest down as explicitly out of scope.

Why one, again: the one-demo discipline is what made the five-day sprint work — and the S-1 economics from class 13 are why narrow first engagements are survival, not modesty. One thing, provably done, beats three things almost.
Sessions 17–19 · The signature

“Approve” means the owner signs.

What gets signed

The Rotation-Day scope memo, validated against ground truth and re-signed — now carrying written acceptance criteria (class 13’s craft, executed): deliverable, criteria, deadline, exclusions by name.

Run it as a decision event

The bootcamp mechanic: a concrete plan in front of the person who can say yes forces a decision. Mechanics: the approval IS visit 2’s close — the Echo books it before visit 1 ends; bring two printed copies of the revised memo and criteria; present the map and the one target; signatures in the meeting, not by email later.

Block exit — all four or you’re not out:approved plan, signedwritten acceptance criteriaone demo targetaccess that actually works
Compendium Part II — the approval as forced decision event
Connect.AI logoConnect.AI
Sessions 17–19 · Scoping the Engagement01 / 06
Checking access…