{"id":254,"date":"2025-03-27T18:00:27","date_gmt":"2025-03-27T18:00:27","guid":{"rendered":"https:\/\/aboutpetertran.com\/?p=254"},"modified":"2025-03-27T18:00:27","modified_gmt":"2025-03-27T18:00:27","slug":"case-study-how-i-built-a-scalable-automated-compliance-framework-that-reduced-manual-effort-by-85","status":"publish","type":"post","link":"https:\/\/aboutpetertran.com\/?p=254","title":{"rendered":"Case Study: How I Built a Scalable, Automated Compliance Framework That Reduced Manual Effort by 85%"},"content":{"rendered":"

\"text\"<\/span><\/span><\/p>\n

The Story<\/h2>\n

As our company planned expansion into new states<\/strong>, our compliance onboarding process<\/strong> was a clear bottleneck. <\/strong>One that would only grow worse over time. Each client was required to meet a unique set of regulatory and internal requirements<\/strong>, but the existing system was manual, inefficient, and lacked transparency<\/strong>. Clients had to submit all documents through a single, lengthy HubSpot form<\/strong> that didn\u2019t save progress\u2014if they missed something, they wouldn\u2019t find out until days later, when a compliance specialist manually reviewed<\/strong> the submission.<\/p>\n

This created a frustrating experience<\/strong> for both clients and internal teams. Clients had no real-time visibility<\/strong> into their progress, often unsure of what had been submitted or what remained. Meanwhile, compliance specialists were bogged down with repetitive, manual tasks<\/strong>\u2014spending 30 to 45 minutes per case<\/strong> just to determine document requirements and follow up on missing information.<\/p>\n

Recognizing that true optimization isn\u2019t just about automation<\/strong>, but about designing scalable systems<\/strong> aligned with business processes<\/strong>, I stepped in to reimagine the experience<\/strong>. With a deep understanding of workflows and stakeholder needs<\/strong>, I saw an opportunity to use the strengths of our existing tools<\/strong>\u2014leveraging Moxo for structured onboarding<\/strong> and HubSpot for automation, workflow logic, and reporting<\/strong>.<\/p>\n

By aligning the right tools<\/strong> to the right parts of the process, we laid the groundwork for a scalable, transparent system<\/strong> that could grow with the business<\/strong>.<\/p>\n

The Problem:<\/h3>\n

Before a client could work with us, they had to meet certain regulatory and compliance requirements<\/strong> based on local government rules and internal company standards<\/strong>. However, the onboarding process was slow, manual, and lacked transparency<\/strong>, causing inefficiencies across teams.<\/p>\n

The Solution:<\/h3>\n

I replaced the flawed ticketing system<\/strong> with a structured deal pipeline in HubSpot<\/strong>, allowing us to track progress through each compliance stage<\/strong> and identify bottlenecks<\/strong>. I also automated the compliance determination process<\/strong> by expanding dynamic form logic<\/strong> and building workflows<\/strong> that generated tailored document checklists<\/strong> based on each client\u2019s services and state<\/strong>. This eliminated manual effort<\/strong>, improved accuracy<\/strong>, and reduced processing time<\/strong> from 30\u201345 minutes to just 5 minutes per client<\/strong>.<\/p>\n

Process Documentation is a Prerequisite for Automation<\/strong><\/h4>\n

A common misconception is that automation or AI can “fix” inefficiencies, but the reality is that automation is only as good as the understanding and documentation of the process it\u2019s applied to<\/strong>. If a process only exists in someone\u2019s head, and automation is built without a complete understanding of it, the automation is useless<\/strong>.<\/p>\n

This is why documentation practices are critical<\/strong>. I ensured that compliance logic was fully documented<\/strong> so that it wasn\u2019t dependent on a few individuals’ knowledge. Instead of compliance specialists manually determining requirements on a case-by-case basis, I built a structured, referenceable system<\/strong> that allowed for scalable decision-making.<\/p>\n

This documentation didn\u2019t just support automation\u2014it also created transparency<\/strong>, enabling the team to train others, troubleshoot issues, and continuously refine the process<\/strong> without bottlenecks.<\/p>\n

Stakeholder Buy-in, Training, & Implementation Velocity<\/strong><\/h4>\n

Stakeholder buy-in wasn\u2019t the only concern\u2014minimizing behavioral changes also reduced the need for extensive training<\/strong> and accelerated implementation<\/strong>. The less a process disrupts how people are used to working, the faster it can be adopted without resistance.<\/p>\n

The key wasn\u2019t just making a better system\u2014it was ensuring that the improvements worked within the natural flow<\/strong> of how stakeholders already operated, rather than forcing them to drastically change their approach. This allowed for a smoother rollout and meant that teams required far less time to get up to speed.<\/p>\n

This again highlights the importance of having someone build the process who actually understands it<\/strong>. If a system is designed without deep knowledge of how people actually work, adoption slows down, training time increases, and resistance builds. By taking a process-first approach<\/strong> and applying technical solutions where they naturally fit, I was able to remove unnecessary friction and increase velocity.<\/p>\n

Replacing the Ticketing System with a Structured Deal Pipeline<\/strong><\/h4>\n

The original ticketing system was fundamentally flawed because it only tracked when a case was opened and closed<\/strong>, making it impossible to measure progress between stages. Since ticket pipelines in HubSpot are designed for support cases, they focus only on total resolution time rather than tracking step-by-step progress.<\/p>\n

This led to several critical issues<\/strong>:<\/p>\n

    \n
  • \n

    No way to measure time spent at each stage<\/strong> \u2192 We couldn\u2019t track where clients were getting stuck.<\/p>\n<\/li>\n

  • \n

    No visibility into bottlenecks<\/strong> \u2192 There was no structured reporting on why onboarding was delayed.<\/p>\n<\/li>\n

  • \n

    Heavy manual effort<\/strong> \u2192 Compliance specialists had to manually check records to understand the status.<\/p>\n<\/li>\n<\/ul>\n

    Solution: Building a Deal Pipeline for Compliance<\/strong><\/h5>\n

    Instead of using tickets, I built a structured deal pipeline in HubSpot<\/strong> specifically for compliance tracking.<\/p>\n

      \n
    • \n

      Created two distinct pipelines<\/strong> to separate different compliance journeys:<\/p>\n

        \n
      • \n

        Business Owner Compliance Pipeline<\/strong> \u2192 Ensuring the entity was legally compliant.<\/p>\n<\/li>\n

      • \n

        Service Provider Compliance Pipeline<\/strong> \u2192 Ensuring the individual provider met all regulatory requirements.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n

      • \n

        Designed deal stages<\/strong> that mapped to the actual compliance process<\/strong> instead of just \u201copen\u201d or \u201cclosed.\u201d<\/p>\n<\/li>\n

      • \n

        Implemented workflow automations<\/strong> to progress deals based on milestone completions.<\/p>\n<\/li>\n<\/ul>\n

        Automating Compliance Determination with Dynamic Forms & Workflows<\/strong><\/h3>\n

        One of the biggest inefficiencies was that compliance specialists manually determined document requirements on a case-by-case basis, which was time-consuming and prone to inconsistencies.<\/p>\n

        The core issue was that compliance requirements were dependent on two variables:<\/strong><\/p>\n

          \n
        • \n

          The services the client intended to offer<\/strong> \u2192 Each service had its own unique documentation requirements.<\/p>\n<\/li>\n

        • \n

          The regulatory requirements of the state they operated in<\/strong> \u2192 Different states required different compliance steps.<\/p>\n<\/li>\n<\/ul>\n

          This meant that compliance specialists had to cross-reference multiple factors without a structured system<\/strong>, relying on memory or internal documents. As we expanded, this would become unmanageable and error-prone<\/strong>.<\/p>\n

          Solution: Expanding the Form Logic & Automating Document Determination<\/strong><\/h4>\n

          To eliminate manual document determination<\/strong>, I built an automated compliance workflow in HubSpot:<\/p>\n

            \n
          • \n

            Expanded the existing dynamic form<\/strong> to account for all necessary variables, ensuring that all compliance requirements were captured<\/strong>.<\/p>\n<\/li>\n

          • \n

            Removed document uploads from the form entirely<\/strong>, allowing clients to complete the questionnaire quickly<\/strong>.<\/p>\n<\/li>\n

          • \n

            Created a custom HubSpot CRM property<\/strong> that stored the required compliance documents<\/strong> specific to each client\u2019s responses.<\/p>\n<\/li>\n

          • \n

            Built multiple workflows<\/strong> that analyzed the form responses, determined which documents were required, and updated the custom property<\/strong> to create a customized checklist<\/strong> for each client.<\/p>\n<\/li>\n

          • \n

            Upon form completion<\/strong>, the checklist was automatically emailed<\/strong> to the compliance specialist, eliminating the need for manual assessment<\/strong>.<\/p>\n<\/li>\n<\/ul>\n

            This meant that compliance specialists were no longer spending 30-45 minutes manually determining requirements<\/strong>\u2014the system did it instantly, reducing the task to 5 minutes per client<\/strong>.<\/p>\n

            Results and Impact<\/h2>\n
              \n
            • Reduced the manual effort required for compliance specialists\u2014document determination previously took 30-45 minutes per client and was reduced to 5 minutes, freeing up significant time.<\/span><\/li>\n
            • Enabled specialists to handle more clients per month by removing the need for manual cross-referencing and decision-making, allowing them to focus on higher-value tasks.<\/span><\/li>\n
            • Eliminated client confusion by replacing a cumbersome, one-time upload form with a step-by-step onboarding experience that allowed for phased document submission.<\/span><\/li>\n
            • Provided real-time visibility into onboarding progress<\/strong> through a structured deal pipeline<\/strong>, replacing the ticketing system\u2019s limited tracking capabilities.<\/span><\/li>\n<\/ul>\n
                \n
              • Created a scalable compliance framework<\/strong> that automatically adapts to different service offerings and state regulations<\/strong>, ensuring that as the company expands, compliance requirements do not become a bottleneck.<\/span><\/li>\n
              • Established a fully documented compliance process<\/strong>\u2014where all roles, responsibilities, and steps are now clearly defined. Instead of relying on individual\u2019s knowledge, new team members can now quickly understand the process.<\/span><\/li>\n
              • Conducted extensive stakeholder interviews<\/strong> to map out who was responsible for what<\/strong>, what they were collecting, and how the process flowed across teams. These conversations were critical\u2014not only did they ensure the automation was built with a deep understanding of real-world operations<\/strong>, but they also built trust with stakeholders, reducing friction and increasing adoption<\/strong>.<\/span><\/li>\n
              • Standardized workflows ensure accuracy and consistency, eliminating the previous variability in compliance determinations that resulted from specialists manually reviewing requirements.<\/span><\/li>\n<\/ul>\n
                  \n
                • Increased operational scalability\u2014By reducing manual workload, the company can scale onboarding without increasing headcount, making growth more cost-efficient.<\/span><\/li>\n
                • Reduced training and implementation time\u2014Because the new process preserved how teams naturally worked, onboarding specialists required less training and the rollout was significantly faster than if an entirely new system had been introduced.<\/span><\/li>\n
                • Improved data hygiene and reporting accuracy<\/strong>\u2014By moving to a structured pipeline<\/strong>, compliance progress is now accurately tracked in real-time<\/strong> instead of relying on inconsistent manual updates, improving the accuracy of compliance reporting.<\/span><\/li>\n<\/ul>\n

                  Takeaways & Lessons Learned<\/strong><\/h3>\n

                  1. Stakeholder Buy-in & Process Familiarity<\/strong>Stakeholder buy-in isn\u2019t just about securing agreement\u2014it\u2019s about reducing the friction of adoption<\/strong>. By designing a process that minimized required behavioral changes<\/strong>, I reduced training time, accelerated implementation, and increased overall adoption. The key was ensuring that changes preserved stakeholder workflows while improving efficiency<\/strong>, rather than forcing a disruptive shift.<\/p>\n

                  This again highlights the importance of having someone with deep process knowledge<\/strong> design solutions. A technical implementation alone isn\u2019t enough\u2014without a strong understanding of how people interact with the system<\/strong>, adoption will suffer, and friction will increase.<\/p>\n

                  2. Process Documentation is a Prerequisite for Automation<\/strong>A common misconception is that automation or AI can \u201cfix\u201d inefficiencies<\/strong>, but automation is only as good as the understanding and documentation of the process it\u2019s applied to<\/strong>. If a process only exists in someone\u2019s head and isn\u2019t properly documented, automation is ineffective<\/strong>.<\/p>\n

                  Documenting compliance logic was critical\u2014instead of relying on a few individuals\u2019 expertise, I structured a referenceable system<\/strong> that allowed for scalable, repeatable decision-making<\/strong>. This ensured that new team members could quickly learn the process, automation could be built properly, and ongoing improvements could be made without starting from scratch each time.<\/strong><\/p>\n

                  3. No Single Tool is a Silver Bullet\u2014Understanding the Process is Key<\/strong>The expectation when adopting new tools is often that they\u2019ll \u201cfix\u201d operational problems, but tools are only as effective as the strategy behind their use<\/strong>. The key isn\u2019t just picking the right tools\u2014it\u2019s having a holistic understanding of the process<\/strong> and knowing how to leverage each tool\u2019s strengths where they naturally fit.<\/strong><\/p>\n

                    \n
                  • \n

                    Moxo<\/strong> was ideal for structured, phased onboarding and document collection but lacked advanced automation and reporting capabilities.<\/strong><\/p>\n<\/li>\n

                  • \n

                    HubSpot<\/strong> provided powerful automation, logic-based workflows, and reporting, but wasn\u2019t built for managing a step-by-step onboarding experience.<\/strong><\/p>\n<\/li>\n<\/ul>\n

                    By deeply understanding both the process and the tools<\/strong>, I was able to design a system where Moxo handled what it did best<\/strong> while HubSpot provided the automation and transparency<\/strong> needed for scale. This approach eliminated inefficiencies while ensuring stakeholder adoption.<\/strong><\/p>\n

                    4. Future-Proofing Requires Proactive Problem Solving<\/strong>At the time of implementation, leadership hadn\u2019t yet felt the full pain of inefficiencies in compliance tracking\u2014but I recognized that as the company expanded, the current process would become an operational bottleneck.<\/strong><\/p>\n

                    By proactively designing a scalable, automated compliance framework<\/strong>, I ensured that the company could grow without compliance becoming a hiring or workload constraint<\/strong>. Thinking ahead, rather than reacting to problems only when they arise, was essential in ensuring the longevity of this system.<\/p>\n

                    5. Process Ownership Matters\u2014Systems Need a Clear Owner<\/strong>One major inefficiency was that compliance knowledge was fragmented across multiple people<\/strong>, meaning that determining requirements relied on who you asked<\/strong> rather than a standardized system. This created bottlenecks and inconsistencies.<\/p>\n

                    By taking ownership of the process<\/strong>, I structured compliance determination into a single, documented framework<\/strong>, eliminating reliance on individual knowledge. This ensured consistency, reduced errors, and allowed the system to scale beyond individual expertise.<\/strong><\/p>\n

                    6. Process Iteration is Just as Important as Initial Implementation<\/strong>A common mistake in automation is assuming that once a system is built, it\u2019s ‘done.’<\/strong> But real-world adoption often reveals unexpected challenges.<\/p>\n

                    After launching this system, I actively gathered stakeholder feedback<\/strong>, monitored friction points, and adjusted workflows<\/strong> where needed. This iterative approach ensured that the process didn\u2019t just look good on paper\u2014it actually worked seamlessly in daily operations<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"

                    The Story As our company planned expansion into new states, our compliance onboarding process was a clear bottleneck. One that would only grow worse over time. Each client was required to meet a unique set of regulatory and internal requirements, but the existing system was manual, inefficient, and lacked transparency. Clients had to submit all documents through a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-254","post","type-post","status-publish","format-standard","hentry","category-blog","post-wrapper","thrv_wrapper"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/aboutpetertran.com\/index.php?rest_route=\/wp\/v2\/posts\/254","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aboutpetertran.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aboutpetertran.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aboutpetertran.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aboutpetertran.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=254"}],"version-history":[{"count":9,"href":"https:\/\/aboutpetertran.com\/index.php?rest_route=\/wp\/v2\/posts\/254\/revisions"}],"predecessor-version":[{"id":272,"href":"https:\/\/aboutpetertran.com\/index.php?rest_route=\/wp\/v2\/posts\/254\/revisions\/272"}],"wp:attachment":[{"href":"https:\/\/aboutpetertran.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=254"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aboutpetertran.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=254"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aboutpetertran.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=254"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}