FAQ
Common questions.
How engagements work, what we build, how infrastructure is managed, and the stack behind it all.
About The Lobbi
What does “operational systems engineering” mean?
We design and build the automation, data pipelines, and custom apps that make your operations measurable and self-correcting. Not consulting, not templates - production systems delivered to your environment.
What industries do you work with?
Primarily regulated and process-heavy businesses: insurance carriers and brokerages, mortgage origination and servicing, property management, field services, and financial operations. If your team runs on spreadsheets and manual approvals, we can help.
Are you a consulting firm?
No. Consulting firms bill by the hour and deliver recommendations. We bill by deliverable and ship working systems. You know exactly what you're getting before we start.
Who manages the infrastructure?
We do. The Lobbi builds the system and hosts it on infrastructure we manage. Your team logs in and uses it - no IT burden, no on-call obligation. If you stop the engagement, we wind down gracefully with no penalty.
Who owns the code and infrastructure?
You do. Every application, pipeline, and dashboard we build transfers fully to your environment. We are not a lock-in vendor.
Engagements
How do engagements start?
Every engagement starts with a 2 - 3 week Discovery. We map your manual processes, integrations, and data flows, then deliver a prioritized roadmap with defined scope and documented ROI.
How long does a typical build take?
Automation builds and dashboard implementations typically run 4 - 8 weeks. Custom .NET applications with complex integrations run 8 - 16 weeks. Every engagement has a defined timeline upfront.
Do you offer ongoing support after delivery?
Yes. Post-delivery support packages are available for bug fixes, enhancements, and operational monitoring. These are separate from the build engagement and are optional.
What is the minimum engagement size?
The Discovery engagement starts at a fixed fee and can be completed independently. Build engagements are scoped and priced based on complexity - there's no arbitrary minimum.
Technical
What tech stack do you use?
Microsoft Power Platform (Power Automate, Power Apps, Power BI), Azure (Functions, Service Bus, SQL, Container Apps), Microsoft Teams and SharePoint integrations, Copilot Studio, and custom .NET 8 applications with Blazor Server or ASP.NET Core.
Can you integrate with our existing systems?
Yes. Legacy carrier APIs, AMS exports, non-standard data formats - this is our specialty. We take on integrations that low-code platforms can't handle.
Do you use AI?
Yes, where it delivers measurable value. Copilot Studio agents for scoped workflows, Azure OpenAI for document classification and extraction, and decision-support layers embedded inside governed approval workflows.
What's the difference between Power Automate and a custom .NET app?
Power Automate works well for approval chains, routing, and Microsoft 365 integrations. Custom .NET makes more sense when you need complex business logic, legacy integrations, or performance that low-code can't deliver. We'll help you figure out which fits your situation.
Still have questions?
Talk to us directly.
Send us a message. We'll review your operational challenge and respond within one business day - no sales pitch, no commitment.