Skip to content
Software & web

Get an internal dashboard built on your own data

Your team copies numbers between three tools every Monday, or the only way to see an order's status is to ask someone. An internal dashboard puts that on one screen. Developers can quote it well once they know where the data lives, who uses it, and which decisions it should help with.

TW-DRAFTDraft

Build an internal sales dashboard from Shopify and HubSpot data

Budget
You set this
Timeline
3-4 weeks
Category
Software & web

Scope

Our sales team rebuilds a weekly report by hand from Shopify orders and HubSpot deals. We want a dashboard with revenue by channel, open deals by stage and the week's new customers, refreshed daily, behind company sign-in. About 10 people will use it.

Deliverables

  • Dashboard with revenue, pipeline and new-customer views
  • Daily data refresh from Shopify and HubSpot
  • Sign-in limited to company Google accounts
  • Handover document and admin access to every account used

Skills

  • API integration
  • Dashboard development
  • Shopify API
  • HubSpot API
An example brief. Describe your task and the brief writer drafts one like it.

What the work involves

The scope a provider will expect to cover. Leave out what you don't need, and say so in the brief.

  • Connecting to where the data lives: your database, a spreadsheet, or the APIs of the tools you use
  • Designing the screens around the questions people ask most, not every field you have
  • Building it behind sign-in, so only your team can see it
  • Hosting it, or handing it over to run on your own infrastructure
  • Documentation so someone else can change it later

What to put in the brief

The facts a provider needs to give you a real price instead of a guess. Write it in your own words: the brief writer turns it into scope and deliverables, asks about anything missing, and you can edit every line before it goes out.

Start the brief
  1. 1The questions the dashboard should answer, in the words your team uses
  2. 2Every data source, and whether it has an API or only an export
  3. 3Who uses it, how many people, and on what devices
  4. 4Where it should run, and any tools your company already standardises on
  5. 5A sketch, or a screenshot of the spreadsheet it replaces

Ask each provider

Every proposal opens a conversation, so you can ask before you accept. The answers are often what separates two similar prices.

  • Would you build it from scratch, or on a tool like Retool or Looker Studio, and why?
  • Who will own the code and the hosting accounts when you're done?
  • How do you keep our data secure while you build it?

Questions companies ask

Do I need a custom app, or will a no-code tool do?

Often a tool like Looker Studio, Power BI or Retool is enough, and quicker to build and change. Ask each provider which they would use for your case and what it costs to run, so you compare like with like.

Who should own the code?

You should. Say in the deliverables that the code, the repository and any hosting or tool accounts are in your company's name, and that access is handed over when the work is done.

Ready to hand it off?

Describe it in a sentence or two. The brief goes to every provider who lists Software & web, and you compare their proposals side by side. Posting is free, and you set the budget.

Post a task

More software & web guides

All guides