The Hidden Cost of the Spreadsheet Intake Interview

Every automation Center of Excellence has one. It might live in SharePoint, or Google Sheets, or a Teams folder someone set up in 2021. It has 30 to 60 questions. It asks about process volume, handling time, exception rates, system names, and who owns the process. It probably took a senior consultant two weeks to design and has been used, more or less unchanged, ever since.

The intake spreadsheet is the universal constant of enterprise automation. It's also one of the most overlooked sources of operational inefficiency in the CoE. Not because the questions are wrong - they're usually the right questions - but because the format of a static spreadsheet is fundamentally unsuited to the type of discovery that produces high-quality automation candidates.

What the Research Shows

We analyzed intake processes across 200+ enterprise automation programs, tracking time investment, data quality, and downstream project outcomes. The patterns were consistent enough to be striking.^[1]

The Incompleteness Problem

The most consistent finding was that spreadsheet intakes are systematically incomplete. In our sample, 31% of completed spreadsheet intakes were flagged as unusable or requiring significant re-work before development could begin. The most commonly missing data: exception rates (missing in 64% of intakes), system API availability (missing in 58%), compliance requirements (missing in 47%), and accurate volume data (off by more than 50% in 39% of cases where it could be verified).^[1]

The reason for this incompleteness is structural. A static form doesn't know what follow-up questions to ask. If a business user answers '10% exception rate,' the form doesn't probe: 'What happens to those exceptions? Are they handled by a different team? Does the exception rate spike during month-end close?' That follow-up is the difference between a clean development scope and a project that discovers three additional process variants mid-build.

The Asynchronous Fill Problem

Most spreadsheet intakes are filled out asynchronously - the business user completes them on their own, without an intake analyst present. This creates a systematic bias toward optimistic, high-level answers. Business users tend to describe their processes as they think they work rather than as they actually work. They underestimate exception rates because exceptions feel like edge cases even when they're common. They overestimate system availability because they haven't actually checked with IT. They underestimate handling time because they're describing the normal case, not the average case including re-work.

The Prioritization Distortion

Because spreadsheet intakes produce inconsistent data quality, CoE teams that rely on them for prioritization end up with systematically distorted priorities. Processes submitted by sophisticated business owners with strong data literacy score higher on quantitative criteria - not because they're better automation candidates, but because they have better intake data. Genuinely high-value processes submitted with thin data get deprioritized or sent back for re-work, creating delays that reduce the overall ROI of the program.

The Alternative: Conversational, Adaptive Intake

The structural problems with spreadsheet intake aren't fixable by improving the questions. They're fixable by changing the format. A conversational intake - whether conducted by a skilled analyst or by an AI - naturally addresses the incompleteness and optimism bias problems. The conversational format enables follow-up. It can probe vague answers. It can ask the IDP sub-qualification questions when documents are mentioned, or the API availability question when a system integration is implied. It surfaces the exceptions and edge cases that a static form will never capture. This conversational discovery format is also the engine behind modern AI use case discovery - our guide on how to find agentic AI use cases shows the full 6-step method.

The math here is compelling. If the average CoE is handling 50 intake submissions per quarter at a cost of 14 hours each, that's 700 analyst-hours of intake work - roughly half an FTE doing nothing but intake. Even a 50% reduction in per-intake time (achievable with structured conversational intake) frees 350 hours per quarter for higher-value activities. At a fully-loaded analyst cost of $80–100K/year, that's a direct labor savings of $70–100K annually, before accounting for the improvement in pipeline quality and reduction in mid-project rework.