Developers for your Tableau dashboards

Hire developers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce developers for Tableau dashboards, matched to your work, so you choose who joins your team.

Thanks, we’ll be in touch soon.

{{ heroStatus }}

You’re in good company

A few of the companies we’ve worked with.

How hiring works

From the first call to their first day, you decide each step.

  1. You tell us.

    Tell us about the work

    A short call about your dashboards, the data behind them, and who you need. The first call is free.

  2. We introduce.

    Meet developers matched to it

    Within 48 hours, we introduce developers whose experience fits, with the work each has done.

  3. You choose.

    Choose who joins

    You talk to each one and decide who starts.

  4. They start.

    Start on a date you agree

    They join your team in your tools, and work in your time zone.

What they work on

Data sources, dashboards, extracts and permissions, and the servers or sites behind them.

Data sources

Published, related at each table’s level, and shared by the workbooks that need them.

Calculations

Written once, with level of detail expressions where a number needs another level.

Dashboards

Built around the questions people ask, with filters and actions that move together.

Extracts

Incremental refresh and schedules spread out, so refreshes finish.

Permissions and row-level access

Locked project permissions, and each person shown only their rows.

Performance

Slow dashboards recorded, and the slowest query fixed first.

Upgrades and moves

Tableau Server deployments kept within their support window, or moved to a Tableau Cloud site.

Planning shared data sources, or a move to the cloud? Dashboard development

Ways to hire

One developer

Full time, by the month, working as part of your team.

A small team

Developers who look after your dashboards together, from the data sources and the calculations to the extracts, the permissions and the next upgrade.

How each is paid for: PricingWhen each way of working fits: Engagement Models

Working in your team

They work the way your team already does.

  • Your tools. Your own chat, tickets and code repository, so you see the work as it happens.
  • Your hours. They work in your time zone, on hours you agree before anyone starts.
  • Your access. You decide what they can reach, and remove it when they leave.

Tell us who you need

A few details are enough to start. We’ll reply by email to arrange a short call.

What should they work on?

{{ eWork }}

How many developers?

{{ eDevs }}

When should they start?

{{ eStart }}

{{ eHName }}

{{ eHMail }}

{{ eHSend }}

{{ hireThanks }}

We’ll be in touch by email, and introduce developers matched to your request within 48 hours.

Questions worth asking

How soon can a developer start?

We introduce developers matched to your work within 48 hours. Once you’ve chosen, they start on a date you agree.

Can we interview them first?

Yes. You talk to each developer and choose who joins.

Will they work in our time zone?

Yes. They work in your time zone, on hours you agree before anyone starts.

What does it cost?

It depends on the experience you need and how long you need them. Your proposal sets out the monthly fee and how you pay before anyone starts.

Pricing

Can they spread out refreshes that all start at once?

Yes. They look at when each extract refresh starts and how long it runs, move the longest to quieter hours, and switch the ones that can to incremental refresh, with a full one now and then.

Can they put our dashboards in our own app?

Yes. They embed them with each person signed in through your app, so each sees only their own data.

Can they set our permissions by project, not workbook by workbook?

Yes. They move permissions onto projects and groups, lock them to the project where it helps, and check what each site role can open.

Can you take on the whole project instead?

Yes. That starts with a written review of your server or site, the dashboards people open most and the data sources behind them, and a proposal for a first step, such as two workbooks brought onto one shared data source.

Dashboard development

Tableau, Tableau Cloud and Tableau Server are trademarks of Salesforce, Inc., and the other Salesforce product names on this page may be too. Webair is independent of Salesforce, Inc., and isn’t sponsored by, endorsed by or affiliated with it.

Let’s build it better

Tell us about your dashboards, the data sources behind them and the work ahead, and we’ll introduce developers who can start there.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}