Software examples

Custom software and legacy .NET modernization case studies

Two engagements show how focused software delivery can validate a new product while protecting a core roadmap and modernize a legacy order-intake workflow while preserving its operational requirements.

Two client case studies

New software and older systems both start with a business need

Explore custom software development for a new SaaS product and legacy .NET modernization for a production workflow.

Kansas City Union Station
Custom software and modernization from a Kansas City team.

Client engagement 01

Validating a new SaaS product without pulling the core team away

Situation

A SaaS company saw an opportunity for a product that analyzed webpages and reported information and statistics about their content. Its existing development teams still needed to concentrate on the company's core product.

Business constraint

Speed mattered because a competitor could pursue the same idea. The company also needed a disciplined way to stop if a milestone failed, limiting prototype cost and protecting its core roadmap.

Transcendent's role

Transcendent Software developed the product through a sequence of working milestones, keeping each next step contingent on what the preceding increment proved.

Approach

  1. Break the product concept into small, testable increments

  2. Deliver a working result at each milestone before advancing

  3. Keep explicit stop conditions around competition, feasibility, and cost

Outcome

The milestone-based delivery model let the company validate and advance the new product while its internal engineering teams remained focused on the core platform.

What this engagement demonstrates

A focused external product team can help an organization pursue a new opportunity without sacrificing the delivery capacity committed to its core business.

Client engagement 02

Modernizing email order intake for production operations

Situation

A business-critical Windows Forms application built on .NET Framework handled orders received by email and converted them into jobs sent to the production floor. It relied on Microsoft Outlook, Adobe Acrobat, and other third-party applications.

Business constraint

The application drove production jobs, so modernization had to preserve the operational requirements of the existing order-to-production workflow.

Transcendent's role

Transcendent Software converted the legacy order-intake application into a modular system with Windows Services and a web interface.

Approach

  1. Ground modernization in the email-to-production workflow

  2. Carry its business-critical operational requirements into the modernization work

  3. Move background processing into .NET 10 Windows Services within a modular, service-oriented architecture

  4. Build the portable web UI with ASP.NET and Blazor

  5. Use SQLite for portable, centralized settings storage

Outcome

The modernized application preserved the workflow’s operational requirements, reduced third-party dependencies, and provided a portable web UI and settings store.

What this engagement demonstrates

Operational context is essential when modernizing legacy software connected directly to production.

Let’s talk about your software

Have an idea to build or a system to improve?

Tell us what the software needs to do and what’s getting in the way. We’ll help work through the options and a sensible next step.

Continue exploring