Sound familiar?

Twelve situations that shaped what Decolla is — drawn from the day job at a working UK IT consultancy, not a whiteboard. If more than a couple read like your week, you're who we built this for.

None of these are exotic. Most of them are Tuesday.

Decolla is a product of The Cloud Platform, a working UK IT consultancy — which means it grew out of the same situations you deal with: machines that need building, people who are waiting for them, and a provisioning process that lives half in Intune and half in somebody's head.

Below are twelve of those situations. Each has its own page with the longer story and what Decolla actually does about it. Start with the one that stung.

When someone is waiting

The clock scenarios. The work is invisible until it's late — then it's the only thing anyone can see.

1. The Monday-morning starter

The kit arrived Thursday. The account exists. HR has sent the welcome email. The only thing standing between a new hire and a first day that works is an afternoon you don't have.

2. The pallet in the corridor

A hardware refresh doesn't arrive as a project plan. It arrives as boxes — and every box in that stack is an evening of somebody's time, written down nowhere.

3. The rebuild that can't wait

A machine needs flattening today. How it was built last time lives in the head of someone who's already left.

4. The laptop everyone's watching

A director's replacement machine, built by hand, while their first meeting on it sits in the calendar. Nothing sharpens the fear of a missed step like an audience.

When the knowledge lives in one head

The memory scenarios. The process works — for now, and for reasons nobody has written down.

5. The engineer who knows where everything lives

Provisioning is fine — provided one specific person never books leave, changes jobs, or falls ill. That isn't a process. It's a dependency with a pulse.

6. "It worked on the last one"

Two machines. Same model, same day, same hands. One behaves differently, and nobody can say why — because the build was never a single, inspectable thing.

7. The blank tenant

A fresh Intune tenant is hundreds of decisions dressed up as a checkbox exercise. Assembling a defensible baseline by hand is weeks of work everyone assumes is already done.

8. The image that was golden once

The golden image is now a maintenance debt with a build date nobody says out loud.

When the risk lands on you

The accountability scenarios. Whatever happens, the signature on it is yours.

9. The policy nobody dares touch

Years of accumulated configuration, and no one is certain which parts still do anything. So nothing is ever removed — it just settles, like sediment.

10. The tickets you shipped with the device

Every new machine goes out the door with the same future helpdesk tickets already on board, because the known fixes never quite make it into the build.

11. "What exactly will it change?"

Security asks what the build actually does to a device. Today the honest answer is: it depends who ran it, and on what kind of day.

12. The person you can't yet let loose

You'd hand provisioning to the newest member of the team tomorrow — if you could read exactly what they were about to run, before anything ran.

The pattern underneath all twelve

Look across them and the pattern is consistent: the pain is almost never Microsoft's machinery. Autopilot enrols, Intune delivers, the Enrollment Status Page does what it does — at Microsoft's pace, and Decolla doesn't pretend otherwise. The pain is everything around it: deciding what a build should contain, assembling it, remembering why, and carrying the risk when it changes.

That's the part Decolla takes on, inside your own tenant. A guided wizard walks the build — platform, chassis, scenario, make — and a conditional engine filters and defaults a catalogue of 260+ build items across 21 sections: OEM tooling matched to the make, power settings to the chassis, drive strategy, locale, the HVCI gate, existing tenant or new. Behind it sits a library of pre-built, industry-tested policies, scripts and fixes — including the recurring mundane helpdesk fixes and the hardening that usually gets left for later — so the weeks of do-it-yourself assembly happen in seconds. Defining a build takes minutes.

Before anything runs, you get an itemised written plan to read and approve, with every item showing its delivery method and its reversibility class — automatic, reversible, or flagged irreversible. Afterwards, you can roll back per item or the whole build. That rollback covers Decolla's own changes, plainly scoped — it won't rewind a Microsoft install failure, and we won't tell you it will.

Decolla is in private build, and early access is by waitlist. If one of the twelve above happened to you this month, that's exactly who it's for.