Whoz connector

Use your Whoz data for reporting, automation and AI.

Data Panda pulls your Whoz consultant profiles, skills, missions, opportunities, staffings and timesheets into the same warehouse as your finance, sales and HR data. From one place we turn it into dashboards, automations, AI workflows and custom apps that staffing leads, partners and finance use every week, not only when a quarterly review or a margin slip forces the question.

About Whoz

The cloud platform that matches consultants to projects for IT services firms, consultancies and engineering offices.

Whoz was founded in 2016 in Paris by Jean-Philippe Couturier and is headquartered in the city today, with PSG Equity as the lead growth investor since 2022. The platform reports more than 800,000 users across 115 countries, with the customer base concentrated in IT services firms, management consultancies, audit and advisory shops, and engineering offices that bill their people by the day.

The product sits on four pieces. Talent Cloud holds the consultant register, the skills graph (the company maintains a Professional Services Ontology with roughly 1.2 million skills and 5,000 certifications, plus 300,000 skill synonyms in the matching engine) and external bench like freelancers and partner firms. Business & Staffing Studio runs the opportunity-to-staffing flow: missions and their phases, the talent requests against them, the Wise matching engine that ranks candidate consultants, and the staffing decisions that land on the planning. Performance Analytics surfaces activity rate, billable FTE, margin per mission and pipeline coverage across business units, geographies and grades. AImplify is the layer of AI agents on top. Pulled into a warehouse next to a CRM like HubSpot or Salesforce, a finance system like Exact Online, and an HRIS, the Whoz record finally answers questions that one screen alone does not: which practice is below billable target while another is turning down work, where the next quarter's pipeline already outstrips the staffed bench, and which opportunities went to a competitor because the right-skilled consultant came free three weeks too late.

What your Whoz data is for

What you get once Whoz is connected.

Staffing and margin reporting

Billable load, pipeline coverage, bench composition and margin per mission on one page across every practice and geography.

Billable activity rate per consultant, grade and practice, against the planned target
Mission margin per project, partner and account, with the cases below band named
Bench composition per skill cluster and seniority, projected on the next two quarters of pipeline

Process automation

Turn Whoz opportunity, staffing and mission events into the downstream work the rest of the stack expects, without a per-tool handoff.

Sync new Whoz missions and won opportunities into the CRM and the finance system on the same key
Push staffing decisions into the planning, the project tool and the timesheet ledger as they land
Trigger an alert when a Wise match returns no in-band consultant for a high-value opportunity

AI workflows

Put the Whoz consultant register, skills graph and pipeline behind AI that reads the full staffing picture.

Skill-gap scoring across the bench against the next two quarters of opportunity demand
Win-likelihood scoring on opportunities joined to staffing feasibility per practice
Natural-language Q&A across consultants, skills, missions and the opportunity pipeline

Custom apps on your data

Lightweight tools on Whoz data for partners and BU leads who should not need a Staffing Studio seat to read their own practice.

Partner cockpit with practice billable load, pipeline coverage and bench risk
Staffing-conflict workbench with the missions where two requests fight for the same consultant
Opportunity-to-staffing tracker with the deals at risk for lack of an in-band match

Use cases

Use cases we deliver with Whoz data.

A list of concrete reports, automations and AI features we have built on Whoz data. Pick the one that matches your situation.

Billable load per practiceBillable activity rate per consultant, grade, practice and geography against the approved target.

Bench-versus-pipelineAvailable consultants per skill cluster and seniority, plotted against the next two quarters of opportunity demand.

Mission margin trackingMargin per mission, project and account, joined to the staffed grades and the actual billed days.

Opportunity-to-staffing lead timeDays from opportunity creation to first proposed staffing, per practice, partner and account size.

Wise match coverageTalent requests where the Wise engine returned no in-band candidate, per skill cluster and grade.

Skill-gap heatmapSkill demand from the pipeline minus skill supply on the bench, per cluster and seniority.

Pipeline coverage per BUWeighted opportunity value against billable capacity for the next two quarters, per BU and partner.

Subcontractor versus internal mixShare of billed days delivered by external partners and freelancers per mission, account and practice.

Timesheet completion lagDays from week-end to validated timesheet per consultant, manager and practice.

Bench-aging by skill clusterConsultants on the bench past their target window, per skill cluster, seniority and office.

Won-versus-lost opportunity reasonsClosed opportunities by stage, reason and competitor, joined to staffing feasibility at the time of decision.

Account profitability per practiceRevenue, billed days, margin and discount per account, plotted across practices and over time.

Real business questions

Answers you will finally get.

Which practice is sitting below billable target while another is refusing work?

Billable activity rate per consultant rolled up to grade, practice and geography, plotted next to the open talent requests the same practice could not fill. The managing partner sees the office where Cloud Engineering sits four points below target while Data is turning down two missions a week for lack of seniors, four weeks before the next P&L review would have surfaced the same gap.

Which opportunities are at risk because the Wise engine cannot find an in-band consultant?

Talent requests joined to the Wise match output and the underlying opportunity stage, weighted by deal value. The sales partner sees the deals already in late stage where no in-band candidate exists, and the skill clusters where the bench is structurally short, before three of those opportunities slip to the next quarter for staffing reasons rather than commercial ones.

What does a delivered consultant-day really cost across practice, grade and account?

