--- title: "Most transformation is a slide deck with a budget attached." url: "https://vucale.com" description: "VUCALE is a vendor-neutral biz-tech consultancy for companies becoming data-driven and AI-native: diagnosis, a working pilot, and change work that actually lands." --- Pre-launch · no engagements yet # Most transformation is a slide deck **with a budget attached.** VUCALE works with companies trying to become genuinely data-driven and AI-native. We sell diagnosis you can act on, a working pilot in weeks rather than a design in months, and the change work that decides whether any of it survives contact with the organisation. We resell nothing, so the recommendation is not shaped by anybody's margin. [Join the waitlist](https://vucale.com/contact)[Read the blog](https://vucale.com/blog) - No reselling, no partner quotas - A working pilot, not a target model - No clients to name yet The problem ## Why transformation programmes fail in ways nobody writes down Rarely the strategy. Almost always one of these three, and none of them appears in the proposal. ### The constraint is change capacity The strategy is fine. The organisation has four other programmes running, the same six people are on all of them, and there is no capacity left to absorb another. Nobody measures this, so every plan assumes it away. ### Advice you cannot act on The deliverable is a document. It is thorough, it is correct, and six months later nothing runs differently — because the gap between a recommendation and a working system was never anybody's scope. ### Advice shaped by the margin A consultancy that resells licences and implementation hours has an answer before it has a question. That does not make the advice wrong; it makes it impossible for you to tell whether it is. How we work ## Frame, build, hand over Three phases, and the last one is the one most consultancies are structured to avoid. 1. 01 ### Frame What problem, what would measurably change, and what the organisation can actually absorb this quarter. Short, paid, and yours to keep — including the version where the answer is that this is not the right problem to solve now. 2. 02 ### Build Something working, in weeks. Not a target operating model, not a maturity assessment — a real thing running against real data that people can use and criticise. Being wrong in week six is cheap; being wrong in month nine is not. 3. 03 ### Hand over Your team runs it, documented, in your repositories, with our involvement declining on a written schedule. If the engagement does not get smaller over time, one of us is not doing the job. What we do ## Six things, and one of them is not a deck The work a company needs between deciding to change and something actually being different. ### Diagnosis you can act on Where the decisions actually get made, what data they use, and where the process breaks. Written as a set of specific changes with owners rather than as a maturity score. ### A working pilot One real problem, solved end to end, in weeks. It either works or it does not, and both outcomes are worth more than a design that has never met an operator. ### Data and BI foundations The unglamorous part: definitions people agree on, pipelines that run, numbers that reconcile. No amount of AI compensates for two departments meaning different things by revenue. ### AI where it earns its place Agents and models applied to processes that are actually defined, with the boundary written down and a person approving anything irreversible. Applied to an undefined process, they produce confident nonsense faster. ### Change work as real work Who loses something, who has to learn something, and who has been through three failed programmes already. Budgeted properly rather than added as a workstream nobody staffs. ### Vendor selection with nothing at stake We are not a reseller, implementation partner or certified anything. There is no margin, quota or partner tier behind a recommendation, which is the only structural reason to believe one. ## The stacks we work across Companies rarely get to start from nothing. Most already have commitments — a data platform, a cloud, a licence estate — and the useful question is what to do with what you have rather than what you would buy if you were starting again. So the work spans commercial platforms and sovereign open-source ones, and which one is right depends entirely on the company. - **Commercial platforms.** Palantir, Microsoft, Google and AWS estates, where they are already in place or genuinely the right answer. - **Sovereign open source.** Where owning the system matters more than the shortest path, and increasingly that is a procurement requirement rather than a preference. - **No partner status is claimed.** We are not a partner, reseller or certified implementer for any vendor and use no vendor logos. If that ever changes, it will be stated here plainly. - **Mixed is normal.** Most real answers are a commercial platform for one thing and an open stack for another, which is unsatisfying to everybody selling a single answer. ## What a consultancy with no clients can honestly say This industry sells on case studies and logos, and we have neither. Rather than describing hypothetical engagements in the past tense, here is what we would ask you to judge instead — and what we would put in a contract so that judging us is possible at all. - **No case studies.** None, because there are no engagements. Any that appear here later will name what actually happened, including what did not work. - **Judge the framing.** Ask us to frame your problem in an hour and see whether the questions are better than the ones being asked internally. - **Judge the exit.** How the engagement gets smaller, what gets handed over, and what happens if you stop. Written in at the start. - **Judge the writing.** The blog is the closest thing to a work sample we have, and it is deliberately specific enough to disagree with. Where we are ## No engagements, said plainly A consultancy that has not delivered anything should lead with that rather than with a methodology diagram. 1. Now ### Our own transformations Applying the method to a family of pre-launch companies we are responsible for, which is a smaller test than a client but an honest one. 2. Next ### First engagements A small number, starting with framing rather than a programme, and chosen for fit rather than size. Some will end at the framing, which is a legitimate outcome. 3. Later ### Publishing the method Written down in enough detail that a company could run it without us. A method that only works when we are in the room is a dependency, not a method. FAQ ## Frequently asked questions What is VUCALE in one sentence? A vendor-neutral biz-tech consultancy that frames the problem, builds something working in weeks, and does the change work that decides whether it survives — for companies trying to become data-driven and AI-native. What does the name mean? VUCA plus agile. VUCA is the old shorthand for volatile, uncertain, complex and ambiguous conditions; agile is the response most organisations adopted in name. The interesting work is in the gap between those two things. Are you a Palantir, Microsoft, Google or AWS partner? No. Not a partner, not a reseller, not a certified implementer, and we use no vendor logos. We work across those platforms where they are already in place or genuinely right, and there is no margin behind the recommendation. Then how do you make money? Fees for the work: framing, building, and change support. Nothing from licences, nothing from referrals. It is a smaller business model and it is the only one where our advice and your interest point the same way. What size of company is this for? Companies large enough to have real process complexity and small enough that a decision does not need four committees. Somewhere between a hundred and a couple of thousand people, roughly, though the shape of the problem matters more than the headcount. Do you do the technical work or just advise? Both, and the reason is that separating them is how transformation programmes fail. A recommendation nobody builds and a build nobody adopted are the two standard outcomes, and they have the same root cause. Do you have clients or case studies? No. Not one. Describing hypothetical engagements as though they happened is the most common dishonesty in consulting, and the first real one will be described here with what went wrong in it. How do you price? Framing is a small fixed fee. Build work is fixed-scope in short increments rather than open-ended time and materials, because a consultancy paid by the hour has an incentive nobody should have to manage around. ## Start with an hour, not a programme The waitlist form goes live soon. Until then the blog is the work sample: specific enough to argue with, which is the point. [Contact](https://vucale.com/contact)[Read the blog](https://vucale.com/blog) No form yet, no data collected — just come back.