Case studies

What this looks like in practice.

Three situations, one pattern: capable partners whose Databricks relationships weren't producing anything, and what changed when they were worked systematically.

01
Building from zero

A seven-figure Databricks practice in a new geography

  • Role In-house, UK lead
  • Starting point No UK presence
  • Market United Kingdom

The situation

A US-headquartered data and AI consultancy wanted to establish itself in the UK. The firm had genuine Databricks credentials in its home market, but none of that travelled. In the UK there were no Databricks relationships, no local reference customers, and no recognition whatsoever with the Databricks field team who decide which partners get put in front of which accounts.

Databricks runs largely on regional teams. A partner's standing in one geography counts for very little in another — the AEs, solution architects and partner managers in London had no reason to know the name, and no reason to recommend it.

The approach

  • Mapped the UK Databricks field organisation and worked out who actually influenced referral decisions, by account and by vertical
  • Built relationships deliberately rather than opportunistically — consistent contact, useful to them before asking anything in return
  • Aligned the firm's positioning to what Databricks UK was actively selling that year, rather than what the firm wanted to talk about
  • Delivered early engagements visibly well, so the field team had something concrete to point to
  • Turned those first wins into reference stories the Databricks team could use in their own accounts

Why it worked

Nothing here was a shortcut. The method was simply being useful, visible and credible to the same group of people over a sustained period, in a way that made recommending the firm the obvious low-risk choice for a Databricks seller with a customer to serve.

The outcome

The UK practice grew from a standing start into a seven-figure Databricks-attached business. It now receives millions in Databricks-referred opportunity each year, with referrals arriving as a matter of course rather than as a favour.

ZeroUK relationships at the outset
7 figuresDatabricks-attached UK business
MillionsIn referred opportunity annually
02
Dormant to referred

Activating relationships a partner already had

  • Client US boutique consultancy
  • Focus Private equity & portfolio
  • First referral Within 3 months

The situation

A New York boutique with a strong enterprise client list and real Databricks delivery experience. On paper everything was in place — certifications, completed projects, a registered partner profile, and people who had met Databricks staff at events and on delivery.

And yet referrals weren't coming. The relationships existed but had gone quiet, the partner narrative sounded like every other firm on the portal, and nobody internally owned the Databricks partnership as a dedicated responsibility.

The approach

  • Assessed the partnership across five dimensions — positioning, relationship health, technical credibility, customer base alignment and internal ownership
  • Identified the niche the firm could credibly own, rather than competing as a generalist against every other partner
  • Rewrote the partner narrative so a Databricks AE could explain in one sentence what made them worth recommending
  • Agreed a go-to-channel plan: which Databricks people to re-engage, in what order, and what to say
  • Ran weekly coaching with the team — preparing before Databricks conversations, debriefing afterwards, clearing blockers as they came up

What made the difference

The relationships were already there. What changed was the discipline around them — a clear reason for Databricks to care, a sharper story, and a weekly rhythm that kept the work moving instead of slipping behind delivery. The team executed consistently between calls, which is the single biggest predictor of how quickly this works.

The outcome

The first Databricks referral arrived within three months of the engagement starting. New client wins followed, and the firm's Databricks conversations shifted from occasional and reactive to regular and expected.

The engagement was extended into a longer-term arrangement.

3 monthsTo first Databricks referral
WeeklyCoaching cadence maintained
ExtendedEngagement renewed long-term
03
Reclaiming a buried practice

When Databricks sits second to another platform

  • Client European boutique
  • Team size 40–60 people
  • Starting tier Entry level

The situation

A consultancy with deep credentials on a competing data platform and a smaller, newer Databricks practice alongside it. The Databricks work was good, but it was always framed as an adjunct to the primary platform rather than a capability in its own right.

The effect on the Databricks field team was predictable. Asked to recommend a partner, an AE hesitated — not because the firm lacked skill, but because there was a real chance the customer would be steered toward the competing platform instead. A partner who might not advocate for Databricks is a partner who doesn't get the call.

The approach

  • Agreed the prerequisite first: a genuine commitment to presenting as a Databricks consultancy, not a firm that happens to do Databricks
  • Appointed a named Databricks lead internally and a dedicated seller who owned the partnership commercially
  • Separated the Databricks story from the primary platform story so each could stand on its own
  • Chose a single industry where the firm's delivery history was strongest and built the narrative around it
  • Re-engaged the Databricks field team with a clear, differentiated proposition and a visible internal counterpart

What made the difference

The hard part was not the positioning work — it was the decision that preceded it. Once leadership committed to Databricks as a practice rather than a hedge, everything downstream became straightforward. Partners who treat the partnership as optional get treated the same way in return.

The outcome

Within the programme the firm moved from being an unknown quantity to a named partner the regional Databricks team actively considered for relevant opportunities in its chosen vertical.

1 verticalClear position established
2 rolesDedicated lead and seller appointed
4 monthsProgramme duration

Recognise your own situation?

Tell us about your Databricks practice and what you're trying to achieve. We'll tell you honestly whether we can help.

Start a conversation