[{"data":1,"prerenderedAt":1350},["ShallowReactive",2],{"site-nav-content":3,"blog:/blog/loops-for-revenue-operations":179,"blog-index-copy":756,"blog:/blog/loops-for-revenue-operations:surround":777,"hiring-banner-content":1319,"site-cta-content":1331},{"header":4,"productNav":9,"nav":42,"footer":61,"askAI":132,"id":163,"title":164,"archived":165,"authors":166,"badge":166,"body":167,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":175,"relatedHeading":166,"seo":176,"series":166,"sitemap":165,"status":166,"stem":177,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":178},{"productLabel":5,"loginLabel":6,"contactLabel":7,"contactSalesLabel":8},"Product","Log in","Contact","Get started for free",[10,14,18,22,26,30,34,38],{"label":11,"to":12,"description":13},"Overview","/overview","Seven layers. One closed loop.",{"label":15,"to":16,"description":17},"Conflux","/product/conflux","Where your team, workstreams, and agents meet.",{"label":19,"to":20,"description":21},"Agent Teams","/product/agent-teams","Specialist teams - governed from day one.",{"label":23,"to":24,"description":25},"Lifecycle Graph","/product/lifecycle-graph","Intelligence that compounds across every interaction.",{"label":27,"to":28,"description":29},"Company Wiki","/product/wiki","Playbooks and policies where expertise stays.",{"label":31,"to":32,"description":33},"Workstreams","/product/workstreams","From brief to signed-off deliverable on one canvas.",{"label":35,"to":36,"description":37},"Perception Console","/product/perception","Ask your whole business in plain English.",{"label":39,"to":40,"description":41},"Governance","/product/governance","Frontier AI you can actually sign off on.",[43,46,49,52,55,58],{"label":44,"to":45},"Models","/models",{"label":47,"to":48},"Pricing","/pricing",{"label":50,"to":51},"Integrations","/integrations",{"label":53,"to":54},"Security","/security",{"label":56,"to":57},"Partners","/partners",{"label":59,"to":60},"Insights","/blog",{"productHeading":5,"companyHeading":62,"resourcesHeading":63,"legalHeading":64,"docsLabel":65,"docsUrl":66,"statementLines":67,"copyright":70,"companyLinks":71,"resourcesLinks":86,"legalLinks":102,"socialLinks":109,"bottomLinks":119},"Company","Resources","Legal","Docs","https://docs.gonimbus.ai",[68,69],"Stop training someone else's model.","Control your AI.","© 2026 Nimbus Intelligence, Inc. All rights reserved.",[72,73,74,75,76,78,81,84],{"label":47,"to":48},{"label":50,"to":51},{"label":53,"to":54},{"label":59,"to":60},{"label":77,"to":57},"Partner Program",{"label":79,"to":80},"Careers","/careers",{"label":82,"to":83},"System status","/status",{"label":7,"to":85},"/contact",[87,90,93,96,99],{"label":88,"to":89},"Glossary","/glossary",{"label":91,"to":92},"Compare","/compare",{"label":94,"to":95},"Evaluate","/evaluate",{"label":97,"to":98},"Problems","/problems",{"label":100,"to":101},"Use cases","/use-cases",[103,106],{"label":104,"to":105},"Terms of Service","/terms",{"label":107,"to":108},"Privacy Policy","/privacy",[110,113,116],{"label":111,"href":112},"LinkedIn","https://www.linkedin.com/company/gonimbusai/",{"label":114,"href":115},"X","https://x.com/gonimbusai",{"label":117,"href":118},"Instagram","https://www.instagram.com/gonimbus_ai/",[120,122,124,127,128],{"label":121,"to":105},"Terms",{"label":123,"to":108},"Privacy",{"label":125,"to":126},"Compliance","/compliance",{"label":82,"to":83},{"label":129,"to":130,"external":131},"LLMs.txt","/llms.txt",true,{"text":133,"prompt":134},"Ask AI about Nimbus",{"I'm researching enterprise intelligence platforms and want to know how Nimbus combines perception, collaboration, and autonomous agents to drive strategic decision-making":135,"platforms":137},{" Summarize the highlights from Nimbus's website":136},"https://gonimbus.ai",[138,143,148,153,158],{"name":139,"label":140,"icon":141,"hrefPrefix":142},"chatgpt","ChatGPT","simple-icons:openai","https://chatgpt.com/?prompt=",{"name":144,"label":145,"icon":146,"hrefPrefix":147},"perplexity","Perplexity","mdi:magnify","https://www.perplexity.ai/search/new?q=",{"name":149,"label":150,"icon":151,"hrefPrefix":152},"grok","Grok","simple-icons:x","https://x.com/i/grok?text=",{"name":154,"label":155,"icon":156,"hrefPrefix":157},"claude","Claude","simple-icons:anthropic","https://claude.ai/new?q=",{"name":159,"label":160,"icon":161,"hrefPrefix":162},"google-ai","Google AI","simple-icons:google","https://www.google.com/search?udm=50&aep=11&q=","content/shared/nav.md","Site navigation",false,null,{"type":168,"value":169,"toc":170},"minimark",[],{"title":171,"searchDepth":172,"depth":172,"links":173},"",2,[],"md","/shared/nav",{"title":164,"description":171},"shared/nav","1dD7ahDRl0SQ4hz53-kKo0tEFrGaLuaztZ3PPfp6a9k",{"id":180,"title":181,"archived":165,"authors":182,"badge":185,"body":187,"date":728,"definedTerm":166,"department":166,"description":729,"extension":174,"eyebrow":166,"faqHeader":730,"faqs":733,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":746,"relatedHeading":166,"seo":747,"series":748,"sitemap":131,"status":166,"stem":749,"subhead":166,"tags":750,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":755},"content/blog/loops-for-revenue-operations.md","Loops for Revenue Operations",[183],{"name":184,"to":136},"Nimbus Research",{"label":186},"Use case",{"type":168,"value":188,"toc":719},[189,201,218,221,261,264,269,277,298,306,309,312,325,329,332,335,346,349,363,375,379,428,431,435,438,444,454,460,465,483,489,501,508,572,583,587,590,612,615,618,625,629,639,642,659,676,689,692,696,706,715],[190,191,192,193,200],"p",{},"Revenue operations already lives between systems. CRM says one Amount. The regional sheet says another. The AE’s message says “slipped.” Monday hygiene is the ritual that tries to list those conflicts before finance signs a number: missing close dates, stages that do not match activity, commit deals with no activity, duplicates. The failure mode is a fluent story that hides the disagreement — or an unattended job that “fixes” stages in bulk before anyone names who wins. McKinsey’s ",[194,195,199],"a",{"href":196,"rel":197},"https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai",[198],"nofollow","State of AI"," (2025) finds AI adoption deep in commercial functions while scaling governance lags: hygiene still wins forecast quality, not a better paragraph.",[190,202,203,204,208,209,212,213,217],{},"This page is ",[205,206,207],"strong",{},"unattended standing-order work",", not the shared collaborative room where RevOps, sales, and finance sign a forecast. The standing order runs when the opportunity moves, the sheet lands in the folder, or the calendar says Monday, and it ",[205,210,211],{},"skips"," when nothing material changed. It produces the artefact the room needs — a conflict list, a hygiene CSV, a skip log — and stops. For the room that resolves conflicts and signs the number, read ",[194,214,216],{"href":215},"collaborative-ai-for-revenue-operations","collaborative AI for revenue operations",".",[190,219,220],{},"Three nouns get conflated in every vendor deck. Keep them as vocabulary, not as a product menu:",[222,223,224,235,251],"ul",{},[225,226,227,230,231,217],"li",{},[205,228,229],{},"Eval loop"," — a sensor that grades a run after the fact. Did the write match the signed payload? See ",[194,232,234],{"href":233},"eval-loops-for-enterprise-agent-harnesses","eval loops for enterprise agent harnesses",[225,236,237,240,241,245,246,250],{},[205,238,239],{},"Standing-order loop"," — a compiled recipe that admits a run when a trigger fires. Trigger, steps, run record, notify. See ",[194,242,244],{"href":243},"what-is-loop-engineering","what is loop engineering"," and the ",[194,247,249],{"href":248},"what-is-a-nimbus-loop","standing-order loop"," definition.",[225,252,253,256,257,217],{},[205,254,255],{},"Agentic workflow"," — an interactive path that still reasons when the route is not fully known. See ",[194,258,260],{"href":259},"what-is-an-agentic-workflow","what is an agentic workflow",[190,262,263],{},"The hygiene and definitional work still wins forecast quality, not better paragraph generation. Automate the hygiene signal. Keep the number on the roster.",[265,266,268],"h2",{"id":267},"what-a-revops-standing-order-loop-is","What a RevOps standing-order loop is",[190,270,271,272,276],{},"Three common starts, from ",[194,273,275],{"href":274},"six-things-that-start-a-loop","six things that start a loop",":",[278,279,280,286,292],"ol",{},[225,281,282,285],{},[205,283,284],{},"When the opportunity moves"," — stage, close date, or Amount changes in CRM against the rule set finance cares about.",[225,287,288,291],{},[205,289,290],{},"When the file lands"," — the regional sheet appears in the shared location with yesterday’s timestamp.",[225,293,294,297],{},[205,295,296],{},"When the calendar says Monday"," — the hygiene list: missing fields, duplicates, commit deals with no activity.",[190,299,300,301,305],{},"The job is narrow: detect that start, run the saved steps, produce the artefact the room needs, and stop. It does not resolve conflicts. Resolution has a name on the collaborative job. ",[194,302,304],{"href":303},"a-loop-is-not-an-agent","A loop is not an agent",": the standing order does not negotiate with sales. It runs the recipe or skips.",[190,307,308],{},"Deterministic triggers matter more here than model routing. If the start condition is fuzzy, you will run every Monday even when nothing moved — or miss the week the sheet arrived on Tuesday. Prefer sensors you can explain to finance: field delta, file mtime, calendar with a timezone.",[190,310,311],{},"Skip when nothing changed. That skip is a first-class outcome. A loop that always produces a narrative trains people to ignore it. A loop that writes “skipped: no delta since last run” is evidence you are not burning tokens for theatre.",[190,313,314,315,319,320,324],{},"Compare ",[194,316,318],{"href":317},"loop-vs-workflow-vs-agent","loop vs workflow vs agent",": the standing order is the deployed, unattended instance; the collaborative forecast is the human-stopped workflow; an agent is the reasoning actor for unknown branches. ",[194,321,323],{"href":322},"loop-vs-rpa","Loop vs RPA"," is the cousin when someone still wants a bot to click the CRM screen.",[265,326,328],{"id":327},"why-revops-should-care","Why RevOps should care",[190,330,331],{},"Because the conflict is the work, and unattended listing is the part worth automating.",[190,333,334],{},"RevOps already pays a reinterpretation tax every week. Someone re-exports. Someone else filters a different region. Audit — or just next quarter’s new hire — asks what ran last Monday and the answer is “ask Sarah.” A personal script, a fragile Zap, or a heroic analyst export can produce a list. They rarely produce a skip log, a recipe version, and a run record the controller would recognise.",[190,336,337,338,341,342,345],{},"The failure mode for automation is picking the fluent story. The model summarises “pipeline is healthy” while Amount still disagrees with the sheet. Or the automation writes stages in bulk because the demo looked tidy. The collaborative room exists so ",[205,339,340],{},"resolution"," stays human and signed. The standing order exists so ",[205,343,344],{},"detection and listing"," do not depend on someone remembering to export.",[190,347,348],{},"You should care if:",[222,350,351,354,357,360],{},[225,352,353],{},"Monday hygiene already happens in a personal script, a Zap, or an export nobody can replay",[225,355,356],{},"Amount disagrees with the board pack and nobody can tell what ran last week",[225,358,359],{},"“CRM fixes” still happen in side chats after the list exists",[225,361,362],{},"finance opens the meeting by asking whether the sheet arrived",[190,364,365,369,370,374],{},[194,366,368],{"href":367},"what-is-collaborative-ai","What is collaborative AI"," remains the definition for the room. This page is only the standing order beside it. ",[194,371,373],{"href":372},"how-to-evaluate-loop-engineering","How to evaluate loop engineering"," is the buying sheet: triggers, skip logs, and replay matter more than eloquence.",[265,376,378],{"id":377},"words-you-will-hear","Words you will hear",[222,380,381,387,393,399,405,411,422],{},[225,382,383,386],{},[205,384,385],{},"Trigger."," What admits a run: field change, file landing, Monday calendar, manual start.",[225,388,389,392],{},[205,390,391],{},"Compiled recipe."," The fixed steps for this hygiene job. Not “fix pipeline.”",[225,394,395,398],{},[205,396,397],{},"Skip."," A deliberate halt when nothing changed or preconditions failed. Recorded, not hidden.",[225,400,401,404],{},[205,402,403],{},"Run record."," What ran, on which scope, with which recipe version, what was produced or skipped.",[225,406,407,410],{},[205,408,409],{},"Write-back."," A CRM field change. Default off for the standing order.",[225,412,413,416,417,421],{},[205,414,415],{},"Eval loop."," The sensor ",[418,419,420],"em",{},"after"," a signed write: read-back Amount matches the payload.",[225,423,424,427],{},[205,425,426],{},"Agentic workflow."," Open-ended replan — “make pipeline healthy” with no saved recipe.",[190,429,430],{},"Do not collapse those last two with the standing order because a slide said “agentic loops.” Ask what starts the run, what is compiled, and what grades the finish.",[265,432,434],{"id":433},"how-to-compile-one-revops-standing-order","How to compile one RevOps standing order",[190,436,437],{},"Start from a job people already run without the model.",[190,439,440,441],{},"Example: ",[205,442,443],{},"Monday hygiene for Region West",[190,445,446,449,450,453],{},[205,447,448],{},"Trigger:"," Monday 07:00 Europe/London ",[205,451,452],{},"or"," manual “run hygiene.”",[190,455,456,459],{},[205,457,458],{},"Preconditions:"," read-only CRM connection scoped to West pipeline; last-run timestamp stored.",[190,461,462],{},[205,463,464],{},"Steps:",[278,466,467,470,477,480],{},[225,468,469],{},"Query opportunities missing close date, stage inconsistent with last activity, Amount null.",[225,471,472,473,476],{},"Compare to last run’s id set. If identical, ",[205,474,475],{},"skip"," and log.",[225,478,479],{},"If delta, write the hygiene list and attach a CSV.",[225,481,482],{},"Notify the RevOps roster — not the whole company.",[190,484,485,488],{},[205,486,487],{},"Explicit non-goals:"," no stage writes; no customer email; no forecast number.",[190,490,491,492,495,496,500],{},"When a row needs a CRM write, open or update the ",[205,493,494],{},"collaborative"," forecast job for that week. The standing order may attach the hygiene list there. Finance still signs the number in the room. ",[194,497,499],{"href":498},"what-is-write-back-governance","Write-back governance"," applies to the write, not to the read-only list.",[190,502,503,504,507],{},"A second common compile: ",[205,505,506],{},"when Amount moves",". Trigger on field delta against finance’s rule set. Produce a conflict row with both CRM and sheet values if the sheet trigger also fired. Do not average them. Do not pick the fluent story. List both. Name who wins on the collaborative job.",[509,510,514],"pre",{"className":511,"code":512,"language":513,"meta":171,"style":171},"language-mermaid shiki shiki-themes github-light github-dark","flowchart TD\n  trigger[\"Opportunity moved or Monday\"] --> precheck{\"Ready to run?\"}\n  precheck -->|no| skipLog[\"Skip with a reason\"]\n  precheck -->|yes| delta{\"Anything changed?\"}\n  delta -->|no| skipLog\n  delta -->|yes| recipe[\"Run the saved recipe\"]\n  recipe --> runPage[\"Outputs on the run page\"]\n  runPage --> notify[\"Notify the roster\"]\n  runPage --> collabRoom[\"Forecast room, if needed\"]\n","mermaid",[515,516,517,525,530,536,542,548,554,560,566],"code",{"__ignoreMap":171},[518,519,522],"span",{"class":520,"line":521},"line",1,[518,523,524],{},"flowchart TD\n",[518,526,527],{"class":520,"line":172},[518,528,529],{},"  trigger[\"Opportunity moved or Monday\"] --> precheck{\"Ready to run?\"}\n",[518,531,533],{"class":520,"line":532},3,[518,534,535],{},"  precheck -->|no| skipLog[\"Skip with a reason\"]\n",[518,537,539],{"class":520,"line":538},4,[518,540,541],{},"  precheck -->|yes| delta{\"Anything changed?\"}\n",[518,543,545],{"class":520,"line":544},5,[518,546,547],{},"  delta -->|no| skipLog\n",[518,549,551],{"class":520,"line":550},6,[518,552,553],{},"  delta -->|yes| recipe[\"Run the saved recipe\"]\n",[518,555,557],{"class":520,"line":556},7,[518,558,559],{},"  recipe --> runPage[\"Outputs on the run page\"]\n",[518,561,563],{"class":520,"line":562},8,[518,564,565],{},"  runPage --> notify[\"Notify the roster\"]\n",[518,567,569],{"class":520,"line":568},9,[518,570,571],{},"  runPage --> collabRoom[\"Forecast room, if needed\"]\n",[190,573,574,578,579,582],{},[194,575,577],{"href":576},"rbac-for-enterprise-ai","RBAC for enterprise AI"," belongs here: the standing order runs with ",[205,580,581],{},"read"," grants. It does not inherit a human’s write token.",[265,584,586],{"id":585},"what-done-looks-like","What “done” looks like",[190,588,589],{},"A good RevOps standing-order week:",[222,591,592,599,606,609],{},[225,593,594,595,598],{},"The hygiene list exists ",[205,596,597],{},"only if"," something changed — or a skip log says why not.",[225,600,601,602,605],{},"Conflicts are visible with ",[205,603,604],{},"both"," CRM and sheet values when the sheet trigger fired.",[225,607,608],{},"No CRM field changed without a collaborative sign.",[225,610,611],{},"A new team member can open last Monday’s run and reconstruct what ran without asking the hero who “owns the script.”",[190,613,614],{},"The signed forecast still lives on the collaborative job: number, definition, signer, accepted conflicts. The standing order feeds that job. It does not replace it.",[190,616,617],{},"Measure: Did finance open the list before the forecast meeting? Did side-chat “CRM fixes” fall? If not, you built another report. Keep a run-log habit the controller would recognise: trigger type, scope, row counts, skip reason, recipe version. When board week goes wrong, you want to open 14 September’s run — not Slack.",[190,619,620,621,624],{},"That log is also the bridge to ",[205,622,623],{},"eval loops"," on the write path: the list is feed-forward; the read-back after sign is the oracle. Do not collapse them because both contain the word “loop.”",[265,626,628],{"id":627},"how-to-start-with-one-trigger","How to start with one trigger",[190,630,631,632,634,635,638],{},"Pick one start from ",[194,633,275],{"href":274},". ",[205,636,637],{},"File lands"," is often easiest — the sheet already has a ritual.",[190,640,641],{},"Four weeks:",[278,643,644,647,653,656],{},[225,645,646],{},"Read-only CRM plus folder watch for one region’s sheet.",[225,648,649,650,217],{},"A conflict or hygiene list with ",[205,651,652],{},"skip when unchanged",[225,654,655],{},"Outputs on a run record, not in email only.",[225,657,658],{},"No CRM writes from the standing order — zero.",[190,660,661,665,666,670,671,675],{},[194,662,664],{"href":663},"collaborative-ai-for-finance-and-planning","Collaborative AI for finance and planning"," may consume the same hygiene output when pipeline disputes affect the number finance signs. ",[194,667,669],{"href":668},"loops-for-finance-and-planning","Loops for finance and planning"," and ",[194,672,674],{"href":673},"loops-for-legal-and-compliance","loops for legal and compliance"," are the sibling patterns when the trigger is a close pack or a policy file.",[190,677,678,679,681,682,685,686,688],{},"If you are still naming the object, ",[194,680,244],{"href":243}," is the discipline and ",[194,683,684],{"href":372},"how to evaluate loop engineering"," is how you refuse a vendor that cannot skip. ",[194,687,304],{"href":303}," is why hygiene should not invent a stage change.",[190,690,691],{},"Unattended work should be boring: same recipe, honest skip, a run record audit trail. Leave the forecast number to the room where someone signs.",[265,693,695],{"id":694},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[190,697,698,699,702,703,705],{},"Nimbus ",[194,700,701],{"href":32},"workstreams"," can host the standing-order loop and the collaborative forecast room side by side: trigger, compiled recipe, run page, roster notification — and a separate job where finance signs the number. ",[194,704,39],{"href":40}," stays on the CRM write, not on the read-only hygiene list.",[190,707,708,711,712,714],{},[194,709,710],{"href":248},"What is a Nimbus Loop"," is the product noun for the standing order. Score it with ",[194,713,684],{"href":372}," before you let it touch stages.",[716,717,718],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":171,"searchDepth":172,"depth":172,"links":720},[721,722,723,724,725,726,727],{"id":267,"depth":172,"text":268},{"id":327,"depth":172,"text":328},{"id":377,"depth":172,"text":378},{"id":433,"depth":172,"text":434},{"id":585,"depth":172,"text":586},{"id":627,"depth":172,"text":628},{"id":694,"depth":172,"text":695},"2026-09-12","A standing-order loop for RevOps is unattended hygiene when the opportunity moves, the file lands, or Monday is due — not the shared forecast room. Skip when nothing changed.",{"eyebrow":731,"title":732},"Common questions","Standing orders vs the forecast room",[734,737,740,743],{"question":735,"answer":736},"Is a standing-order loop the same as the weekly forecast meeting?","No. The meeting is collaborative AI — conflicts, a named finance signer, a signed number. A standing-order loop is the unattended recipe that runs when data moves or the calendar says Monday, and skips when nothing material changed. It produces the list the room needs. It does not resolve conflicts and it does not sign the forecast. If you collapse the two, you either get a bot that rewrites stages before a signer exists, or a meeting that still starts with a heroic export. Keep listing unattended. Keep the number on the roster.",{"question":738,"answer":739},"What is the difference between a standing-order loop and an eval loop?","An eval loop is a sensor that checks whether a harness job finished correctly — tests, read-backs, payload hash. A standing-order loop is an operator recipe that admits a run when a trigger fires: detect change, run saved steps, land outputs, notify the roster. An agentic workflow is the third noun: an interactive path that still reasons when the route is not fully known. Vendors blur all three because they contain the word loop or the word agent. Ask what starts the run, what is compiled, and what grades the finish. Those are three jobs.",{"question":741,"answer":742},"Should the loop fix CRM stages on its own?","List and draft first. Treat stage or Amount changes as write-back. If nobody approves on the collaborative job, nothing happens in CRM — even if the loop flagged the row. Bulk cosmetics before a signer exists are how data goes wrong quickly. The loop may attach the hygiene list to the forecast job for that week. Finance still signs the number in the room. A loop that inherits a humans write token is not a standing order. It is an unattended clerk.",{"question":744,"answer":745},"What does a good skip look like?","A skip is a first-class outcome: the trigger fired, preconditions were checked, nothing material changed, and the run page says so. A loop that always produces a narrative trains people to ignore it. A loop that writes skipped, no delta since last run is evidence you are not burning tokens for theatre. Ten runs with unchanged inputs should produce ten skip records and zero spurious writes. If Finance still got paged, you built an alert, not a standing order.","/blog/loops-for-revenue-operations",{"title":181,"description":729},"use-case","blog/loops-for-revenue-operations",[748,751,752,753,754],"RevOps","loops","pipeline","CRM","AIiSyje3ZsKCEAyuwW_39_gz20h7-427-Sy5APLE0TI",{"hero":757,"id":759,"title":760,"archived":165,"authors":166,"badge":166,"body":761,"date":166,"definedTerm":166,"department":166,"description":765,"extension":174,"eyebrow":766,"faqHeader":166,"faqs":166,"footerBand":767,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":60,"relatedHeading":773,"seo":774,"series":166,"sitemap":131,"status":166,"stem":775,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":776},{"filename":758},"u2221455217_Flat_design_of_a_futuristic_minimalist_landscape__5d589295-cdea-4ea9-a262-be766881accf_1.png","content/blog/index.md","Exploring the future of intelligence.",{"type":168,"value":762,"toc":763},[],{"title":171,"searchDepth":172,"depth":172,"links":764},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":768,"description":769,"primaryLabel":770,"primaryTo":771,"secondaryLabel":772,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","/newsletter","Explore the platform","More research",{"title":760,"description":765},"blog/index","BFSWGYO9bcTlaulivKYWyg08_DJHsdGg3OC6g_CG1Hw",[166,778],{"id":779,"title":780,"archived":165,"authors":781,"badge":783,"body":784,"date":728,"definedTerm":166,"department":166,"description":1296,"extension":174,"eyebrow":166,"faqHeader":1297,"faqs":1299,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1311,"relatedHeading":166,"seo":1312,"series":748,"sitemap":131,"status":166,"stem":1313,"subhead":166,"tags":1314,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1318},"content/blog/loops-for-legal-and-compliance.md","Loops for Legal and Compliance",[782],{"name":184,"to":136},{"label":186},{"type":168,"value":785,"toc":1287},[786,799,812,815,840,843,847,851,870,884,896,899,903,913,916,931,950,952,966,977,979,1020,1023,1027,1030,1035,1040,1045,1049,1080,1085,1088,1093,1098,1104,1153,1158,1160,1163,1181,1184,1189,1209,1213,1224,1226,1244,1247,1265,1268,1270,1278,1285],[190,787,788,789,792,793,798],{},"Legal and compliance already watch incoming paper and policy changes — or they mean to. Customer paper lands in a folder. A playbook PDF is replaced. A regulator feed publishes. Sales learns “legal is comfortable” from a retrieval snippet. Incoming MSAs sit until someone remembers. The failure mode is fluency treated as review, and a watch that ",[205,790,791],{},"guesses"," which version applies instead of escalating. The ",[194,794,797],{"href":795,"rel":796},"https://eur-lex.europa.eu/eli/reg/2024/1689/oj",[198],"EU Artificial Intelligence Act"," (Regulation (EU) 2024/1689, 2024) is not a clause playbook; it is a reminder that automated systems carry duties chat etiquette does not satisfy.",[190,800,203,801,803,804,807,808,217],{},[205,802,207],{},", not the shared collaborative room where legal, sales, and compliance quote a clause, pin a playbook version, and a named lawyer refuses or signs. The standing order watches a clause source, a policy repository, or an incoming file queue. It quotes or hashes what changed, compares it to the version on the job, and ",[205,805,806],{},"escalates",". It does not approve send. It does not paraphrase the clause into “legal OK.” For that room, read ",[194,809,811],{"href":810},"collaborative-ai-for-legal-and-compliance-review","collaborative AI for legal and compliance review",[190,813,814],{},"Three nouns, as vocabulary:",[222,816,817,824,833],{},[225,818,819,821,822,217],{},[205,820,229],{}," — a completion sensor. Did the sent message match the signed payload hash? See ",[194,823,234],{"href":233},[225,825,826,828,829,245,831,250],{},[205,827,239],{}," — a compiled watch that admits a run when a trigger fires. See ",[194,830,244],{"href":243},[194,832,249],{"href":248},[225,834,835,837,838,217],{},[205,836,255],{}," — open-ended replan, such as “review this contract” with no quote, version, or rejector. See ",[194,839,260],{"href":259},[190,841,842],{},"A watch that logs what it saw is more useful than a bot that guesses comfort. Escalate. Do not guess.",[265,844,846],{"id":845},"what-a-legal-and-compliance-standing-order-loop-is","What a legal and compliance standing-order loop is",[190,848,271,849,276],{},[194,850,275],{"href":274},[278,852,853,859,864],{},[225,854,855,858],{},[205,856,857],{},"When the policy changes"," — playbook PDF updated, wiki revision, grid effective date crossed.",[225,860,861,863],{},[205,862,290],{}," — customer paper in the intake folder, vendor MSA upload, RFP attachment.",[225,865,866,869],{},[205,867,868],{},"When the clause source moves"," — standard terms URL changed, registry filing published, regulator update feed.",[190,871,872,873,876,877,880,881,883],{},"The job is narrow: detect the start, ",[205,874,875],{},"quote or hash"," what changed, compare to the version pinned on the job, and ",[205,878,879],{},"escalate"," — open a collaborative matter or notify the named lawyer roster. It does not approve send. ",[194,882,304],{"href":303},": the standing order does not bind the company.",[190,885,886,887,890,891,895],{},"Do not let the watch ",[205,888,889],{},"guess"," which playbook applies when three PDFs share a title. Escalate with the diff and let the lawyer pick the version on the collaborative job. Retrieval that prefers an obsolete doc because it ranked well is a harness failure, not a legal skill issue. ",[194,892,894],{"href":893},"what-is-harness-engineering","What is harness engineering"," covers pinning versions on the job.",[190,897,898],{},"Skip when the file is a duplicate of an open matter, or when the policy diff is empty. That skip is a first-class outcome. A watch that always opens a matter trains lawyers to ignore it. A watch that writes “skipped: hash matches open matter” is evidence you are not paging people for theatre.",[265,900,902],{"id":901},"why-legal-should-care","Why legal should care",[190,904,905,906,909,910,217],{},"Because fluency is not review, and ",[205,907,908],{},"watching"," is not ",[205,911,912],{},"signing",[190,914,915],{},"Legal is often late because nobody routed the matter — not because the model cannot summarise. A standing order fixes routing: file landed, policy delta detected, matter opened with sources attached. The collaborative room fixes substance: quote, version, named rejector, send gate.",[190,917,918,919,924,925,930],{},"In February 2024 Air Canada was held to chatbot-invented fare terms — ",[194,920,923],{"href":921,"rel":922},"https://www.cbc.ca/news/canada/british-columbia/air-canada-chatbot-lawsuit-1.7116416",[198],"CBC News",", decision ",[194,926,929],{"href":927,"rel":928},"https://decisions.civilresolutionbc.ca/crt/crtd/en/525448/1/document.do",[198],"Moffatt v. Air Canada",". A watch would not have saved that alone; a send gate on customer-facing claims would. Standing orders and collaborative review are complementary: detect and route fast; refuse and sign in the room.",[190,932,933,934,939,940,943,944,949],{},"NIST’s ",[194,935,938],{"href":936,"rel":937},"https://www.nist.gov/itl/ai-risk-management-framework",[198],"AI Risk Management Framework"," (2023) maps govern-measure-manage for AI systems. A watch that logs triggers and skips is a ",[205,941,942],{},"measure"," input. It is not a substitute for a named rejector on Tuesday’s concession. In June 2023 a New York federal judge sanctioned two lawyers who filed a brief citing cases ",[194,945,948],{"href":946,"rel":947},"https://www.reuters.com/legal/new-york-lawyers-sanctioned-using-fake-chatgpt-cases-legal-brief-2023-06-22/",[198],"ChatGPT had invented",". Fiction had been written into a court record. The analogue here is “legal OK” written into a CRM field because a summary ranked well.",[190,951,348],{},[222,953,954,957,960,963],{},[225,955,956],{},"policy changes already arrive as email attachments and sales learns from a snippet",[225,958,959],{},"incoming MSAs sit in a folder until someone remembers",[225,961,962],{},"three playbook PDFs share a title and retrieval picks the obsolete one",[225,964,965],{},"customer-facing claims leave the building without a send gate",[190,967,968,971,972,976],{},[194,969,970],{"href":498},"What is write-back governance"," stays on customer messages, contract repositories, and CRM terms fields. ",[194,973,975],{"href":974},"what-is-ai-governance","What is AI governance"," is the wider map.",[265,978,378],{"id":377},[222,980,981,987,993,999,1005,1010,1015],{},[225,982,983,986],{},[205,984,985],{},"Quote."," The clause as written, extracted — not a paraphrase.",[225,988,989,992],{},[205,990,991],{},"Pinned playbook version."," The version the watch diffs against. Not “the legal PDF.”",[225,994,995,998],{},[205,996,997],{},"Diff."," What changed between pinned version and new source, as an artefact.",[225,1000,1001,1004],{},[205,1002,1003],{},"Escalate."," Open a collaborative matter or notify the named roster. Do not guess.",[225,1006,1007,1009],{},[205,1008,397],{}," Duplicate hash or empty diff, recorded with a reason.",[225,1011,1012,1014],{},[205,1013,415],{}," After send, did the message match the signed payload?",[225,1016,1017,1019],{},[205,1018,426],{}," “Handle contracts” with no saved escalation path.",[190,1021,1022],{},"Regulators and general counsel reconstruct matters, not token traces. Your watch should produce: file hash, quoted sections, playbook version pinned, diff summary, skip log, matter id opened. Engineers may need traces for debugging; the company needs the matter record.",[265,1024,1026],{"id":1025},"how-to-compile-one-legal-standing-order","How to compile one legal standing order",[190,1028,1029],{},"Start from intake people already perform badly when busy.",[190,1031,440,1032],{},[205,1033,1034],{},"Incoming customer paper",[190,1036,1037,1039],{},[205,1038,448],{}," file lands in the legal-intake folder with extension pdf or docx.",[190,1041,1042,1044],{},[205,1043,458],{}," job pinned to current playbook version; roster includes the duty lawyer.",[190,1046,1047],{},[205,1048,464],{},[278,1050,1051,1056,1063,1070,1073],{},[225,1052,1053,1054,476],{},"Hash file; if duplicate of open matter, ",[205,1055,475],{},[225,1057,1058,1059,1062],{},"Extract ",[205,1060,1061],{},"quoted"," limitation-of-liability and data-processing sections — not summary-only.",[225,1064,1065,1066,1069],{},"Compare keywords against pinned playbook sections; flag deltas as ",[205,1067,1068],{},"questions",", not approvals.",[225,1071,1072],{},"Open a collaborative matter with quote, file, playbook version, and flag list.",[225,1074,1075,1076,1079],{},"Notify the named roster. ",[205,1077,1078],{},"Disable send"," on any draft until a lawyer joins the matter.",[190,1081,1082,1084],{},[205,1083,487],{}," no customer email; no CRM “legal approved” field; no auto-redline send.",[190,1086,1087],{},"When policy changes:",[190,1089,1090,1092],{},[205,1091,448],{}," playbook repository commit or effective date.",[190,1094,1095,1097],{},[205,1096,464],{}," diff old vs new pinned version; list clauses affected; open matters for templates that reference changed sections; skip if diff empty.",[190,1099,1100,1101,217],{},"Write-back — customer messages, contract repositories, CRM terms fields — stays on the collaborative path with ",[194,1102,1103],{"href":498},"write-back governance",[509,1105,1107],{"className":511,"code":1106,"language":513,"meta":171,"style":171},"flowchart TD\n  watchTrigger[\"Policy changes or a file lands\"] --> seen{\"Already seen this file?\"}\n  seen -->|yes| skipLegal[\"Skip, logged\"]\n  seen -->|no| quoteExtract[\"Quote the key clauses\"]\n  quoteExtract --> diffPlaybook[\"Compare to the pinned playbook\"]\n  diffPlaybook --> escalate[\"Open a review matter\"]\n  escalate --> notifyLawyer[\"Notify the named lawyer\"]\n  escalate --> reviewRoom[\"Collaborative review\"]\n  reviewRoom -->|signed| sendGate[\"Send or write\"]\n",[515,1108,1109,1113,1118,1123,1128,1133,1138,1143,1148],{"__ignoreMap":171},[518,1110,1111],{"class":520,"line":521},[518,1112,524],{},[518,1114,1115],{"class":520,"line":172},[518,1116,1117],{},"  watchTrigger[\"Policy changes or a file lands\"] --> seen{\"Already seen this file?\"}\n",[518,1119,1120],{"class":520,"line":532},[518,1121,1122],{},"  seen -->|yes| skipLegal[\"Skip, logged\"]\n",[518,1124,1125],{"class":520,"line":538},[518,1126,1127],{},"  seen -->|no| quoteExtract[\"Quote the key clauses\"]\n",[518,1129,1130],{"class":520,"line":544},[518,1131,1132],{},"  quoteExtract --> diffPlaybook[\"Compare to the pinned playbook\"]\n",[518,1134,1135],{"class":520,"line":550},[518,1136,1137],{},"  diffPlaybook --> escalate[\"Open a review matter\"]\n",[518,1139,1140],{"class":520,"line":556},[518,1141,1142],{},"  escalate --> notifyLawyer[\"Notify the named lawyer\"]\n",[518,1144,1145],{"class":520,"line":562},[518,1146,1147],{},"  escalate --> reviewRoom[\"Collaborative review\"]\n",[518,1149,1150],{"class":520,"line":568},[518,1151,1152],{},"  reviewRoom -->|signed| sendGate[\"Send or write\"]\n",[190,1154,1155,1157],{},[194,1156,373],{"href":372}," applies to watch loops too: can you replay why a matter opened, or why it skipped?",[265,1159,586],{"id":585},[190,1161,1162],{},"A good legal standing-order week:",[222,1164,1165,1172,1175,1178],{},[225,1166,1167,1168,1171],{},"Every new file either opened a matter with ",[205,1169,1170],{},"quotes"," or logged a skip with reason.",[225,1173,1174],{},"Policy-change runs produced a diff artefact, not a chat summary.",[225,1176,1177],{},"No customer send from the standing-order path.",[225,1179,1180],{},"A later reader can reconstruct intake without asking who “checked the bot.”",[190,1182,1183],{},"The signed review still lives on the collaborative job: quoted text, playbook version, rejector, send log. The standing order is the doorbell, not the judge.",[190,1185,1186,1188],{},[194,1187,577],{"href":576}," applies: outside counsel may see the matter, not every connector. Retention should match how long you must explain the language.",[190,1190,1191,1192,1195,1196,1199,1200,1204,1205,1208],{},"Website and support bots need the same escalation split: a watch may ",[205,1193,1194],{},"detect"," that public terms changed; the ",[205,1197,1198],{},"send"," of customer-facing language still routes to ",[194,1201,1203],{"href":1202},"collaborative-ai-for-customer-support","collaborative AI for customer support"," or the legal review room with a signer class. ",[194,1206,929],{"href":927,"rel":1207},[198]," is the reminder that the message can be the write.",[265,1210,1212],{"id":1211},"how-to-start-with-one-watch","How to start with one watch",[190,1214,1215,1216,1219,1220,1223],{},"Pick ",[205,1217,1218],{},"file lands"," for one intake folder you already have — or ",[205,1221,1222],{},"policy change"," if version chaos is the pain.",[190,1225,641],{},[278,1227,1228,1231,1238,1241],{},[225,1229,1230],{},"One folder or one playbook repo path.",[225,1232,1233,1234,1237],{},"Quote extraction plus diff against a ",[205,1235,1236],{},"pinned"," version — no approval language.",[225,1239,1240],{},"Automatic open of a collaborative matter with sources attached.",[225,1242,1243],{},"Zero sends from the standing order.",[190,1245,1246],{},"Measure: time from upload to lawyer on the matter; count of “legal OK” messages in side chat. If side chat wins, you built notification, not routing.",[190,1248,1249,670,1251,1255,1256,1258,1259,1261,1262,1264],{},[194,1250,669],{"href":668},[194,1252,1254],{"href":1253},"loops-for-revenue-operations","loops for revenue operations"," cover packs and pipeline triggers. If you are still choosing the discipline, start with ",[194,1257,244],{"href":243}," and score a vendor with ",[194,1260,684],{"href":372}," before you let a watch open matters on its own. ",[194,1263,304],{"href":303}," is the rule that keeps the watch from drafting a customer email at 3am.",[190,1266,1267],{},"Watch faithfully. Escalate honestly. Leave the signature to the room where a lawyer can refuse.",[265,1269,695],{"id":694},[190,1271,698,1272,1274,1275,1277],{},[194,1273,701],{"href":32}," can host the watch and the review room: file hash, quoted clauses, pinned playbook, run page, and a collaborative matter the named lawyer can refuse. ",[194,1276,39],{"href":40}," is the send gate — not a prompt that says “ask legal.”",[190,1279,1280,711,1282,1284],{},[194,1281,710],{"href":248},[194,1283,684],{"href":372}," before you let a watch look like review.",[716,1286,718],{},{"title":171,"searchDepth":172,"depth":172,"links":1288},[1289,1290,1291,1292,1293,1294,1295],{"id":845,"depth":172,"text":846},{"id":901,"depth":172,"text":902},{"id":377,"depth":172,"text":378},{"id":1025,"depth":172,"text":1026},{"id":585,"depth":172,"text":586},{"id":1211,"depth":172,"text":1212},{"id":694,"depth":172,"text":695},"A standing-order loop for legal watches clause sources, policy changes, and incoming files — then escalates to a person. It is not the collaborative clause-review room, and it must not guess.",{"eyebrow":731,"title":1298},"Watchers vs the review room",[1300,1303,1306,1308],{"question":1301,"answer":1302},"Is a standing-order loop the same as shared legal review?","No. Review is collaborative AI — quoted clause, playbook version, named lawyer who can refuse. A standing-order loop watches for change or arrival and routes a matter; it does not approve language. It is the doorbell, not the judge. If you collapse the two, you get a watch that writes legal OK into chat, or a review room that never sees the file because nobody routed it. Detect and route fast. Refuse and sign in the room.",{"question":1304,"answer":1305},"Can the loop rewrite the clause if the policy changed?","No. Escalate to a person with the quote, the new policy version, and the diff. Drafting without a named rejector is how obsolete PDFs win because they ranked well. Do not let the loop guess which playbook applies when three PDFs share a title. Pin a version on the job and let the lawyer pick. Retrieval that prefers an obsolete doc is a harness failure, not a legal skill issue. The standing order quotes and flags. It does not bind the company.",{"question":738,"answer":1307},"A standing-order loop is a watch that admits a run when a file lands or a policy changes. An eval loop is a harness sensor — for example, did the sent message match the signed payload — not a watch on incoming contracts. An agentic workflow is the third noun: review this contract with no quote, version, or rejector. Score the watch on whether you can replay why a matter opened or skipped. Score the send on whether the message matched the signed text.",{"question":1309,"answer":1310},"Can the loop send a customer email if the flags look clean?","No. Disable send on any draft until a named lawyer joins the matter. Clean flags are questions, not approvals. Air Canada was held to chatbot-invented fare terms with no CRM write. A watch would not have saved that alone; a send gate on customer-facing claims would. The standing order may open the matter with quotes attached. The collaborative room still refuses or signs. Zero sends from the loop path.","/blog/loops-for-legal-and-compliance",{"title":780,"description":1296},"blog/loops-for-legal-and-compliance",[748,1315,1316,752,1317],"legal","compliance","policy","HuWs_EuMXxdW-9WB8YQhVQTlC0KN4Zl-NUriFdPYzCk",{"enabled":165,"message":1320,"linkLabel":79,"linkHref":80,"id":1321,"title":1322,"archived":165,"authors":166,"badge":166,"body":1323,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1327,"relatedHeading":166,"seo":1328,"series":166,"sitemap":165,"status":166,"stem":1329,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1330},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":168,"value":1324,"toc":1325},[],{"title":171,"searchDepth":172,"depth":172,"links":1326},[],"/shared/hiring",{"title":1322,"description":171},"shared/hiring","1zs3boivKda1e-b-hAyuNcmZSKjZUAXmecnwHVgcHzk",{"fold":1332,"id":1336,"title":1337,"archived":165,"authors":166,"badge":166,"body":1338,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":1342,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1346,"relatedHeading":166,"seo":1347,"series":166,"sitemap":165,"status":166,"stem":1348,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1349},{"headline":1333,"description":1334,"primaryLabel":8,"primaryTo":1335,"secondaryLabel":772,"secondaryTo":12},"Run frontier AI your business actually owns.","Governed agent swarms, 2,000+ integrations, and a knowledge graph that stays inside your walls. Start on Free.","/signup?plan=free","content/shared/cta.md","Site CTAs",{"type":168,"value":1339,"toc":1340},[],{"title":171,"searchDepth":172,"depth":172,"links":1341},[],{"headline":1343,"description":1344,"primaryLabel":8,"primaryTo":1335,"secondaryLabel":1345,"secondaryTo":85},"See what governed AI looks like on your stack.","Connect your tools, run a workstream, and keep every decision on your ledger. Start on Free.","Talk to our team","/shared/cta",{"title":1337,"description":171},"shared/cta","PS2VPJsszmUpMBZT6nEp8cWXCdeiN6zDRl-p8d0uY2k",1789797894523]