Billing platforms
We have architected and delivered production microservices and backend services for billing, invoice processing, data gathering, and integrations. One platform we helped shape supports ~100,000 API requests per day for about 1,000 users across roughly 10 million invoices.
- Service boundaries and API design that operations can actually support
- SQL Server / EF Core work under real data volume
- Observability and on-call practices (PagerDuty, Datadog) instead of “hope and email”
AMI and metering workflows
Metering issues hide in shared folders and overnight jobs. We consolidated seven manual document workflows into a single dashboard for about 100 internal users, replaced spreadsheet and email chains with auditable processes, and cut time to resolution by about 40%.
When to call
If billing or AMI work is blocked on architecture, reliability, or a modernization path that will survive the next audit, we should talk. Related: legacy .NET modernization and selected work.