# Create the operating system for the next stage of growth

Executives need a software decision that improves visibility, reduces key-person dependency, standardizes acquired operators, and gives teams the infrastructure to scale.

- Frame the software decision around growth, margin, and integration risk.
- Help the buying committee align without turning the evaluation into a feature debate.
- Connect standardization to better execution across branches and acquisitions.

## Operator fit  
Multi-line Rolloff, commercial, residential, portable toilet, scale, and customer-service workflows in one operating model.

## Buying support  
RFP ready Requirements, scorecards, demo scripts, migration scope, and internal requisition copy.

## Implementation lens  
90-day plan Designed around migration, training, integrations, rollout, and adoption risk.

# Growth exposes the limits of informal systems

The systems that work for one yard or one founder-led operation rarely hold up across acquisitions, new markets, and multi-line branches.

- Leadership cannot compare branch performance cleanly.
- Acquired operators keep separate workflows and customer data.
- Owners rely on a few people who know the local system history.
- Growth initiatives slow down because the operating backbone is fragmented.

## Executive requirements to include

Executives should make sure the evaluation supports the company's strategic operating model.

### Standard operating model

Define the workflows all branches should share across dispatch, billing, customer service, driver proof, and reporting.

### Acquisition integration

Require a path for onboarding acquired customers, sites, assets, prices, invoices, routes, and teams.

### Visibility across business units

Compare revenue, service quality, route performance, AR, and exceptions by branch and line of business.

### Change management

Evaluate the vendor's implementation support, training, adoption plan, and executive reporting cadence.

## How this role should run the evaluation

### Define the strategic job

Decide whether the purchase is about replacement, consolidation, acquisition integration, or growth infrastructure.

### Align the committee

Give each role a clear evaluation lane and shared scorecard.

### Inspect implementation risk

Review migration, rollout, adoption, and reporting before signing.

## What other stakeholders need from this role

### Operations

Confidence the platform improves field execution instead of creating executive-only dashboards.

### Finance

A business case tied to revenue capture, cash, cost of manual work, and reporting.

### IT and procurement

Clear risk, migration, security, and contract requirements.

## Build the packet, then align the room

## Enterprise buyer questions

### Why should executives care about the RFP details?

## Start with the RFP, then make the demo prove the workflow

Build a requirements packet for procurement, then bring real dispatch, billing, route, scale, customer, and migration examples to the sales conversation.