[{"data":1,"prerenderedAt":883},["ShallowReactive",2],{"insight-insights_en-why-95-percent-of-ai-pilots-never-reach-production":3,"insight-related-insights_en-why-95-percent-of-ai-pilots-never-reach-production":240},{"id":4,"title":5,"author":6,"blobHue":10,"body":11,"category":214,"date":215,"description":216,"draft":217,"extension":218,"featured":219,"headline":220,"hue":221,"letter":222,"meta":223,"navigation":219,"path":224,"readMinutes":225,"related":226,"seo":230,"stem":231,"summary":232,"toc":233,"__hash__":239},"insights_en\u002Finsights\u002Fwhy-95-percent-of-ai-pilots-never-reach-production.md","Why 95% of AI pilots never reach production",{"name":7,"role":8,"bio":9},"André","Founder & CTO","André is the founder and CTO of WizardingCode. Eight years building the software companies run on, now putting agents into production.","blue",{"type":12,"value":13,"toc":205},"minimark",[14,23,26,31,36,42,46,49,72,76,79,166,170,192,196,199],[15,16,17,18,22],"p",{},"In 2025, MIT’s NANDA initiative looked at how companies were using generative AI and found that about 95% of enterprise pilots delivered no measurable impact on the P&L.",[19,20,21],"sup",{},"1"," Billions spent, demos applauded, and almost nothing changed in how the business actually ran.",[15,24,25],{},"We’ve seen the same pattern from the inside. Most of the companies that call us have already run a pilot. It worked in the demo. It never went live.",[27,28,30],"h2",{"id":29},"the-number-everyone-quotes","The number everyone quotes",[15,32,33,34],{},"The headline is easy to misread. It doesn’t say AI doesn’t work. It says pilots don’t turn into production. The same report found that projects built with specialised external partners reached deployment about twice as often as internal builds, and that the biggest returns came from unglamorous back-office work, not from customer-facing chatbots.",[19,35,21],{},[37,38,39],"blockquote",{},[15,40,41],{},"The model is rarely the problem. The plumbing is.",[27,43,45],{"id":44},"its-not-the-model","It’s not the model",[15,47,48],{},"When we look at why a pilot stalled, the answer is almost never “the AI wasn’t smart enough”. It is one of three things:",[50,51,52,60,66],"ol",{},[53,54,55,59],"li",{},[56,57,58],"strong",{},"No live data."," The pilot ran on an export. Connecting it to the real ERP, inbox or helpdesk was “phase two”, and phase two never came.",[53,61,62,65],{},[56,63,64],{},"No owner."," The innovation team built it. The team whose work it would take never asked for it, and never adopted it.",[53,67,68,71],{},[56,69,70],{},"No number."," Success was “a good demo”. Nobody agreed what had to move, so nobody could say it had worked.",[27,73,75],{"id":74},"four-things-the-5-do","Four things the 5% do",[15,77,78],{},"The projects that ship look different from day one. They connect to live systems in week one, not month six. The metric is agreed before a line of code is written, and it belongs to the team whose work changes. People approve the decisions that carry risk, so nobody has to trust the agent blindly. And there is a date: production in weeks, not a roadmap.",[80,81,82,97],"table",{},[83,84,85],"thead",{},[86,87,88,91,94],"tr",{},[89,90],"th",{},[89,92,93],{},"A PILOT",[89,95,96],{},"A SYSTEM IN PRODUCTION",[98,99,100,114,127,140,153],"tbody",{},[86,101,102,108,111],{},[103,104,105],"td",{},[56,106,107],{},"Data",[103,109,110],{},"A sample export",[103,112,113],{},"Your live systems",[86,115,116,121,124],{},[103,117,118],{},[56,119,120],{},"Success",[103,122,123],{},"A good demo",[103,125,126],{},"A number agreed on day one",[86,128,129,134,137],{},[103,130,131],{},[56,132,133],{},"Owner",[103,135,136],{},"The innovation team",[103,138,139],{},"The team whose work it takes",[86,141,142,147,150],{},[103,143,144],{},[56,145,146],{},"Humans",[103,148,149],{},"Watching",[103,151,152],{},"Approving what matters",[86,154,155,160,163],{},[103,156,157],{},[56,158,159],{},"Timeline",[103,161,162],{},"Open-ended",[103,164,165],{},"Weeks",[27,167,169],{"id":168},"a-checklist-before-you-start","A checklist before you start",[171,172,174],"prose-checklist",{"title":173},"Before you approve the next AI project, ask",[175,176,177,180,183,186,189],"ul",{},[53,178,179],{},"Which live system does it read and write, in week one?",[53,181,182],{},"Which number moves, and who owns it?",[53,184,185],{},"Which decisions stay with a person?",[53,187,188],{},"What happens on day 30?",[53,190,191],{},"Who owns the code, the prompts and the data?",[27,193,195],{"id":194},"what-this-means-for-you","What this means for you",[15,197,198],{},"If your last pilot is gathering dust, it probably wasn’t a bad idea. It was missing the boring parts. Start from one process that hurts, connect it to the real systems, agree the number and put a date on it. That’s the whole method. It isn’t magic; it’s engineering.",[200,201,202],"prose-footnotes",{},[15,203,204],{},"¹ MIT NANDA, “The GenAI Divide: State of AI in Business 2025”.",{"title":206,"searchDepth":207,"depth":207,"links":208},"",2,[209,210,211,212,213],{"id":29,"depth":207,"text":30},{"id":44,"depth":207,"text":45},{"id":74,"depth":207,"text":75},{"id":168,"depth":207,"text":169},{"id":194,"depth":207,"text":195},"strategy","2026-09-22","In 2025, MIT’s NANDA initiative looked at how companies were using generative AI and found that about 95% of enterprise pilots delivered no measurable impact on the P&L.1 Billions spent, demos applauded, and almost nothing changed in how the business actually ran.",false,"md",true,"Why 95% of AI pilots never reach ==production.==","magenta","95",{},"\u002Finsights\u002Fwhy-95-percent-of-ai-pilots-never-reach-production",7,[227,228,229],"what-an-agentic-os-is-and-what-it-isnt","every-agent-needs-a-judge","the-30-day-playbook-week-by-week",{"title":5,"description":216},"insights\u002Fwhy-95-percent-of-ai-pilots-never-reach-production","It’s rarely the model. It’s the data, the owner and the missing number. Here’s what the ones that ship do differently.",[234,235,236,237,238],{"id":29,"label":30},{"id":44,"label":45},{"id":74,"label":75},{"id":168,"label":169},{"id":194,"label":195},"9wJDwNO8uXgEwGK-cE1WYthNEN-J5Ic1e7kI_crM30g",[241,484,673],{"id":242,"title":243,"author":244,"blobHue":245,"body":246,"category":214,"date":464,"description":250,"draft":217,"extension":218,"featured":217,"headline":465,"hue":466,"letter":467,"meta":468,"navigation":219,"path":469,"readMinutes":470,"related":471,"seo":474,"stem":475,"summary":476,"toc":477,"__hash__":483},"insights_en\u002Finsights\u002Fwhat-an-agentic-os-is-and-what-it-isnt.md","What an Agentic OS is, and what it isn’t",{"name":7,"role":8,"bio":9},null,{"type":12,"value":247,"toc":457},[248,251,254,258,261,264,268,274,306,312,318,324,390,395,399,405,411,417,421,424,427,431,454],[15,249,250],{},"Most people meet AI agents as a chat window. You ask, it answers, and then nothing happens. That is useful, but it isn’t how a business runs. A business runs on work that moves between systems, people and decisions, every day, whether anyone is watching or not.",[15,252,253],{},"An Agentic OS is what it takes to hand some of that work to agents and still sleep at night.",[27,255,257],{"id":256},"a-plain-definition","A plain definition",[15,259,260],{},"An Agentic OS is a team of AI agents trained on how your business works, running inside the tools you already use, following rules your people set. Each agent owns one job. They share what they know. They stop and ask when a decision is above their limits. And everything they do is visible on one screen.",[15,262,263],{},"The word “OS” is deliberate. An operating system is not an app you open. It is what sits underneath and keeps everything else running. The agents are the visible part; the layers around them are what make it safe.",[27,265,267],{"id":266},"the-four-layers","The four layers",[15,269,270,273],{},[56,271,272],{},"Agents"," do the work. We use five kinds, and most companies go live with two or three:",[50,275,276,282,288,294,300],{},[53,277,278,281],{},[56,279,280],{},"Responder"," answers customers, suppliers and colleagues, in your tone, from your data.",[53,283,284,287],{},[56,285,286],{},"Classifier"," reads what comes in, from emails to tickets to documents, and sends it to the right place.",[53,289,290,293],{},[56,291,292],{},"Scraper"," watches the sources you care about and brings back what changed.",[53,295,296,299],{},[56,297,298],{},"Orchestrator"," runs work that spans several systems: the refund, the CRM update, the courier booking.",[53,301,302,305],{},[56,303,304],{},"Analyst"," reads the numbers and has the report ready before the meeting.",[15,307,308,311],{},[56,309,310],{},"Shared memory"," is what the agents know about your business: policies, price lists, customer history, past decisions. Every agent reads from the same source, and it stays current as you work. No more “ask Maria, she knows”.",[15,313,314,317],{},[56,315,316],{},"Approval rules"," decide what an agent may do alone. They are written in plain language and set by your team. Above the limit, the agent pauses and a person decides, in the tools they already use.",[15,319,320,323],{},[56,321,322],{},"The command center"," shows every run, cost and result on one screen. You can replay any decision step by step, pause any agent, and follow the number you agreed on, every day.",[80,325,326,339],{},[83,327,328],{},[86,329,330,333,336],{},[89,331,332],{},"LAYER",[89,334,335],{},"WHAT IT ANSWERS",[89,337,338],{},"WITHOUT IT",[98,340,341,353,365,377],{},[86,342,343,347,350],{},[103,344,345],{},[56,346,272],{},[103,348,349],{},"Who does the work?",[103,351,352],{},"Nothing gets done",[86,354,355,359,362],{},[103,356,357],{},[56,358,310],{},[103,360,361],{},"What do they know?",[103,363,364],{},"Every agent guesses",[86,366,367,371,374],{},[103,368,369],{},[56,370,316],{},[103,372,373],{},"What can they do alone?",[103,375,376],{},"Nobody dares switch them on",[86,378,379,384,387],{},[103,380,381],{},[56,382,383],{},"Command center",[103,385,386],{},"What did they do, and did it work?",[103,388,389],{},"Nobody can prove it",[37,391,392],{},[15,393,394],{},"Agents alone are a demo. What makes them safe is everything around them.",[27,396,398],{"id":397},"what-it-isnt","What it isn’t",[15,400,401,404],{},[56,402,403],{},"It isn’t a chatbot."," A chatbot waits for a question. An Agentic OS works through a queue. It reads the inbox overnight, reconciles the stock file, drafts the replies, and leaves the three decisions that need a person at the top of the list in the morning.",[15,406,407,410],{},[56,408,409],{},"It isn’t a platform licence."," You don’t rent seats in someone else’s product and bend your process to fit it. The agents are built around your process, inside your systems, and you own the code, the prompts and the data.",[15,412,413,416],{},[56,414,415],{},"It isn’t a pilot."," A pilot runs on an export, for a demo, with nobody accountable for the result. An Agentic OS runs on live systems from the first week, against a number that the team whose work it takes has signed off. If it isn’t in production, it isn’t an OS yet.",[27,418,420],{"id":419},"where-to-start","Where to start",[15,422,423],{},"Nobody builds all four layers for the whole company at once. You start with one process that hurts, usually one with volume, clear rules and a number: the support inbox, the supplier files, the weekly report. You build the first squad of agents with its memory, its rules and its screen. Then you add a squad at a time.",[15,425,426],{},"The layers are what make the second squad cheaper than the first. The memory is already there. The rules have a format the team knows. The command center already shows the first squad’s numbers, so the next one is judged on the same screen, against the same kind of target.",[27,428,430],{"id":429},"how-to-tell-if-you-have-one","How to tell if you have one",[171,432,434],{"title":433},"You have an Agentic OS if the answer is yes to all of these",[175,435,436,439,442,445,448,451],{},[53,437,438],{},"Do the agents work inside the systems your team already uses?",[53,440,441],{},"Can you say, in one sentence, which decisions they may not take alone?",[53,443,444],{},"Do they all read from the same, current source of policies and history?",[53,446,447],{},"Can you open one screen and see what they did today, what it cost and what is waiting for you?",[53,449,450],{},"Has a number moved, and does the team that owns it agree?",[53,452,453],{},"Do you own the code, the prompts and the data?",[15,455,456],{},"If any answer is no, you have agents. That is a good start. The rest is the part that lets you rely on them.",{"title":206,"searchDepth":207,"depth":207,"links":458},[459,460,461,462,463],{"id":256,"depth":207,"text":257},{"id":266,"depth":207,"text":267},{"id":397,"depth":207,"text":398},{"id":419,"depth":207,"text":420},{"id":429,"depth":207,"text":430},"2026-09-15","What an Agentic OS is, and what it ==isn’t.==","violet","OS",{},"\u002Finsights\u002Fwhat-an-agentic-os-is-and-what-it-isnt",4,[472,228,473],"why-95-percent-of-ai-pilots-never-reach-production","what-agents-should-never-do-alone",{"title":243,"description":250},"insights\u002Fwhat-an-agentic-os-is-and-what-it-isnt","Not a chatbot, not a platform licence. A plain-language definition, with the four layers that make agents safe to run a business.",[478,479,480,481,482],{"id":256,"label":257},{"id":266,"label":267},{"id":397,"label":398},{"id":419,"label":420},{"id":429,"label":430},"O4B58r8Hq-cONZEYpn0ps8PFaK7Sr4eN71hJvwSQj0c",{"id":485,"title":486,"author":487,"blobHue":245,"body":488,"category":655,"date":656,"description":492,"draft":217,"extension":218,"featured":217,"headline":657,"hue":10,"letter":658,"meta":659,"navigation":219,"path":660,"readMinutes":470,"related":661,"seo":663,"stem":664,"summary":665,"toc":666,"__hash__":672},"insights_en\u002Finsights\u002Fevery-agent-needs-a-judge.md","Every agent needs a judge",{"name":7,"role":8,"bio":9},{"type":12,"value":489,"toc":648},[490,493,496,500,503,506,509,513,516,584,587,590,594,597,617,620,624,627,630,633,638,642,645],[15,491,492],{},"A language model is very good at sounding right. That is the problem. An answer with a wrong refund amount reads exactly as confidently as one with the right amount, and a person skimming a queue of drafts will not catch it every time.",[15,494,495],{},"So we don’t ask people to catch it. In the marketplace system we built, 90 agents work across eight departments, and every team has a judge: 9 judges in all. A judge is a second model whose only job is to check another agent’s answer before anyone relies on it.",[27,497,499],{"id":498},"why-a-second-model","Why a second model",[15,501,502],{},"Asking the same model to review its own work helps less than you would think. It tends to agree with itself, and it shares the blind spots that produced the mistake in the first place.",[15,504,505],{},"That is why our judges run on a different model family from the agents they check. Different training, different habits, different failure modes. When two unrelated models agree that an answer is grounded and within policy, that means much more than one model agreeing with itself twice.",[15,507,508],{},"A judge also sees the answer differently. The agent was trying to be helpful. The judge is only trying to find what is wrong. Giving it a narrow brief, and nothing else to do, is what makes it useful.",[27,510,512],{"id":511},"block-or-grade-later","Block or grade later",[15,514,515],{},"There are two ways to put a judge in the path, and choosing between them is the main design decision.",[80,517,518,530],{},[83,519,520],{},[86,521,522,524,527],{},[89,523],{},[89,525,526],{},"BLOCK AND REPAIR",[89,528,529],{},"SHIP, THEN GRADE",[98,531,532,545,558,571],{},[86,533,534,539,542],{},[103,535,536],{},[56,537,538],{},"When the judge runs",[103,540,541],{},"Before the answer leaves",[103,543,544],{},"After it has gone out",[86,546,547,552,555],{},[103,548,549],{},[56,550,551],{},"If it fails",[103,553,554],{},"Sent back once with the reasons, then shipped with reservations",[103,556,557],{},"Flagged, counted, fed into the next lessons",[86,559,560,565,568],{},[103,561,562],{},[56,563,564],{},"Cost to the user",[103,566,567],{},"Some extra seconds",[103,569,570],{},"None",[86,572,573,578,581],{},[103,574,575],{},[56,576,577],{},"Use it for",[103,579,580],{},"Anything a customer sees, anything with money",[103,582,583],{},"High volume, low risk, easy to correct",[15,585,586],{},"In the blocking path, a failed answer is not simply rejected. It goes back to the agent once, with the judge’s reasons, and the agent gets a chance to repair it. If the repaired answer still fails, it goes out marked with the judge’s reservations, or, where the rules require it, to a person. Nothing leaves without a verdict.",[15,588,589],{},"In the grading path, the answer goes out and the judge scores it afterwards. The scores show where an agent drifts, and they feed the lessons the system learns overnight. Those lessons are not applied on their own: a person approves each one before agents use it.",[27,591,593],{"id":592},"what-a-judge-checks","What a judge checks",[15,595,596],{},"A judge with a vague brief (“is this a good answer?”) is expensive noise. Ours check specific things, and each check can fail on its own:",[171,598,600],{"title":599},"What a judge checks, every time",[175,601,602,605,608,611,614],{},[53,603,604],{},"Can every number in the answer be traced to data the agent actually read in this run?",[53,606,607],{},"Does it contradict a policy in the shared memory?",[53,609,610],{},"Does it answer the question that was asked, completely?",[53,612,613],{},"Does it propose an action the approval rules do not allow?",[53,615,616],{},"Is the tone right for who will read it?",[15,618,619],{},"The first check is the one that matters most. A refund amount, a delivery date or a stock figure that does not appear in any tool result is treated as invented, however plausible it looks.",[27,621,623],{"id":622},"what-it-costs-and-when-to-skip-it","What it costs, and when to skip it",[15,625,626],{},"A judge is another model call on every answer. It adds tokens, and in the blocking path it adds seconds. For a customer reply that is cheap insurance. For some work, it is waste.",[15,628,629],{},"We skip the judge, or move it to grading later, when the output is low stakes, reversible and cheap to check. An internal tag suggestion that a person sees anyway, or a draft that someone always edits before sending, does not need a second model standing in front of it.",[15,631,632],{},"We also never ask a model to check what code can check. Whether a price is above its floor, whether a date is in the future or whether an order exists are deterministic questions. They get deterministic answers, which are faster and do not have opinions.",[37,634,635],{},[15,636,637],{},"A judge is for judgement. If a rule can be written as code, write it as code.",[27,639,641],{"id":640},"fail-loudly-not-silently","Fail loudly, not silently",[15,643,644],{},"Judges fail too. They time out, or their provider is down for a few minutes. The worst thing a system can do then is pretend the check happened.",[15,646,647],{},"When a judge cannot run, the answer is shown with a visible “not validated” mark, and the person reading it decides whether to rely on it. A silent pass is how a system loses the trust of the people who work with it, and that trust is much harder to rebuild than a timeout is to fix.",{"title":206,"searchDepth":207,"depth":207,"links":649},[650,651,652,653,654],{"id":498,"depth":207,"text":499},{"id":511,"depth":207,"text":512},{"id":592,"depth":207,"text":593},{"id":622,"depth":207,"text":623},{"id":640,"depth":207,"text":641},"engineering","2026-09-01","Every agent needs a ==judge.==","J",{},"\u002Finsights\u002Fevery-agent-needs-a-judge",[473,227,662],"testing-a-campaign-on-customers-who-dont-exist",{"title":486,"description":492},"insights\u002Fevery-agent-needs-a-judge","Why we put a second model in front of every answer, and when it isn’t worth the cost.",[667,668,669,670,671],{"id":498,"label":499},{"id":511,"label":512},{"id":592,"label":593},{"id":622,"label":623},{"id":640,"label":641},"XzL5diXOtcDslArv3P74XXRkQd_4qZoVSP7GUPDaC8E",{"id":674,"title":675,"author":676,"blobHue":245,"body":677,"category":864,"date":865,"description":681,"draft":217,"extension":218,"featured":217,"headline":866,"hue":221,"letter":867,"meta":868,"navigation":219,"path":869,"readMinutes":470,"related":870,"seo":872,"stem":873,"summary":874,"toc":875,"__hash__":882},"insights_en\u002Finsights\u002Fthe-30-day-playbook-week-by-week.md","The 30-day playbook, week by week",{"name":7,"role":8,"bio":9},{"type":12,"value":678,"toc":856},[679,682,685,689,692,695,699,702,728,731,735,738,741,744,748,751,754,836,840,843,846,850,853],[15,680,681],{},"Thirty days sounds fast for putting AI agents into production. It is fast. It is also the reason most of our projects ship: a fixed date forces every decision that a pilot would postpone to be taken in the first week.",[15,683,684],{},"This is the playbook we follow. Every step ends with something written down and someone’s name next to it.",[27,686,688],{"id":687},"week-0-diagnose","Week 0: diagnose",[15,690,691],{},"It starts with a free call. If there is a fit, we spend the next week inside your operations, most of it with the people who do the work. We sit in on the inbox, the report, the supplier file. We want to see where the hours go and where the money leaks, not how the process is described in a slide.",[15,693,694],{},"The artefact is a map of your operations with the value of every agent we would build, and a fixed price. The sign-off is yours: which process goes first. We push for one with volume, clear rules and a number someone already cares about.",[27,696,698],{"id":697},"week-1-map","Week 1: map",[15,700,701],{},"This is the week most pilots skip, and the week that decides whether yours ships.",[50,703,704,710,716,722],{},[53,705,706,709],{},[56,707,708],{},"Access."," Real credentials to the real systems: the CRM, the helpdesk, the ERP, the inbox. Not an export.",[53,711,712,715],{},[56,713,714],{},"Real cases."," A set of past emails, tickets or files, with what a good answer looked like. They become the tests.",[53,717,718,721],{},[56,719,720],{},"One metric, signed off."," First response time, time to spot a new listing, partner hours on admin. One number, owned by the team whose work changes, signed by the person who owns it.",[53,723,724,727],{},[56,725,726],{},"First approval rules."," What the agents may do alone, and what always goes to a person, written in plain language.",[15,729,730],{},"If week 1 ends without access and a signed metric, we say so, because it is cheaper for both sides than finding out on day 29.",[27,732,734],{"id":733},"week-2-build","Week 2: build",[15,736,737],{},"Now we build the agents, the rules, the shared memory and the command center, wired into your tools. The agents live where your team already works; nobody gets a new app to learn.",[15,739,740],{},"The real cases from week 1 become evals: automated tests that run every answer against what a good answer looked like. Customer-facing answers get a judge. Tone is agreed with the people who own it, often in a single working session with a pile of past replies.",[15,742,743],{},"The sign-off at the end of the week is a walkthrough with the team lead, on their own cases.",[27,745,747],{"id":746},"week-3-prove","Week 3: prove",[15,749,750],{},"First the evals, on real cases the agents have never seen. Then shadow mode on live work: the agents draft, people send. Every edit a person makes is a signal, and we read them daily.",[15,752,753],{},"This is also where the handoff rules are tuned with the team. Which cases go straight to a person, at what threshold, through which channel. The team should be able to change a rule themselves, and in week 3 they practise doing it.",[80,755,756,769],{},[83,757,758],{},[86,759,760,763,766],{},[89,761,762],{},"STEP",[89,764,765],{},"ARTEFACT",[89,767,768],{},"WHO SIGNS",[98,770,771,784,797,810,823],{},[86,772,773,778,781],{},[103,774,775],{},[56,776,777],{},"Week 0",[103,779,780],{},"Operations map, value per agent, fixed price",[103,782,783],{},"You: which process first",[86,785,786,791,794],{},[103,787,788],{},[56,789,790],{},"Week 1",[103,792,793],{},"Access, real cases, first approval rules",[103,795,796],{},"The owner of the metric",[86,798,799,804,807],{},[103,800,801],{},[56,802,803],{},"Week 2",[103,805,806],{},"Agents, memory, rules, command center, evals",[103,808,809],{},"The team lead, after a walkthrough",[86,811,812,817,820],{},[103,813,814],{},[56,815,816],{},"Week 3",[103,818,819],{},"Eval results, shadow-mode log, tuned handoffs",[103,821,822],{},"The team lead: ready to go live",[86,824,825,830,833],{},[103,826,827],{},[56,828,829],{},"Day 30",[103,831,832],{},"Production, monitoring, trained team",[103,834,835],{},"Both of us, against the metric",[27,837,839],{"id":838},"day-30-live","Day 30: live",[15,841,842],{},"On day 30 the agents are in production, on live work, monitored from the command center. The team is trained on it: how to read a run, how to approve, how to pause an agent, how to change a rule.",[15,844,845],{},"Production means the agents answer, route or update on their own inside the rules, and the number from week 1 is tracked every day from then on. It does not mean “available on request” or “ready for phase two”.",[27,847,849],{"id":848},"why-the-date-holds","Why the date holds",[15,851,852],{},"Three things keep the date honest. The scope is one process, not the company. The metric is agreed before a line of code, so nobody can move the goalposts later. And we put our money on it: live in 30 days, or your money back.",[15,854,855],{},"After day 30 we run the fleet: monitoring, tuning and, when you are ready, the next squad. On our largest project that became one new squad a month, each built on the memory and rules of the ones before it.",{"title":206,"searchDepth":207,"depth":207,"links":857},[858,859,860,861,862,863],{"id":687,"depth":207,"text":688},{"id":697,"depth":207,"text":698},{"id":733,"depth":207,"text":734},{"id":746,"depth":207,"text":747},{"id":838,"depth":207,"text":839},{"id":848,"depth":207,"text":849},"playbooks","2026-08-18","The 30-day playbook, week by ==week.==","30",{},"\u002Finsights\u002Fthe-30-day-playbook-week-by-week",[472,473,871],"build-buy-or-both",{"title":675,"description":681},"insights\u002Fthe-30-day-playbook-week-by-week","From the first call to production: the exact steps, artefacts and sign-offs we use.",[876,877,878,879,880,881],{"id":687,"label":688},{"id":697,"label":698},{"id":733,"label":734},{"id":746,"label":747},{"id":838,"label":839},{"id":848,"label":849},"rT6HBQ-x40ciVZH-qHpcDH1wLuGv79MQR2E3ffHF_dY",1790618465009]