◆ Case study · Estimating · Workflow Automation · Construction

From estimating inputs to approved quotes in one operational system.

Cass & York rebuilt Horizon Roofing’s quoting application around the full lifecycle of creating, pricing, reviewing, approving, and managing roofing estimates.

Client
Horizon Roofing
Sector
Construction / Roofing
Services
Custom Operations Software, Software Modernization, Workflow Automation, PDF Generation
Stack
.NET · PostgreSQL
Drop: quote builder screenshot (16:8)

[01] The operation

Quoting is more than generating a number.

The workflow involves project information, roof specifications, pricing rules, additional items, notes, attachments, internal review, approvals, historical quotes, customer records, and the final document delivered to the customer.

Horizon needed that process represented as a structured operational system.

[02] The existing systems

An existing quoting application and the records behind each estimate.

Horizon already had a quoting application built with Next.js and Supabase. Its workflow involved project specifications, pricing settings, customer records, attachments, approvals, and quote documents.

[03] The gap

The quote needed a complete operational lifecycle.

Creating a quote was only one part of the job. Pricing, internal review, approvals, revisions, and history needed to work together as structured business records.

[04] What we built

The full quote lifecycle, modeled as software.

Cass & York rebuilt the application using a new .NET and PostgreSQL architecture and modeled the business processes behind the quote lifecycle.

The underlying system models quotes, companies, locations, pricing settings, approvals, notes, attachments, users, and activity as structured business records.

  • 01Multi step quote creation
  • 02Pricing calculations
  • 03Roof and project information
  • 04Additional item pricing
  • 05Notes and file attachments
  • 06Approval workflows
  • 07Quote editing and renewal
  • 08Archiving and quote history
  • 09Company and location records
  • 10User management
  • 11Administrative settings
  • 12Activity logging
  • 13Reporting
  • 14PDF quote generation

[05] Systems involved

The tools and records connected by the work.

  • 01Existing Next.js and Supabase application
  • 02New .NET application
  • 03PostgreSQL
  • 04Server-side PDF generation

[06] The resulting workflow

One system from project information to reporting.

01

Project information

02

Estimate inputs

03

Pricing rules

04

Quote review

05

Approval

06

Generated quote

07

History & reporting

The application brings those stages into one system rather than treating the quote as a standalone document.

[07] Modernizing the application

Keep the workflow. Replace the foundation.

The project also involved migrating the application away from its previous Next.js and Supabase implementation.

The architecture is secondary to the business goal: creating a maintainable system around an important operational workflow.

  • 01ASP.NET Core Blazor Server
  • 02C#
  • 03Entity Framework Core
  • 04PostgreSQL
  • 05ASP.NET Core Identity
  • 06Docker
  • 07Server side PDF generation

Start a conversation

Have a workflow like this?

If estimating, pricing, approvals, and customer documents are spread across several tools, show us how the process works today.

Book a Workflow Call →
Systems involved