The First 8 Weeks of Witboost – From Installation to Production

Here’s a question we hear a lot from data leaders evaluating platforms: “Once we sign, how long until we actually see something running in production?”

It’s a fair question — and it comes from experience. Most of these leaders have been through at least one platform initiative that took six months to deliver an architecture document, another three to set up infrastructure, and then quietly stalled when the team realised nobody had agreed on what “governance” actually meant in their context. By the time the first data product went live, the original sponsor had moved on and the budget was under review.

We’ve designed our onboarding to work differently. Our target is to have you running real data products in production within eight weeks. A working platform with governance, access control, CI/CD, and actual data products that your organisation can discover and consume.

This article walks you through exactly what those eight weeks look like — phase by phase, decision by decision. We’re sharing this because we believe transparency about the implementation process is the best way to set expectations, and because we’ve found that customers who understand the journey upfront get to production faster.

Why Most Platform Rollouts Stall Before They Start

If you’ve been in the data space long enough, you’ve seen the pattern. A new platform initiative kicks off with a big vision:

The first three months are spent in architecture workshops. The next two months go to vendor evaluation. Then procurement takes another six months. By the time the platform is actually installed, you’re ten months in and nobody has built anything.

The root causes are usually the same:

1. Scope paralysis — the team tries to solve every governance question before writing a single line of configuration. “We can’t start until we’ve defined our complete RBAC model across all 14 business units.”
   
   
2. The perfect architecture trap — endless debates about target-state architecture when what you need is a working starting point. Perfect is the enemy of production.
   
   
3. Training gaps — the platform team doesn’t get hands-on training early enough, so they can’t make informed decisions during design workshops. This creates a dependency on external consultants for every question.
   
   
4. No starter kit — teams start from a blank canvas, which means the first data product takes as long to build as setting up the entire platform.

The industry is moving away from this model. According to Gartner’s latest guidance on composable data platforms, organisations that adopt an incremental, MVP-first approach to platform implementation see significantly faster time-to-value compared to those that attempt comprehensive rollouts. The message is clear: get to production with something small, prove it works, then expand.

That’s exactly the philosophy behind our eight-week fast track.

The 8-Week Fast Track: What Actually Happens

Our onboarding follows five distinct phases, each with a clear outcome. Here’s the high-level view:

A few things to notice about this timeline:

First, the early phases are intentionally compressed. We don’t want you spending weeks on preparation — we want you building.

Second, the “Groundwork” phase is where most of the critical decisions happen. This is the design workshop series where we define your platform landscape, access model, data contracts, and governance policies together.

Third, building starts with sample products — working examples that prove the platform operates correctly — before you bring in your real data products.

The philosophy is simple: start opinionated, then customise. We give you a working baseline through the starter kit, you validate it with sample products, then you adapt it to your specific requirements. This is fundamentally different from starting with a blank canvas and building everything from scratch. 

Week 1–2: Training, Installation, and the Design Workshop Series

The first two weeks are the densest part of the journey. Three things happen almost in parallel:

Platform Team Training (18 hours)

Before we touch any configuration, we invest 18 hours in training your platform team. This isn’t a passive webinar — it’s a hands-on programme covering four capability areas:

Why train before you design? Because we’ve learned that design workshops produce dramatically better outcomes when the platform team understands the art of the possible.

A team that has seen how RBAC actually works in Witboost makes sharper decisions about their access model. A team that understands templates can design a realistic architecture blueprint. Training isn’t a prerequisite — it’s an accelerator.

Installation (Half a Day to 2 Days)

Installation itself is straightforward. Depending on your environment complexity (cloud provider, network restrictions, SSO integration requirements), it takes between half a day and two days.

The key dependencies are:

• SSO integration (your identity provider needs to be reachable)
  
  
• Git repository access (where data product definitions will live)
  
  
• Network and security configurations (firewall rules, private endpoints if needed)

We’ve deliberately engineered the installation to be fast. Witboost is a control plane, not a data processing engine — it doesn’t need complex infrastructure provisioning or heavy compute clusters.

The Design Workshop Series (2 Days)

This is where the real decisions happen. Over approximately two days of intensive workshops, we work through seven design topics with your team. Each topic answers a specific question about how your platform will operate.

