Cass&York

Selected work/ Operational systems

Different businesses. The same underlying problem.

Important workflows often span multiple systems, documents, teams, and manual handoffs. We connect what’s already there, bring the data together, and build the missing software around it.

Connect systems. Consolidate data. Automate the handoffs. Build what’s missing.

Show Us Your Workflow →Explore the work ↓

The workflow comes first.

Each project starts with a specific operational problem and ends with a system shaped around the people who use it.

Horizon Roofing

Work · Estimating · AI Automation & Agents · 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
Capabilities
Custom Operations Software, Software Modernization, AI Automation & Agents, PDF Generation
Team
Strategy · Design · Engineering

Fig. 01 · The system at a glance

From an operational problem to a working software layer.

Select a stage to explore

Active stage · 02

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

  • Approval workflows
  • PDF generation
  • Administrative controls

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.

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.

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.

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

The tools and records connected by the work.

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

One system from project information to reporting.

  1. 01

    Project information

  2. 02

    Estimate inputs

  3. 03

    Pricing rules

  4. 04

    Quote review

  5. 05

    Approval

  6. 06

    Generated quote

  7. 07

    History & reporting

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

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
AutoTakeoff

Work · Documents · Estimating · AI

Turning construction plans into structured estimating workflows.

Cass & York built an AI assisted construction application that combines project plans, measurement tools, material workflows, document processing, and billing in one platform.

Client
AutoTakeoff
Sector
Construction
Capabilities
Custom Operations Software, AI Automation, Document Intelligence, Data Platforms
Team
Strategy · Design · Engineering

Fig. 01 · The system at a glance

From an operational problem to a working software layer.

Select a stage to explore

Active stage · 02

Cass & York built an AI assisted construction application that combines project plans, measurement tools, material workflows, document processing, and billing in one platform.

  • Material workflows
  • Project data
  • AI assistance

Construction estimating begins with information embedded in plans.

Turning those plans into usable quantities requires people to inspect documents, understand scale, identify materials, measure drawings, and organize the resulting data around a project.

AutoTakeoff was designed around that workflow.

Construction plans were the source of the estimating information.

The workflow starts with construction PDFs. People need to inspect drawings, establish scale, measure quantities, and organize materials around a project.

Document information needed to become project data.

Plans, measurements, material records, and estimating needed a connected workspace, with AI assistance integrated into that workflow.

Plans, measurements, materials, and billing in one platform.

The application uses both JavaScript and Python document tooling alongside multiple AI providers.

  • 01Project management
  • 02PDF plan viewing
  • 03Vector overlays
  • 04Drawing tools
  • 05Scale selection
  • 06DPI calibration
  • 07Measurements
  • 08Material records
  • 09Material locations
  • 10Price history
  • 11AI assisted document analysis
  • 12OCR and PDF processing
  • 13Billing and subscriptions
  • 14Account workflows

The tools and records connected by the work.

  • 01Construction PDFs
  • 02PDF viewing and measurement tools
  • 03Python PDF processing and OCR
  • 04PostgreSQL
  • 05AI providers
  • 06Stripe

Document understanding connected to estimating.

  1. 01

    Construction plans

  2. 02

    PDF processing

  3. 03

    Scale & measurement

  4. 04

    AI assisted interpretation

  5. 05

    Materials & quantities

  6. 06

    Project estimate workflow

The value comes from connecting document understanding to the larger estimating process rather than treating AI extraction as an isolated feature.

The plan and the project data share one workspace.

Dedicated tools for interacting with plans allow document information and project data to exist in the same application.

  • 01PDF viewer
  • 02Vector overlays
  • 03Drawing toolbar
  • 04Scale selector
  • 05DPI calibration
  • 06Measurement display
  • 07Material tables

A mixed application and document processing stack.

  • 01React
  • 02TypeScript
  • 03Node.js / Express
  • 04PostgreSQL
  • 05Drizzle
  • 06Python PDF processing
  • 07PyMuPDF
  • 08OCR
  • 09OpenAI
  • 10Anthropic
  • 11Google Generative AI
  • 12Stripe
Vintel / GovIntel

Work · Systems Integration · Customer Operations

Connecting onboarding, provisioning, CRM, inventory, and billing.

Cass & York worked across a connected set of customer facing and internal systems spanning onboarding, account management, automated provisioning, CRM, inventory, billing, ecommerce, and operational synchronization.

Client
Vintel / GovIntel
Sector
B2B Operations
Capabilities
Portals, systems integration services, Custom Operations Software, Data Synchronization
Team
Strategy · Design · Engineering

Fig. 01 · The system at a glance

From an operational problem to a working software layer.

Select a stage to explore

Active stage · 02

Cass & York worked across a connected set of customer facing and internal systems spanning onboarding, account management, automated provisioning, CRM, inventory, billing, ecommerce, and operational synchronization.

  • Zoho integrations
  • Account management
  • Billing systems

