A distributor who tries to short-circuit the structural-fit question and move directly to the unit-price question has not yet read the rest of this playbook.

Yayınlandı: Eki 09, 2024

Smart Lock Opportunities for Distributors

Smart Lock Opportunities for Distributors — A Seven-Protocol Playbook for Sizing, Qualifying and Closing Distributor Channel Whitespace

Smart lock opportunities for distributors are the protocol-driven outcome of a seven-gate distributor channel scan — territory sizing, vertical prioritisation, product-fit mapping, channel-whitespace audit, pilot-site selection, qualification criteria, and close-loop conversion — applied to a 79-model catalogue across 24 hotel, 37 fingerprint, 18 keypad, 10 outdoor, 9 RFID, 6 face, 6 cabinet, 3 video and 3 glass lines. The opportunity is structural, not market-size-dependent: a distributor either funds the territory-and-vertical surface they intend to serve, or the opportunity was never an opportunity in the first place. This SOP/Playbook names the seven protocols, the IF-THEN decision rules each one carries, the exception paths the distributor must declare up front, the per-model figures the protocols route to documentation, and the per-deal figures the protocols route to /request-a-quote. No distributor reads this article and walks away with a market-size number; every distributor who finishes the playbook walks away with a written opportunity map that names the protocols, the exceptions, the qualification gates, and the structural reasons the territory either carries the program or does not.

The article sits inside the C17 Market/Trends cluster alongside the wholesale, dealer, system-integrator and brand-owner opportunity siblings, and inside the wider C14 Distributor cluster alongside the distributor business-model sibling Smart Lock Distributor Business Model and the distributor product-portfolio sibling Smart Lock Distributor Product Portfolio. The argument across the cluster is the same one this playbook executes: a distributor opportunity is not the headline economics the factory-side sales conversation offers, the distributor opportunity is the structural-fit between the territory, the vertical, the product portfolio, the channel whitespace, the pilot site, the qualification gates and the close loop. The headline economics flow from the structural fit; they do not precede it. A distributor who reads this playbook and runs the seven protocols in order — not in parallel, not on instinct, not on the headline margin — leaves with the structural-fit map the rest of the distributor decisions ride on.

The opportunity is a structural-fit outcome, not a market-size question

The first editorial claim this playbook makes is the one the rest of the protocols rely on: the smart-lock distributor opportunity is a structural-fit outcome, not a market-size question. The market exists; the catalogue exists; the territory exists; the question is not whether the territory carries demand — every territory carries demand for some lock category at some price band through some channel — the question is whether the distributor has the structural surface to capture that demand through the factory's catalogue at a cost the program can fund for the life of the program. The structural-fit question is upstream of every other question the distributor will be asked in the first ninety days: territory scope, vertical priority, product mix, channel positioning, pilot site, qualification gates, close loop. A distributor who tries to short-circuit the structural-fit question and move directly to the unit-price question has not yet read the rest of this playbook.

This framing matters because the distributor conversation almost always starts with the wrong question. The factory-side sales conversation opens with the catalogue, the unit-price tier, and the MOQ ladder. The distributor-side sales conversation opens with the territory, the vertical, and the marketing surface. Neither opening question names the structural-fit outcome the program survives on, and that is the gap this playbook exists to fill. The seven protocols below walk the distributor from the structural-fit question through to the close loop, in the order the structural-fit question has to be answered, and the protocols refuse to allow the distributor to skip a gate the gate's exit criteria do not pass.

The cluster context matters here. The distributor business-model sibling Smart Lock Distributor Business Model names the cost-shape, the working-capital shape and the after-sales shape the distributor is taking over the moment the program signs. The distributor product-portfolio sibling Smart Lock Distributor Product Portfolio names the five-pillar SKU-mix framework the distributor carries inside that business model. This playbook sits one level upstream of those two: the opportunity scan that decides whether the territory-and-vertical surface the distributor intends to fund will, in fact, fund the cost-shape the business model demands and the SKU mix the product portfolio requires. A distributor who passes the opportunity scan and then refuses to fund the surfaces the business model and the product portfolio demand has run a clean opportunity scan and refused to honour it. The first is forgivable; the second is the re-quote conversation with the factory eighteen months later.

Protocol 01 — Territory sizing as a funding question, not a geography question

Protocol 01 reframes territory sizing from a geography question into a funding question. The question is not "how big is the territory in square kilometres" or "how many smart-lock households does the territory contain"; the question is "what is the smallest territory whose structural surface the distributor can fund, operate and defend for the life of the program". The smallest territory carries the least working capital, the least staffing overhead, the least channel conflict, the least brand-positioning cost, and the least after-sales surface. The smallest territory is, almost always, the right territory for a first-program distributor. The largest territory carries the inverse of every one of those attributes and is almost always the wrong territory for a first-program distributor.

The protocol carries three IF-THEN decision rules that have to be passed before the territory exits Protocol 01:

  • IF the distributor can name the territory in terms of vertical channels rather than in terms of postal codes or administrative regions, the territory is funding-shaped. A territory named as "hospitality and build-to-rent in the western coastal urban corridor" is funding-shaped; a territory named as "the western province" is geography-shaped. The protocol exits only when the territory is funding-shaped.
  • IF the distributor can size the stocking capital the territory demands against the working-capital envelope the distributor actually holds, the territory is capital-shaped. A territory whose stocking capital exceeds the working-capital envelope by more than the distributor can finance is over-territory; the protocol exits only when stocking capital is inside the envelope or the envelope is enlarged to cover the territory.
  • IF the distributor can name the after-sales surface the territory commits the distributor to fund — installation sub-network, RMA bin, spare-parts kit, training hours, support staff, escalation path — the territory is service-shaped. A territory that names only the sales surface has under-territoried the after-sales surface; the protocol exits only when the after-sales surface is named in writing.