Billed day from Whoz joined to consultant cost from payroll, expenses from finance and the staffed margin per mission, rolled up to grade, practice and account. The CFO sees that the loaded margin on a strategic account is running below the headline rate because three senior consultants are running fifteen percent over allocation, before the next quarterly account review prices in a renewal at the wrong band.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Billed days, mission margin and bench cost per practice and account, lined up with the GL, the consultant cost from payroll and the staffed plan. Group finance stops waiting on a Whoz export and a project tool extract per BU, and the gross-margin line on the management report ties back to the missions and consultants it came from.

For sales leaders

Pipeline coverage joined to the staffed bench per skill cluster and grade, with the deals at risk for lack of an in-band match named. The commercial partner sees which late-stage opportunities cannot be staffed in time and which clusters need a hire or a partner before the next quarter, instead of finding out at sign-off.

For operations

Mission staffings, talent requests and timesheet state across practices in one delivery picture. The COO sees which BU is staffing past start dates, which missions are running over allocation, and which timesheets are sitting unvalidated past the close window.

Ideas

What you can automate with Whoz.

Pair with Slack

Drive staffing, bench and unmatched-request Slack moments from the Whoz timeline

New Whoz missions post in the practice channel with the requested skills, grade and start date, so the staffing lead sees the request the moment it lands. Talent requests where the Wise engine returns no in-band candidate ping the practice partner directly, and consultants who roll onto the bench past their target window post in the staffing channel with the open requests they could fit. Staffing meetings stop opening with someone reading three Whoz screens out loud.

Pair with HubSpot

Match HubSpot pipeline to the Whoz-staffed bench per practice

HubSpot opportunities, weighted value and expected close dates land next to Whoz bench composition per skill cluster and grade. The revenue partner sees which late-stage HubSpot deals have no in-band match in Whoz today, and which skill clusters are about to be over-sold for the next quarter. Won opportunities flow back from HubSpot to Whoz as a mission shell with the requested skills already attached, so the staffing lead is not retyping the brief in two systems.

Pair with Salesforce

Keep Salesforce opportunities and Whoz missions on one key per account

Salesforce opportunity stage, weighted value and account hierarchy land next to the Whoz mission, talent requests and staffed grades on a shared account key. Account partners see the full picture per logo: pipeline weight, missions in delivery, billed days and bench composition aimed at the same account. Account reviews stop being a Salesforce export merged with a Whoz screenshot in a slide, and the won-versus-lost reason captured in Salesforce can finally be read against the staffing feasibility at the time of decision.

Pair with Exact Online

Reconcile Whoz billed days with Exact Online revenue per mission

Whoz mission, staffed consultants and billed days flow into Exact Online on the same project key, so the issued invoice ties back to the mission and the consultants it covers. Group finance closes the month without waiting on a billable-days export per BU, and the revenue line per practice on the management report can be read down to the consultants who delivered the days. The cases where a Whoz timesheet validation landed after the Exact period closed are listed by name, not absorbed into a generic accrual.

Pair with monday.com

Plan delivery work on monday.com against Whoz staffing per mission

Whoz staffings, allocated percentages and approved leave per consultant flow into the same view as the monday.com delivery board, so project leads see when an upcoming sprint runs into a week where the lead architect is staffed at eighty percent on another mission and the second senior is on holiday. Delivery conflicts that used to surface on the Friday stand-up surface on the planning page when the work is being scheduled, and the project-margin view ties Whoz days to the monday.com task they were booked against.

Pair with HiBob

Keep the Whoz consultant register and the HiBob people record on one employee key

HiBob joiner, mover and leaver events drive the Whoz consultant register: a new HiBob person lands as an active Whoz profile with the right office and grade, a department move re-routes the practice and reporting line, and a leaver record retires the Whoz profile and frees the staffings on the planning. The HR record stays the source of truth for who works here, and the staffing lead is not maintaining a parallel people list in Whoz that drifts from HiBob within a quarter.

Data model

Tables we make available.

These are the 1 tables we currently pull from Whoz into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.

Workspaces

Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Whoz data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Whoz to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Whoz connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Which Whoz tables land in the warehouse?

The connector pulls the consultant register with grades, practices and custom fields, the skills graph and per-consultant skill assignments, missions and their phases, talent requests with their Wise match output, staffings with allocated percentages and start and end dates, opportunities with their stages and weighted values, accounts and account hierarchy, and timesheet entries where the time module is in use. Authentication runs through a Whoz service-user API token scoped to your tenant.

Do we need every Whoz module to make this useful?

No. Whoz is sold as a suite but the connector reads what you have licensed. A firm running only the Talent Cloud and Business & Staffing Studio gets the bench-versus-pipeline, billable-load and staffing-conflict dashboards on day one. Adding the opportunity pipeline lights up the win-likelihood and pipeline-coverage views, and adding the timesheet module fills out the margin-per-mission and timesheet-completion cuts. Each module added expands the joins available across the warehouse.

How are consultant rates and other sensitive Whoz fields handled?

Day rates, cost rates and individual margin detail can be kept in restricted schemas that only finance, partners and staffing leadership reach, while the consultant register, skills, missions and bench composition power the dashboards the rest of the firm uses. Access is enforced in the warehouse, not in each dashboard, so a new operations report cannot accidentally surface a rate column it should not see.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Whoz setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors