Case studies

Problem

Technical debt was slowing the product: outdated Angular, manual deployments, an incomplete QuickBooks integration, and a mobile app that could no longer ship.

What we found

Deprecated Cordova mobile tooling, an expired Android developer account, features left incomplete by an old QuickBooks integration, and a production TLS certificate problem.

Result

Current Angular in an Nx monorepo, CI/CD into AWS, secrets in Secrets Manager, a working QuickBooks integration, and mobile apps that can ship again.

Problem

Feature development had stopped. Releases shipped with bugs, and a system defect let purchases go through outside approved price ranges.

What we found

Environments that did not match, no formal delivery process, hardcoded payment API credentials, and old VPN and SSH access nobody had reviewed.

Result

Four aligned environments, one agile process in Jira, rotated credentials with least-privilege access, and features that ship predictably.

Angular 7 to 17and .NET Core 3.1 to .NET 8 (LTS)

Problem

Angular 7 and .NET Core 3.1 nearing end of life, failing test suites, and infrastructure that depended on a third party.

What we found

Jest and Cypress suites that broke during the upgrade, an end-of-life identity server, WordPress plugins that failed on PHP 8, and a planned Azure subscription transfer that risked major downtime.

Result

Angular 7 to 17, .NET Core 3.1 to .NET 8, working test suites, and repositories, pipelines and documents in an Azure DevOps environment PSIA owns.

Problem

A secure healthcare exchange portal with a tight contractual deadline, an under-resourced team, and little experience with React and TypeScript.

What we found

One shared integration environment, schema changes applied by hand, front-end changes that broke other screens, and back end and front end out of sync.

Result

Delivered on time, with TypeScript throughout, local Docker environments, database migrations in code, and automated tests.

2,137customer accounts created in Microsoft Entra on release night, with zero errors

Problem

An independent security assessment flagged critical weaknesses in a live portal that thousands of members use every day.

What we found

Credentials stored in the portal's own database with no second factor, internal services that did not check callers, hardcoded secrets, and manual releases.

Result

MFA sign-in through Microsoft Entra, every service verifying every caller, secrets in Key Vault, and automated, scanned releases. 2,137 accounts migrated with zero errors.

9 daysearly: every release feature done by April 21, ahead of the April 30, 2025 release date

Problem

A rebuild of the contractor mobile app from AngularJS to modern Angular, with a hard April 30, 2025 release date and not enough velocity to hit it.

What we found

A technical assessment measured velocity against the backlog and sized the gap: three Angular engineers and two native mobile engineers.

Result

Every release feature done by April 21, nine days early. The app released to its first customers, with Cypress tests in the pipeline.

8s to under 1sfor a key operations query, in initial testing

Problem

Several high-stakes clearance programs, including a legacy system retirement and an EU customs launch, all competing for the same small group of domain experts.

What we found

Air waybill logic locked inside the legacy system, a broken test suite on the EU launch, 8-second queries, and EU and non-EU code tangled together.

Result

A new air waybill service to replace the legacy logic, the EU customs soft launch pushed to production, and a key query cut from 8 seconds to under 1.

Disclosure: ReachWell is a Briebug affiliate (a related party), not an arm's-length client.

Problem

A legacy CakePHP and jQuery application sent messages from schools, counties and nonprofits, and some admin screens did not work.

What we found

A new Angular front end, a REST API in place of the PHP back end, a message queue for reliable delivery, and accessibility and tests built in.

Result

The rewritten platform went into service on June 1, 2026, and the new website and admin app launched in October 2026.

Situation

BACB planned to add new modules to its in-house Angular application and wanted an outside review first.

What we found

The review covered monorepo use, testing, RxJS, data and code conventions, package structure, NgModules and HTTP services.

Result

BACB received an on-site walkthrough of the findings and a written technical assessment report.

Situation

Crownpeak wanted an outside review of its V3 web content management UI, which mixed AngularJS and Angular with Bootstrap and jQuery.

What we found

We ran a two-day on-site review and delivered prioritized, sequenced guidance on upgrades, state management, builds and testing.

Result

Crownpeak's engineering team scoped the findings, and in March 2020 Crownpeak came back to us about larger projects.

Situation

