Sound familiar?
What teams building dashboards in Tableau tell us before a project starts.
- Our dashboard shows last week's numbers and nobody knows when it last refreshed.
- Two dashboards give two different totals for the same thing.
- Every new chart means someone first pulling and cleaning a spreadsheet.
- Extract refreshes fail overnight and we find out from a manager.
- Only one person knows how the workbooks were built.
What we build
Each one is a working piece you can open and check when it's done.
Data sources from your systems
Tables from your CRM, store, accounting tool and spreadsheets combined into one clean source, with joins and definitions written down.
ETL and data pipelines Dashboards and reportingScheduled extracts and emailed views
Extract refreshes on Tableau Cloud or Server, timed after the upstream data lands, a notice if one fails, and the key views sent to the people who want them in their inbox.
ETL and data pipelines n8n, Make and Zapier automationDashboards built around decisions
A small number of views for the questions asked in each meeting, with filters that make sense and a layout that works on a laptop and a phone.
Dashboards and reportingMetric definitions in one place
Revenue, margin, active customer and other terms defined once and used everywhere, so totals agree.
Dashboards and reportingSpreadsheet-to-source pipelines
The files that people maintain by hand turned into a managed source, with checks for missing columns and odd values before load.
Python scripts and utilities ETL and data pipelinesHandover and upkeep notes
Documentation of each workbook and source, who owns it and how to change it, so the dashboards do not depend on one person.
Dashboards and reportingWhat we connect it to: Salesforce, HubSpot, Shopify, QuickBooks, Google Sheets, Excel, Snowflake, BigQuery.
Industries that use it: Ecommerce, Wholesale, Marketing agencies, Manufacturing.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Sales view from CRM and invoices
Example: a distributor wants pipeline and invoiced revenue side by side. We load both nightly into one source and publish a dashboard of targets, actuals and the gap by rep.
CRM API, accounting export, Tableau CloudExample project
Marketing results by channel
Example: an agency tracks several clients' ad spend and leads. A scheduled job combines each platform's figures into one table, and the dashboard shows cost per lead by client and channel.
Python, Google Sheets, Tableau extractExample project
Workbooks that stopped refreshing
Example: a company's inherited Tableau workbooks fail each night. We find the broken connections and expired credentials, repair them, and add a failure email.
Tableau Server, database, schedulerQuestions people ask first
Do you need to replace our existing Tableau setup?
No. We start by reading your workbooks and sources, and work with what is there unless something has to change, which we tell you first.
Can you work with Tableau Cloud and Server?
Yes, both. Where a data source can't be reached from the cloud, we plan a gateway or a pre-built extract.
Is Tableau the right tool for us?
Sometimes Power BI or a simple sheet does the job. If another tool suits you better, we say so before you invest more.
How do we start?
Tell us which numbers people argue about and where the data comes from. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com