Who hurts
Ops teams running core processes on a shared sheet that's outgrown itself.
The problem
The sheet is now load-bearing: slow, conflict-ridden, no history, no validation. Migrating means rebuilding a workflow twelve people rely on daily, so nobody does it.
What you build
Infer schema and validation rules from the existing data, stand up a real backing table with history and permissions, and keep the sheet as a live two-way view so nobody has to change how they work on Monday.
Why now
Schema inference from messy real-world sheets — mixed types, merged cells, notes columns — is exactly the fuzzy job models handle well.
Validate it this week
Migrate one company's worst sheet by hand. What you hated doing is the product.
Why you'd keep winning
Sync correctness. Two-way sync that never loses an edit is genuinely hard, and being the one that doesn't lose data is the whole reputation.
The honest risk
Two-way sync is a data-loss machine if you get it wrong, and one lost row ends the account. Be conservative and log everything.
The prompt is written to make an AI argue with you before it writes code — that first round of pushback is worth more than the scaffold.