Protocol 01 entry criterionIF the criterion passesIF the criterion failsConfirm on / exception routed to
Territory named in vertical-channel termsProtocol 01 exits to Protocol 02Re-scope territory to vertical-channel naming before any further sizingDistributor's own market map; cross-check with /become-a-distributor
Stocking capital ≤ working-capital envelopeProtocol 01 exits to Protocol 02Re-scope territory to a smaller vertical band, or arrange working-capital envelope first/request-a-quote for stocking-cap posture per category
After-sales surface named in writingProtocol 01 exits to Protocol 02Add named after-sales surface (install sub-network / RMA / spare-parts / training / support / escalation) before sizingSmart Lock Distributor Installation Support + Smart Lock Distributor Technical Support

The exception path the protocol carries is explicit: IF the distributor cannot pass all three gates inside Protocol 01, the distributor does not have an opportunity yet — the distributor has a territory map. The two are not the same. The opportunity is downstream of the territory map; the territory map is upstream of the opportunity. A distributor who tries to convert the territory map directly into the opportunity skips the structural-fit question the protocols exist to enforce.

Protocol 02 — Vertical prioritisation as a depth question, not a breadth question

Protocol 02 reframes vertical prioritisation from a breadth question — "which verticals does the territory carry" — into a depth question — "which vertical does the distributor carry deeper than the competitor surface the vertical is currently buying from". The vertical the distributor does not carry deeper than the competitor is a vertical the distributor does not have an opportunity in. The vertical the distributor carries deeper than the competitor — deeper on stocking capital, deeper on installer network, deeper on spare-parts posture, deeper on after-sales response time, deeper on channel credibility, deeper on RFQ turn-around, deeper on the per-vertical credential stack the vertical actually buys — is the vertical the distributor has the only available opportunity in.

The catalogue scope supports the depth-first framing. The 79-model catalogue covers 24 hotel-class locks, 37 fingerprint locks, 18 keypad locks, 10 outdoor locks, 9 RFID locks, 6 face-recognition locks, 6 cabinet locks, 3 video-camera locks and 3 glass-door locks. The verticals a distributor can prioritise against that catalogue include hospitality fleets, build-to-rent operators, residential new-build developers, residential retrofit contractors, commercial office facilities, small-business retail, education campuses, healthcare facilities, mixed-use property managers, security installers, e-commerce direct-to-consumer, and trade-counter resellers. The protocol does not ask the distributor to serve all twelve verticals. The protocol asks the distributor to pick the one or two verticals the distributor can carry deeper than the competitor surface, and refuse the rest for the first program.

The IF-THEN decision rule is binary:

  • IF the distributor names one to two verticals and refuses the other ten or eleven, Protocol 02 exits to Protocol 03.
  • IF the distributor names three or more verticals, Protocol 02 rejects and re-runs until the vertical list shrinks to one or two.

The exception path Protocol 02 carries: a distributor with an established channel credibility in three or more verticals may run Protocol 02 with a three-vertical list for the first program, IF the distributor can demonstrate that the channel credibility in the third vertical is at least as deep as the channel credibility in the first two. The exception is documented — the distributor carries written evidence of the channel credibility the third vertical depends on, and the exception is named in the RFQ the distributor submits to /request-a-quote. The default protocol refuses the three-vertical path; the exception allows it conditionally; the protocol refuses the four-or-more-vertical path unconditionally.

Vertical candidateCatalogue coverage the vertical touchesStocking-capital band relative to program envelopeInstaller-network depth requirementAfter-sales surface the vertical commits the distributor to
Hospitality fleet24 hotel locks + adjacent fingerprint/keypadHigh per-door; wide door-thickness band; confirm per-SKU door-thickness on the product pageHotel-grade installer sub-network; PMS-coordination depth if mobile-key laneMultilingual software posture; 24/7 RMA; spare-parts kit per door
Build-to-rent operatorFingerprint + keypad + RFID; tenant churn credential stackMedium per-door; tenant-cycle credential capacity; check the model’s published specificationTenant-onboarding sub-network; PMS-light or app-based onboarding laneCredential-cycling discipline; per-tenant RMA; spare-parts posture
Residential new-buildFingerprint + keypad; door-prep envelope mattersLow per-door; bulk-order cadenceDeveloper-grade installer; door-prep coordination; trade-counter relationshipNew-build warranty-window discipline; spare-parts kit per development
Residential retrofit contractorFingerprint + keypad + RFID; retrofit-friendly door-prepLow per-door; small-batch cadenceRetrofit-grade installer; door-prep tolerance discipline; existing-cylinder handlingRetrofit-cycle warranty discipline; spare-parts posture
Commercial officeKeypad + RFID + face; audit depth requiredMedium per-door; audit-event buffer per SKU; check the model’s published specificationOffice-grade installer; access-control coordination; HR-roster interopAudit-retrieval discipline; per-employee RMA; spare-parts posture
Small-business retailKeypad + RFID; simple credential stackLow per-door; small-volume cadenceTrade-counter or small-volume installerSingle-site RMA; spare-parts kit per site
Education campusKeypad + RFID + face; credential capacity at scaleHigh per-door; per-student credential capacityCampus-grade installer; access-control coordination; off-hours disciplineCredential-cycling at semester cadence; spare-parts posture
Healthcare facilityKeypad + RFID; audit depth + infection-control surfaceMedium per-door; wipe-clean finish postureHealthcare-grade installer; audit retrieval disciplineAudit-grade RMA; spare-parts posture
Mixed-use property managerFingerprint + keypad + RFID; multi-tenant surfaceMedium per-door; multi-tenant credential capacityMulti-tenant installer sub-networkMulti-tenant credential cycling; spare-parts posture
Security installerFingerprint + keypad + RFID + face; deep technical surfaceMedium per-door; technical-spec reading depthInstaller-led sub-network; specification-document fluencyInstaller-grade RMA; spare-parts posture
E-commerce direct-to-consumerFingerprint + keypad; consumer-friendly appLow per-door; consumer-pack cadenceConsumer self-install lane; documentation and video disciplineConsumer RMA; spare-parts posture; remote-troubleshooting surface
Trade-counter resellerFull catalogue breadthVariable; depends on territoryTrade-counter relationship; counter-staff technical depthCounter-grade RMA; spare-parts posture