An internal Angular ERP system had pages that had grown too large, and the team was fighting bugs.

What we found

Large pages needed to break into smaller components, and the app needed feature modules and container and presentational components.

Result

The team received a written recommendations document, a refactor plan and a training session.

Situation

The nGenius Pulse UI was built entirely on AngularJS, which was going end of life in June 2021, with over 200 pages to migrate.

What we found

The UI relied on $scope and $rootScope contracts, lacked test coverage, and had an unclear startup flow and unclear state and caching.

Result

A migration plan with a hybrid Angular 9 and AngularJS proof of concept and a build-out plan. NETSCOUT moved into a prototype phase.

Situation

SwitchDin had two Angular projects that were not progressing because its small team was busy elsewhere. Its CTO wanted an assessment before any open-ended spend.

What we found

Our review found no proper state management, which caused performance issues, plus platform layers mixed with business logic and no end-to-end tests.

Result

SwitchDin received a recommendations log, a delivery timeline and an options deck, and gave NPS scores of 9 and then 10.

9.9average monthly client NPS across 29 responses, 2021 to 2023

Situation

New competitors offered state agencies bundled products. JPMA needed to upgrade its app and add features agencies would choose.

What we did

An embedded team supports the WICShopper app on iOS and Android, the admin portal, and the backend services, APIs and hosting.

Result

Monthly client feedback averaged an NPS of 9.9, and JPMA renewed for a five-year term to June 2030.

90 to 45 minMaster pipeline gate time, December 2020

Situation

The HCI team wanted to deliver key features faster, move its main app to a trunk-based monorepo workflow, and test on virtualized hardware.

What we did

Senior Angular developers built a Jenkins Shared Library, feature toggles, faster pipelines, a component library site and an Angular 11 upgrade.

Result

Master pipeline gates went from 90 to 45 minutes and Staging from 30 to 20, and the Angular 11 upgrade fixed a memory error.

Situation

Brandfolder was ready to accelerate after COVID, with a two-person integrations team, little React test coverage and plans to grow from 10 to 30.

What we did

We built integrations for Canva, Salesforce, Smartsheet and Microsoft Office, and mentored the internal team on process and testing.

Result

Monthly NPS stayed between 8 and 10 through 2021, and Brandfolder referred one of its own customers' projects to us.

Situation

CareMetx wanted to modernize its end-customer portals and level up its internal team at the same time.

What we did

We embedded React and .NET developers, a solution architect and a scrum master to build portal features and mentor the team.

Result

The engagement ran from July 2020 into 2022, with client NPS scores of 8 to 10.

Situation

The Unity client was hard to maintain and upgrade, the code base was complex and fragile, and the team was stuck in maintenance mode.

What we did

We extended the team to build a new React web application and guided the move to Scrum, GraphQL and written acceptance criteria.

Result

The site went live on time, and Circadence extended the engagement twice into 2022.

Situation

ClickFox needed senior software engineers to build its Fox product, the ClickFox application MVP.

What we did

Our engineers worked from ClickFox's Denver office inside its agile process and wrote unit and component-integration tests.

Result

ClickFox asked to extend both engineers to the end of July 2017.

Situation

A legacy platform mixed Angular, MVC and jQuery, a Xamarin app had to be retired, and testing was manual only.

What we did

Our engineers built an Angular and Ionic adjuster app, SLA tracking, a new EDI ingestion process and automated tests.

Result

The app reached the Apple App Store and Google Play, and Eberl renewed the engagement three times through December 2023.

5 amendmentsextended the engagement to about 20 months

Situation

ERCOT needed development and solution-architect capacity for its RIOO-RS application while architecture requirements were still being discovered.

What we did

Four Briebug people joined ERCOT's Scrum teams for Angular, Java and architecture work, then handed off with a transition plan.

Result

The engagement ran about 20 months, was extended through five amendments and ended with a planned knowledge transfer.

Situation

One Terraform mono repo had grown so large that plans timed out and the blast radius was too large. Only one half-time engineer did DevOps.

What we did

We embedded an AWS DevOps engineer to rebuild the infrastructure as code in layers, implement EKS, and advise on messaging and BI.

Result

Nevro adopted the layered approach for all new projects and implemented a Snowflake and Lambda initiative.

Situation

