Guides

How to see Buildertrend, your CRM and your project board in one dashboard

Goodluck Ogundare ·

Most building and remodeling firms I talk to run Buildertrend for jobs, a CRM for leads, a project board for the work between sale and site, and an accounting package for the money. Each one has its own reports. None of them shows the whole business.

I recently built a reporting system for a residential design-build firm that pulls five systems, including Buildertrend, HubSpot and monday.com, into six dashboards. This is the method I used. You can follow it with your own team or hand it to someone like me.

Start with the questions, not the software

Write down every number the owners want to see. Do not filter yet. On that build the list came to 83.

Then sort the list into three groups:

  • Numbers you can have now, because the data is already in a system.
  • Numbers that need a decision first, because two people in the firm define them differently.
  • Numbers that need new data, because nobody records the thing yet.

This step saves the most time later. It tells you what the first dashboards can show, and it tells the owners which gaps are theirs to close. On that build, 76 of the 83 ended up on a dashboard.

Get the data out the supported way

Each system has an official way to hand over its data. HubSpot and monday.com have APIs. Buildertrend lets you export its lists to spreadsheet files. Use those.

Do not pay anyone to scrape the screens. A scraper breaks the first time a page layout changes, and nobody notices until the numbers are already wrong.

Exports need care. Three habits prevent most problems:

  • Widen every filter before you export, so you get all jobs and all statuses, not just the default view.
  • Write down the row count the screen shows, and check the file has the same number.
  • Name each file with the company, the list, the date range and the row count.

Keep three layers of data

  • Raw: an exact copy of what each system gave you. Never edit it.
  • Clean: the same data with dates, names and codes made consistent.
  • Reporting: the tables the dashboards read from.

When a number looks wrong, the layers let you trace it back quickly. Without a raw layer, you end up arguing about whether the source or your own work caused it.

Build one list of jobs that everything hangs on

The same job has a different name in every system. The CRM knows it as a deal. The project board knows it as a card. Buildertrend knows it as a job. Build one master list of jobs and map each system's version to it. Every dashboard then reads from that list.

If you run more than one company, put the company on every row from the start. Adding it later means rebuilding.

Cost codes need the same treatment. Two companies can use the same code for different things, so translate them by company and code together.

Check every total before you build on it

Before a source feeds any dashboard, add it up and compare it with a figure the firm already trusts: a total on the screen, a report the bookkeeper runs, a number the owner knows. If they do not match, stop and find out why.

Run the same check every time new data loads. A dashboard that is wrong once stops being used.

Show what is missing

No firm records everything. Say so on the dashboard. If a number covers 60 of 90 jobs, show that count next to it. Put records with a blank field in their own tile, not as a bar beside the real categories.

An owner can work with a number that is honest about its gaps. They cannot work with one that hides them.

Automate last

Get the numbers right by hand first. Then schedule the feeds so the dashboards refresh without anyone re-keying a spreadsheet, and keep the checks running on every load.

What you need

The tools are ordinary: a PostgreSQL database, Python scripts to load the data, and Metabase for the dashboards. The work is in the matching and the checking, not the software.

If you would rather have this built for you, I do it for building and remodeling firms. It starts with a small fixed-price review.