Prepared by CallCraft
CallCraft · Meeting recap — Northwind Logistics onboarding refresh · kickoff check-in · 14 Aug 2026
Northwind Logistics and CallCraft agreed to anchor the onboarding refresh on a four-week build, with three milestones kept explicit so the client can hold the work without rerunning the discovery thread.
Northwind's internal pilot deadline lands 30 Sep 2026, which forces a hard cut on any scope that has not started by the end of week two; north-of-scope work will be quoted under a separate change order rather than absorbed into the base engagement.
TL;DR
- Phase one ships as a four-week single-team build (audit, two sprints, retro).
- Northwind logistics ops owns field rollout; the Northwind IT lead owns the auth cutover.
- A separate procurement week is held off the main schedule and gated on Northwind finance sign-off in week three.
Phase one ships in Q3 as a four-week build. A procurement week is held off the main schedule and gated on Northwind finance sign-off — anything past that window moves to a separate change order.
Key decisions
- Decision: Phase one is a four-week single-team build, not a phased cross-team rollout. — Decided by Priya (Northwind ops) and corroborated by Devon (CallCraft).
- Decision: The auth cutover ships inside phase one rather than a separate phase. — Decided by Marcus (Northwind IT) with Devon (CallCraft) signing off on the integration risk.
- Decision: Northwind field training is held until the pilot is complete. — Decided by Priya (Northwind ops) after weighing the pilot deadline.
- Decision: Procurement scoping is gated on Northwind finance sign-off in week three. — Decided by Devon (CallCraft) and accepted by Priya (Northwind ops).
Action items
| # | Owner | Action | Due |
|---|---|---|---|
| 1 | Marcus (Northwind IT) | Send SSO metadata and the list of identity-claim mappings CallCraft needs for the integration spike. | Tue 19 Aug |
| 2 | Priya (Northwind ops) | Name the two pilot sites and confirm the field lead for each. | Wed 20 Aug |
| 3 | Devon (CallCraft) | Run the architecture spike against the SSO metadata and write up either a fit/fix or a second-pass integration. | Fri 22 Aug |
| 4 | Devon (CallCraft) | Draft the SOW draft reflecting the four-week build and route it to Priya for redlines. | Mon 25 Aug |
| 5 | Devon (CallCraft) | Hold a procurement scoping-quote line-item for Northwind finance sign-off in week three. | Open; gated on finance sign-off in week three |
| 6 | Priya (Northwind ops) | Schedule a 30-minute check-in once the SSO spike lands. | After #3 |
Discussion highlights
SSO and identity integration
Northwind IT is migrating from a legacy SSO into a modern identity provider and the integration risk sits in the claim-mapping middle. Marcus confirmed the migration is mid-flight, so the spike is the spec-driving input rather than a parallel track. CallCraft will scope the integration against the spike output rather than the legacy auth contract.
Pilot scope and field rollout
Priya confirmed two pilot sites for the phase-one test, with field training intentionally slotted after pilot completion rather than during the four-week build. That schedule protects Northwind from a rollout race with the pilot itself and gives CallCraft a clean retro window with the field leads.
Procurement hand-off
Northwind finance has to sign off on the procurement scoping before the quote is firm. Devon honoured that gating in the SOW draft — the quote line-item sits open until the week-three finance sign-off, then closes inside the same engagement so the Northwind procurement hand-off stays inside the CallCraft single-team envelope.
Risk on the auth cutover
The SSO metadata may not arrive clean. Marcus accepted the risk of a second-pass integration at the Cost of a longer week-two spike, so the SOW draft reserves an explicit contingency in week two rather than collapsing the timeline.
Open questions
- Will Northwind IT standardise the SSO claim-mapping in time for the spike, or do we plan for two mapping iterations?
- Does Northwind Ops want the field lead copied on the weekly status note, or do we hold that report inside Northwind ops leadership?
- Is the procurement scoping expected to land inside the same engagement envelope, or do we cut a sub-engagement letter for that week?
Next step
Devon sends the SOW draft by Mon 25 Aug with the four-week build, the auth cutover inside phase one, and an open procurement line-item guarded by week-three finance sign-off.
— CallCraft