Fixed scope · Six weeks · A foundation you can build on
A governed lakehouse your executives can question in plain English
If your Databricks pilot stalled, or the business still reports off a legacy warehouse nobody quite trusts, the Launchpad gets a working lakehouse in front of your executives in six weeks, with the scope fixed at the start. Governance in Unity Catalog comes first.
Then come ingestion that holds, bronze, silver and gold layers for the business areas we agree during scoping, dashboards people actually open, and a Genie space with real semantic definitions, so leadership can ask questions in plain English and you can check the answers.
- Length
- Six weeks
- Who it is for
- Teams modernising off a legacy warehouse, or stalled after a pilot
- Bench
- 80 Databricks-certified engineers
What exists at the end of week six
- 01A workspace foundation with an identity and environment strategy you can defend
- 02Unity Catalog structure and the governance patterns that go with it
- 03Ingestion paths through Lakeflow or Jobs, whichever suits the source
- 04Bronze, silver and gold layers for the domains you named at the start
- 05AI/BI dashboards for the people who asked for them
- 06A working Genie space with real semantic definitions
- 07Runbooks, and your team able to use them
What makes it faster
Where the Launchpad replaces an existing warehouse, we migrate it underneath the build with Airlift, which profiles the old estate, converts what it can, reconciles the numbers and cuts over in reversible steps.
Clients we have done this for
B2B ecommerce
DealerIQ
TotalLoop finds a dealership's customers with equity in their vehicle and matches them to cars on the lot. DealerIQ brought the idea and the dealership know-how, and our senior engineers worked inside its team to build it on Azure, test it with one dealer account and ship a lean first version. Later we moved it off Cosmos DB and SQL Server onto Databricks Lakebase, in waves that could each be rolled back.
Automotive / Fintech
Location Services
Location Services' repossession platform automates assignment intake, so fewer people handle each case, and our engineers built it with the company's own technology team. When it was time to leave Synapse and SQL Server, we moved it onto Databricks in waves that could each be rolled back, and the rules engine that checks every assignment came through unchanged.
FAQ
Questions about Lakehouse Launchpad
Is six weeks realistic, or is it a sales number?
It is the programme length, and it holds because the scope is fixed at the start. What moves the date is access: if credentials and source system owners take three weeks to appear, the clock reflects that. We say so during scoping.
What if our data is messier than we admitted?
It usually is, and the two-to-three week discovery before the build exists to find that out while it is still cheap. If discovery shows six weeks is not honest for your estate, we say so and rescope before anything starts.
Do you leave, or do we get stuck with you?
The runbooks and the enablement are deliverables, and the point of them is that your team can run this without us. Plenty of clients keep us on for the next programme, but that should be a decision rather than a dependency.
We already have a lakehouse. Is this still relevant?
Then you probably want the Health Check instead, which assesses what is there before anyone proposes rebuilding it. The Launchpad is for standing something up, not for replacing a platform that works.