// case study
Tele Business USA
Their operations platform had served them well — until the system it ran on became the bottleneck. When a foundation stops supporting the business built on top of it, you don't patch it forever. You replace it properly.
Where they started
Tele Business USA specializes in business-to-business tele-services. For years, their operations ran on a Microsoft Access application that communicated with Microsip services. Access is a capable tool in the right context — but that context has limits.
As the business grew, those limits started showing. A system that worked fine for one or two people became harder to maintain as more staff needed to use it simultaneously. The codebase had grown organically over time and was becoming increasingly fragile to change — adding new survey types, adjusting workflows, or customizing forms for specific clients required more effort than it should. And the concurrency model of an Access database just wasn't designed for the volume they were moving toward.
The team had a running list of things they wished the platform could do. Not exotic things — just the configuration flexibility and operational tools that a growing B2B operation actually needs. None of it was practical in the existing system without significant rework of something that was increasingly risky to touch.
What we built
A custom ASP.NET Core 9 MVC application backed by SQL Server — designed from the start around the assumption that the business should be able to configure it, not just use it. The new system preserves the Microsip service integration the business depends on while replacing everything else with a proper web stack.
Flexible survey creation and management
Getting a survey live went from a developer task to a configuration task. The team can define questions, set response options, configure branching logic, and publish — without writing code or waiting on IT. What used to take days takes minutes.
Deep backend configuration
Workflows, response handling, notifications, data exports — all configurable from the admin backend. The system was architected around the certainty that requirements change, because in a B2B environment they always do. New client requirements, new service types, new reporting needs — all handled through configuration, not code changes.
WebAPI and webhook integration
The platform exposes a WebAPI layer and supports webhooks, letting it connect to external systems and react to events in real time. This was especially important for maintaining the Microsip integration that underpins the core business workflow.
Built to scale
The architecture was designed from the start to handle concurrent users and growing data volumes. The Access concurrency issues — where the system's behavior under load was unpredictable — were resolved at the data and application layers, not worked around with workarounds layered on top.
Technical stack
The result
Tele Business USA moved from a system that had become a bottleneck to one that actively supports how their business operates today. New surveys go live faster. Backend configuration is something the team handles themselves. The Microsip integration that drives their core workflow is preserved and stable. And the platform has room to grow — which is what made the rebuild worth doing.
This is what the right rebuild looks like: not a feature-for-feature copy of what existed before, but a system redesigned around what the business needs to do next.
Is your system becoming a ceiling?
If you're working around your own software instead of with it — if the list of things it can't do is longer than the list of things it can — that's worth a conversation. Sometimes the answer is a targeted fix. Sometimes it's a real rebuild. Let's figure out which one you're looking at.