Magic Spoon renewal call prep — Feb 2026
Purpose: Confirm deliverables, lock in 6‑month scope ahead of renewal.
Context: Contract was up end of Jan 2026. Mary (Magic Spoon) said they want to see MMM/MMT through before signing the next contract; otherwise they’re happy to continue. Renewal conversation is happening this week (per ops sync 2026-02-06, 2026-02-10).
1. Agreed / current deliverables (from syncs)
From 2026-01-30 Magic Spoon — Brainforge sync, Demi stated the final project deliverables as:
| Deliverable | Status / notes |
|---|---|
| SPINS API | Pipeline implemented; final stages of QA. Waiting on comparison dataset and/or Heather (Magic Spoon) for QA. Rate limits and weekly vs 4‑week aggregation mismatches documented; doc sent/planned for SPINS team. Option discussed: SPINS backfill flat file + incremental API on top. |
| MMM mart (MMM/MMT) | First phase done: non-CSV sources that were “yes to be modeled” and already in warehouse — PR in progress. Michael & JT are focused on getting MMM/MMT “all set up”; Mary said they want to see this through before signing the next contract. |
Other work referenced in scope:
- dbt audit — Delivered (or out the door). “Quick fixes” from audit to be implemented.
- Prefect / pipeline reliability — Ownership and visibility: tests, Slack alerting when pipelines break or timeout (so they don’t find out months later that data was missing and financials were off). You offered to layer tests and improve Prefect ownership so it’s not a black box.
- Knowledge transfer / working sessions — Magic Spoon (e.g. Honey Nut, team) wanted working sessions on existing structure, who uses what and why, to refine what goes in scope for February (Jan 06 sync). Focus may be less on new connector build-outs and more on updating existing tables from prior partner transition work.
2. What Mary said (Jan 23) — renewal conditions
- Impressed with the partnership; happy to continue assuming things go well.
- Condition: See MMM and MMT work “all set up” through to the end before signing the next contract.
- Next‑contract focus (from her words):
- Implement quick fixes from the dbt audit.
- Pipeline reliability / “insurance policy”: Know when a pipeline breaks or times out; avoid discovering months later that data was missing and financials were off.
- Initial QA and setting those checks up (not the “fun stuff” but important).
- Appetite: Team wants to be more in the weeds and self-serve; open to knowledge transfer and learning how to do things correctly (you offered to share how pipelines work and how to add more).
3. Suggested 6‑month scope to confirm on the call
Use this as a checklist to confirm with Mary/Michael (and JT if on the call), not as a final SOW.
Phase 1 — Close current engagement (now)
- SPINS API — Sign-off on QA (their comparison + any Heather QA). Confirm path for backfill + incremental (or agreed subset, e.g. last 2 months) and SPINS thread/decisions.
- MMM mart — Confirm first phase (non-CSV, in-warehouse) is accepted and MMM/MMT “set up” is done to their satisfaction so they’re comfortable signing.
6‑month scope (renewal)
- Pipeline reliability & observability
- Tests in place; Slack (or equivalent) alerting for failures/timeouts.
- Clear Prefect ownership and documentation so they’re not a black box.
- dbt audit follow-through
- Implement agreed quick wins from the audit.
- Ongoing support & enablement
- Working sessions / knowledge transfer so their team can self-serve and own pipelines.
- Option: cadenced office hours or “how to add/change pipelines” guidance.
- Optional / if in scope
- New connectors (you’d said ~1–2 weeks per connector for standard cases once the pattern is in place).
- Any “existing table updates” from the transition project (per Jan 06) — align with what they want in the 6‑month window.
Out of scope / clarify
- SPINS API: Whether any ongoing “we run the pipeline and fix SPINS issues” is part of the 6‑month scope or handoff + their/SPINS ownership after handoff.
- Exact number of new connectors or table updates in the 6 months — agree whether it’s “as needed” or a cap.
4. Talking points for the call
- Recap deliverables — “Our understanding of what we’re closing out: SPINS API pipeline + QA, MMM mart first phase. Want to confirm that matches yours and that MMM/MMT is in a place you’re comfortable with for renewal.”
- Renewal condition — “You’d said you wanted to see MMM/MMT through before signing. Can we confirm that’s done from your side, or what’s left to feel good about it?”
- 6‑month scope — “We’re proposing a 6‑month scope that focuses on: (1) pipeline reliability and alerting, (2) implementing dbt audit quick fixes, (3) knowledge transfer and working sessions so your team can own and extend this. Then we can add specific items like new connectors or table updates as we lock the SOW.”
- Pricing / terms — Have internal numbers ready. Playbook anchor for Magic Spoon–type pilot: 22k for a 5–6 week pilot; 6 months will be a different structure (e.g. monthly retainer or phased milestones). Confirm term (6 months), start date, and what’s in/out of scope.
5. Internal context (vault only)
- Ops (2026-02-06): Magic Spoon and Remo contracts expired; renewal negotiations in progress. Uttam talking to Magic Spoon this week.
- CSO sync (2026-02-09): Magic Spoon incident referenced (breakdown, catching things late); feedback on taking control when needed. Demi’s focus post–other work: Magic Spoon.
- Data service standups: SPINS pipeline and API issues (rate limits, aggregation differences) and QA have been ongoing; Ashwini/Uttam working SPINS data and documentation.
6. Pre-call checklist
- Confirm who’s on the call (Mary, Michael, JT, others).
- Have a one-pager or short doc with: deliverables closed, proposed 6‑month scope, and pricing/term (if you’re sending ahead).
- Know internal walk-away and flexibility on term (6 months) and price.
- If SPINS or MMM mart have open items, have a one-line status for each so you can say “we’re here, next step is X.”