{"version":"https://jsonfeed.org/version/1.1","title":"The Lobbi Insights","home_page_url":"https://thelobbi.io/insights","feed_url":"https://thelobbi.io/insights/feed.json","description":"Operational intelligence, systems thinking, and engineering guidance from The Lobbi.","items":[{"id":"https://thelobbi.io/insights/the-spreadsheet-that-runs-your-business","url":"https://thelobbi.io/insights/the-spreadsheet-that-runs-your-business","title":"The Critical Spreadsheet Every Business Depends On","summary":"Every company has a mission-critical spreadsheet nobody else understands. Here is why it exists, what it actually costs, and when to replace it.","content_text":"Every company has one. It lives on someone's desktop or a shared drive with a name like 'Master Tracker FINAL v3 (2) - Copy.xlsx.' It has 47 tabs, formulas that reference other files, and exactly one person who understands how it works. If that person is out sick, the operation slows down. If they leave, it stops.","date_published":"2026-04-09T00:00:00.000Z","tags":["spreadsheets","operations","process","tribal-knowledge","risk"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/microsoft-copilot-operations-reality","url":"https://thelobbi.io/insights/microsoft-copilot-operations-reality","title":"Microsoft Copilot in Operations - Real Capabilities","summary":"Where Microsoft Copilot delivers genuine operational value and where it stops. A framework for regulated businesses evaluating AI adoption.","content_text":"Microsoft Copilot is genuinely useful - inside a narrow band. Understanding exactly where that band ends is the difference between a productivity win and a six-figure disappointment.","date_published":"2026-04-08T00:00:00.000Z","tags":["microsoft-copilot","ai","automation","strategy","regulated-industries"],"authors":[{"name":"Markus Ahling"}]},{"id":"https://thelobbi.io/insights/ops-person-holds-it-together-about-to-quit","url":"https://thelobbi.io/insights/ops-person-holds-it-together-about-to-quit","title":"Your Operations Glue Person Is Burning Out","summary":"The person who holds the operation together is burning out on workarounds. What happens next - and what to do before they give notice.","content_text":"They trained everyone. They built the workarounds. They absorbed three years of increasing complexity without complaint. They are the person everybody calls when something breaks. And right now, they are updating their resume.","date_published":"2026-04-07T00:00:00.000Z","tags":["burnout","retention","operations","leadership","culture"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/automation-market-april-2026-landscape","url":"https://thelobbi.io/insights/automation-market-april-2026-landscape","title":"Automation Market April 2026: Who Builds, Who Consults","summary":"The BPA market hit $18.83B in 2026. Analysis of provider tiers, macro signals, and what separates firms that deliver from firms that consult.","content_text":"The business process automation market hit $18.83B in 2026, up 15.4% year-over-year. Not every firm selling automation is actually building anything. Here is what the landscape looks like, what macroeconomic headwinds mean for buying decisions, and what separates firms that deliver from firms that consult.","date_published":"2026-04-06T00:00:00.000Z","tags":["market-intelligence","automation","custom-engineering","regulated-industries"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/integration-tax-connecting-systems","url":"https://thelobbi.io/insights/integration-tax-connecting-systems","title":"Why System Integrations Cost More Than Expected","summary":"Every integration estimate is wrong. Undocumented APIs, dirty data, and edge case multiplication are why. Here is the engineering reality.","content_text":"Every integration estimate is wrong by the same amount, for the same reasons. Undocumented API behavior, data normalization, and edge case multiplication form a predictable tax that most teams only discover during the build.","date_published":"2026-04-04T00:00:00.000Z","tags":["integration","engineering","api","data-normalization","architecture"],"authors":[{"name":"Markus Ahling"}]},{"id":"https://thelobbi.io/insights/best-employee-biggest-risk","url":"https://thelobbi.io/insights/best-employee-biggest-risk","title":"Key-Person Risk in Business Operations","summary":"Your most reliable employee is your biggest operational risk. Tribal knowledge, undocumented processes, and single points of failure are systems problems, not people problems.","content_text":"The person who knows where everything is, how everything works, and what to do when it breaks. They are indispensable - and that is the problem. Indispensable means the operation cannot function without them. That is not a compliment. It is a risk.","date_published":"2026-04-02T00:00:00.000Z","tags":["tribal-knowledge","risk","operations","leadership","process"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/mapping-your-operation-before-you-automate","url":"https://thelobbi.io/insights/mapping-your-operation-before-you-automate","title":"Map Your Operation Before You Automate It","summary":"The diagnostic framework that belongs before any automation build. Three questions, structured investigation, and a prioritized roadmap.","content_text":"Most automation projects fail not because the technology is wrong but because the problem was never properly defined. Here is the diagnostic framework that belongs before any line of code.","date_published":"2026-04-01T00:00:00.000Z","tags":[],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/meeting-that-should-have-been-a-dashboard","url":"https://thelobbi.io/insights/meeting-that-should-have-been-a-dashboard","title":"Replace Status Meetings with Operational Dashboards","summary":"Most status meetings exist because the data is not accessible. Replace the meeting with a dashboard and give everyone an hour back every week.","content_text":"If a recurring meeting exists so people can share status updates and ask 'where are we on this?' - the meeting is a symptom. The actual problem is that the data those people need is not accessible without assembling everyone in a room.","date_published":"2026-03-30T00:00:00.000Z","tags":["meetings","dashboards","visibility","operations","leadership"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/fixed-scope-vs-hourly-billing","url":"https://thelobbi.io/insights/fixed-scope-vs-hourly-billing","title":"Fixed-Scope vs Hourly: Aligning Vendor Incentives","summary":"Hourly billing misaligns vendor incentives. Fixed-scope pricing requires diagnostic precision but inverts the risk. Here is what the model requires.","content_text":"Hourly billing creates a fundamental misalignment: the vendor benefits from complexity, the client bears the risk of unknowns. Fixed-scope pricing inverts that dynamic. Here is what the model requires and where it breaks down.","date_published":"2026-03-28T00:00:00.000Z","tags":[],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/onboarding-process-losing-clients","url":"https://thelobbi.io/insights/onboarding-process-losing-clients","title":"Client Onboarding Automation for Service Businesses","summary":"Client onboarding is where deals go to die. The first 72 hours determine retention. Here is what a modern onboarding system looks like.","content_text":"The first 72 hours after a client says yes determines whether they stay. If your onboarding involves emailed PDFs, manual follow-ups, and a week of silence while paperwork is processed, you are losing clients before the relationship begins.","date_published":"2026-03-25T00:00:00.000Z","tags":["onboarding","client-experience","automation","operations","process"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/operational-visibility-beyond-dashboards","url":"https://thelobbi.io/insights/operational-visibility-beyond-dashboards","title":"What Operational Visibility Actually Means","summary":"Dashboards deliver reporting, not decision support. Real operational visibility requires instrumented workflows and event-driven architecture.","content_text":"Most teams that want better visibility build dashboards nobody uses after the first month. Operational visibility is decision support - the right information at the right moment in the workflow.","date_published":"2026-03-24T00:00:00.000Z","tags":[],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/nobody-reads-process-documentation","url":"https://thelobbi.io/insights/nobody-reads-process-documentation","title":"Why Process Documentation Fails - And What Works","summary":"Process manuals become fiction within six months. The problem is not discipline - it is that documentation and execution are separate systems. Here is the alternative.","content_text":"You spent two weeks writing the process manual. It lives in a SharePoint folder. Six months later, the actual process has drifted, new hires learn by watching the person next to them, and the manual is fiction. The documentation failed - but not because of laziness. The medium is wrong.","date_published":"2026-03-22T00:00:00.000Z","tags":["documentation","process","training","operations","knowledge-management"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/commission-reconciliation-data-problem","url":"https://thelobbi.io/insights/commission-reconciliation-data-problem","title":"Commission Reconciliation Automation for FMOs","summary":"Commission reconciliation is a data normalization problem, not a staffing problem. Here is the engineering approach that reduces 180-hour cycles to 12.","content_text":"Throwing more people at commission reconciliation does not fix it. The problem is structural - multiple carrier feeds, inconsistent schemas, no canonical source of truth. The solution is a data normalization pipeline, not a bigger team.","date_published":"2026-03-20T00:00:00.000Z","tags":["commission-reconciliation","insurance","data-normalization","fmo","automation"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/stop-hiring-for-problems-you-should-automate","url":"https://thelobbi.io/insights/stop-hiring-for-problems-you-should-automate","title":"Automation vs. Hiring for Operational Capacity","summary":"When the team is overwhelmed, hiring scales cost linearly. Automation scales capacity. Here is the decision framework for when to hire and when to build.","content_text":"When the team is overwhelmed, the reflex is to hire. But if the work overwhelming them is repetitive, rule-based, and high-volume, adding a person scales the cost linearly without changing the fundamental capacity problem. A system scales the capacity without scaling the cost.","date_published":"2026-03-18T00:00:00.000Z","tags":["hiring","automation","strategy","capacity","operations"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/power-automate-vs-custom-code-decision","url":"https://thelobbi.io/insights/power-automate-vs-custom-code-decision","title":"Power Automate vs Custom Code: A Decision Framework","summary":"The decision between Power Automate and custom code depends on integration depth, exception volume, compliance, and total cost of ownership.","content_text":"The decision is not ideological. It is a function of integration depth, exception volume, compliance requirements, and total cost of ownership. Here is the decision framework.","date_published":"2026-03-17T00:00:00.000Z","tags":[],"authors":[{"name":"Markus Ahling"}]},{"id":"https://thelobbi.io/insights/power-automate-flows-breaking-under-load","url":"https://thelobbi.io/insights/power-automate-flows-breaking-under-load","title":"Why Power Automate Flows Break Under Load","summary":"Most Power Automate failures are architectural, not logical. Throttling ceilings, concurrency defaults, and trigger design cause production breakdowns.","content_text":"Most Power Automate failures are not bugs. They are architectural decisions that work at low volume and collapse under production traffic. Here is the pattern behind most breakdowns and the structural fix.","date_published":"2026-03-15T00:00:00.000Z","tags":[],"authors":[{"name":"Markus Ahling"}]},{"id":"https://thelobbi.io/insights/data-when-you-cancel-saas-subscription","url":"https://thelobbi.io/insights/data-when-you-cancel-saas-subscription","title":"SaaS Data Portability - What You Actually Get","summary":"When you cancel a SaaS subscription, your data export is rarely usable. Here is what data portability actually means and how to protect yourself.","content_text":"Every SaaS vendor says you own your data. They are technically correct - you do own it. What they do not mention is that the data export they provide is a flat file dump with no relationships, no workflow history, and a format that nothing else can import without significant engineering work.","date_published":"2026-03-14T00:00:00.000Z","tags":["saas","data-portability","vendor-lock-in","strategy","operations"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/measure-automation-roi-after-go-live","url":"https://thelobbi.io/insights/measure-automation-roi-after-go-live","title":"Measuring Automation ROI After Deployment","summary":"Pre-build ROI projections are easy. Post-deployment measurement is where most teams fail. A framework for closing the loop on automation investments.","content_text":"Every automation project has a projected ROI. Almost nobody measures the actual ROI after deployment. The pre-build estimate is a sales tool. The post-deployment measurement is an engineering discipline - and it is where the real learning happens.","date_published":"2026-03-12T00:00:00.000Z","tags":["roi","measurement","strategy","automation","operations"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/insurance-quote-to-bind-automation","url":"https://thelobbi.io/insights/insurance-quote-to-bind-automation","title":"Automating Insurance Quote-to-Bind Workflows","summary":"What a fully automated quote-to-bind process looks like for independent agencies: carrier API integration, AMS sync, and the operational dashboard.","content_text":"The quote-to-bind workflow in most independent insurance agencies still runs through carrier portals, email, and shared Excel files. Here is what a fully automated version looks like and what it takes to build one.","date_published":"2026-03-10T00:00:00.000Z","tags":[],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/how-to-scope-automation-project","url":"https://thelobbi.io/insights/how-to-scope-automation-project","title":"How to Scope an Automation Project That Ships","summary":"The five components of a complete automation scope: trigger, transformation, exceptions, acceptance criteria, and boundaries. Most scopes miss three.","content_text":"Most automation projects that fail do so at the scoping stage. Vague requirements, scope creep, and undefined success criteria are predictable failure modes. Here is what a complete scope looks like.","date_published":"2026-03-10T00:00:00.000Z","tags":[],"authors":[{"name":"Markus Ahling"}]},{"id":"https://thelobbi.io/insights/90-day-trap-new-software-honeymoon","url":"https://thelobbi.io/insights/90-day-trap-new-software-honeymoon","title":"Why New Software Fails After 90 Days","summary":"New software always works for the first 90 days. Then adoption stalls, workarounds return, and the old process runs in parallel. Here is why and how to prevent it.","content_text":"New software always works great for the first 90 days. Adoption is high, the team is optimistic, the old problems seem solved. Then the exceptions pile up, the workarounds return, and six months later the team is running two systems instead of one.","date_published":"2026-03-08T00:00:00.000Z","tags":["software-adoption","operations","process","change-management","tools"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/two-questions-operation-can-scale","url":"https://thelobbi.io/insights/two-questions-operation-can-scale","title":"Can Your Operation Scale? Two Diagnostic Questions","summary":"Two questions predict whether your operation can scale: does volume require headcount, and does headcount require management? The answers determine your growth ceiling.","content_text":"Every scaling problem reduces to two questions. Does more volume require more people? Does more people require more management? If both answers are yes, the operation has a growth ceiling determined by how fast you can hire and how much management overhead you can absorb.","date_published":"2026-03-05T00:00:00.000Z","tags":["scaling","growth","operations","strategy","leadership"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/real-cost-of-manual-data-entry","url":"https://thelobbi.io/insights/real-cost-of-manual-data-entry","title":"The Real Cost of Manual Data Entry","summary":"Manual data entry costs 3-5x what operations teams measure. Downstream errors, reconciliation cycles, and the trust deficit are what actually compound.","content_text":"Every operations leader knows manual data entry is expensive. Most measure the wrong cost. Downstream errors, reconciliation cycles, and the trust deficit are what actually compound.","date_published":"2026-03-01T00:00:00.000Z","tags":[],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/three-layers-every-operational-system-needs","url":"https://thelobbi.io/insights/three-layers-every-operational-system-needs","title":"The Three Layers Every Operational System Needs","summary":"Visibility, routing, and execution - the three layers missing from most operations. Why the build order matters and how to get it right.","content_text":"The same three missing layers appear in almost every broken operation across insurance, mortgage, and field services: visibility, routing, and execution. Here is what each one means and why the build order matters.","date_published":"2026-02-28T00:00:00.000Z","tags":[],"authors":[{"name":"Markus Ahling"}]},{"id":"https://thelobbi.io/insights/vendor-demo-looked-nothing-like-reality","url":"https://thelobbi.io/insights/vendor-demo-looked-nothing-like-reality","title":"Why Software Demos Never Match Reality","summary":"Software demos show perfect data in perfect workflows. Your reality has 14 exception paths and dirty data. Here is how to evaluate software against your actual process.","content_text":"The demo was flawless. Clean data, logical workflow, three clicks to resolution. Then the software met your actual operation - with its messy data, exception paths, and users who do things differently from each other. The gap between the demo and reality is where six-figure disappointments are born.","date_published":"2026-02-25T00:00:00.000Z","tags":["software-evaluation","vendor-management","operations","decision-making"],"authors":[{"name":"The Lobbi Delivery Team"}]},{"id":"https://thelobbi.io/insights/map-your-process-before-buying-saas","url":"https://thelobbi.io/insights/map-your-process-before-buying-saas","title":"Map Your Process Before Buying SaaS","summary":"Buying software to solve an unmapped process creates friction, not solutions. The diagnostic that should come before any purchase decision.","content_text":"The most expensive mistake operations teams make is buying software to solve a process problem they have not mapped. The tool becomes a new source of friction instead of a solution.","date_published":"2026-02-10T00:00:00.000Z","tags":[],"authors":[{"name":"The Lobbi Delivery Team"}]}]}