Everyone is telling businesses to automate. Fewer people are explaining what that actually means in practice, what it costs, how long it takes, or how you know whether a specific process is even worth automating in the first place.
The result is a lot of companies either waiting on the sidelines, overwhelmed by the noise, or making expensive commitments to vendors who deliver far less than promised.
Jimmy Lewis has been on the inside of this problem since before AI became a boardroom buzzword. The co-founder of TrueFocus Automation, Lewis spent nearly 15 years in title insurance operations before building one of the most specialized automation firms in that industry. His team has developed 844 bots, automated more than 2,500 workflows, and returned over 1.3 million working hours to clients.
His advice for companies considering their first automation project is less about technology and more about asking the right questions before spending a dollar.
Start With the Friction, Not the Technology
The most common mistake Lewis sees is companies beginning the automation conversation with a tool rather than a problem. They have heard about RPA, or they have seen a competitor demo something, and they want to implement that same thing without first identifying what is actually costing them time and money.
A better starting point is a straightforward internal audit: where are people getting stuck, what tasks are being done manually that feel like they should not be, and which processes break down when a specific person is out of the office.
Lewis’s team conducts what they call a shadow session with prospective clients, a recorded walkthrough where the people actually doing the work demonstrate their process step by step. That session often surfaces inefficiencies that management was not aware of, not because they were hidden, but because the people doing the work had normalized the friction. “We ask them where they see roadblocks, or people getting bogged down with manual work,” Lewis says. “Sometimes they don’t even realize how much time is being lost until they walk us through it.”
The Half-FTE Rule
Not every manual process is a good candidate for automation. Lewis uses a simple benchmark to filter out projects unlikely to justify the investment: the process should consume at least half a full-time equivalent role’s working hours.
That threshold exists because automation has real costs. A typical bot build runs around $9,500. Annual maintenance adds another $8,000 to $10,000. Hosting, licensing, and support bring the first-year total to roughly $18,000 for many projects. If the automation only recovers an hour or two of work per day, the payback period stretches out to a point where the investment is hard to justify.
For a process consuming half a person’s day, or four to five hours spread across a team, the numbers typically work within the first year. Lewis notes that the actual payback timeline depends on volume and process complexity.
There is an important exception. High-stakes compliance processes may justify automation even at low volume. A monthly government filing with significant penalties for a missed deadline might run once a day or once a month, but the risk of human error or absence can easily outweigh the cost of a $4,000 bot that runs reliably on schedule every time.
What to Ask Any Vendor Before You Commit
Every business owner should put several direct questions to an automation vendor before signing anything, according to Lewis.
The first is whether the vendor understands the industry. General automation firms can build workflows, but they do not arrive with knowledge of specific documents, systems, exception patterns, or compliance requirements. That gap costs time and money during implementation and often surfaces as underperformance after go-live. A vendor with genuine domain expertise should be able to describe a client’s processes accurately before those processes have been explained in detail.
The second is the ownership model. There is a meaningful difference between a vendor who builds code the client owns and one who provides access to a platform the client rents. Both have legitimate uses, but they carry very different long-term cost profiles and risk implications.
The third is whether the vendor can provide a realistic return on investment estimate before the project starts. A credible automation partner should be able to model expected ROI for a specific process, accounting for build cost, maintenance, licensing, and the volume of work being displaced. If a vendor cannot or will not provide that, it is a meaningful signal.
The fourth is references. Not every client will agree to provide one, but a firm with a solid track record should have at least a few clients willing to speak to the results they have seen.
What the First Three Months Actually Look Like
For businesses that have never implemented automation before, Lewis outlines a realistic timeline. The process starts with a discovery session, which is typically a couple of hours of shadowing the workflow and documenting every step. Within two to three days, the vendor should present a proposal with a defined scope of work, a cost, and a timeline.
Development of a typical project runs about five weeks. Integration, testing, and handoff bring the total to roughly eight weeks from signing to go-live, meaning clients should see real output from the automation within two months of starting.
The first few weeks of live operation usually surface edge cases, the small percent of files that behave unexpectedly. A competent vendor handles those adjustments as part of the implementation, not as change requests billed separately. “We lay it all out up front,” Lewis says. “There should be no surprises.”
The Thing Nobody Tells You About Automation and Your Team
One consistent pattern Lewis has observed across dozens of implementations: the teams most resistant to automation at the start become its biggest advocates once it is running.
The resistance is almost always rooted in fear of job loss. The advocacy that follows is almost always rooted in the experience of no longer spending half the day on tasks that felt beneath their skills. When someone who was manually entering data from emails to open 50 new files a day is suddenly opening 100, because the bot handles the data entry, and now they spend the recovered time on client calls and problem-solving, the conversation about automation changes entirely.
The technology does not get credit for that shift. The honest conversation beforehand does.
Jimmy Lewis is the co-founder of TrueFocus Automation, a specialist automation firm serving the title insurance, mortgage, and real estate industries. TrueFocus has built more than 800 bots supporting over 2,500 workflows and has returned more than 1.3 million working hours to client teams.
Disclaimne: This article is based on information provided by the expert source cited above. It is intended for general informational purposes only and does not constitute legal, financial, or real estate advice. Readers should conduct their own research and consult qualified professionals before making any real estate or financial decisions.
