1import{j as e}from"./index-BTAdPjYI.js";import{A as a}from"./Navbar-CtTWVxwW.js";import{d as o,a as i,D as r,b as t,P as n}from"./PageSections-C7wAIqQX.js";import{P as l}from"./PageShell-FlRXku-3.js";const c=s=>e.jsx("video",{src:s,autoPlay:!0,muted:!0,loop:!0,playsInline:!0,preload:"metadata",style:{width:"100%",display:"block"}});function m(){return e.jsxs(l,{children:[e.jsx(o,{title:"How your business actually runs â auto-generated, health-scored, and always current.",lede:"Every company has a capability map; almost no company can show you theirs. Node assembles one from your real systems and keeps it alive as the org changes.",cta:e.jsxs("a",{className:"btn btn-primary btn-lg",href:"https://calendly.com/steve-baker-vs/30-minutes-with-steve",children:["Book a demo ",e.jsx(a,{})]}),image:c("/uploads/capability.mp4")}),e.jsx(i,{title:"Your business has a model. You've just never seen it.",intro:"Node assembles it from your systems, docs, and conversations. Three things make it different from what you've tried before.",items:[{title:"Built, not drawn.",body:"No workshops. No discovery phases. Node reads your tools, documents, and communication to assemble the map. The result is a connected graph of capabilities, workflows, tools, and owners."},{title:"Every node has a health score.",body:"Usage, ownership, redundancy, age, incident history â weighted into a single score per workflow. You'll see what's drifting a quarter before it becomes someone's emergency."},{title:"It doesn't go stale.",body:"Most maps die the week they're finished. This one is rebuilt continuously from live systems. The org changes; the map follows."}]}),e.jsxs(r,{title:"A map you can actually ask things of.",intro:"Slides describe your stack. The map answers questions about it. Three things it does that decks can't.",children:[e.jsx(t,{label:"Compose",title:"Pick a thread. Pull it.",body:"Start with a Salesforce contract and walk up to the business outcome it supports. Or start with âlead-to-cashâ and walk down to the exact step where it breaks. The graph holds in both directions because the relationships are real â captured from how people actually work, not drawn by hand.",items:[{k:"Layers",v:"Capability ⺠Workflow ⺠Step ⺠Tool"},{k:"Traversal",v:"Up or down without losing context"},{k:"Relationships",v:"Many-to-many, explicit dependencies"},{k:"Coverage",v:"94% owner clarity, typical"}]}),e.jsx(t,{reverse:!0,label:"Score",title:"Scored, not vibes.",body:"Every node carries a composite health score â usage, ownership, redundancy, age, and incident history rolled into one number. Trends show where things are heading, not just where they are. The signal a quarterly architecture review used to surface, on tap.",items:[{k:"Inputs",v:"Usage · ownership · redundancy · age · incidents"},{k:"Refresh",v:"Recomputed on every behaviour signal"},{k:"Risk flags",v:"Single-point-of-failure · drifting cycle time · silent owner"},{k:"Comparability",v:"Same rubric across every workflow"}]}),e.jsx(t,{label:"Ask",title:'"What breaks if we cancel Salesforce?"',body:"Ask in plain English. Get a cited answer: which workflows depend on it, who owns each one, what's downstream, and what a sensible exit looks like. The question your architecture review used to spend a workshop on â answered in a sentence, with the map to back it up.",items:[{k:"Workflows affected",v:"23 · 8 critical"},{k:"Capabilities at risk",v:"Lead-to-cash · Customer Success"},{k:"Daily users",v:"412"},{k:"Exit estimate",v:"~11 weeks · high risk"}]})]}),e.jsx(n,{})]})}export{m as component};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.