Customer operations rarely live inside one platform.

The challenge is keeping the systems aligned while giving both the customer and internal team a usable interface.

  • 01Signup
  • 02Authentication
  • 03Customer records
  • 04CRM
  • 05Inventory
  • 06Product data
  • 07Provisioning
  • 08Billing
  • 09Payments
  • 10Administration

Customer operations crossed CRM, inventory, and billing.

The environment included Zoho CRM and inventory alongside signup, billing, ecommerce, and pricing applications. Customer and financial records needed to stay aligned across them.

One customer journey crossed several applications.

Signup, provisioning, support, and billing depended on information held in different systems. The gap was coordinating those records while giving customers and administrators usable interfaces.

A B2B customer portal and the systems around it.

The surrounding ecosystem included billing, signup, ecommerce, and pricing applications.

  • 01Authentication
  • 02Role separation
  • 03Customer onboarding
  • 04Customer dashboard
  • 05Automated provisioning
  • 06Customer records
  • 07Administrative management
  • 08Integration testing
  • 09Synchronization monitoring

CRM and inventory connected to the customer lifecycle.

A separate Go synchronization service supported heavier synchronization workloads, while logs and monitoring exposed integration activity.

  • 01Contacts
  • 02Accounts
  • 03Products
  • 04Customers
  • 05Invoices
  • 06Payments
  • 07Subscriptions
  • 08Sales orders
  • 09Contact persons

The tools and records connected by the work.

  • 01Zoho CRM
  • 02Zoho inventory
  • 03Signup and customer portal
  • 04Billing and ecommerce applications
  • 05Go synchronization service
  • 06Integration logs and monitoring

One customer lifecycle across several systems.

  1. 01

    Customer signup

  2. 02

    Onboarding

  3. 03

    Customer record

  4. 04

    Provisioning

  5. 05

    CRM / Inventory synchronization

  6. 06

    Billing & account operations

  7. 07

    Administration & monitoring

Taste the Local Difference

Work · Operational Data · Search · Publishing

A partner ecosystem built around structured data, search, maps, and publishing.

Cass & York helped build and maintain the WordPress technology behind Taste the Local Difference's partner and directory ecosystem.

Client
Taste the Local Difference
Sector
Partner Networks
Capabilities
WordPress Development, Data Platforms, systems integration services, Directories & Maps
Team
Strategy · Design · Engineering

Fig. 01 · The system at a glance

From an operational problem to a working software layer.

Select a stage to explore

Active stage · 02

Cass & York helped build and maintain the WordPress technology behind Taste the Local Difference's partner and directory ecosystem.

  • Search and filtering
  • Maps
  • Content workflows

Structured organizational data and public discovery.

Taste the Local Difference manages a network of businesses and partners that needs to function both as structured organizational data and as a public discovery experience.

That requires considerably more than standard page publishing.

WordPress supported a partner and publishing ecosystem.

Taste the Local Difference uses WordPress for partner listings, directories, and publishing. Partner information also supports imports, exports, subscriptions, orders, and reporting.

Partner information had to serve operations and discovery.

The organization needed to maintain structured partner records internally and make them useful through public search, maps, and publishing.

Custom WordPress functionality across the ecosystem.

  • 01Partner listings
  • 02Directory experiences
  • 03REST APIs
  • 04Custom taxonomies
  • 05Partner forms
  • 06Data synchronization
  • 07Maps
  • 08Advertising
  • 09Subscriptions
  • 10Orders
  • 11Galleries
  • 12Imports and exports
  • 13Administrative settings
  • 14Reporting

Partner records feed the public experience.

The system also exposes structured data through custom REST endpoints.

  • 01Structured categories
  • 02Filtering
  • 03Map markers
  • 04Popup content
  • 05List/map switching
  • 06Individual listing data

More than a publishing website.

The installation supports internal workflows around partners, listings, subscriptions, orders, imports, exports, reporting, and site configuration.

That is why this project is better understood as a custom platform built on WordPress rather than simply a website.

The tools and records connected by the work.

  • 01WordPress
  • 02Custom plugins and taxonomies
  • 03REST APIs
  • 04Partner forms
  • 05Import and export workflows
  • 06Directory and maps

From partner information to public discovery.

  1. 01

    Partner information

  2. 02

    Import / synchronization

  3. 03

    WordPress data model

  4. 04

    Custom plugins & APIs

  5. 05

    Directory · Search · Maps · Publishing

  6. 06

    Public experience

Appreciation Financial

Work · AI Workflow · CRM Integration · Automation

Turning a detailed financial intake process into a guided AI workflow.

Cass & York built an AI driven client intake experience designed to collect financial information, apply structured business logic, produce useful outputs, and connect the resulting data to GoHighLevel.

Client
Appreciation Financial
Sector
Financial Services
Capabilities
AI Agents, systems integration services, AI Automation & Agents
Team
Strategy · Design · Engineering

