Vol. 01 · Cohort I · Nov ’25 → Mar ’26

A private recap, for Sarah.

Five sessions, re-assembled. Please enter the key to continue.

Compiled in Chilean Patagonia · Bound for Fort Collins
Private portal NoCo Artisan × AI Ranking · Cohort I
← Index · Session 05 of 05
05

Sitemap reset (cut short)

2026-03-31 · 33 minutes
StrategyOpsWebsite / ExecutionAI Tooling

Open full recording in Fathom →

Summary

Short session, cut at 32 minutes when Sarah had a family emergency. Before that: Sarah asks whether there's room to extend the engagement. She loves Co-work, wants to graduate to Claude Code, and feels two remaining sessions isn't enough. Nico proposes a flexible 12-week bi-weekly extension: same 6 remaining sessions, stretched across the schedule instead of stacked. They review a shared marketing-team Google Sheet that has Sarah's name next to a huge backlog of page work, and agree the web team should build the empty templates first so Sarah only has to populate content. Quick tour of Sarah's recent Co-work usage (including pulling emails into a legal-evidence folder against a subcontractor dispute). Nico walks through the context-window concept: million-token ceiling on paper, but quality degrades past ~30-40%, so summarise-and-restart long conversations. Then points Sarah at Cowork's new scheduling feature: kick off content generation overnight, wake up to finished pages. Installs VS Code, opens the context MD file, opens the SEO-work folder in Cowork again. While stepping through the page structure they hit a problem: the site's parent / child / service-in-location hierarchy isn't mapped cleanly, and generating more content without a proper sitemap will make it worse. Nico commits to drawing a Figma sitemap in the next 30 minutes so they can reset in the following session. Session ends there.

Chapters

Highlights

  • Sarah wants to keep going. Loves Co-work, wants Claude Code next. 2 sessions isn't enough.
  • Her team is 2 web + 2–3 social/ads. Dividing labour cleanly: they build empty templates, Sarah fills content.
  • Cowork is earning its keep outside SEO too: pulled a full evidence folder together for a subcontractor dispute.
  • Context windows: the million-token ceiling is marketing. Quality degrades past roughly 30-40% utilisation. Summarise and restart.
  • Cowork scheduling is unlocked: overnight runs mean Sarah wakes up to finished pages to review, not write.
  • The real blocker isn't content generation, it's the site map. Generating more location + service pages without a proper hierarchy will multiply the mess.

Decisions

  • Propose a 12-week bi-weekly extension (6 more sessions). Sarah to confirm.
  • Build the full sitemap in Figma before generating more content — Nico commits to doing this in the next 30 minutes.
  • Web team builds blank templates; Sarah writes and pastes the content.
  • Add 30 minutes to the next session to reset scope after the sitemap is done.

To-dos from this session · 07

Confirm the 12-week bi-weekly extension (6 more sessions) or close the engagement
open StrategyOps
Sarah is in; Nico to hold the slot. Decision pending written confirmation.
Replicate the approved Figma sitemap in a Google Sheet for the web team
open OpsWebsite / Execution
Install VS Code (already done in-session) and use it as the default opener for MD / context files
done OpsAI Tooling
Activate the internal city-section links on the already-published location pages
open Website / Execution
Schedule overnight Co-work runs so content generation happens while Sarah sleeps
open AI ToolingOpsContent
Finish the remaining location × service child pages via the Co-work flow once the sitemap is signed off
blocked Website / ExecutionContent
Blocked on sitemap — intentionally held until Session 6.
Summarise and restart long Co-work conversations once they pass ~30-40% of the context window
open AI ToolingOps