Back to example builds

Trades and contractors

Example build: custom CRM for a small trades company

Trades company scenario, Fraser Valley BC

A small plumbing and heating company where per-user pricing on their current SaaS grows every quarter. This is the shape of custom CRM we would build for them: intake, dispatch, quotes, deposits, invoices, and an owner's dashboard on a phone.

Example build, not client work. We don't publish case studies until a real client gives us permission and real numbers.

Illustration for Example build: custom CRM for a small trades company

The problem

Where they would be stuck

  • Per-user pricing means every new tech costs more in software.

  • The reports the owner wants need spreadsheet stitching every month.

  • Quote follow-ups rely on someone remembering.

  • Office and techs share the same tool but hate different parts of it.

The approach

What we would build and why

  1. 1

    Map the real flow over two discovery calls.

  2. 2

    Three tailored views: tech (mobile-first), office (dispatch, invoicing, customers), owner (dashboard).

  3. 3

    Stripe for deposits and card payments.

  4. 4

    Clean monthly export for the bookkeeper.

What it would do

Where the CRM would change the day

  • One CRM your office and your techs both use, instead of three tools that almost fit.

  • The per-user SaaS bill goes away and adding a tech costs nothing in software.

  • The bookkeeper gets a clean monthly export, so month-end still works.

  • The owner sees the pipeline on a phone.

Under the hood

What it would be built on

Stack & shape

  • Web app that works on phone, tablet, and desktop
  • Postgres database, owned by the client
  • Stripe for deposits and card payments
  • Monthly export to the bookkeeper's year-end tool

Scope

Typical scope for a build like this.

Custom CRM

Have a project that looks like this?

Tell us what's slowing you down. We'll give you a straight answer about whether a custom CRM makes sense, and roughly what it would take.