The table is illustrative not exhaustive, and the per-vertical figures the distributor needs to fund each row are routed to /request-a-quote and the per-program fact sheet the factory returns. The protocol's job is not to size the per-vertical funding band for the distributor; the protocol's job is to force the distributor to commit to one or two verticals the distributor can fund deeper than the competitor surface those verticals are currently buying from.

Protocol 03 — Product-fit mapping against the vertical, with the SLK-9936S yardstick invoked once

Protocol 03 maps the catalogue to the one or two verticals Protocol 02 named, and the mapping is done one product family at a time, one per-vertical-fit-row at a time, and one figure-routing at a time. The protocol is explicit: every per-model figure — door thickness envelope, credential stack, RFID frequency and read distance, audit-event buffer, battery format, mechanical override path, finish options, firmware revision label, app-platform binding (TTLock / Tuya / Doodle / hotel PC software), environmental envelope, mortise form factor — routes to documentation. The protocol refuses to allow the distributor to import a per-model figure from one SKU into the decision for another SKU, and the protocol refuses to allow the distributor to import a per-model figure from the catalogue into the decision for any individual deal.

The one product-page-documented spec block the protocol invokes is the SLK-9936S first-party block — door thickness 36–100 mm · RFID Mifare 1 @ 13.56 MHz · read distance 0–5 cm · read time <0.25 s · 4 × AA · battery operating cycles >15,000 · audit/event records up to 1,000 · 5-pin cylinder · 3-point latch · stainless steel + alloy body · multiple finish options · mechanical emergency access · multilingual management software · standalone or centralized database modes · positioned for 1–5 star hotels — and the protocol invokes it ONCE as the documentation-granularity yardstick that tells the distributor what a complete hotel-class datasheet looks like. Every figure outside the SLK-9936S yardstick — every SLK-9936G, SLK-9905A, SLK-9951TH, SLK-9962S, SLK-G200, SLK-8831 5-in-1, narrow-edge 4-in-1, SLK-3108 password-lock, cylindrical-latch Tuya round-code, 3D-face remote-intercom, outdoor D11/D12/D15/ODS/DQ, face 9L5-R/Q7/Future 1, 516 cat-eye, Q7 intercom, 4G, cabinet 6-model family, RFTC/RF card-and-code 118/118E/228/230/232/238/239/253/305/306/308/309/502/620/621/911/002/019/022/2020/760, and stainless 019/022/309 — is checked against the model’s published specification. The protocol enforces the firewall in writing: SLK-9936S figures do not port across siblings, the SLK-9936S yardstick documents the granularity the distributor should expect from every other SKU's product page, and the per-model decision for every other SKU is a documentation decision, never a copy-from-SLK-9936S decision.

The IF-THEN decision rule Protocol 03 enforces:

  • IF the catalogue SKU the distributor is considering carries a complete datasheet on the product page AND the datasheet figures match the vertical-fit row the vertical requires, Protocol 03 accepts the SKU for the vertical-fit map.
  • IF the catalogue SKU the distributor is considering does not carry a complete datasheet on the product page OR the datasheet figures do not match the vertical-fit row, Protocol 03 rejects the SKU from the vertical-fit map.
  • IF the catalogue SKU the distributor is considering carries a complete datasheet but the distributor wants to import a per-model figure from another SKU (for example, importing the SLK-9936S 13.56 MHz RFID figure into a different hotel-class SKU decision), Protocol 03 refuses the import and re-routes the figure to documentation.