Structural decisions:

Data product decisions:

These workshops aren’t theoretical exercises. Each one produces a concrete decision that directly feeds into platform configuration. By the end of the two days, you have a complete set of design decisions documented and ready to implement. We bring blueprints and reference architectures for everything.

A common pattern we see: customers initially want to over-engineer the RBAC model or define policies for every possible scenario. We push back on this — gently. The goal is to define what’s needed for the MVP, not the final state.

You can always add more policies, refine access controls, and expand landscapes later. What you can’t do is recover the weeks lost to premature optimisation. 

Week 3–8: Building with the Starter Kit and Going Live

Once the design decisions are locked, implementation starts — and it starts fast, because you’re not building from zero.

The Starter Kit Approach

Witboost ships with a starter kit: a pre-built, opinionated implementation that includes sample templates, tech adapters, governance policies, and data product examples. Instead of asking your team to build everything from scratch, we say: “Here’s a working setup. Now let’s adapt it to the decisions we made in the workshops.”

This is a critical difference from most platform implementations. Typical projects start with documentation, then architecture, then implementation — a waterfall inside an agile wrapper. The starter kit inverts this: you start with something that works, then evolve it.

The adaptation process follows a clear sequence:

1. Deploy the starter kit — install sample templates, tech adapters, and policies into your configured Witboost instance
   
   
2. Validate with sample products — create and deploy sample data products to verify the end-to-end lifecycle works (creation, versioning, deployment, governance checks, discovery)
   
   
3. Customise templates — adapt the starter kit templates to match your specific technology stack and the architecture blueprint from the design workshops
   
   
4. Build your first real data products — your team builds 2–3 real data products using the customised templates, going through the full lifecycle
   
   
5. Enforce governance — activate the automated governance policies defined in the workshops, verify they trigger correctly, iterate on edge cases

Throughout this phase, our customer success team works alongside yours, as a coach. The explicit goal is that by week 8, your platform team owns the platform. They can create templates, modify policies, onboard new domains, and troubleshoot issues without calling us.

What “Going Live” Actually Looks Like

At the end of week 8, you have:

• A running Witboost instance connected to your SSO, Git provider, and CI/CD pipelines
  
  
• A configured platform landscape with defined domains, environments, and boundaries that mirror your organisational structure
  
  
• Working governance — RBAC enforced through your identity provider, computational policies running on every data product operation, access control automated
  
  
• 2–3 real data products in production — not sample data, not synthetic datasets, real data products that your organisation can discover and consume through the marketplace
  
  
• A trained platform team that understands how to operate, extend, and customise the platform

What you don’t have on week 8 (like we said at the beginning, fully transparency), is a fully scaled platform.

You haven’t onboarded every domain, and you haven’t built templates for every technology in your stack. You haven’t written policies for every compliance scenario. And that’s exactly the point. 

What “Production” Really Means on Week 8 and What Comes Next

We’re deliberately precise about what “production” means at the 8-week mark, because over-promising is the fastest way to destroy trust.

At week 8, you have an MVP: a Minimum Viable Platform.

It’s real, it’s in production, and it works. But it’s the starting point, not the destination. Here’s how to think about the maturity curve:

The reason we push hard for an MVP in 8 weeks isn’t just about speed. It’s about organisational dynamics.

In our experience, data platform initiatives that don’t show production results within the first quarter lose executive sponsorship. The budget review comes, someone asks “what have we delivered?”, and if the answer is “we’re still in the design phase”, the project gets deprioritised.

An MVP that’s live in production — even a small one — changes the conversation entirely.

Instead of defending the investment, you’re discussing how to scale it. Instead of explaining what the platform will do someday, you’re showing what it does today.

This is also where the starter kit pays dividends after week 8. Because your first data products were built on standardised templates, adding the next ten is dramatically faster. The patterns are established, the governance is already running, and your team knows how to operate the platform.

We’ve seen customers go from 3 data products at week 8 to 30 by month 4, because the hard decisions were already made.

The customer success team doesn’t disappear after week 8 either. We shift from a coaching role to a support and enablement role, helping you onboard new domains, build advanced policies, and integrate new technology stacks as your platform grows.