Should I buy a dashboard or have one built?
Buy when the job is generic and a big vendor already does it well. Have one built when the value is in the shape of your own process, or when the numbers live in three systems and no product reads all three.
| What you need | Off-the-shelf tool | Built for you |
|---|---|---|
| A sales dashboard from one CRM | Good, and quick to start | Only worth it if the CRM cannot reach your other data |
| Ecommerce numbers from two shops plus your accounts | Two subscriptions and a weekly export to join them | One screen that reads both shops and your ledger |
| Stock, orders and jobs in the same view | Rarely available at all | This is what I build most often |
| An approval flow that follows your rulebook | You bend the rules to fit the tool | The tool follows the rules |
| Who owns the data | The vendor, and exporting is limited | You, in a database you can read |
What does a dashboard cost?
Small jobs start at $50, so one report or a fix to a screen you already have is cheap to try. A full internal tool is quoted as one fixed price after a free call, because the number depends on how many screens there are, where the data comes from and how many people log in.
Can it read the systems I already use?
Usually yes. Most businesses already have the data somewhere: a shop platform, an accounts package, a form tool, a spreadsheet nobody dares to close. I read from those sources instead of asking your team to type everything twice, and I keep a copy of the numbers so the dashboard still loads when one source goes down.