Skip to content
CASE STUDY

Custom Software

Custom operations CRM for utility contracts and field agents

SOS Bollette ran contracts and agents across spreadsheets and inboxes. We rebuilt the workflow into one operations CRM with roles, status, and a file the whole team can trust.

The operational problem

Agent activity, contract state, and customer documents were not in the same place. Managers reconstructed the week from WhatsApp and Excel.

Disputes and delays came from missing paperwork, not from the commercial offer. Scale made that worse.

What was breaking down

  • Contract versions living on laptops
  • Agent performance assembled by hand
  • No single customer file for support

How Striders Tech approached it

We sat with ops, not sales, and modeled the contract lifecycle. The CRM is the process: create, verify, assign, complete, and file.

What we built

  • Contract pipeline with required documents
  • Agent workspace with only their book of work
  • Role-based access for office vs field
  • Customer file that support can open without calling ops

Results the team can measure

  • One file per customer instead of a folder hunt
  • Visible book of work for every agent
  • Fewer disputes caused by the wrong contract version

Who this case study is for

Multi-agent service businesses in regulated or paperwork-heavykets who still run the company in spreadsheets.

SOS Bollette operates in utilities / operations. The work is a custom system designed around their process, not a generic template with extra fields bolted on.

THE OUTCOME

What changed after the system went live

One file

per customer instead of a folder hunt

Visible book

of work for every agent

Fewer disputes

caused by the wrong contract version

THE TAKEAWAY

Good software doesn't add complexity. It removes it.

Discuss your project