Vertical-fit rowCatalogue SKU class the row touchesPer-model figure the distributor needs
Hospitality guestroomHotel-class RFID mortise (e.g. SLK-9936S class; other hotel locks check the model’s published specification)Door thickness envelope · RFID frequency · read distance · read time · battery format · battery operating cycles · audit-event buffer · cylinder · latch · body material · finish options · mechanical emergency access · software posture · database mode · star-positioning
Hospitality common-areaHotel-class RFID or keypad (multiple SKU classes)Same as guestroom + multi-software-side coordination depth
Build-to-rent tenant doorFingerprint / keypad / RFID residential mortise (multiple SKU classes)Door thickness · credential stack · tenant-cycle credential capacity · audit-event buffer · battery format · app-platform binding (TTLock / Tuya / Doodle)
Residential new-buildFingerprint / keypad (multiple SKU classes)Door thickness · door-prep envelope · credential stack · bulk-order finish posture
Residential retrofitFingerprint / keypad / RFID (multiple SKU classes; retrofit-friendly)Door thickness · retrofit-friendly door-prep · existing-cylinder handling · battery format
Commercial officeKeypad / RFID / face (multiple SKU classes)Door thickness · credential stack · audit-event buffer · HR-roster interop · app-platform binding (TTLock / Tuya / Doodle)
Small-business retailKeypad / RFID (multiple SKU classes)Door thickness · credential stack · simple-app posture · battery format
Education campusKeypad / RFID / face (multiple SKU classes)Door thickness · per-student credential capacity · audit-event buffer · off-hours discipline
Healthcare facilityKeypad / RFID (multiple SKU classes)Door thickness · audit-event buffer · wipe-clean finish posture · battery format
Mixed-use propertyFingerprint / keypad / RFID (multiple SKU classes)Door thickness · multi-tenant credential capacity · credential-cycling discipline · app-platform binding
Security installer channelFingerprint / keypad / RFID / face (multiple SKU classes)Door thickness · credential stack · technical-spec reading depth · mechanical-override posture
E-commerce direct-to-consumerFingerprint / keypad (multiple SKU classes)Door thickness · consumer-friendly app posture · self-install envelope · battery format
Trade-counterFull catalogue breadthPer-SKU figures as listed above for each vertical served

The table is illustrative not exhaustive, the per-vertical SKU classes are documented as examples not as a closed list, and every per-model figure the protocol needs to make a vertical-fit decision is documentation. The protocol refuses to operate on any per-model figure that has not been recorded in the model specification of the SKU under consideration.

Protocol 04 — Channel-whitespace audit as a competitive-structure question

Protocol 04 audits the channel whitespace against the one or two verticals Protocol 02 named, and the audit is a competitive-structure question, not a market-size question. The question is not "how big is the channel"; the question is "where in the channel does the distributor have a competitive-structure advantage the competitor surface does not have". The audit walks three layers — the upstream supplier surface (the factory and competing factories), the distributor's own internal surface, and the downstream channel surface (the installer, the dealer, the trade counter, the e-commerce shelf, the direct sales motion) — and the audit names the layer the distributor's competitive-structure advantage lives on.

The protocol carries three IF-THEN decision rules:

  • IF the distributor's competitive-structure advantage is upstream (factory-side), the advantage is fragile — a competing factory can match it; a competing distributor can replicate it — and the protocol exits only if the distributor also carries a downstream or internal-surface advantage that defends the upstream advantage.
  • IF the distributor's competitive-structure advantage is internal (sales process, RFQ turn-around, technical-support response, sample-kit depth, training depth), the advantage is structurally defensible — it is funded by the distributor's own staffing — and the protocol exits to Protocol 05.
  • IF the distributor's competitive-structure advantage is downstream (installer network, dealer network, trade-counter shelf, e-commerce shelf, direct-customer relationship), the advantage is the strongest channel-whitespace advantage the distributor can carry, and the protocol exits to Protocol 05.
