Victor's question lands hard: what happens when the augmentation becomes full automation? This practitioner just collapsed five days of financial modeling work into one day using Claude's Excel plugin — not by doing the work for them, but by becoming a debugging partner that actually understands circular references and cross-sheet dependencies. The productivity gain is real and measured. But here's the uncomfortable part: they're still constructing the sheets, still making the strategic choices about what to model. The tool is a spectacular co-pilot. The next step Victor's pointing at — where Claude builds the entire model from a prompt — feels both inevitable and destabilizing. We're watching the last mile of human-in-the-loop knowledge work, and it's compressing faster than anyone expected. The practitioner didn't expect it to 'hit this hard.' Neither did most of us.
I'd be prototyping the agentic version this weekend — prompt-to-model pipeline with validation loops. The hard part isn't generation, it's knowing when the model is actually correct, which is exactly what this practitioner still provides.
Five days to one day is a 400% productivity gain on complex deliverables. If my analysts can produce models this fast without quality degradation, I'm rethinking headcount plans and what 'senior analyst' even means in 18 months.
Everyone's celebrating the speed gain. Nobody's talking about the new failure mode: analysts who can't build models from scratch anymore, completely dependent on a tool they don't understand when it hallucinates a formula.
Why this matters for operators: Operators need to map which knowledge work tasks are in this augmentation zone now versus full automation in 12 months — the transition window is shorter than planning cycles.
I cover AI×GTM intelligence like this every Wednesday.
Get STEEPWORKS Weeklyinteresting discussion on how much to build context engineering vs. the model being everything
This is the operator-builds-with-AI story I keep seeing. Non-technical person automates their actual workflow, not a toy project. The specificity of what they built matters more than the tools they used.
This analysis was produced using the STEEPWORKS system — the same agents, skills, and knowledge architecture available in the GrowthOS package.