[{"data":1,"prerenderedAt":118},["ShallowReactive",2],{"blog-archive-2026-08":3},[4,25,36,47,57,68,79,89,98,108],{"id":5,"slug":6,"body":7,"html":8,"title":9,"description":10,"category":11,"tags":12,"author":16,"date":17,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":24},"2026\u002F08\u002Foffers\u002Fwhy-we-do-not-sell-compliance-advisory","why-we-do-not-sell-compliance-advisory","\n“Compliance advisory” is a phrase that hides three different jobs:\n\n1. **Legal and licensing** — counsel.\n2. **Policy theatre** — documents nobody runs.\n3. **Production controls and evidence** — what operators actually need on Tuesday.\n\nWe only sell (3), productized.\n\n## What we will write\n\n- Control matrices tied to a workflow\n- Evidence-plane design\n- Dual-control operating models\n- Exam-oriented packs (no pass promise)\n\n## What we will not sell as a product\n\n- Jurisdiction shopping\n- “We’ll get you licensed”\n- Securities or virtual-asset opinions\n- Speaking to the regulator as your representative\n- Generic AML opinions\n\nIf your RFP is mostly (1), hire counsel.\nIf your pain is (3), see [Offers](https:\u002F\u002Ffazezero.com\u002Foffers).\n\n## Why this is commercial, not only ethical\n\nBlurred advisory is how boutiques get two empty years of “strategic conversations.” Fixed production SOWs with deposits are how cash shows up.\n\n[How we work](https:\u002F\u002Ffazezero.com\u002Fhow-we-work)\n\n**Next step:** If a proposal reads like a law firm brochure, it is not us — even if the logo is crypto.\n\n*Fence: Implementation and operating-model services only.*\n","\u003Cp>“Compliance advisory” is a phrase that hides three different jobs:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Legal and licensing\u003C\u002Fstrong> — counsel.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Policy theatre\u003C\u002Fstrong> — documents nobody runs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Production controls and evidence\u003C\u002Fstrong> — what operators actually need on Tuesday.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>We only sell (3), productized.\u003C\u002Fp>\n\u003Ch2>What we will write\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Control matrices tied to a workflow\u003C\u002Fli>\n\u003Cli>Evidence-plane design\u003C\u002Fli>\n\u003Cli>Dual-control operating models\u003C\u002Fli>\n\u003Cli>Exam-oriented packs (no pass promise)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What we will not sell as a product\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Jurisdiction shopping\u003C\u002Fli>\n\u003Cli>“We’ll get you licensed”\u003C\u002Fli>\n\u003Cli>Securities or virtual-asset opinions\u003C\u002Fli>\n\u003Cli>Speaking to the regulator as your representative\u003C\u002Fli>\n\u003Cli>Generic AML opinions\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If your RFP is mostly (1), hire counsel.\nIf your pain is (3), see \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Foffers\">Offers\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>Why this is commercial, not only ethical\u003C\u002Fh2>\n\u003Cp>Blurred advisory is how boutiques get two empty years of “strategic conversations.” Fixed production SOWs with deposits are how cash shows up.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Fhow-we-work\">How we work\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If a proposal reads like a law firm brochure, it is not us — even if the logo is crypto.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Implementation and operating-model services only.\u003C\u002Fem>\u003C\u002Fp>\n","Why we do not sell “compliance advisory”","We do not sell legal advice or policy theatre. We sell production controls and evidence, productized as fixed offers.","offers",[13,14,15],"compliance","governance","operations","fazezero-editorial","2026-08-31T00:00:00.000Z",2026,8,3,"published",false,"product-offers",10,{"id":26,"slug":27,"body":28,"html":29,"title":30,"description":31,"category":11,"tags":32,"author":16,"date":34,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":35},"2026\u002F08\u002Foffers\u002Fyou-licence-we-productionize","you-licence-we-productionize","\nLaw firms get clients authorised. Then the client discovers that **licence ≠ production**.\n\nThat failure is not a legal drafting problem. It is dual control, evidence, day-1 ops, and a book that still runs on sheets.\n\n## Clean fence (why counsel can refer)\n\n**Counsel** owns the licence, legal work, and regulatory representation — applications and opinions.\n\n**fazeZERO** owns implementation, the operating model, and evidence packs — fixed Production Sprint, Exam War Room, and a pre-licence **ops skeleton** (ops only).\n\nWe do **not** file licences, give VA advisory, or hold keys.\nYou do **not** need us competing as fake counsel.\n\n## The ask\n\nOne warm intro to a CCO\u002FCOO at a licensed or just-licensed operator.\nWe send implementation-ready clients your way when we see pure licence need.\n\nSwap one-pagers. One intro each way in seven days beats a partnership MoU that never moves.\n\n[Offers](https:\u002F\u002Ffazezero.com\u002Foffers) · [How we work](https:\u002F\u002Ffazezero.com\u002Fhow-we-work)\n\n**Next step:** Partners — reply with preferred intro format. Operators — ask your counsel whether day-1 production is staffed.\n\n*Fence: Referral is intro-only. No legal work by fazeZERO.*\n","\u003Cp>Law firms get clients authorised. Then the client discovers that \u003Cstrong>licence ≠ production\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>That failure is not a legal drafting problem. It is dual control, evidence, day-1 ops, and a book that still runs on sheets.\u003C\u002Fp>\n\u003Ch2>Clean fence (why counsel can refer)\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Counsel\u003C\u002Fstrong> owns the licence, legal work, and regulatory representation — applications and opinions.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>fazeZERO\u003C\u002Fstrong> owns implementation, the operating model, and evidence packs — fixed Production Sprint, Exam War Room, and a pre-licence \u003Cstrong>ops skeleton\u003C\u002Fstrong> (ops only).\u003C\u002Fp>\n\u003Cp>We do \u003Cstrong>not\u003C\u002Fstrong> file licences, give VA advisory, or hold keys.\nYou do \u003Cstrong>not\u003C\u002Fstrong> need us competing as fake counsel.\u003C\u002Fp>\n\u003Ch2>The ask\u003C\u002Fh2>\n\u003Cp>One warm intro to a CCO\u002FCOO at a licensed or just-licensed operator.\nWe send implementation-ready clients your way when we see pure licence need.\u003C\u002Fp>\n\u003Cp>Swap one-pagers. One intro each way in seven days beats a partnership MoU that never moves.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Foffers\">Offers\u003C\u002Fa> · \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Fhow-we-work\">How we work\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Partners — reply with preferred intro format. Operators — ask your counsel whether day-1 production is staffed.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Referral is intro-only. No legal work by fazeZERO.\u003C\u002Fem>\u003C\u002Fp>\n","You licence. We productionize.","Counsel gets the licence. We productionize day-one operations: dual control, evidence, and a book that does not still run on sheets.",[33,15,14],"licensing","2026-08-30T00:00:00.000Z",9,{"id":37,"slug":38,"body":39,"html":40,"title":41,"description":42,"category":11,"tags":43,"author":16,"date":46,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":19},"2026\u002F08\u002Foffers\u002Fstack-bought-not-wired","stack-bought-not-wired","\nBull markets sell software. Production needs **wiring**.\n\nFamiliar failure mode:\n\n- Custody platform live.\n- Travel Rule tool live.\n- KYC live.\n- Tickets live.\n- Dual control not enforced.\n- TR hit not bound to evidence.\n- Shared admin still smiling in the corner.\n\n## What SI is\n\nFixed implementation work packages on **client-owned** configuration:\n\n- Policy \u002F dual-control settings you can defend\n- TR path wired to ticket = evidence\n- Shared-admin removal plan\n- Export \u002F rec job design\n- Runbooks for handover\n\n## What SI is not\n\n- Rip-replace the vendor\n- Host keys\n- Compete as another custody product\n- Open-ended “integration partner” without a fixed SOW\n\n## How it enters the funnel\n\nBest after a Production Sprint design, or via a **vendor PS\u002FCS intro** on a stuck account. Cold “we’ll re-architect your stack” is usually the wrong open.\n\nVendors: we are capacity for dual-control and evidence pain — [How we work](https:\u002F\u002Ffazezero.com\u002Fhow-we-work).\n\n**Next step:** Name the stack and the failure. If you only name the logo, you are still in procurement theatre.\n\n*Fence: Configure client systems only. No owner keys.*\n","\u003Cp>Bull markets sell software. Production needs \u003Cstrong>wiring\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>Familiar failure mode:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Custody platform live.\u003C\u002Fli>\n\u003Cli>Travel Rule tool live.\u003C\u002Fli>\n\u003Cli>KYC live.\u003C\u002Fli>\n\u003Cli>Tickets live.\u003C\u002Fli>\n\u003Cli>Dual control not enforced.\u003C\u002Fli>\n\u003Cli>TR hit not bound to evidence.\u003C\u002Fli>\n\u003Cli>Shared admin still smiling in the corner.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What SI is\u003C\u002Fh2>\n\u003Cp>Fixed implementation work packages on \u003Cstrong>client-owned\u003C\u002Fstrong> configuration:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Policy \u002F dual-control settings you can defend\u003C\u002Fli>\n\u003Cli>TR path wired to ticket = evidence\u003C\u002Fli>\n\u003Cli>Shared-admin removal plan\u003C\u002Fli>\n\u003Cli>Export \u002F rec job design\u003C\u002Fli>\n\u003Cli>Runbooks for handover\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What SI is not\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Rip-replace the vendor\u003C\u002Fli>\n\u003Cli>Host keys\u003C\u002Fli>\n\u003Cli>Compete as another custody product\u003C\u002Fli>\n\u003Cli>Open-ended “integration partner” without a fixed SOW\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>How it enters the funnel\u003C\u002Fh2>\n\u003Cp>Best after a Production Sprint design, or via a \u003Cstrong>vendor PS\u002FCS intro\u003C\u002Fstrong> on a stuck account. Cold “we’ll re-architect your stack” is usually the wrong open.\u003C\u002Fp>\n\u003Cp>Vendors: we are capacity for dual-control and evidence pain — \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Fhow-we-work\">How we work\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Name the stack and the failure. If you only name the logo, you are still in procurement theatre.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Configure client systems only. No owner keys.\u003C\u002Fem>\u003C\u002Fp>\n","Stack bought, not wired","Custody, Travel Rule, and KYC can all be live while dual control and evidence remain unwired. Integration work closes that gap.",[44,45,15],"integration","implementation","2026-08-29T00:00:00.000Z",{"id":48,"slug":49,"body":50,"html":51,"title":52,"description":53,"category":11,"tags":54,"author":16,"date":55,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":56},"2026\u002F08\u002Foffers\u002Foperator-lab-after-the-sprint","operator-lab-after-the-sprint","\nHiring is slow. Volume is not.\n\nOperator Lab is **not** a public “crypto course.” It is practice on the operating model — dual control, evidence, exceptions — with a take-home CLIENT folder, not slideware only.\n\n## Rule we enforce\n\n**After the sprint is paid** (or equivalent design exists).\nOtherwise you train people on fog.\n\n## Formats\n\n- Closed firm workshop (1–2 days), or\n- Seats when a cohort makes sense\n\nDeposit holds the date.\n\n## What success looks like\n\nOperators can run the path without the consultant in the chair.\nCCO still owns accountability. We do not take keys or become the shadow ops team through training alone.\n\n[Operator Lab](https:\u002F\u002Ffazezero.com\u002Foffers\u002Foperator-lab)\n\n**Next step:** If the sprint folder exists and the team cannot execute it, Lab is the buy — not another strategy offsite.\n\n*Fence: Training on production ops\u002Fevidence. Not licensing education. Not advice on buying or selling assets.*\n","\u003Cp>Hiring is slow. Volume is not.\u003C\u002Fp>\n\u003Cp>Operator Lab is \u003Cstrong>not\u003C\u002Fstrong> a public “crypto course.” It is practice on the operating model — dual control, evidence, exceptions — with a take-home CLIENT folder, not slideware only.\u003C\u002Fp>\n\u003Ch2>Rule we enforce\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>After the sprint is paid\u003C\u002Fstrong> (or equivalent design exists).\nOtherwise you train people on fog.\u003C\u002Fp>\n\u003Ch2>Formats\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Closed firm workshop (1–2 days), or\u003C\u002Fli>\n\u003Cli>Seats when a cohort makes sense\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Deposit holds the date.\u003C\u002Fp>\n\u003Ch2>What success looks like\u003C\u002Fh2>\n\u003Cp>Operators can run the path without the consultant in the chair.\nCCO still owns accountability. We do not take keys or become the shadow ops team through training alone.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Foffers\u002Foperator-lab\">Operator Lab\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If the sprint folder exists and the team cannot execute it, Lab is the buy — not another strategy offsite.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Training on production ops\u002Fevidence. Not licensing education. Not advice on buying or selling assets.\u003C\u002Fem>\u003C\u002Fp>\n","Operator Lab after the sprint","Operator Lab is practice on the operating model after the sprint is paid, so the team can run the path without a consultant.",[15,45,14],"2026-08-28T00:00:00.000Z",7,{"id":58,"slug":59,"body":60,"html":61,"title":62,"description":63,"category":11,"tags":64,"author":16,"date":66,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":67},"2026\u002F08\u002Foffers\u002Fwhat-you-get-in-three-weeks","what-you-get-in-three-weeks","\nIf the output is only slides, you bought theatre.\n\nThe Production Sprint is built around a **folder** a decision-maker can act on.\n\n## In the pack (typical)\n\n1. Kick-off pack and RACI for one workflow\n2. As-is map — people, systems, tickets, evidence gaps\n3. To-be operating model — dual control, gates, exceptions\n4. Requirements and use cases (when the thick pack applies)\n5. Architecture views — context, sequences, components, data\u002Fcontrol flow\n6. Control matrix mapped to that workflow\n7. Evidence-plane design on your systems\n8. 90-day production path, SOP outlines, go-live checklist\n9. Executive one-pager for CCO or board\n\nExact composition is in the [Production Sprint brief](https:\u002F\u002Ffazezero.com\u002Foffers\u002Fproduction-sprint). Samples of shape (not a paid client case) live under [Work](https:\u002F\u002Ffazezero.com\u002Fwork).\n\n## What “done” means\n\n- Named workflow has a clear to-be.\n- CCO can point to control + evidence model.\n- 90-day path is accepted or explicitly deferred with owners.\n\nNot: “we aligned stakeholders.” Not: “platform roadmap.”\n\n## After the sprint\n\nOptional: Production Build, Integration SI, Operator Lab, fractional Production Owner.\nNone of those are forced. None replace the deposit-backed sprint.\n\n**Next step:** Open the [sample pack](https:\u002F\u002Ffazezero.com\u002Fwork\u002Fsample-production-pack). If the shape is wrong for you, do not force a fit call.\n\n*Fence: Implementation folder. Not a software licence. Not custody.*\n","\u003Cp>If the output is only slides, you bought theatre.\u003C\u002Fp>\n\u003Cp>The Production Sprint is built around a \u003Cstrong>folder\u003C\u002Fstrong> a decision-maker can act on.\u003C\u002Fp>\n\u003Ch2>In the pack (typical)\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Kick-off pack and RACI for one workflow\u003C\u002Fli>\n\u003Cli>As-is map — people, systems, tickets, evidence gaps\u003C\u002Fli>\n\u003Cli>To-be operating model — dual control, gates, exceptions\u003C\u002Fli>\n\u003Cli>Requirements and use cases (when the thick pack applies)\u003C\u002Fli>\n\u003Cli>Architecture views — context, sequences, components, data\u002Fcontrol flow\u003C\u002Fli>\n\u003Cli>Control matrix mapped to that workflow\u003C\u002Fli>\n\u003Cli>Evidence-plane design on your systems\u003C\u002Fli>\n\u003Cli>90-day production path, SOP outlines, go-live checklist\u003C\u002Fli>\n\u003Cli>Executive one-pager for CCO or board\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Exact composition is in the \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Foffers\u002Fproduction-sprint\">Production Sprint brief\u003C\u002Fa>. Samples of shape (not a paid client case) live under \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Fwork\">Work\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>What “done” means\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Named workflow has a clear to-be.\u003C\u002Fli>\n\u003Cli>CCO can point to control + evidence model.\u003C\u002Fli>\n\u003Cli>90-day path is accepted or explicitly deferred with owners.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Not: “we aligned stakeholders.” Not: “platform roadmap.”\u003C\u002Fp>\n\u003Ch2>After the sprint\u003C\u002Fh2>\n\u003Cp>Optional: Production Build, Integration SI, Operator Lab, fractional Production Owner.\nNone of those are forced. None replace the deposit-backed sprint.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Open the \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Fwork\u002Fsample-production-pack\">sample pack\u003C\u002Fa>. If the shape is wrong for you, do not force a fit call.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Implementation folder. Not a software licence. Not custody.\u003C\u002Fem>\u003C\u002Fp>\n","What you get in three weeks","The Production Sprint leaves a folder a decision-maker can act on: as-is, to-be, controls, evidence, and a ninety-day path.",[45,15,65],"enterprise","2026-08-27T00:00:00.000Z",6,{"id":69,"slug":70,"body":71,"html":72,"title":73,"description":74,"category":11,"tags":75,"author":16,"date":77,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":78},"2026\u002F08\u002Foffers\u002Fwhen-the-calendar-is-the-enemy","when-the-calendar-is-the-enemy","\nSome problems are design problems. Some are **calendar** problems.\n\nIf mock or exam is inside roughly 60 days, a three-week architecture romance may be the wrong buy. You need a pack path, gap burn-down, and a dry-run — fast — without pretending a consultant can guarantee a pass.\n\n## What the War Room is\n\n**1–2 weeks. Fixed fee.**\nExaminer-oriented structure for **one** workflow:\n\n- Where evidence lives today\n- Pack layout by question themes you actually face\n- Critical gaps with owners and dates\n- Exception register design\n- Dry-run checklist\n\n## What it is not\n\n- A shorter, discounted Production Sprint\n- A pass promise\n- Counsel or regulator representation\n- A rewrite of your entire policy suite\n\n## When to buy the Sprint instead\n\nIf you have time and the book is wrong at the root (no dual control model, no to-be, no 90-day path), buy **SKU-01**. Use the War Room when the date is the constraint.\n\n## Commercial reality\n\nDeposit to start. Same week if you can staff access. If you cannot name an owner, do not buy.\n\n[Exam War Room](https:\u002F\u002Ffazezero.com\u002Foffers\u002Fexam-war-room)\n\n**Next step:** Put the exam\u002Fmock date in the first message. We will tell you War Room vs Sprint vs not-a-fit.\n\n*Fence: No guarantee of exam outcome. No regulator liaison.*\n","\u003Cp>Some problems are design problems. Some are \u003Cstrong>calendar\u003C\u002Fstrong> problems.\u003C\u002Fp>\n\u003Cp>If mock or exam is inside roughly 60 days, a three-week architecture romance may be the wrong buy. You need a pack path, gap burn-down, and a dry-run — fast — without pretending a consultant can guarantee a pass.\u003C\u002Fp>\n\u003Ch2>What the War Room is\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>1–2 weeks. Fixed fee.\u003C\u002Fstrong>\nExaminer-oriented structure for \u003Cstrong>one\u003C\u002Fstrong> workflow:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Where evidence lives today\u003C\u002Fli>\n\u003Cli>Pack layout by question themes you actually face\u003C\u002Fli>\n\u003Cli>Critical gaps with owners and dates\u003C\u002Fli>\n\u003Cli>Exception register design\u003C\u002Fli>\n\u003Cli>Dry-run checklist\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What it is not\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A shorter, discounted Production Sprint\u003C\u002Fli>\n\u003Cli>A pass promise\u003C\u002Fli>\n\u003Cli>Counsel or regulator representation\u003C\u002Fli>\n\u003Cli>A rewrite of your entire policy suite\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>When to buy the Sprint instead\u003C\u002Fh2>\n\u003Cp>If you have time and the book is wrong at the root (no dual control model, no to-be, no 90-day path), buy \u003Cstrong>SKU-01\u003C\u002Fstrong>. Use the War Room when the date is the constraint.\u003C\u002Fp>\n\u003Ch2>Commercial reality\u003C\u002Fh2>\n\u003Cp>Deposit to start. Same week if you can staff access. If you cannot name an owner, do not buy.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Foffers\u002Fexam-war-room\">Exam War Room\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Put the exam\u002Fmock date in the first message. We will tell you War Room vs Sprint vs not-a-fit.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: No guarantee of exam outcome. No regulator liaison.\u003C\u002Fem>\u003C\u002Fp>\n","When the calendar is the enemy","When a mock or exam is inside sixty days, the buy is a pack path and dry-run, not a three-week architecture programme.",[13,76,15],"regulation","2026-08-26T00:00:00.000Z",5,{"id":80,"slug":81,"body":82,"html":83,"title":84,"description":85,"category":11,"tags":86,"author":16,"date":87,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":88},"2026\u002F08\u002Foffers\u002Fticket-equals-evidence","ticket-equals-evidence","\nExaminers do not want your mythology. They want a path from **decision → actor → artefact**.\n\nIf proof lives in:\n\n- personal email,\n- chat exports,\n- desktop folders,\n- or “we can rebuild it if asked,”\n\nyou do not have an evidence plane. You have archaeology.\n\n## The production rule\n\n**The ticket (or equivalent work object) is the primary key for evidence.**\n\nScreenshots may attach. They do not replace the key.\n\nExports and reports should be reproducible from the same model — not handmade the night before a mock.\n\n## What “evidence plane” means in a sprint\n\n- Where proof lives today (honest as-is).\n- Where it will live (to-be) on **your** systems.\n- Retention and export shape.\n- Linkage to dual control and exceptions.\n- A pack structure a CCO can defend.\n\n## Exam pressure\n\nIf a mock or exam is inside 60 days, do not start with a platform RFP. Start with an **Evidence War Room**: pack structure, gaps, dry-run checklist — still no pass promise, still no regulator liaison.\n\n[Exam War Room](https:\u002F\u002Ffazezero.com\u002Foffers\u002Fexam-war-room) · [Sample pack](https:\u002F\u002Ffazezero.com\u002Fwork)\n\n**Next step:** Ask internally: “Show me last week’s first transfer with dual control and evidence in one path.” If the room goes quiet, you know what to buy.\n\n*Fence: Evidence design on client systems. We do not speak to the regulator for you.*\n","\u003Cp>Examiners do not want your mythology. They want a path from \u003Cstrong>decision → actor → artefact\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>If proof lives in:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>personal email,\u003C\u002Fli>\n\u003Cli>chat exports,\u003C\u002Fli>\n\u003Cli>desktop folders,\u003C\u002Fli>\n\u003Cli>or “we can rebuild it if asked,”\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>you do not have an evidence plane. You have archaeology.\u003C\u002Fp>\n\u003Ch2>The production rule\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>The ticket (or equivalent work object) is the primary key for evidence.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Screenshots may attach. They do not replace the key.\u003C\u002Fp>\n\u003Cp>Exports and reports should be reproducible from the same model — not handmade the night before a mock.\u003C\u002Fp>\n\u003Ch2>What “evidence plane” means in a sprint\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Where proof lives today (honest as-is).\u003C\u002Fli>\n\u003Cli>Where it will live (to-be) on \u003Cstrong>your\u003C\u002Fstrong> systems.\u003C\u002Fli>\n\u003Cli>Retention and export shape.\u003C\u002Fli>\n\u003Cli>Linkage to dual control and exceptions.\u003C\u002Fli>\n\u003Cli>A pack structure a CCO can defend.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Exam pressure\u003C\u002Fh2>\n\u003Cp>If a mock or exam is inside 60 days, do not start with a platform RFP. Start with an \u003Cstrong>Evidence War Room\u003C\u002Fstrong>: pack structure, gaps, dry-run checklist — still no pass promise, still no regulator liaison.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Foffers\u002Fexam-war-room\">Exam War Room\u003C\u002Fa> · \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Fwork\">Sample pack\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Ask internally: “Show me last week’s first transfer with dual control and evidence in one path.” If the room goes quiet, you know what to buy.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Evidence design on client systems. We do not speak to the regulator for you.\u003C\u002Fem>\u003C\u002Fp>\n","Ticket = evidence","Examiners want a path from decision to actor to artefact. The ticket is the primary key for evidence, not a folder of screenshots.",[13,14,15],"2026-08-25T00:00:00.000Z",4,{"id":90,"slug":91,"body":92,"html":93,"title":94,"description":95,"category":11,"tags":96,"author":16,"date":97,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":20},"2026\u002F08\u002Foffers\u002Fdual-control-that-survives-tuesday","dual-control-that-survives-tuesday","\nMost “dual control” is a slide.\n\nIt dies when:\n\n- Shared admin is still on.\n- The maker and checker are the same person after hours.\n- The tool allows a bypass that nobody logs.\n- The ticket closed without the evidence primary key.\n\nTuesday is the test. Volume is up. Someone is on leave. The corridor is hot. Policy PDFs do not move.\n\n## Production dual control has four parts\n\n1. **Policy that the system can enforce** (or a manual gate that is actually staffed).\n2. **Segregation that survives staffing gaps** — named roles, not heroics.\n3. **Exception path** with a register, not a private chat.\n4. **Evidence** that the dual control event happened — linked to the ticket.\n\nIf any one of those is missing, you have theatre.\n\n## What a sprint does\n\nWe do not sell a new custody product. We design dual control **on the stack you already run** (or have contracted), map the as-is failures, and leave a to-be model plus control matrix for **one** workflow.\n\nWiring configuration often follows as Integration SI — after the design is accepted, or via a vendor who is stuck on implementation.\n\n## Red flags in a fit call\n\n- “We have dual control” but cannot show last week’s maker\u002Fchecker record.\n- Owner keys discussed as something we would hold. (We will not.)\n- Request to “make the tool compliant” without naming the workflow.\n\n[Offers](https:\u002F\u002Ffazezero.com\u002Foffers) · [How we work](https:\u002F\u002Ffazezero.com\u002Fhow-we-work)\n\n**Next step:** If dual control fails on a real book this month, say so on the fit call. That is a production problem, not a branding problem.\n\n*Fence: We configure guidance on client-owned systems. No owner\u002Froot admin. No keys.*\n","\u003Cp>Most “dual control” is a slide.\u003C\u002Fp>\n\u003Cp>It dies when:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Shared admin is still on.\u003C\u002Fli>\n\u003Cli>The maker and checker are the same person after hours.\u003C\u002Fli>\n\u003Cli>The tool allows a bypass that nobody logs.\u003C\u002Fli>\n\u003Cli>The ticket closed without the evidence primary key.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Tuesday is the test. Volume is up. Someone is on leave. The corridor is hot. Policy PDFs do not move.\u003C\u002Fp>\n\u003Ch2>Production dual control has four parts\u003C\u002Fh2>\n\u003Col>\n\u003Cli>\u003Cstrong>Policy that the system can enforce\u003C\u002Fstrong> (or a manual gate that is actually staffed).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Segregation that survives staffing gaps\u003C\u002Fstrong> — named roles, not heroics.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Exception path\u003C\u002Fstrong> with a register, not a private chat.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Evidence\u003C\u002Fstrong> that the dual control event happened — linked to the ticket.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If any one of those is missing, you have theatre.\u003C\u002Fp>\n\u003Ch2>What a sprint does\u003C\u002Fh2>\n\u003Cp>We do not sell a new custody product. We design dual control \u003Cstrong>on the stack you already run\u003C\u002Fstrong> (or have contracted), map the as-is failures, and leave a to-be model plus control matrix for \u003Cstrong>one\u003C\u002Fstrong> workflow.\u003C\u002Fp>\n\u003Cp>Wiring configuration often follows as Integration SI — after the design is accepted, or via a vendor who is stuck on implementation.\u003C\u002Fp>\n\u003Ch2>Red flags in a fit call\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>“We have dual control” but cannot show last week’s maker\u002Fchecker record.\u003C\u002Fli>\n\u003Cli>Owner keys discussed as something we would hold. (We will not.)\u003C\u002Fli>\n\u003Cli>Request to “make the tool compliant” without naming the workflow.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Foffers\">Offers\u003C\u002Fa> · \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Fhow-we-work\">How we work\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If dual control fails on a real book this month, say so on the fit call. That is a production problem, not a branding problem.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: We configure guidance on client-owned systems. No owner\u002Froot admin. No keys.\u003C\u002Fem>\u003C\u002Fp>\n","Dual control that survives Tuesday","Dual control that only exists in a policy PDF fails on a busy Tuesday. Production dual control is enforced, staffed, and evidenced.",[14,15,13],"2026-08-24T00:00:00.000Z",{"id":99,"slug":100,"body":101,"html":102,"title":103,"description":104,"category":11,"tags":105,"author":16,"date":106,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":107},"2026\u002F08\u002Foffers\u002Fone-workflow-not-a-transformation","one-workflow-not-a-transformation","\nTransformation 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 remains unfinished while workshops multiply.\n\nOur public offers are narrow on purpose.\n\n## The rule\n\n**One named workflow per SOW.**\nDefault: onboarding → first transfer (or the first settlement event that creates real risk).\n\nA second workflow is a **change**, not a favour.\n\n## Why buyers accept this\n\n- Scope fits a three-week fixed fee.\n- The readout has a decision: run the 90-day path, or don’t.\n- Evidence and controls are testable on one path before you industrialise everything.\n\n## Why sellers hate this (and still do it)\n\nBecause “transformation” sells decks. Production sells folders. Folders are harder to fake.\n\nIf a vendor cannot describe deliverables for **one** workflow without inventing a programme office, they are not selling production.\n\n## How this shows up in the sprint\n\nWeek 1 defines production for *this* book.\nWeek 2 designs dual control and evidence on *your* systems.\nWeek 3 leaves a 90-day path with owners — not another discovery.\n\n[Production Sprint brief](https:\u002F\u002Ffazezero.com\u002Foffers\u002Fproduction-sprint)\n\n**Next step:** Bring the workflow name to the fit call. If you cannot name it, do not buy.\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 remains unfinished while workshops multiply.\u003C\u002Fp>\n\u003Cp>Our public offers are narrow on purpose.\u003C\u002Fp>\n\u003Ch2>The rule\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>One named workflow per SOW.\u003C\u002Fstrong>\nDefault: onboarding → first transfer (or the first settlement event that creates real risk).\u003C\u002Fp>\n\u003Cp>A second workflow is a \u003Cstrong>change\u003C\u002Fstrong>, not a favour.\u003C\u002Fp>\n\u003Ch2>Why buyers accept this\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Scope fits a three-week fixed fee.\u003C\u002Fli>\n\u003Cli>The readout has a decision: run the 90-day path, or don’t.\u003C\u002Fli>\n\u003Cli>Evidence and controls are testable on one path before you industrialise everything.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Why sellers hate this (and still do it)\u003C\u002Fh2>\n\u003Cp>Because “transformation” sells decks. Production sells folders. Folders are harder to fake.\u003C\u002Fp>\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\u003Ch2>How this shows up in the sprint\u003C\u002Fh2>\n\u003Cp>Week 1 defines production for \u003Cem>this\u003C\u002Fem> book.\nWeek 2 designs dual control and evidence on \u003Cem>your\u003C\u002Fem> systems.\nWeek 3 leaves a 90-day path with owners — not another discovery.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Foffers\u002Fproduction-sprint\">Production Sprint brief\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Bring the workflow name to the fit call. If you cannot name it, do not buy.\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.",[15,45,65],"2026-08-23T00:00:00.000Z",2,{"id":109,"slug":110,"body":111,"html":112,"title":113,"description":114,"category":11,"tags":115,"author":16,"date":116,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":117},"2026\u002F08\u002Foffers\u002Flicence-is-not-production","licence-is-not-production","\nThe certificate on the wall is not an operating model.\n\nA VARA (or equivalent) licence answers a different question than production does. The licence says you are allowed to run certain activities. Production asks whether **onboarding → first transfer** (or the one workflow that actually makes money) runs with dual control, a real evidence plane, and owners who can show the path without archaeology in email.\n\nWe see the same pattern repeatedly:\n\n- Licence is live.\n- Stack is partly bought (custody, TR, KYC, tickets).\n- The book still lives in sheets, chat, and “the person who knows.”\n- Dual control exists in a policy PDF and dies on Tuesday afternoon.\n\nThat gap is not a strategy problem. It is a **production** problem.\n\n## What “production” means here\n\nFor one named workflow:\n\n1. **As-is** is written: people, systems, tickets, where proof actually lives.\n2. **To-be** is operable: dual control, gates, exceptions — not a vision deck.\n3. **Evidence** is addressable: ticket (or equivalent) equals proof, not a folder of screenshots after the fact.\n4. **90-day path** has owners inside the firm — not a consultant forever.\n\nIf you cannot name the workflow, you are not ready to buy a sprint. You are still in narrative mode.\n\n## What we sell\n\nA **three-week Production Sprint**: fixed fee, one workflow, folder a decision-maker can act on. Not a platform demo. Not a multi-year transformation. Not “we’ll get you licensed.”\n\nSee: [Production Sprint](https:\u002F\u002Ffazezero.com\u002Foffers\u002Fproduction-sprint) · [Sample pack](https:\u002F\u002Ffazezero.com\u002Fwork\u002Fsample-production-pack)\n\n## What we do not sell\n\n- Keys or custody\n- Licence filing\n- VA advisory\n- A promise that an exam will pass\n\nImplementation services under a mainland DLT \u002F cloud licence. **Not a VASP.**\n\n**Next step:** If the licensed entity and one workflow are nameable, [book a fit call](https:\u002F\u002Ffazezero.com\u002Fcontact). Twenty minutes. Yes, later, or no.\n\n*Fence: No custody, no keys, no licence filing, no VA advisory.*\n","\u003Cp>The certificate on the wall is not an operating model.\u003C\u002Fp>\n\u003Cp>A VARA (or equivalent) licence answers a different question than production does. The licence says you are allowed to run certain activities. Production asks whether \u003Cstrong>onboarding → first transfer\u003C\u002Fstrong> (or the one workflow that actually makes money) runs with dual control, a real evidence plane, and owners who can show the path without archaeology in email.\u003C\u002Fp>\n\u003Cp>We see the same pattern repeatedly:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Licence is live.\u003C\u002Fli>\n\u003Cli>Stack is partly bought (custody, TR, KYC, tickets).\u003C\u002Fli>\n\u003Cli>The book still lives in sheets, chat, and “the person who knows.”\u003C\u002Fli>\n\u003Cli>Dual control exists in a policy PDF and dies on Tuesday afternoon.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>That gap is not a strategy problem. It is a \u003Cstrong>production\u003C\u002Fstrong> problem.\u003C\u002Fp>\n\u003Ch2>What “production” means here\u003C\u002Fh2>\n\u003Cp>For one named workflow:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>As-is\u003C\u002Fstrong> is written: people, systems, tickets, where proof actually lives.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>To-be\u003C\u002Fstrong> is operable: dual control, gates, exceptions — not a vision deck.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Evidence\u003C\u002Fstrong> is addressable: ticket (or equivalent) equals proof, not a folder of screenshots after the fact.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>90-day path\u003C\u002Fstrong> has owners inside the firm — not a consultant forever.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If you cannot name the workflow, you are not ready to buy a sprint. You are still in narrative mode.\u003C\u002Fp>\n\u003Ch2>What we sell\u003C\u002Fh2>\n\u003Cp>A \u003Cstrong>three-week Production Sprint\u003C\u002Fstrong>: fixed fee, one workflow, folder a decision-maker can act on. Not a platform demo. Not a multi-year transformation. Not “we’ll get you licensed.”\u003C\u002Fp>\n\u003Cp>See: \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Foffers\u002Fproduction-sprint\">Production Sprint\u003C\u002Fa> · \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Fwork\u002Fsample-production-pack\">Sample pack\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch2>What we do not sell\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Keys or custody\u003C\u002Fli>\n\u003Cli>Licence filing\u003C\u002Fli>\n\u003Cli>VA advisory\u003C\u002Fli>\n\u003Cli>A promise that an exam will pass\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Implementation services under a mainland DLT \u002F cloud licence. \u003Cstrong>Not a VASP.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If the licensed entity and one workflow are nameable, \u003Ca href=\"https:\u002F\u002Ffazezero.com\u002Fcontact\">book a fit call\u003C\u002Fa>. Twenty minutes. Yes, later, or no.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: No custody, no keys, no licence filing, no VA advisory.\u003C\u002Fem>\u003C\u002Fp>\n","Licence is not production","A licence says you may operate. Production asks whether one named workflow actually runs with dual control and evidence.",[33,15,14],"2026-08-22T00:00:00.000Z",1,1789210411452]