Product & software builds
A business-critical sourcing platform, lifted off a dying stack.
A ~278-table Microsoft-SQL/IIS application rebuilt onto Laravel, React, and Postgres, then run as a managed service.
A competitive-bidding platform for enterprise telecom procurement was running on an aging Microsoft SQL Server / IIS stack. A sourcing team publishes structured RFPs, carriers submit priced bids under NDA, and the team scores them toward an award. Business-critical, but near end-of-life and costly to change. Its whole value is running fair, auditable, on-time sourcing events; a brittle platform put that at risk.
We lifted the full ~278-table legacy schema onto a modern stack, a Laravel API and a React single-page app on PostgreSQL, through a documented migration toolchain that dumped the SQL Server structure, converted the old naming to clean, current conventions across 280 versioned migrations, and loaded it into Postgres. On that foundation we carried the entire sourcing workflow: RFP authoring with compliance templates, rate templates across nine telecom service types, the carrier response side with bulk import/export, and the evaluation engine: decision matrices, reverse-auction analysis, and total-cost-of-ownership modeling. Then we containerized it with CI-built images and now run it as a managed service on self-hosted infrastructure.
- The business-critical platform is off a dying Microsoft stack and onto one the team can actually maintain and extend. The end-of-life risk is retired.
- Years of real carrier pricing data survived the migration intact; no institutional knowledge was lost in the cutover.
- It now runs as a managed service on owned infrastructure: hosting, email, and cloud handled by one accountable team instead of a retired platform and an absent vendor.
- Every sourcing event runs on a modern, auditable system, protecting the fairness and defensibility the product’s entire value depends on.
in production as a managed service
carrier pricing migrated intact
end-of-life risk retired
every sourcing event defensible
Client name and identifying details withheld by design. Every figure here is drawn from the system we actually delivered.
More case studies
All workMembership & advocacy · Organization-wide platform
One operating platform for a 600,000-supporter organization.
ReadData architecture · Coordinated back-office systems
Four department systems that finally agree on who someone is.
ReadCommunications · Deliverability engineering
A self-hosted email operating system, built to survive Gmail.
ReadYour work would get the same discretion.
Tell us what's breaking. We'll tell you whether we've solved something like it. And if we take it on, your name stays yours.
Start with a diagnostic