[{"data":1,"prerenderedAt":24},["ShallowReactive",2],{"blog-article-one-workflow-not-a-transformation":3},{"id":4,"slug":5,"body":6,"html":7,"title":8,"description":9,"category":10,"tags":11,"author":15,"date":16,"year":17,"month":18,"quarter":19,"status":20,"featured":21,"series":22,"seriesOrder":23},"2026\u002F08\u002Fdigital-assets\u002Fone-workflow-not-a-transformation","one-workflow-not-a-transformation","Transformation programmes are how regulated teams postpone production.\n\nThey sound responsible: multi-workstream, multi-vendor, multi-quarter. They also guarantee that dual control on the *money* workflow stays unfinished while the workshops multiply.\n\nOur engagements are narrow on purpose.\n\n## The rule\n\n**One named workflow per engagement.**\nThe usual default is onboarding → first transfer, or the first settlement event that creates real risk.\n\nA second workflow is a **change request**, not a favour.\n\n## Why buyers accept this\n\n- Scope is fixed and deliverables are clear.\n- The outcome is a decision: build it, or don't.\n- Controls and evidence are proven on one path before you industrialise everything.\n\n## Why this is easier for us than for most\n\nWe don't start from a blank repository. The workflow is mapped onto an existing application foundation built on the same architecture as everything else we deliver. A narrow first scope is cheap to extend later through an [Application Family Program](\u002Fservices\u002Fapplication-family-program), because the identity, integrations and evidence model are shared.\n\n## How it shows up\n\n- A [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint) defines production for *this* book: as-is, to-be, controls, evidence and the delta.\n- An [AI Production Sprint](\u002Fservices\u002Fai-production-sprint) configures and integrates the application on *your* systems.\n\nIf a vendor cannot describe deliverables for **one** workflow without inventing a programme office, they are not selling production.\n\n**Next step:** [Bring the workflow name](\u002Fcontact). If you cannot name it, don't buy yet.\n\n*Fence: Implementation only. Not a VASP.*\n","\u003Cp>Transformation programmes are how regulated teams postpone production.\u003C\u002Fp>\n\u003Cp>They sound responsible: multi-workstream, multi-vendor, multi-quarter. They also guarantee that dual control on the \u003Cem>money\u003C\u002Fem> workflow stays unfinished while the workshops multiply.\u003C\u002Fp>\n\u003Cp>Our engagements are narrow on purpose.\u003C\u002Fp>\n\u003Ch2>The rule\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>One named workflow per engagement.\u003C\u002Fstrong>\nThe usual default is onboarding → first transfer, or the first settlement event that creates real risk.\u003C\u002Fp>\n\u003Cp>A second workflow is a \u003Cstrong>change request\u003C\u002Fstrong>, not a favour.\u003C\u002Fp>\n\u003Ch2>Why buyers accept this\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Scope is fixed and deliverables are clear.\u003C\u002Fli>\n\u003Cli>The outcome is a decision: build it, or don't.\u003C\u002Fli>\n\u003Cli>Controls and evidence are proven on one path before you industrialise everything.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Why this is easier for us than for most\u003C\u002Fh2>\n\u003Cp>We don't start from a blank repository. The workflow is mapped onto an existing application foundation built on the same architecture as everything else we deliver. A narrow first scope is cheap to extend later through an \u003Ca href=\"\u002Fservices\u002Fapplication-family-program\">Application Family Program\u003C\u002Fa>, because the identity, integrations and evidence model are shared.\u003C\u002Fp>\n\u003Ch2>How it shows up\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa> defines production for \u003Cem>this\u003C\u002Fem> book: as-is, to-be, controls, evidence and the delta.\u003C\u002Fli>\n\u003Cli>An \u003Ca href=\"\u002Fservices\u002Fai-production-sprint\">AI Production Sprint\u003C\u002Fa> configures and integrates the application on \u003Cem>your\u003C\u002Fem> systems.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If a vendor cannot describe deliverables for \u003Cstrong>one\u003C\u002Fstrong> workflow without inventing a programme office, they are not selling production.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> \u003Ca href=\"\u002Fcontact\">Bring the workflow name\u003C\u002Fa>. If you cannot name it, don't buy yet.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Implementation only. Not a VASP.\u003C\u002Fem>\u003C\u002Fp>\n","One workflow, not a transformation","Public offers stay narrow: one named workflow per statement of work, not a multi-quarter transformation programme.","digital-assets",[12,13,14,10],"operations","implementation","enterprise","xzero-media-editorial","2026-08-23T00:00:00.000Z",2026,8,3,"published",false,"digital-asset-operations",2,1791555299192]