[{"data":1,"prerenderedAt":1202},["ShallowReactive",2],{"article-\u002Fen\u002Fknowledge\u002Flead-handoffs":3,"knowledge-reader-en":216},{"id":4,"title":5,"body":6,"description":198,"extension":199,"eyebrow":200,"featured":201,"format":202,"locale":203,"meta":204,"navigation":201,"path":205,"readingTime":206,"seo":207,"stageIds":208,"stem":212,"takeaway":213,"updated":214,"__hash__":215},"knowledge\u002Fen\u002Fknowledge\u002Flead-handoffs.md","A qualified lead can still arrive useless",{"type":7,"value":8,"toc":190},"minimark",[9,13,16,21,24,30,108,112,115,131,134,138,141,144,148,151,169,172,182],[10,11,12],"p",{},"A lead can be qualified in the CRM and still be useless to sales.",[10,14,15],{},"The status is set. Name, company and email are present. Nobody recorded why the person is acting now, which problem they want to solve or what has already been agreed.",[17,18,20],"h2",{"id":19},"the-handoff-rule-in-one-sentence","The handoff rule in one sentence",[10,22,23],{},"A useful rule names five things:",[25,26,27],"blockquote",{},[10,28,29],{},"When trigger X occurs, role A hands the case with context Y to role B. Role B accepts within time Z or returns it with a reason.",[31,32,33,49],"table",{},[34,35,36],"thead",{},[37,38,39,43,46],"tr",{},[40,41,42],"th",{},"Element",[40,44,45],{},"Weak",[40,47,48],{},"Usable",[50,51,52,64,75,86,97],"tbody",{},[37,53,54,58,61],{},[55,56,57],"td",{},"Trigger",[55,59,60],{},"lead looks good",[55,62,63],{},"three criteria met",[37,65,66,69,72],{},[55,67,68],{},"Context",[55,70,71],{},"contact link",[55,73,74],{},"problem, reason, fit, next step",[37,76,77,80,83],{},[55,78,79],{},"Receiver",[55,81,82],{},"sales",[55,84,85],{},"accountable role plus backup",[37,87,88,91,94],{},[55,89,90],{},"Time",[55,92,93],{},"soon",[55,95,96],{},"same working day",[37,98,99,102,105],{},[55,100,101],{},"Return",[55,103,104],{},"private message",[55,106,107],{},"reason code in the CRM",[17,109,111],{"id":110},"four-required-fields","Four required fields",[10,113,114],{},"Many B2B handoffs work with four fields:",[116,117,118,122,125,128],"ol",{},[119,120,121],"li",{},"Problem: What does the buyer want to change?",[119,123,124],{},"Reason: Why now?",[119,126,127],{},"Fit: Which criteria are met or open?",[119,129,130],{},"Next step: What was agreed with whom and for when?",[10,132,133],{},"The sales role confirms that it can work with the case. A completed form does not prove acceptance.",[17,135,137],{"id":136},"a-workflow-with-the-wrong-trigger","A workflow with the wrong trigger",[10,139,140],{},"A download creates a deal and posts a Slack message. The workflow runs as configured. It also creates work: Every download becomes a deal, no owner is assigned and the note contains only the whitepaper title.",[10,142,143],{},"The fix starts with the rule. A deal is created only after the criteria are met. Every other contact goes to a review or nurture path with a reason.",[17,145,147],{"id":146},"measure-the-change-in-ownership","Measure the change in ownership",[10,149,150],{},"Five signals show whether the handoff works:",[152,153,154,157,160,163,166],"ul",{},[119,155,156],{},"share of accepted cases",[119,158,159],{},"time to acceptance",[119,161,162],{},"common return reasons",[119,164,165],{},"missing required information",[119,167,168],{},"exceptions without an owner",[10,170,171],{},"One conversion rate mixes source, fit, speed and sales work. Measure the point where ownership changes first.",[10,173,174,175],{},"Article 5 of the GDPR requires data minimisation. Collect only information with a defined purpose. Legal basis and retention need review for the specific process. This article is not legal advice. ",[176,177,181],"a",{"href":178,"rel":179},"https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg\u002F2016\u002F679\u002Foj",[180],"nofollow","GDPR, Article 5",[10,183,184,185,189],{},"The ",[176,186,188],{"href":187},"\u002Fen\u002Fsystem-check","Growth System Stress Test"," checks acceptance time, documentation and ownership.",{"title":191,"searchDepth":192,"depth":192,"links":193},"",2,[194,195,196,197],{"id":19,"depth":192,"text":20},{"id":110,"depth":192,"text":111},{"id":136,"depth":192,"text":137},{"id":146,"depth":192,"text":147},"Marketing and sales hand over a lead with the problem, reason, fit, next step and confirmed acceptance.","md","Lead handoffs",true,"guide","en",{},"\u002Fen\u002Fknowledge\u002Flead-handoffs","6 min",{"title":5,"description":198},[209,210,211],"qualification","handover","delivery","en\u002Fknowledge\u002Flead-handoffs","A lead handoff needs a trigger, context, receiver, acceptance time and recorded return reason.","2026-08-23","R4cWyrWVy2R7mX0ccrJAJCEN2X6Qu_axQi2W7e0gIjs",[217,418,619,767,894,1072],{"id":218,"title":219,"body":220,"description":405,"extension":199,"eyebrow":406,"featured":201,"format":407,"locale":203,"meta":408,"navigation":201,"path":409,"readingTime":206,"seo":410,"stageIds":411,"stem":415,"takeaway":416,"updated":214,"__hash__":417},"knowledge\u002Fen\u002Fknowledge\u002Fb2b-growth-system.md","A B2B growth system needs clean handoffs",{"type":7,"value":221,"toc":399},[222,225,228,232,315,318,322,325,339,342,346,349,352,355,369,373,376,379,387,392],[10,223,224],{},"A funnel can look healthy while every team rebuilds the same context.",[10,226,227],{},"This happens when marketing, sales and delivery maintain their own numbers and tools. The lead moves forward. The problem, promises and ownership stay behind.",[17,229,231],{"id":230},"the-six-stages","The six stages",[31,233,234,247],{},[34,235,236],{},[37,237,238,241,244],{},[40,239,240],{},"Stage",[40,242,243],{},"Working question",[40,245,246],{},"Output",[50,248,249,260,271,282,293,304],{},[37,250,251,254,257],{},[55,252,253],{},"Positioning",[55,255,256],{},"Whose problem do we solve?",[55,258,259],{},"inclusion and exclusion criteria",[37,261,262,265,268],{},[55,263,264],{},"Demand",[55,266,267],{},"How does a suitable buyer enter?",[55,269,270],{},"traceable entry point",[37,272,273,276,279],{},[55,274,275],{},"Qualification",[55,277,278],{},"When is the next step worthwhile?",[55,280,281],{},"fixed criteria",[37,283,284,287,290],{},[55,285,286],{},"Handoff",[55,288,289],{},"What must the next role receive?",[55,291,292],{},"context and acceptance",[37,294,295,298,301],{},[55,296,297],{},"Delivery",[55,299,300],{},"Can we fulfil the promise?",[55,302,303],{},"scope, capacity and start",[37,305,306,309,312],{},[55,307,308],{},"Measurement",[55,310,311],{},"Which number changes a decision?",[55,313,314],{},"source, owner and cadence",[10,316,317],{},"Measurement feeds positioning. Recurring returns change the qualification rule. Missing capacity changes the offer. A better source changes the channel.",[17,319,321],{"id":320},"what-every-handoff-needs","What every handoff needs",[10,323,324],{},"Four details are enough to begin:",[116,326,327,330,333,336],{},[119,328,329],{},"What triggers the handoff?",[119,331,332],{},"Which information must travel with it?",[119,334,335],{},"Which role accepts it?",[119,337,338],{},"How is acceptance or return recorded?",[10,340,341],{},"When one detail is missing, shadow work begins. Someone asks in chat, copies data or keeps a private list. More leads create more of this work.",[17,343,345],{"id":344},"example-80-webinar-contacts","Example: 80 webinar contacts",[10,347,348],{},"A webinar generates 80 contacts. Marketing marks 15 as interesting. Sales receives a CSV without the problem, reason to act or next step. Seven contacts get a call. Three receive a proposal.",[10,350,351],{},"After signature, delivery learns that required data access takes six weeks.",[10,353,354],{},"The visible success is 80 contacts. The operating failure sits later in the flow. Four changes would do more than another batch of registrations:",[152,356,357,360,363,366],{},[119,358,359],{},"problem, reason, fit and next step as required fields",[119,361,362],{},"acceptance by the responsible sales role",[119,364,365],{},"capacity and data check before the proposal",[119,367,368],{},"completion and return reasons fed into reporting",[17,370,372],{"id":371},"test-your-own-flow","Test your own flow",[10,374,375],{},"Take one real case from the last 30 days. Put emails, CRM fields, calendar events and handoff documents side by side. Mark every question and every search for an owner.",[10,377,378],{},"Choose one point. Define the trigger, required information, receiver, acceptance time and return. Automate after this test.",[10,380,381,386],{},[176,382,385],{"href":383,"rel":384},"https:\u002F\u002Fwww.iso.org\u002Fiso-9001-quality-management.html",[180],"ISO also describes management systems as connected processes"," that are planned, operated and checked. The implementation shown here is the MMM method for commercial operations. It is not an ISO certification.",[10,388,184,389,391],{},[176,390,188],{"href":187}," checks the same six stages through nine questions.",[10,393,184,394,398],{},[176,395,397],{"href":396},"\u002Fen\u002Fsystem-check\u002Flinkedin-draft","LinkedIn Post Drafter"," turns a thesis about positioning or handoffs into a first draft without invented facts.",{"title":191,"searchDepth":192,"depth":192,"links":400},[401,402,403,404],{"id":230,"depth":192,"text":231},{"id":320,"depth":192,"text":321},{"id":344,"depth":192,"text":345},{"id":371,"depth":192,"text":372},"Six stages show where leads, context and ownership get lost between positioning, CRM, delivery and reporting.","B2B growth system","blueprint",{},"\u002Fen\u002Fknowledge\u002Fb2b-growth-system",{"title":219,"description":405},[412,413,209,210,211,414],"positioning","demand","measurement","en\u002Fknowledge\u002Fb2b-growth-system","Every stage needs a trigger, the required information, an accountable role and confirmed acceptance.","n392jaQdIZoklSeNohqJNufZMiCAj828LRODf8D-rdg",{"id":419,"title":420,"body":421,"description":609,"extension":199,"eyebrow":610,"featured":611,"format":202,"locale":203,"meta":612,"navigation":201,"path":613,"readingTime":206,"seo":614,"stageIds":615,"stem":616,"takeaway":617,"updated":214,"__hash__":618},"knowledge\u002Fen\u002Fknowledge\u002Fcrm-automation-sme.md","CRM automation makes a bad process fail faster",{"type":7,"value":422,"toc":598},[423,426,429,433,516,519,523,528,531,535,538,542,545,549,552,555,563,567,590,593],[10,424,425],{},"CRM automation makes a bad process fail faster and harder to see.",[10,427,428],{},"An email goes out. A deal is created. A task appears. When the underlying decision is unclear, the system only distributes the mistake more consistently.",[17,430,432],{"id":431},"six-details-per-workflow","Six details per workflow",[31,434,435,448],{},[34,436,437],{},[37,438,439,442,445],{},[40,440,441],{},"Part",[40,443,444],{},"Question",[40,446,447],{},"Example",[50,449,450,461,472,483,494,505],{},[37,451,452,455,458],{},[55,453,454],{},"Event",[55,456,457],{},"What happened?",[55,459,460],{},"demo request received",[37,462,463,466,469],{},[55,464,465],{},"Condition",[55,467,468],{},"What must be true?",[55,470,471],{},"company email, target market, problem",[37,473,474,477,480],{},[55,475,476],{},"Action",[55,478,479],{},"What changes in the CRM?",[55,481,482],{},"create contact, deal and task",[37,484,485,488,491],{},[55,486,487],{},"Owner",[55,489,490],{},"Who accepts?",[55,492,493],{},"sales role by region",[37,495,496,499,502],{},[55,497,498],{},"Exception",[55,500,501],{},"Where does an error go?",[55,503,504],{},"review queue with reason code",[37,506,507,510,513],{},[55,508,509],{},"Signal",[55,511,512],{},"What is measured?",[55,514,515],{},"acceptance time and return reason",[10,517,518],{},"These details belong in the process definition. The tool implements them afterwards.",[17,520,522],{"id":521},"three-bad-starts","Three bad starts",[524,525,527],"h3",{"id":526},"fields-before-criteria","Fields before criteria",[10,529,530],{},"The team builds pipelines, scores and sequences. It ends up with more fields and no rule for when a case should reach sales.",[524,532,534],{"id":533},"only-the-happy-path","Only the happy path",[10,536,537],{},"The workflow understands complete records. Duplicates, missing domains, existing clients and wrong regions end up in Slack or private lists.",[524,539,541],{"id":540},"no-observation","No observation",[10,543,544],{},"Emails and tasks are triggered. Errors, runtime and stop reasons are not logged. The team learns about failures from clients or sales.",[17,546,548],{"id":547},"start-with-20-cases","Start with 20 cases",[10,550,551],{},"Take 20 real cases. Run the flow manually and record every deviation. Then set required fields, owners and return reasons.",[10,553,554],{},"Build the first version with manual approval. Once the exceptions are known, the CRM can take over the repeated steps.",[10,556,184,557,562],{},[176,558,561],{"href":559,"rel":560},"https:\u002F\u002Fwww.nist.gov\u002Fitl\u002Fai-risk-management-framework",[180],"NIST AI Risk Management Framework"," treats governance, measurement and monitoring as ongoing work. Not every CRM automation uses AI. The operating logic still helps in both cases.",[17,564,566],{"id":565},"what-to-document","What to document",[152,568,569,572,575,578,581,584,587],{},[119,570,571],{},"purpose and boundary of the workflow",[119,573,574],{},"triggering and receiving role",[119,576,577],{},"fields and data sources",[119,579,580],{},"known exceptions",[119,582,583],{},"error and escalation path",[119,585,586],{},"changes",[119,588,589],{},"shutdown and fallback",[10,591,592],{},"Another team member can then inspect, change or stop the workflow.",[10,594,184,595,597],{},[176,596,188],{"href":187}," simulates missing data, unclear ownership and founder absence.",{"title":191,"searchDepth":192,"depth":192,"links":599},[600,601,607,608],{"id":431,"depth":192,"text":432},{"id":521,"depth":192,"text":522,"children":602},[603,605,606],{"id":526,"depth":604,"text":527},3,{"id":533,"depth":604,"text":534},{"id":540,"depth":604,"text":541},{"id":547,"depth":192,"text":548},{"id":565,"depth":192,"text":566},"Define the event, condition, action, owner, exception and signal before the CRM acts on its own.","CRM automation for SMEs",false,{},"\u002Fen\u002Fknowledge\u002Fcrm-automation-sme",{"title":420,"description":609},[210,211,414],"en\u002Fknowledge\u002Fcrm-automation-sme","Run the workflow with manual approval first. Automate after you know the exceptions and owners.","P2wLTFOQ_Is6_FhxVnR6fKBNdOTIsa-9shfFdreaYtY",{"id":620,"title":621,"body":622,"description":757,"extension":199,"eyebrow":758,"featured":611,"format":202,"locale":203,"meta":759,"navigation":201,"path":760,"readingTime":761,"seo":762,"stageIds":763,"stem":764,"takeaway":765,"updated":214,"__hash__":766},"knowledge\u002Fen\u002Fknowledge\u002Fcustomer-to-delivery-handoff.md","Signed work can still start badly",{"type":7,"value":623,"toc":750},[624,627,630,634,637,654,657,661,721,725,728,732,735,739,742,745],[10,625,626],{},"Signed work can still start badly.",[10,628,629],{},"Sales knows the conversation, objections and promises. Delivery knows the effort, capacity and dependencies. Without joint acceptance, the project begins with questions.",[17,631,633],{"id":632},"what-delivery-must-confirm","What delivery must confirm",[10,635,636],{},"Delivery needs five details before work starts:",[116,638,639,642,645,648,651],{},[119,640,641],{},"promised outcome and scope",[119,643,644],{},"acceptance criteria and decision maker",[119,646,647],{},"capacity and target date",[119,649,650],{},"technical and organisational dependencies",[119,652,653],{},"risks and first review date",[10,655,656],{},"The responsible delivery role accepts the case or records a deviation. A signature alone does not replace this acceptance.",[17,658,660],{"id":659},"the-one-page-handoff","The one-page handoff",[31,662,663,672],{},[34,664,665],{},[37,666,667,670],{},[40,668,669],{},"Field",[40,671,444],{},[50,673,674,682,690,698,706,714],{},[37,675,676,679],{},[55,677,678],{},"Outcome",[55,680,681],{},"What should be demonstrably different?",[37,683,684,687],{},[55,685,686],{},"Scope",[55,688,689],{},"What is included?",[37,691,692,695],{},[55,693,694],{},"Exclusion",[55,696,697],{},"What is outside scope?",[37,699,700,703],{},[55,701,702],{},"Acceptance",[55,704,705],{},"Who confirms against which criteria?",[37,707,708,711],{},[55,709,710],{},"Inputs",[55,712,713],{},"Which access, data and people does the client provide?",[37,715,716,718],{},[55,717,498],{},[55,719,720],{},"What happens when an input is missing?",[17,722,724],{"id":723},"put-capacity-before-the-date","Put capacity before the date",[10,726,727],{},"A delivery date depends on capacity, dependencies and client response time. Delivery confirms the start and date together. If access is missing, the impact is recorded before work begins.",[17,729,731],{"id":730},"what-returns-after-completion","What returns after completion",[10,733,734],{},"After completion, scope changes, missing inputs, recurring objections and recorded effort feed back into the offer, qualification and planning.",[17,736,738],{"id":737},"the-two-week-test","The two-week test",[10,740,741],{},"Assume the original contact is unavailable for two weeks. Can the team reconstruct promises, files, decisions and next steps without private messages?",[10,743,744],{},"If not, the handoff is missing documentation.",[10,746,184,747,749],{},[176,748,188],{"href":187}," runs founder absence and missing data through the flow.",{"title":191,"searchDepth":192,"depth":192,"links":751},[752,753,754,755,756],{"id":632,"depth":192,"text":633},{"id":659,"depth":192,"text":660},{"id":723,"depth":192,"text":724},{"id":730,"depth":192,"text":731},{"id":737,"depth":192,"text":738},"Sales and delivery confirm scope, acceptance, capacity, access and risks before project work begins.","Handoff Atlas \u002F Delivery",{},"\u002Fen\u002Fknowledge\u002Fcustomer-to-delivery-handoff","5 min",{"title":621,"description":757},[210,211,414],"en\u002Fknowledge\u002Fcustomer-to-delivery-handoff","Delivery confirms the promise, scope, acceptance, capacity, access and risks before project start.","oaGar4rxv-j7OpquF-RCWYSvX1egwRYOMIsYAZSxmxs",{"id":4,"title":5,"body":768,"description":198,"extension":199,"eyebrow":200,"featured":201,"format":202,"locale":203,"meta":891,"navigation":201,"path":205,"readingTime":206,"seo":892,"stageIds":893,"stem":212,"takeaway":213,"updated":214,"__hash__":215},{"type":7,"value":769,"toc":885},[770,772,774,776,778,782,836,838,840,850,852,854,856,858,860,862,874,876,881],[10,771,12],{},[10,773,15],{},[17,775,20],{"id":19},[10,777,23],{},[25,779,780],{},[10,781,29],{},[31,783,784,794],{},[34,785,786],{},[37,787,788,790,792],{},[40,789,42],{},[40,791,45],{},[40,793,48],{},[50,795,796,804,812,820,828],{},[37,797,798,800,802],{},[55,799,57],{},[55,801,60],{},[55,803,63],{},[37,805,806,808,810],{},[55,807,68],{},[55,809,71],{},[55,811,74],{},[37,813,814,816,818],{},[55,815,79],{},[55,817,82],{},[55,819,85],{},[37,821,822,824,826],{},[55,823,90],{},[55,825,93],{},[55,827,96],{},[37,829,830,832,834],{},[55,831,101],{},[55,833,104],{},[55,835,107],{},[17,837,111],{"id":110},[10,839,114],{},[116,841,842,844,846,848],{},[119,843,121],{},[119,845,124],{},[119,847,127],{},[119,849,130],{},[10,851,133],{},[17,853,137],{"id":136},[10,855,140],{},[10,857,143],{},[17,859,147],{"id":146},[10,861,150],{},[152,863,864,866,868,870,872],{},[119,865,156],{},[119,867,159],{},[119,869,162],{},[119,871,165],{},[119,873,168],{},[10,875,171],{},[10,877,174,878],{},[176,879,181],{"href":178,"rel":880},[180],[10,882,184,883,189],{},[176,884,188],{"href":187},{"title":191,"searchDepth":192,"depth":192,"links":886},[887,888,889,890],{"id":19,"depth":192,"text":20},{"id":110,"depth":192,"text":111},{"id":136,"depth":192,"text":137},{"id":146,"depth":192,"text":147},{},{"title":5,"description":198},[209,210,211],{"id":895,"title":896,"body":897,"description":1062,"extension":199,"eyebrow":1063,"featured":611,"format":1064,"locale":203,"meta":1065,"navigation":201,"path":1066,"readingTime":206,"seo":1067,"stageIds":1068,"stem":1069,"takeaway":1070,"updated":214,"__hash__":1071},"knowledge\u002Fen\u002Fknowledge\u002Fmeasuring-growth.md","A correct dashboard can be useless in Monday's meeting",{"type":7,"value":898,"toc":1051},[899,902,905,909,961,964,968,972,975,978,981,984,987,991,994,998,1001,1004,1008,1011,1028,1036,1039,1044],[10,900,901],{},"A correct dashboard can be useless in Monday's meeting.",[10,903,904],{},"The numbers are current. Nobody knows whether to move budget, change a qualification rule or reduce demand.",[17,906,908],{"id":907},"start-with-the-decision","Start with the decision",[31,910,911,919],{},[34,912,913],{},[37,914,915,917],{},[40,916,444],{},[40,918,447],{},[50,920,921,929,937,945,953],{},[37,922,923,926],{},[55,924,925],{},"Which decision?",[55,927,928],{},"hold, reduce or move channel budget",[37,930,931,934],{},[55,932,933],{},"Who decides?",[55,935,936],{},"growth lead",[37,938,939,942],{},[55,940,941],{},"When?",[55,943,944],{},"every second Tuesday",[37,946,947,950],{},[55,948,949],{},"Which source?",[55,951,952],{},"CRM status plus confirmed costs",[37,954,955,958],{},[55,956,957],{},"Which boundary?",[55,959,960],{},"no decision below 90 percent data coverage",[10,962,963],{},"Without one of these details, the metric is information without an owner.",[17,965,967],{"id":966},"separate-four-levels","Separate four levels",[524,969,971],{"id":970},"activity","Activity",[10,973,974],{},"Posts, clicks, calls and messages show work and reach.",[524,976,286],{"id":977},"handoff",[10,979,980],{},"Acceptance time, return reason, completeness and owner show whether the case moves between roles.",[524,982,678],{"id":983},"outcome",[10,985,986],{},"Qualified conversations, contracts, cycle time and usage sit closer to the business. Their definitions must stay stable across reviews.",[524,988,990],{"id":989},"data-quality","Data quality",[10,992,993],{},"Coverage, freshness, duplicates and conflicting definitions determine whether the other numbers can be used.",[17,995,997],{"id":996},"two-conversion-rates","Two conversion rates",[10,999,1000],{},"Marketing reports 8 percent from landing page visit to form. Sales reports 24 percent from conversation to contract. The meeting compares both as conversion rate.",[10,1002,1003],{},"Every rate needs a numerator, denominator, period, cohort and purpose. That shows whether the problem sits at entry, qualification or after the conversation.",[17,1005,1007],{"id":1006},"a-small-decision-board","A small decision board",[10,1009,1010],{},"A small team can start with five rows:",[116,1012,1013,1016,1019,1022,1025],{},[119,1014,1015],{},"demand from a defined source",[119,1017,1018],{},"one handoff metric",[119,1020,1021],{},"one outcome",[119,1023,1024],{},"one data quality warning",[119,1026,1027],{},"last and next decision",[10,1029,1030,1031],{},"Google describes events as measurable user interactions. The company still has to define the owner and business decision. ",[176,1032,1035],{"href":1033,"rel":1034},"https:\u002F\u002Fsupport.google.com\u002Fanalytics\u002Fanswer\u002F10089681",[180],"Google Analytics documentation",[10,1037,1038],{},"Four questions are enough for the review: Which assumption was wrong? Which rule changes? Who changes it by when? Which signal do we check afterwards?",[10,1040,184,1041,1043],{},[176,1042,188],{"href":187}," shows how missing measurement data affects earlier decisions.",[10,1045,184,1046,1050],{},[176,1047,1049],{"href":1048},"\u002Fen\u002Fsystem-check\u002Fdashboard","Client Command Demo"," shows how source, handoff, outcome and data quality can come together in a client dashboard.",{"title":191,"searchDepth":192,"depth":192,"links":1052},[1053,1054,1060,1061],{"id":907,"depth":192,"text":908},{"id":966,"depth":192,"text":967,"children":1055},[1056,1057,1058,1059],{"id":970,"depth":604,"text":971},{"id":977,"depth":604,"text":286},{"id":983,"depth":604,"text":678},{"id":989,"depth":604,"text":990},{"id":996,"depth":192,"text":997},{"id":1006,"depth":192,"text":1007},"Connect every B2B metric to a source, owner, cadence, threshold and defined decision.","Measuring growth","system-note",{},"\u002Fen\u002Fknowledge\u002Fmeasuring-growth",{"title":896,"description":1062},[414,412],"en\u002Fknowledge\u002Fmeasuring-growth","Every core metric needs a source, owner, cadence, threshold and the decision it triggers.","axS4f5WmcGN8Vcl80HZLuO_VpFu5os9UBlGxVmvp-QM",{"id":1073,"title":1074,"body":1075,"description":1193,"extension":199,"eyebrow":1194,"featured":201,"format":1064,"locale":203,"meta":1195,"navigation":201,"path":1196,"readingTime":761,"seo":1197,"stageIds":1198,"stem":1199,"takeaway":1200,"updated":214,"__hash__":1201},"knowledge\u002Fen\u002Fknowledge\u002Fqualifying-demand.md","A full pipeline does not tell sales who to call first",{"type":7,"value":1076,"toc":1187},[1077,1080,1083,1087,1145,1148,1152,1155,1158,1162,1165,1169,1172,1175,1180],[10,1078,1079],{},"A full pipeline does not tell sales who to call first.",[10,1081,1082],{},"Company name, industry and budget help with sorting. Sales can choose the next step once the problem, reason to act and movement are known.",[17,1084,1086],{"id":1085},"four-signals","Four signals",[31,1088,1089,1100],{},[34,1090,1091],{},[37,1092,1093,1095,1097],{},[40,1094,509],{},[40,1096,243],{},[40,1098,1099],{},"Evidence",[50,1101,1102,1112,1123,1134],{},[37,1103,1104,1107,1110],{},[55,1105,1106],{},"Fit",[55,1108,1109],{},"Does the organisation and use case belong?",[55,1111,259],{},[37,1113,1114,1117,1120],{},[55,1115,1116],{},"Problem",[55,1118,1119],{},"What needs to change?",[55,1121,1122],{},"buyer's own statement",[37,1124,1125,1128,1131],{},[55,1126,1127],{},"Reason",[55,1129,1130],{},"Why now?",[55,1132,1133],{},"event, risk or date",[37,1135,1136,1139,1142],{},[55,1137,1138],{},"Movement",[55,1140,1141],{},"What was agreed?",[55,1143,1144],{},"date, participants and decision",[10,1146,1147],{},"A score can summarise this information. The sales role still needs to see why the value was assigned.",[17,1149,1151],{"id":1150},"the-acceptance-rule","The acceptance rule",[10,1153,1154],{},"Set the point where marketing or inbound hands the case to sales. Define required fields, receiving role, acceptance time and return.",[10,1156,1157],{},"Example: When fit, problem and reason are recorded, the responsible sales role receives the case with its source and next step. It accepts on the same working day or returns the case with a reason code.",[17,1159,1161],{"id":1160},"returns-improve-the-entry-point","Returns improve the entry point",[10,1163,1164],{},"Recurring reasons show where the flow starts badly. No reason to act points to the qualification rule. A wrong role points to the form or routing. An unclear problem points to the message or conversation guide.",[17,1166,1168],{"id":1167},"check-ten-cases","Check ten cases",[10,1170,1171],{},"Take the last ten handoffs. Can someone outside the case see why each lead moved, who accepted it and what should happen next?",[10,1173,1174],{},"If those details are missing, the team needs a handoff rule.",[10,1176,184,1177,1179],{},[176,1178,188],{"href":187}," shows whether demand, qualification or handoff gives way first.",[10,1181,184,1182,1186],{},[176,1183,1185],{"href":1184},"\u002Fen\u002Fsystem-check\u002Fpotential","Growth Potential Builder"," scores the current demand and handoff practice from four real answers and returns a 30-day focus.",{"title":191,"searchDepth":192,"depth":192,"links":1188},[1189,1190,1191,1192],{"id":1085,"depth":192,"text":1086},{"id":1150,"depth":192,"text":1151},{"id":1160,"depth":192,"text":1161},{"id":1167,"depth":192,"text":1168},"Qualify technical B2B demand with four signals: fit, problem, reason to act and an agreed next step.","MMM System Note \u002F Qualification",{},"\u002Fen\u002Fknowledge\u002Fqualifying-demand",{"title":1074,"description":1193},[413,209,210],"en\u002Fknowledge\u002Fqualifying-demand","Fit, problem, reason and next step must come from real information. A score should only summarise them.","F6uU8rDCFKIoL9LwBngGkG_Gh1xO8Pl14jYrINeE3XI",1792525064572]