Fig. 01 · The system at a glance

From an operational problem to a working software layer.

Select a stage to explore

Active stage · 02

Cass & York built an AI driven client intake experience designed to collect financial information, apply structured business logic, produce useful outputs, and connect the resulting data to GoHighLevel.

  • Business rules
  • Structured intake
  • Recommendations

Financial intake requires more context than a lead form.

The conversation changes depending on the information provided and must collect enough context to support the next operational step.

  • 01Employment
  • 02Pension
  • 03Retirement goals
  • 04Family
  • 05Housing
  • 06Debt
  • 07Savings
  • 08Retirement accounts
  • 09Insurance
  • 10Protection needs

Financial intake needed to connect to the CRM.

The workflow collects a financial profile and connects resulting information to a GoHighLevel contact. Client summaries, agent summaries, and the fact finder support the next step.

A conversation needed a reliable path into operations.

Intake adapts to the information a client provides. Those answers needed to become structured records, pass through business rules, and reach the agent’s CRM workflow.

A guided intake that adapts as it learns.

Pension and retirement

Financial profile

Conversation and deterministic rules work together.

The workflow was designed to combine conversational intake with deterministic rules controlling important outcomes.

  • 01Insurance coverage calculations
  • 02Debt to income conditions
  • 03Retirement risk assessment
  • 04Recommendation logic

This separates the conversational experience from the business logic that controls important outcomes.

The intake produces usable downstream records.

  • 01Provide a summary to the client
  • 02Provide a summary to the financial agent
  • 03Populate the fact finder
  • 04Attach information to the GoHighLevel contact
  • 05Return risk information
  • 06Provide appropriate recommendations
  • 07Continue into downstream enrollment workflows

The tools and records connected by the work.

  • 01Guided intake experience
  • 02Deterministic business rules
  • 03Fact finder and summaries
  • 04GoHighLevel CRM

From conversation to the agent workflow.

  1. 01

    Client conversation

  2. 02

    Structured intake

  3. 03

    Business rules & calculations

  4. 04

    Summary / recommendations

  5. 05

    GoHighLevel

  6. 06

    Agent workflow

Shopify, New York + Los Angeles

Work · Enterprise Applications · Systems Integration

Maintaining and extending customer facing applications in an enterprise environment.

Cass & York supported existing digital properties for Shopify's New York and Los Angeles locations, maintaining the applications and handling integration work within their existing Next.js and Vercel architecture.

Client
Shopify, New York + Los Angeles
Sector
Enterprise Applications
Capabilities
systems integration services, Application Maintenance, Next.js, Vercel
Team
Strategy · Design · Engineering

Fig. 01 · The system at a glance

From an operational problem to a working software layer.

Select a stage to explore

Active stage · 02

Cass & York supported existing digital properties for Shopify's New York and Los Angeles locations, maintaining the applications and handling integration work within their existing Next.js and Vercel architecture.

  • Production support
  • Next.js
  • Vercel

Supporting established applications rather than claiming the original build.

Cass & York worked with existing applications supporting Shopify's physical space experiences in New York and Los Angeles.

Our responsibility was maintenance and extension of those systems rather than the original application build.

  • 01Next.js
  • 02React
  • 03Vercel
  • 04Third party integration work

Established applications already served the physical locations.

Shopify’s New York and Los Angeles digital properties already used Next.js, React, and Vercel, with existing deployment processes and integration dependencies.

Maintenance and integrations had to fit the existing environment.

The applications needed ongoing support and extension within established technical and operational constraints. Cass & York’s role was to maintain and extend them, rather than create the original applications.

Connected systems around customer and event workflows.

Cass & York worked with integrations connected to the digital properties and supporting the broader customer and event experience.

Enterprise maintenance is different from a greenfield build.

Cass & York maintained and extended the existing applications within established technical and operational constraints.

  • 01Existing architecture
  • 02Existing deployment processes
  • 03Integration dependencies
  • 04Production behavior
  • 05Business requirements
  • 06Changes made without disrupting surrounding functionality

The tools and records connected by the work.

  • 01Next.js
  • 02React
  • 03Vercel
  • 04Third-party integrations

Existing applications, supported and extended.

The customer and event experiences continue within the established Next.js and Vercel environment, with maintenance and integration work supporting the surrounding systems.

Different operations. The same starting point.

1

Understand the operation

Start with the process, the people involved, and the places where information stops moving cleanly.

2

Connect what already works

Keep the systems that still fit and build reliable paths between them.

3

Bring the data together

Create a reliable operational view across the systems the business already uses.

4

Build the missing layer

Turn the approvals, exceptions, documents, and handoffs into software the operation can rely on.

Show us the workflow your existing software can't handle.

You don't need a technical specification. Walk us through the process, the systems involved, and where your team is losing time.

Book a Workflow Call →
Systems involved