A proof of concept made the new SayIt Administration Web Application look further along than it was, and a lot of wiring remained.

What we did

We embedded two senior developer-designers to refine the design, build the Angular web tier, test it and train nVoq staff.

Result

A significant amount of the work was complete by February 2019, and nVoq raised a possible next project with us.

Under 10 minutesfor a full run of 80 end-to-end test suites

Situation

Photobucket needed test coverage to speed up feature releases. Its Cypress tests ran slowly, and some GraphQL calls returned a boolean instead of data.

What we did

We built a Cypress end-to-end suite for the NEXT app, documented the testing process, and added a GraphQL expert to fix the back end.

Result

A suite of 37 spec files and 80 test suites with a full run under 10 minutes, and GraphQL mutations that return data.

98 to 100%integration test coverage on the user management areas

Situation

Weekly releases repeated the same defects, the team needed much more testing, and a hard go-live was set for May.

What we did

We embedded a senior enterprise developer who trained the team, added Cypress and Jest tests, refactored components and built a shared library.

Result

Integration tests reached 98 to 100% coverage on the user management areas, and the team gained reusable components.

Situation

Scaled Agile was rebuilding three AngularJS apps in modern Angular. Its developers were not all enabled equally, and its dev lead lost time bringing others up to speed.

What we did

We ran a discovery phase, did code review and spikes, planned the migration of the first app, and trained the client developers in Angular best practices.

Result

The client approved a further enablement engagement and asked for the same strategic lead to return.

Situation

Schedulicity needed expert bandwidth to migrate its legacy AngularJS code to modern Angular while it kept building new features.

What we did

We embedded engineers in the Schedulicity team for the Angular conversion, with architecture reviews, refactoring, mentorship and biweekly delivery updates.

Result

Schedulicity extended the engagement into a second statement of work, and no client survey response was a detractor score.

Situation

The client needed expert Angular guidance to migrate legacy applications and more development capacity, with gaps in linting, CI/CD and code coverage.

What we did

Senior developers converted legacy AngularJS applications to Angular, built graph and dashboard features and worked closely with the client's QA team.

Result

The client gave an NPS of 10 in May and June 2020 and returned for successive statements of work.

Situation

The client teams needed senior front-end experts who could join existing Scrum teams fast, build new apps and keep legacy apps healthy.

What we did

Our engineers joined the client Scrum teams to build Angular apps, maintain a shared component library, write tests, support operations and train client engineers.

Result

The client has renewed the engagement every year from 2018 into 2026.

Situation

The client was rebuilding its customer web experience in Angular. It needed senior architecture leadership and more delivery capacity.

What we did

We started with one Angular architect and grew to embedded teams for test coverage, a domain layer, a design system, a CMS migration and web commerce.

Result

The client renewed every statement of work without a break from 2019 to 2026, and ran two Briebug teams at once.

Situation

MapQuest's consumer apps and location platforms had to keep moving through a brand sale, a budget freeze and repeated reorganizations.

What we did

Embedded web, iOS and Android engineers who moved from consumer apps to edge-computing R&D to location SDKs as priorities shifted.

Result

When the MapQuest brand was sold in 2019, both the buyer and Verizon kept Briebug. The work ran from 2016 to at least 2022.

Under 6 monthsfrom requirements to launch of two platforms, with a four-person team

Challenge

A new streaming platform for filmmakers, with no existing system, an aggressive timeline and a broad, evolving feature set.

What it needed

A creator app and a consumer app, secure video streaming, and subscription billing that pays creators, all from a small team.

Result

Both platforms launched in under six months by a four-person team, with subscription monetization and automated creator payouts.

Challenge

The college needed its strategic planning web application built in modern Angular to replace an older system, with a firm deadline.

What it needed

Two modules for the executive leadership team: Smart Actions and a Continuous Improvement MVP, plus dashboards and administration tools.

Result

Both modules were live and in business use by December 15, 2021, before the deadline, and the system was stable.

Challenge

A new identity risk product needed a user interface for six system-level use cases and three user roles.

What it needed

Each screen needed a clear contract with back-end REST services, in the client's own style guide and branding.

Result

Storyboards, a screen-to-service mapping, and AngularJS UI code handed over to the client's team.