Case study

What changed when we put AI to work.

Less repetitive work. Better tools for the team. More capacity to serve customers and grow.

This is our experience bringing AI into the systems and daily work of a business we helped build and operate.

Rollout snapshot

August 5–September 12, 2026

This five-week snapshot covers the recent AI rollout. It is separate from the team's ten years of company building, during which the business grew from $0 to more than $25 million in annual revenue.

Business outcomes

Six practical changes across the business.

Less manual order processing

What changed

Emails, purchase orders, par sheets, and driver notes were turned into draft orders for people to review and complete. During the rollout, the workflow prepared 360 drafts and people completed 326. A first restock-ticket run also prepared 33 tickets in about five minutes.

Why it matters

The order desk spends less time copying information between systems and has more time to help customers. People remain responsible for payment terms, review, and completion.

Faster customer support

What changed

Customer history, live delivery information, and support context were brought together. The team also built 67 troubleshooting cards from past tickets and technician reports.

Why it matters

Support teams can find useful context in one place and resolve questions more quickly. The guidance supports the team's judgement rather than replacing it.

More efficient marketing

What changed

AI was used to help manage Google Ads, prepare marketing and social content, review performance, and streamline recurring campaign work. Analytics brought together advertising, website, and sales information.

Why it matters

The team can do more recurring marketing work internally, with less outsourced work and manual effort.

Tools built around our operations

What changed

A custom equipment and asset-management tool brought together 1,008 machine records, service history, fleet information, and troubleshooting guidance. Claude was the AI platform used in this implementation.

Why it matters

Technicians have the history and practical guidance they need in one place. The tool reflects how the operation works rather than forcing the team into a generic process.

Less administration in collections

What changed

A read-only finance connection supported invoice preparation and retrieval, account reviews, and collections follow-up preparation. An invoice-split tool replaced a manual task reported to take 30–45 minutes.

Why it matters

The team can prepare account work with fewer lookups and repeated steps. People continue to review customer communications and make payment decisions.

More time across the business

What changed

Reusable workflows replaced recurring reports, lookups, and checks across purchasing, inventory, sales, finance, leadership, and people operations. A payroll validation and upload workflow remained in progress at the snapshot date.

Why it matters

Teams have more capacity for customers, decisions, and growth. The payroll workflow was still being developed at the end of the rollout.

Connected foundation

Built around the tools already in use.

Live custom connections covered finance, customer support, route planning, internal analytics, and fleet information. A sixth connection for restock tickets was built and awaiting deployment.

Standard connections included ecommerce, email, calendars, shared files, sales tools, meeting notes, code, and the web. Access and review rules kept people responsible for important decisions.

Bring the lesson to your business

Start with the work your team already knows needs to improve.

Join our waitlist

Examples reflect our implementation and the team's reported experience. We are validating the hours saved and financial impact.