Превращение MSP-автоматизации в цифровую трансформацию для клиентов: Фрэнк Мерино, FLOW 2026

Most MSPs automate their own help desk and stop there. Frank Merino, CTO and partner at Forthright, walks through how to point that same skill set at your customers and get paid for it. Frank's framework starts with what he calls the "human glue": every client has a team member manually bridging their CRM, accounting system, HR platform, and line-of-business apps, the same way your own techs bridge your tools. Anywhere those systems need to hand information to each other (sales closing a deal and it needing to hit accounting, for example) is a real automation opportunity, and usually a place your customer already feels the pain. He's specific about the sales approach: avoid the word "automation" when talking to a business owner, since it doesn't mean anything to them. Lead with the outcome instead, and tie it to something concrete, like an SLA built around their business goal rather than yours. He walks through a real client example: a company running HR across multiple countries kept having new hires show up without accounting, IT, or their manager knowing. Forthright mapped out every handoff and approval in that onboarding process and built the automation as a paid project (about 25 hours at $300/hour), then added a $250 per-user onboarding fee going forward. Frank is candid about what went wrong along the way. Automation projects without a clearly documented process become "forever projects" that quietly eat your margin. Full automation isn't always the goal. Sometimes automating 80% of a task and leaving a human for the last 20% is both cheaper and more reliable than chasing 100%. And the value in the work belongs to the customer, not to the engineer who built it, which matters because over-engineering something the client didn't actually ask for is a fast way to burn out a good automation developer. On pricing, he covers four models he actually uses: efficiency dividends (automation you do for goodwill, not direct revenue), project-based work (a strong first step and portfolio builder), consumption-based pricing (works well, but only for customers mature enough to want it), and outcome-based pricing, tied to a percentage of a result the automation helped produce, which he calls his favorite. He explicitly argues against flat monthly retainers for this kind of work, calling it "break-fix at a fixed price." The Q&A covers pricing catalogs tied to a customer maturity model, how to handle maintenance and support on outcome-based deals, and what happens when a client wants to take an automation in-house. Recorded live at Rewst's FLOW 2026 conference. Timestamps 1:31 – Why MSP automation stops at the help desk 4:44 – The "human glue": where client automation opportunities hide 6:36 – Sell value, not "automation as a service" 17:59 – Real example: an onboarding automation across multiple countries 23:05 – Lessons learned the hard way: scope creep and burnout 28:44 – 4 ways to price client-facing automation (and one to avoid)