Set shoring and pyramids for data, BI and advanced-analytics implementations

For data leaders and solutioning teams staffing enterprise data management, BI and advanced-analytics programmes.

Engagement type: Solo Pod
Experts: 1 lead · 1 consulted
Hours: ~30
Duration: 2 weeks

What the client needed

A firm needed the typical onshore, offshore and nearshore split and the resource pyramids for implementing three modules — enterprise data management, BI and visualisation, advanced analytics — function by function, and how the pyramids vary across them.

The experts engaged

Previously at Tech Mahindra, LTIMindtree, TCS, Cognizant · 18 years

Roles helddelivery head and principal data architect · advisory data consultant · senior cloud data architect

Solutioning and oversight of data-architecture engagements for global clients; a team of 20 architects and 40 modellers
As-is and target-state architectures and roadmaps for a UK investment bank
Led a 120-member data-engineering team

Atlas Verified · Tier B

Previously at Nagarro, Cognizant, Deloitte · 25 years

Roles heldassociate director and head of presales, data architecture · principal architect, data modernisation

A decade leading data-mesh and data-lake engagements for global clients
Lakehouse, data fabric and data mesh on AWS and Azure

Atlas Verified · Tier B

A exceptional · B strong · C competent — the tier is derived from the whole assessment, not a single score. The transcript and report are open to you before you engage. How verification works →

The brief

The questions on the table

As the client wrote them, lightly shortened. Client and respondents are not named.

Q1
What onshore/offshore/nearshore split applies to each function inside data management, BI and advanced analytics?
Q2
What do the resource pyramids look like per module, and where do they differ?
Q3
What changes the split — data residency, client access, platform?

The hours

What the work involved

01
Function map per module
The functions inside each module — ingestion, modelling, governance, reporting, data science, MLOps — as the frame for the numbers.
02
Shoring and pyramid workbook
Per function: the split, the pyramid by level, the drivers, and what the expert had actually staffed on comparable programmes.
03
Cross-check
A presales head for data architecture engagements checked the numbers against live bids.
04
Working session
With the client’s data leadership.

Deliverables

What the client received

Shoring split by functionPer module.
Pyramids by moduleWith the variations and reasons.
DriversWhat moves the split.
One working sessionWith notes.

The terms

What an engagement like this costs

You buy hours in blocks and can change the expert at the end of any block, at no extra cost. Longer projects run in stages: pause after a block, pick up the next stage when you are ready.

Pricing in full →

Rate band: $65–$250 /hr; Senior specialists can be up to $500
Hour blocks: 1 · 2 · 5 · 10 · 20 · 50 · custom
This engagement: Solo Pod · ~30 hours · 2 weeks

Staffing a data programme?

Describe what you need

For example: “We need shoring and pyramid norms for a data-management and BI implementation before we negotiate with the vendor.”

We aim to come back with matched experts within 24 to 72 hours.