Canopy showcase, fictional data · return to /work/canopy
Canopyby DBJ TechnologiesBook a call
Guide

What Canopy is, in plain terms

Most businesses run on a stack of rented software. Analytics in one place, a CRM in another, uptime and error and deliverability monitoring in five more, each with its own login and its own monthly invoice, and none of them talking to each other. Canopy is the opposite bet. It is one dashboard that holds the whole business, on an install of its own, behind your own sign-in.

Three pillars, one surface

Everything in Canopy sits under one of three pillars. The daily work is on top, the depth is one calm click down.

CRM

Contacts, companies, deals, a shared inbox, tasks, and a synced calendar with public booking pages, with every interaction on one timeline. A prospect books a slot and Canopy creates the contact, logs the meeting, and sends the invite. Build your own reports and a personal dashboard, and switch on AI assistance that summarizes records and drafts email when you want it.

Signals

First-party analytics, search performance, and website intelligence, joined to the people and deals they belong to.

System

The dashboard watching its own deployment: uptime, errors, email deliverability, certificates, and real spend.

What is actually in here

The tour walks seventeen screens. There are more than two hundred and twenty. Grouped the way the product groups itself, this is the whole surface, so you can price it against what you are renting today rather than against what a tour had room for.

Relationships

  • Contacts, with every interaction on one timeline
  • Companies, and the ones flagged as clients
  • Deals, on a board or a table
  • More than one pipeline, each with its own stages
  • Quotes and line items off a shared catalog
  • Tasks
  • A synced calendar with public booking pages
  • The inbox, threaded to the person it came from
  • Site notes, filed against the page they are about
  • Global search, and duplicate contacts that merge cleanly

Field work

  • Jobs: one piece of work at one address
  • A milestone strip that writes its own history
  • A photo wall ordered by when the shot was taken
  • An offline queue that uploads when the signal returns
  • The whole admin, installed on a phone as an app
  • Documents, emails and texts filed on the job

Money

  • Invoices, from a draft to a frozen PDF
  • Hourly invoices billed from exact minutes
  • Payments, and an invoice that walks its own status
  • An aging strip and a live overdue read
  • Recurring billing reminders that re-schedule themselves
  • Delivery cost logged against the work it belongs to
  • Profit and health, with margin per client
  • The subscriptions register

Signals

  • First-party visitors, with bots kept apart from people
  • Conversion funnels
  • Search performance
  • Real-user Web Vitals
  • Prospecting candidates
  • Change monitoring on sites you watch
  • Visits and leads from a launched client site, filed on its deal
  • Pathlight scans, and a queue for running them in batches
  • Captured leads and suggested contacts
  • Operator, the phone screen, with transcripts and costs

What runs without you

  • Sequences, with reply-exit
  • Workflow rules built visually, no code
  • Versioned email templates
  • Signed agreements that capture themselves
  • Dave, the assistant, and the actions you switch on for him
  • The Morning Brief, live and optionally in words
  • In-app notifications and teammate mentions

Reporting

  • Sales analytics over the pipeline
  • Forecast against quota
  • A report builder, with saved and shared reports
  • A personal dashboard of pinned charts and tiles
  • Monthly client reports, honest about what they cannot see
  • A client portal on your own domain

The system watching itself

  • One banner carrying the worst of every signal
  • Deployment health and error volume
  • Email deliverability
  • Per-domain certificate, domain and email-auth posture
  • Real spend against a budget you set
  • Database and storage census
  • An audit log of every meaningful change

Settings and your install

  • Master controls, every one of them audited
  • A sidebar each person arranges for themselves
  • Custom fields, pipelines, products and quotas
  • Import and export, by CSV or spreadsheet
  • Team and four access tiers
  • API tokens and signed outbound webhooks
  • A full database export
  • The manual, shipped with the install

Your own install, not a shared service

A Canopy install runs on your domain, behind your sign-in, with the records in a database of its own. It is not a shared service that every other customer sits on. It brings the work of eight to twelve separate SaaS products into one install dedicated to your business, which means your first-party data is finally joined to your business outcomes instead of scattered across vendors who each hold a slice of it.

Its own databaseYour sign-inYour domain

Guardrails you can trust

Some of what Canopy can do costs money to run, like a deep website scan or an AI-written summary. So anything billable has to clear a set of guardrails before it fires. If any one of them says no, nothing runs and you are told why. A runaway loop cannot turn into a surprise bill.

Cost ceiling

A monthly budget caps how much can be spent. Nothing runs past the cap, and it starts hard off until you set it.

Trigger rules

Nothing billable fires on its own. A person is always in the loop. Automated jobs can flag work, but only a click runs it.

Feature switches

Every billable capability has its own on and off switch, and everything ships off. What is not switched on cannot run.

How I build it

Canopy is a build, not a signup. I stand up your install, shape it to how your business actually works, connect it to your records, and have it running for your team. Delivery usually lands in about four to eight weeks. The case study walks through what it does every day.

Canopy comes two ways: a one-time productized build, with the source licensed to you to run and modify in house, or a monthly subscription. Either way it is scoped per business, and I quote it in parts after a scoping call, so the number defends itself instead of arriving as a round lump.