UnHacked the podcast with hosts Justin Shelley, Bryan Lachapelle, and Mario Zaki.

Still spending hours on proposals, onboarding, and offboarding? This episode shows what “10x to 50x” automation looks like in real MSP workflows, plus what can go wrong if you build it insecurely.

Justin Shelley is joined by Bryan Lachapelle, Mario Zaki, and Joshua Holloway to kick off a practical Vibe Coding series. This is not a step-by-step “how to vibe code” tutorial. It is a breakdown of specific business processes, what they cost before automation, what they look like after, and how to think about ROI without hand-waving.

Mario walks through two concrete builds:

A customer-facing onboarding and offboarding portal tied into Microsoft 365. What used to take about 45 minutes per request drops to about 3 to 5 minutes, with fewer errors and less “email tennis” for missing details. It can also handle licensing changes and capture agreement acknowledgments so billing stays aligned.

A proposal system that turns “complicated” proposals from 3 to 4 hours into about 10 minutes by selecting predefined items, quantities, and plan comparisons, then exporting to PDF or Word.

The group also gets candid about the real payoff beyond labor: faster sales cycles, fewer math mistakes, fewer late-night escalations, and a better client experience. They also warn about the security trap: by default, AI-built apps often ship with unsafe assumptions, including no login, weak access control, and other “wide open” holes unless you design for security first.

What you’ll learn:

  • How an onboarding/offboarding workflow can drop from ~45 minutes to ~3 to 5 minutes using Microsoft 365 integrations
  • How a proposal process can go from 3 to 4 hours down to ~10 minutes, while reducing formatting and math errors
  • Why speed matters in sales, including Justin’s admission that slow proposals can lose deals
  • How to spot the best automation targets: repetitive, error-prone work that does not require specialized expertise
  • The security reality of vibe-coded apps, and why “do it right” has to start with threat thinking and safeguards