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

Next case study

Keep exploring the work.

Related work
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

02 · Capability

Portals & Member Platforms

+

Start a conversation

Multiple systems supporting one customer workflow?

We build the software layer that coordinates them.