The Pitch vs. The Proof
Every automation vendor has a compelling story. They promise 80% labor savings, seamless integration, AI agents that work "out of the box," and a partnership that will transform your back-office. In the pitch room, this all sounds possible.
Then week one happens.
The onboarding is slower than expected. The API documentation is incomplete. The "no-code" setup requires a developer anyway. The sample workflows don't match your actual data structure. And suddenly you're wondering if you chose wrong.
The problem isn't that vendors lie. Most genuinely believe their tool can solve your problem. The problem is that enterprise automation is fundamentally about execution, not features. And execution only reveals itself in the first seven days of real work.
What to Watch in Week One
Can they actually connect to your systems?
This is the fastest deal-breaker. Ask the vendor for a proof-of-concept (POC) that touches your actual data sources within the first three business days. Not a sandbox. Not a demo environment. Your systems.
Pay attention to how they respond. Do they ask clarifying questions about your stack, or do they assume you run standard software? Do they have a pre-built connector for your ERP, or are they building one on the fly? The difference between "we've integrated with SAP 200 times" and "we can write custom APIs" determines whether you're weeks or months from value.
Do they have a playbook for your workflow, or are they reverse-engineering yours?
Good vendors come with templates for common automation patterns: invoice processing, order reconciliation, expense categorization, lead qualification. These accelerate delivery because the core logic is already battle-tested.
If the vendor is starting from a blank canvas with your workflow, assume 2-3x longer timelines. They're learning your domain alongside building your solution.
Can they show you working automation on day five?
Not a prototype. Not a wireframe. Working automation that processes at least one real transaction end-to-end. This is the clearest signal that the vendor understands how to move fast.
"The difference between a vendor that ships and a vendor that delays isn't intelligence—it's whether they've built this before and can start from templates instead of theory."
The Questions That Separate Leaders from Followers
During your first week conversations, ask these directly:
How many people do you assign to my project from day one? One consultant handling 12 customers isn't a partnership. They're a maintenance contract.
What percentage of your POC workflows go live unchanged? If it's under 60%, they don't understand the domain well enough.
Who owns the failure if the integration doesn't work? Clear ownership—not "we both contributed"—means accountability.
What's your mean time to first automation running? The best vendors ship something in 5-10 business days. The rest ship in 8-12 weeks.
The Trade-off You Actually Care About
You'll be told the choice is between "flexibility" and "speed." Flexible platforms let you build anything but take longer. Pre-built solutions are fast but rigid.
This is misleading. The real trade-off is between vendors who've already solved your problem and vendors who will solve it for the first time with your data.
If your workflow is invoice-to-GL posting, you want a vendor who has done this 50 times. If your workflow is completely custom—a proprietary blend of your business logic and legacy data structures—you need a vendor who builds to order. Most ops leaders are somewhere in the middle: 70% standard, 30% custom.
A strong vendor in week one will separate those two parts and show you working standard automation immediately, while negotiating the custom piece.
How Modulus Approaches This
We don't believe in the 90-day contract theater. From day one, we assign a dedicated automation engineer and a technical lead who own your delivery. Within five business days, you see working automation on a real data sample from your systems—not a generic demo.
We've built hundreds of custom AI workflows across finance, operations, and support. We also ship pre-engineered patterns for the problems that repeat: invoice processing, expense categorization, order exception handling. This means we can be honest about which part of your workflow we can template and which part requires engineering. No false promises. No surprises in week three.
If you're comparing vendors, spend week one watching them work. Not how they present. How they ship.
Learn how Modulus delivers working automation in your first week.
Read next from Modulus1:
Originally published on the Modulus1 insights blog. Browse more analysis on AI, SEO, and automation.
Top comments (0)