Channel layer the distributor's advantage lives onStrength of the competitive-structure advantageDefensibility over the program lifeConfirm-on / figure routed to
Upstream (factory-side)WeakFragile; a competing factory or distributor can match/request-a-quote for factory-side terms
Internal (distributor's own sales / RFQ / support / sample / training surface)StrongStructurally defensible; funded by the distributor's own staffingSmart Lock Distributor Training + Smart Lock Distributor Technical Support
Downstream (installer / dealer / trade-counter / e-commerce / direct-customer)StrongestStrongest; channel relationships are the slowest surface for a competitor to replicateSmart Lock Distributor Installation Support + Smart Lock Distributor Territory Strategy

The exception path the protocol carries is the rare case where the distributor's only competitive-structure advantage is upstream and the distributor refuses to invest in an internal or downstream advantage. The protocol refuses this exception as the default; the exception is only available to distributors who have written evidence — signed RFQ, dated per-program fact sheet, written distributor-agreement clause — that the upstream advantage is contractual, exclusive, and time-bounded in a way the distributor's business can fund against for the program life.

Protocol 05 — Pilot-site selection as a learning-density question

Protocol 05 selects the pilot site the distributor will use to validate the vertical-fit and channel-whitespace outcomes Protocol 02 through Protocol 04 produced, and the pilot site is chosen as a learning-density question, not a visibility question. The pilot site that exposes the most learning per unit of distributor overhead the pilot site consumes is the right pilot site. The pilot site that exposes the least learning per unit of overhead is the wrong pilot site, regardless of how visible or prestigious the wrong pilot site appears.

The IF-THEN decision rule the protocol enforces:

  • IF the pilot site forces the distributor to exercise every layer the program commits the distributor to fund — the sales surface, the RFQ surface, the technical-support surface, the installation sub-network, the after-sales surface, the spare-parts posture, the per-vertical credential stack — the pilot site is learning-dense and Protocol 05 accepts the site.
  • IF the pilot site exercises only the sales surface or only the installation sub-network, the pilot site is learning-thin and Protocol 05 rejects the site in favour of one that exercises every layer.

The exception path the protocol carries: the first pilot site can be learning-thin on one or two layers IF the distributor commits to a second pilot site that exercises the missing layers within ninety days of the first pilot's go-live. The exception is documented, the second pilot is named in writing before the first pilot ships, and the exception is named in the RFQ the distributor submits to /request-a-quote.

Pilot-site candidateLayers the candidate exercisesLearning density per unit of overheadConfirm-on / figure source
Mid-scale hospitality fleet (e.g. 60–200-room property)Sales + RFQ + technical-support + installation sub-network + spare-parts + multi-software postureHigh per pilot/order-samples + Hotel Smart Lock System Architecture for the hospitality-class context
Build-to-rent mid-size block (e.g. 80–300-unit development)Sales + RFQ + installation sub-network + tenant-cycle credential capacityHigh per pilotSmart Lock Access Management for Rentals + /order-samples
Mid-scale commercial officeSales + RFQ + technical-support + installation sub-network + audit retrievalHigh per pilot/order-samples + /request-a-quote
Trade-counter relationshipSales + sample-kit posture + counter-staff technical depthMedium per pilot/order-samples + Smart Lock Distributor Sales Kit
E-commerce pilot shelfSales + consumer RMA + remote-troubleshootingMedium per pilot/order-samples

The table is illustrative not exhaustive, and the protocol refuses any pilot site the table cannot place inside a high-density or documented-low-density-exception row.

Protocol 06 — Qualification criteria as a written scorecard the distributor scores itself

Protocol 06 forces the distributor to score the opportunity against a written scorecard the distributor owns and the protocol audits. The scorecard is not a factory-side tool; the scorecard is the distributor's own opportunity-qualification instrument, and the scorecard carries seven weighted dimensions, each scored one to five, with the pass threshold set in writing before the scoring begins.

The IF-THEN decision rule Protocol 06 enforces is binary:

  • IF the distributor scores above the pass threshold on every dimension, Protocol 06 exits to Protocol 07.
  • IF the distributor scores at or below the pass threshold on any dimension, Protocol 06 rejects the opportunity for the first program and either re-runs Protocols 01–05 or defers the program.
DimensionWeightScoring prompt the distributor answers in writingPass threshold (set in writing before scoring)Confirm-on / source for the score
Territory funding surfaceHigh"Can the territory be funded for the program life without external working-capital injection beyond what the distributor has already arranged?"Distributor-set thresholdDistributor's own balance sheet + /request-a-quote
Vertical depthHigh"Can the distributor carry one to two verticals deeper than the competitor surface the vertical is currently buying from?"Distributor-set thresholdDistributor's own competitive audit
Product-fit completenessHigh"Can the distributor name the catalogue SKU class for every vertical-fit row, with every per-model figure confirmed on the product page?"Distributor-set thresholdPer-SKU product page + SLK-9936S yardstick
Channel-whitespace defensibilityHigh"Does the distributor carry a defensible competitive-structure advantage (internal or downstream) that the upstream advantage alone cannot defend?"Distributor-set thresholdDistributor's own channel audit
Pilot-site learning densityMedium"Does the named pilot site exercise every layer the program commits the distributor to fund?"Distributor-set thresholdDistributor's own pilot-site scope
After-sales envelopeHigh"Has the distributor named the after-sales surface (install sub-network / RMA / spare-parts / training / support / escalation) the territory commits the distributor to fund?"Distributor-set thresholdSmart Lock Distributor Warranty Management + Smart Lock Distributor Spare Parts
Working-capital sustainabilityHigh"Has the distributor sized the working-capital envelope the stocking posture, the marketing posture, the after-sales posture and the per-pilot posture demand for the first eighteen months of the program?"Distributor-set thresholdDistributor's own working-capital model + Smart Lock Distributor Business Model

The scorecard is the distributor's own, the pass threshold is the distributor's own, and the protocol's job is not to set the threshold — the threshold is a function of the distributor's appetite for risk and the working-capital envelope the distributor can fund. The protocol's job is to force the distributor to write the threshold down before the scoring begins, score each dimension in writing against the threshold, and accept the rejection Protocol 06 enforces when the score misses the threshold on any dimension.

The exception path Protocol 06 carries: the distributor may defer the program and re-run Protocols 01–05 IF the rejection is on a single dimension the distributor can address with a single structural change (a working-capital envelope enlargement, a vertical-list trim, a pilot-site reselection). The protocol refuses the exception when the rejection is on more than one dimension; the multi-dimensional rejection forces a full re-run of Protocols 01–05.

Protocol 07 — Close-loop conversion as a written handshake, not a verbal "yes"

Protocol 07 converts the qualified opportunity into a written handshake between the distributor and the factory, and the handshake is not a verbal "yes" the sales conversation closes on. The handshake is a written set of artefacts the distributor assembles and the factory countersigns:

  • A dated per-program fact sheet the factory returns to the distributor carrying the per-deal figures — price band per SKU class, MOQ tier per SKU class, lead-time window per SKU class, territory definition, exclusive terms, after-sales scope, training depth, sample-cession policy, spare-parts kit sizing — every per-deal figure the distributor's program depends on. (Per-deal figures are routed to /request-a-quote; the protocol does not invent them.)
  • A dated distributor agreement the factory issues carrying the commercial terms the per-program fact sheet documented in clauses — pricing, MOQ, territory, exclusivity, after-sales scope, training scope, sample-cession terms, spare-parts terms, payment terms, governing law.
  • A dated sample-kit delivery from the factory to the distributor carrying the SKU samples the distributor committed to fund in the vertical-fit map, every sample kit SKU's product page confirmed in writing, and every sample kit SKU's per-model figure confirmed on the product page before the sample kit ships.
  • A dated pilot-site letter the distributor and the pilot-site customer co-sign, naming the pilot scope, the pilot layers, the pilot success criteria, the pilot close-loop criteria, and the pilot-to-program transition criteria.
  • A dated per-program qualification scorecard — Protocol 06's output — the distributor carries as the audit artefact the program references for the first eighteen months.

The IF-THEN decision rule Protocol 07 enforces:

  • IF every artefact in the handshake list above is dated, written and counter-signed before any sample-kit ships, Protocol 07 exits the distributor into the program.
  • IF any artefact in the handshake list is verbal, undated, or single-sided, Protocol 07 refuses the conversion and re-runs the missing artefacts.
Handshake artefactDated?Written?Counter-signed?Confirm-on / source for the artefact
Per-program fact sheetRequiredRequiredRequired (factory returns to distributor)/request-a-quote + per-program fact sheet
Distributor agreementRequiredRequiredRequired (distributor + factory)/become-a-distributor + legal review
Sample-kit deliveryRequiredRequiredRequired (factory + distributor)/order-samples + per-SKU product page
Pilot-site letterRequiredRequiredRequired (distributor + pilot customer)Distributor's own pilot-scope document
Qualification scorecardRequiredRequiredRequired (distributor-only)Protocol 06 output

The table is the close-loop conversion scorecard; the protocol refuses the close-loop conversion on any artefact that is undated, verbal or single-sided; and the protocol refuses the program the moment any artefact is missing.

Illustrative scenario — A regional distributor qualifying a 120-room mid-scale hospitality fleet as the first pilot

Consider a 120-room mid-scale hospitality fleet in a coastal urban corridor as the first pilot a regional distributor commits to fund against the seven protocols above. The distributor enters Protocol 01 with a territory named in vertical-channel terms ("hospitality and build-to-rent in the western coastal urban corridor"), a stocking capital the distributor has sized inside the working-capital envelope the distributor already holds, and an after-sales surface named in writing — installation sub-network named with three local installers, RMA bin named with a thirty-day turn-around commitment, spare-parts kit named against the per-door spare-parts posture the distributor commits to fund, training hours named at the distributor's expense, support staff named at one full-time equivalent, escalation path named with a written escalation matrix. Protocol 01 exits to Protocol 02.

Protocol 02 forces the distributor to pick the one or two verticals the distributor can carry deeper than the competitor surface. The distributor picks hospitality fleet as the primary vertical and build-to-rent as the secondary vertical; the distributor refuses the other ten verticals the territory could nominally serve. Protocol 02 exits to Protocol 03.

Protocol 03 maps the catalogue to the hospitality-fleet vertical. The distributor enters with the SLK-9936S yardstick as the documentation-granularity benchmark — door thickness envelope, RFID frequency, read distance, audit-event buffer, battery format, mechanical override path, multilingual software posture, standalone-or-centralized database modes — and the distributor confirms every shortlisted SKU's per-model figure on the product page before any vertical-fit decision is recorded. The protocol's firewall holds: SLK-9936S figures do not port across siblings, every other SKU decision is documentation, and the vertical-fit map the protocol produces is fully dated.

Protocol 04 audits the channel whitespace. The distributor's competitive-structure advantage lives on the downstream layer — the distributor has a twenty-year installer-network relationship in the coastal corridor that the competing distributors and the factory direct-sales surface do not carry, and the distributor's installation sub-network is the slowest surface for a competitor to replicate. Protocol 04 exits to Protocol 05.

Protocol 05 selects the pilot site. The 120-room mid-scale hospitality fleet exercises every layer the program commits the distributor to fund — sales surface, RFQ surface, technical-support surface, installation sub-network, after-sales surface, spare-parts posture, per-vertical credential stack — and the pilot site is learning-dense at the per-room overhead the fleet imposes. Protocol 05 accepts the pilot. The protocol's exception path is not triggered; the pilot exercises every layer.

Protocol 06 forces the distributor to score the opportunity against the seven-dimension scorecard, with the pass threshold set in writing before the scoring begins. The distributor scores above the threshold on every dimension, with the working-capital sustainability dimension noted as the closest-to-threshold dimension the distributor commits to monitor monthly for the first eighteen months. Protocol 06 exits to Protocol 07.

Protocol 07 assembles the five-artefact handshake — per-program fact sheet from /request-a-quote, distributor agreement from /become-a-distributor, sample-kit delivery from /order-samples with every SKU's per-model figure confirmed on the product page, pilot-site letter co-signed by the distributor and the 120-room property's general manager, and the dated qualification scorecard Protocol 06 produced. Every artefact is dated, written and counter-signed before the first sample kit ships. Protocol 07 exits the distributor into the program.

The pilot goes live, the per-room installation cycle exposes two per-room credential-stack issues the distributor has to escalate to the factory, the after-sales envelope holds inside the thirty-day RMA turn-around the distributor committed to, and the first eighteen months of the program fund the working-capital sustainability dimension the Protocol 06 scorecard flagged as closest-to-threshold. The distributor converts the pilot into the program, expands the territory inside the Protocol 01 funding envelope, and runs the next pilot against the build-to-rent vertical Protocol 02 named as the secondary.

The scenario is illustrative not a customer story; the per-room figures are illustrative not per-SKU figures; every per-model capability the scenario touches (door thickness, credential stack, RFID posture, audit-event buffer, battery format, multilingual software posture, standalone-or-centralized database modes, mechanical override path, spare-parts posture, after-sales response time) is documentation for every SKU the distributor actually chooses; every per-deal figure the scenario touches (price, MOQ, lead time, territory definition, after-sales scope, spare-parts kit sizing) is routed to /request-a-quote.

The two exception paths the distributor must declare up front

Two exception paths run across the seven protocols, and both have to be declared up front — before Protocol 01 exits, not after — because both exception paths change the per-protocol scoring the distributor commits to fund.

Exception A — the multi-vertical exception. Protocol 02 allows the distributor to run with a three-vertical list for the first program, IF the distributor can demonstrate channel credibility in the third vertical at least as deep as the credibility in the first two, and IF the exception is documented in the RFQ the distributor submits to /request-a-quote. The default protocol refuses the three-vertical path; the exception allows it conditionally. The distributor who declares Exception A pays the cost of writing the channel-credibility evidence the third vertical depends on, and the cost is the cost of writing per vertical the distributor adds to the first program.

Exception B — the multi-pilot exception. Protocol 05 allows the distributor to run with a learning-thin first pilot IF the distributor commits to a second pilot that exercises the missing layers within ninety days of the first pilot's go-live, and IF the second pilot is named in writing before the first pilot ships. The default protocol refuses the learning-thin first pilot; the exception allows it conditionally. The distributor who declares Exception B pays the cost of naming the second pilot before the first pilot ships, and the cost is the cost of the second pilot's per-room overhead the distributor commits to fund against a fixed ninety-day window.

Both exceptions have to be declared in writing in the RFQ the distributor submits to /request-a-quote, both exceptions have to be reflected in the dated per-program fact sheet the factory returns, and both exceptions have to be reflected in the dated distributor agreement the factory issues. A distributor who tries to invoke either exception after the program has started has not invoked an exception; the distributor has asked the factory to renegotiate the per-program terms mid-program, and the factory's response to mid-program renegotiation is the same response every channel program returns: renegotiate from the position the protocol refused to fund the first time.

Where the protocols refuse to operate, and where the per-model and per-deal figures are routed

The seven protocols refuse to operate on three classes of figure, and each class is routed to a different confirmation source. The routing discipline is what makes the protocols defensible; a protocol that operates on an invented figure is not a protocol, it is a brochure.

Figure classExamplesConfirm-on / source
Per-model figuresDoor thickness envelope · credential stack · RFID frequency and read distance · audit-event buffer · battery format · battery operating cycles · mechanical override path · finish options · firmware revision label · app-platform binding (TTLock / Tuya / Doodle / hotel PC software) · environmental envelope · mortise form factor · cylinder type · latch type · body material · standalone-or-centralized database modesThe product page of every shortlisted SKU; SLK-9936S yardstick invoked ONCE inside Protocol 03 as the documentation-granularity benchmark
Per-deal figuresUnit price band per SKU class · MOQ tier per SKU class · lead-time window per SKU class · territory definition · exclusive terms · after-sales scope · training depth · sample-cession policy · spare-parts kit sizing · payment terms/request-a-quote for the per-program fact sheet; /become-a-distributor for the distributor agreement
Per-program figuresWorking-capital envelope the distributor holds · stocking-capital band the territory demands · after-sales surface the distributor commits to fund · installation sub-network depth · RMA turn-around · spare-parts posture · training hours · support staff full-time equivalents · pilot-site learning density · per-dimension qualification score · exception-path declarationsDistributor's own written artefacts (balance sheet · working-capital model · after-sales scope document · pilot-site letter · qualification scorecard · exception declarations)

The routing discipline is the protocol's own audit trail, the factory's input to the per-program fact sheet carries the per-deal figures, the distributor's input to the RFQ carries the per-program figures, and the product page carries the per-model figures. The protocol refuses to operate on any figure whose confirmation source is not named, and the protocol refuses to invent any figure whose confirmation source is not a verifiable written artefact.

The per-protocol hand-off the distributor commits to write before Protocol 01 exits

The seven protocols are designed to be run in sequence, not in parallel, and the per-protocol hand-off the distributor commits to write before Protocol 01 exits is the artefact the next protocol's entry criterion is scored against. The hand-offs are listed below; every hand-off is dated, written and distributor-signed before the next protocol begins.

  • Protocol 01 → Protocol 02 hand-off: dated territory-naming document + dated stocking-capital-vs-envelope sizing + dated after-sales surface document.
  • Protocol 02 → Protocol 03 hand-off: dated vertical-priority list (one to two verticals, three with Exception A, four-or-more refused).
  • Protocol 03 → Protocol 04 hand-off: dated vertical-fit map + per-SKU documentation log + SLK-9936S yardstick invocation record.
  • Protocol 04 → Protocol 05 hand-off: dated channel-whitespace audit + named competitive-structure advantage layer.
  • Protocol 05 → Protocol 06 hand-off: dated pilot-site scope + dated pilot-layer matrix + Exception B declaration if invoked.
  • Protocol 06 → Protocol 07 hand-off: dated seven-dimension qualification scorecard + per-dimension pass-threshold record + dated re-run decision if any dimension failed.
  • Protocol 07 → program hand-off: dated five-artefact handshake + dated sample-kit delivery with per-SKU product-page confirmations + dated pilot-site letter + dated distributor agreement + dated per-program fact sheet.

A distributor who runs the seven protocols in order and produces every hand-off in writing has run the playbook the way the playbook is designed to be run. A distributor who runs fewer than seven protocols, runs the protocols in parallel, skips a hand-off, or substitutes a verbal "yes" for a written hand-off has not run the playbook; the distributor has run a brochure.

What this playbook deliberately does not assert

This playbook deliberately does not assert a market-size figure for the smart-lock distributor opportunity in any territory, any vertical, any region, any country, any corridor or any postal-code band. The market exists; the catalogue exists; the territory exists; the per-territory, per-vertical, per-corridor market-size figure is a function of the distributor's own market map, the factory's per-program fact sheet, and the local market data the distributor sources — none of which this playbook invents or asserts. Any distributor who needs a market-size figure for an internal business case, a bank loan, an investor deck or a board paper must source that figure against the distributor's own market data, not against this playbook.

This playbook deliberately does not assert any per-model figure outside the SLK-9936S yardstick the protocol invokes once inside Protocol 03. Every other per-model figure is documentation for the dated SKU under consideration. A distributor who reads this playbook and treats any per-model figure as portable across SKUs has read the playbook incorrectly; the SLK-9936S yardstick is documentation-granularity documentation, not per-SKU specification.

This playbook deliberately does not assert any per-deal figure — price band, MOQ tier, lead-time window, territory definition, exclusive terms, after-sales scope, training depth, sample-cession policy, spare-parts kit sizing — anywhere. Every per-deal figure is routed to /request-a-quote and the dated per-program fact sheet the factory returns. A distributor who reads this playbook and treats any per-deal figure as portable across deals has read the playbook incorrectly; the per-deal figures are deal-specific, dated, and counter-signed before the program runs.

This playbook deliberately does not assert any certification claim of any kind — no CE / FCC / UL / EN / IEC / BHMA / ANSI / SKG / VdS / ISO claim, no fire-rating / ADA / building-code claim, no IP-rating claim, no radio-approval claim, no privacy / data-residency / encryption-strength claim — for any catalogue SKU or any distributor program. Certification posture is a per-SKU, per-program, per-region question the distributor addresses with the factory and the local authority; this playbook does not invent or assert a certification claim.

This playbook deliberately does not assert any client logo, customer name, factory-floor statistic (area / staff / mold count), specific territory population, specific vertical penetration percentage, specific addressable-market dollar, or per-region exclusive map anywhere in the body. The catalogue is named at the FACT level (79 models, 24 hotel, 37 fingerprint, 18 keypad, 10 outdoor, 9 RFID, 6 face, 6 cabinet, 3 video, 3 glass), the factory posture is named at the FACT level (10+ years in smart locks, 80+ countries, OEM/ODM factory, quote-based commerce), the app-platform lanes are named at the FACT level (TTLock / Tuya / Doodle / hotel PC software), and nothing the playbook names exceeds the FACT scope.

This playbook deliberately does not assert any out-of-catalog capability anywhere. The out-of-catalog firewalls are preserved — no palm-vein / Matter / Zigbee / Z-Wave / Thread / Apple Home Key / UWB / proprietary radio / vein-recognition / proprietary mesh asserted as catalog capability in any protocol, any hand-off, any exception, any scenario, any scorecard, or any table. A distributor who reads this playbook and treats any out-of-catalog capability as in-scope has read the playbook incorrectly; the catalogue scope is the catalogue the factory ships, and the protocols operate inside the catalogue scope.

Routing the distributor from the playbook into the program

The distributor who has finished the seven protocols — every protocol exited in order, every hand-off produced in writing, every per-model figure confirmed on the product page, every per-deal figure routed through /request-a-quote and the per-program fact sheet, every exception declared in writing, every scorecard dimension scored against the distributor's own threshold, every five-artefact handshake dated and counter-signed — is the distributor the program is designed to fund. The next step is the distributor agreement conversation, the sample-kit conversation, the per-program fact sheet conversation, and the pilot-to-program transition conversation, all of which the playbook's Protocol 07 output has already prepared for in writing.

The three closing routes the distributor walks out with are: the primary CTA at /become-a-distributor (the distributor agreement the protocol's Protocol 07 hand-off prepares for), the secondary CTA at /request-a-quote (the per-program fact sheet the protocol's Protocol 07 hand-off depends on), and the tertiary CTA at /order-samples (the sample-kit delivery the protocol's Protocol 03 vertical-fit map drives). The distributor carries the seven protocols' dated hand-offs into the CTA conversation, the CTA conversation references the per-program fact sheet the factory returns, and the program runs against the structural-fit map the playbook produced. A distributor who arrives at the CTA conversation without the seven protocols' hand-offs has arrived at the wrong conversation; the right conversation is the protocol walk-through, run first, in writing, against the distributor's own working-capital envelope, before any CTA is engaged.

Sepetiniz
Bu siteyi kullanırkenizin deneyimini çerezlere izin vererek iyileştirebilirsiniz. Çerez Politikası
Chat on WhatsApp