We think this is exactly the right question to ask. The moment a tutorial jumps from "select this cell" to "write a VBA script" is the moment most beginners feel locked out of their own potential. That gap is not a skill issue, it's a design issue. Traditional spreadsheets demand that you translate your intent into a foreign language of formulas and macros before you can automate anything. The person who knows exactly what cleanup they need but cannot code it is not incompetent; they are underserved.
The user who posted this is experimenting with something smarter: describing cleanup steps in plain English and letting AI execute them. That approach treats natural language as the interface, not a barrier. Think about what that means for someone who spends every Monday filtering the same columns out of a CSV, renaming headers, and removing duplicates. Right now, they either do it manually or hunt through forums for a script they barely understand. A plain-English workflow lets them say "remove rows where the status column is blank, rename 'cust_id' to 'Customer ID', and sort by date descending." The AI handles the syntax. The user keeps the intent.
What makes this idea practical is the reuse factor. Save that description once, and it becomes a reusable workflow for any new dataset with the same structure. No version control headaches, no debugging a macro that breaks when a column moves. The description stays human-readable, so anyone on the team can understand what the automation actually does. That is a significant step toward making data cleanup accessible to people who are not programmers but who spend a disproportionate amount of their week on tasks that feel like programming.
The real test will come from the beginners themselves. If they find describing steps in English more natural than writing formulas, the barrier shifts from technical syntax to clarity of thinking, which is where it should be. That is a trade worth making. So our opinion is clear: keep pushing this experiment. Listen to what beginners say about where complexity sets in, and build the tool around their language, not the other way around. The spreadsheet of the future should understand you, not the other way around.