Playbook

This desk × this list × the unit you sell. SUBLATTICE names the attach. Your desk defines what you may sell. Your list defines who you hunt. We connect them at catalog grain to find their product, their project, the gap, the owner — the layer a BDM can actually walk in on. If we cannot name it, it is not synergy. The rest is noise. CRM in. Packets out. Salesforce keeps the account. Gong keeps the conversation. SUBLATTICE keeps the attach. Packets are engagement products on that object — first contact, comparison, and pilot — this desk’s brand on the mast (logo and color they submit), prepared for the account, catalog units in the architecture, sourced KPIs only. Save PDF is one long page — letter width, height of the sheet.

Customer brief — value proposition and technical brief, ten landscape pages.

Desk × list × unit

The desk is who is scoring. The list is who they hunt. The unit is what they sell — a string they own, not a preset of four commercial words. If we cannot name the intersection, it is not synergy. The rest is noise.

Desk
List
Unit
Desk, list, and unit meet at the attach.

Synergy object

The unit of work is not a company score. It is a layer a BDM can walk in on. Rank is the dossier. Score is the rank chip (L1) — call + one line for the CRM, below threshold. There is no second ranking brain. Pass never opens a packet.

  1. Our unit

    Catalog row that scored Yes or Qualify — product, service, or feature.

  2. Their product

    The SKU that stays. Adjacency, not displacement.

  3. Project

    A named line at them. If none, say so.

  4. Gap

    Why that project is open now.

  5. Owner

    The person who can say yes to that layer. Not found until sourced — then hunt titles, the roles to search, not a fake name.

Type × seat

OEM, ISV, or agency is what the company is. Direct or ecosystem is how this person goes to market — sell to, or sell through. Inclusive of BDM, AE, founder, partnerships, channel, alliances, partner marketing. The pair feeds the job list, hunt, catalog shapes, alliance goals, and packets. An OEM ecosystem hunts VARs and embed partners. An ISV ecosystem hunts complementary products and marketplaces. An agency ecosystem hunts vendors it can keep. Partner brief, discovery, and joint motion are the ecosystem packets. Direct keeps first contact, comparison, and pilot.

Direct

Ecosystem

OEM
Sell to
Sell through
ISV
Sell to
Sell through
Agency
Sell to
Sell through

Direct packets

  1. First contact
  2. Comparison
  3. Pilot

Ecosystem packets

  1. Partner brief
  2. Discovery
  3. Joint motion

Reseller / channel

They sell our unit through their motion. Enablement and margin, not a rip-and-replace.

Referral

They introduce. We close. No SKU this quarter.

Co-sell

Registered deal. Both names on the account. Outflow to CRM as a partner-sourced opp.

Integration partner

Their product × our unit, technically. The sit is an integration type. The motion is the alliance.

Co-marketing

Joint demand: solution brief, webinar, field story. Packet is the product this week.

Marketplace / listed

We sit in their catalog, or they sit in ours. Listing is the wedge.

OEM / embed

They ship our unit under their name or in their device. Same synergy as an OEM desk — alliances owns the program.

SI / implementer

They deliver us into accounts they already own. We do not steal the relationship.

Desk-owned units

A catalog row carries a unit the desk types. Ranking tilt is derived from those units. Hunt titles fall back to the unit owner when the unit is new. Embed / managed / SDK is one desk’s language — a showcase, not a preset we ship.

Showcase packs

Admin sets up a desk as that company would run it, scores a few of their targets, and saves the snapshot. Activate the pack when you walk in. A built-in admin pack is the proof. Every other pack is a desk you prepared for the company in the room. The same snapshot is a handoff: export the pack, they import it as their desk. Until seats exist, the file is their account environment.

Live research

Public walks on this pilot are notes-only — paste their page. Host live research spends the operator’s xAI key and is on only after admin unlock. Paying desks will bring their own key; that needs a signed-in seat, not this cut.

Bake-off

Comparison is one packet, not a stack of PDFs. The desk plus up to three companies they named. Same category is a peer. Adjacent sits next to us — complementary, not a rip-and-replace. Wrong category does not print. Rank fills the cells; a typed name without a report stays Not ranked.

Partner motion

Stages live on the synergy object. CRM stage maps in; ours maps out. Hold, callback, and blacklist are ours — not a Salesforce picklist we pretend to own.

Not started

In the list. No human motion yet.

First contact

Outreach sent or first touch.

Discovery / first meeting

A conversation happened.

Technical meeting

Engineering or product in the room.

Materials / use-cases

They asked for a packet or use-case.

Comparison requested

They named an incumbent or alternative.

Pilot proposal

Eval is on the table.

Live pilot

In field. Outcomes live here.

Hold

Parked. Not a pass.

Callback / follow-up

Date and purpose required.

Blacklist

Do not touch. Outflow as do-not-contact.

Source order

Legacy rank walked Wikipedia, Crunchbase, G2 first — best returning sources for company quality. That order does not return a named owner or a product-layer gap. Walk these lists in order. Stop at the first sourced hit. Apollo is not in live search.

Company

  1. 1. Company site
  2. 2. Wikipedia
  3. 3. Crunchbase
  4. 4. LinkedIn company page
  5. 5. SEC / IR
  6. 6. G2 / Capterra

Gap (this row)

  1. 1. Product pages / datasheets / docs
  2. 2. Job posts (roles they staff for this layer)
  3. 3. Newsroom / roadmap / MOUs
  4. 4. Partners page
  5. 5. Trade press
  6. 6. G2 / Capterra complaints — last, noisy

Owner (this row)

  1. 1. About / team / leadership — named person + title
  2. 2. Newsroom / press quotes — “said X, title”
  3. 3. Product or contact page
  4. 4. Job posts — title of the org that owns this layer; name stays Not found
  5. 5. LinkedIn people — only a public hit. A company page is not a person

Never for owner: Wikipedia · Crunchbase · G2 · Apollo (not in live search) · Invented names. Apollo is a people adapter later: hunt titles + domain, L2 only, human confirm before a name lands. We do not replace Apollo.

Catalog shapes

Internal map of common catalogs — shapes, not SKUs. An OEM embed plus managed ops is one worked shape. A new desk picks a shape and renames the brackets. Hunt titles ride the shape until a named owner is sourced.

OEM embed

They ship a device. You license the runtime that sits inside it.

Hunt · OEM / Product · Head of modules / hardware · Partnerships / BD

Managed / we operate it

You run the control plane. They consume it. Not an embed.

Hunt · VP Cloud / Ops · Head of Product · Partnerships

SDK / component

They keep the application. You sit in a layer they will not staff.

Hunt · CTO / VP Engineering · Head of Product · Partnerships

ISV application

You sell the product. They are a rival, a partner, or a buyer.

Hunt · Head of Product · Partnerships · CTO

Hardware + attach

You sell the device. Software is the attach, not the camera you displace.

Hunt · Product / hardware · Partnerships / BD · Sales engineering

Agency / represented offer

You do not invent product. You introduce a unit the desk can keep.

Hunt · The buyer named on the offer · Partnerships at the target · Product at the target

Integration types

Catalog shape is what we sell. Integration type is how that unit sits on their product. Orthogonal. Eight attach patterns — not an iPaaS list. Hunt titles can tighten to the attach.

Embedded SDK / runtime

Licensed into their binary or device. They keep the product.

API consume

They call us. We are a service, not a library in the box.

Plugin / marketplace

We sit inside their application as an extension they list or load.

Shared protocol

Adjacency via a rail they already speak — MQTT, ONVIF, RTSP, not a new SKU.

Event / telemetry plane

Webhooks, streams, fan-out. The leak is compute or idle video, not a camera.

Cloud companion

We operate next to their on-prem or device stack. Only if they named a gap they will not staff.

OEM / rebrand

They ship our unit under their name. Access and capacity still our commercial rules.

Co-sell / referral

No technical attach this quarter. A meeting, not a runtime.

Playsheet

Same rows on every account — the desk catalog, grouped as entry, product, and feature. Only the checks, the why, and the synergy intel change. Approach is built from Yes / Qualify using a desk persona (pain, value, objection, CTA). First-contact, comparison, and pilot packets are views of the same brief — print the one the meeting needs. Comparison is complementary: their product × where we sit × why it compounds. History together is sourced or “Not found.”

Yes

This catalog row is in play at a named project.

Qualify

Possible — confirm a project, stack, or MOU before a SKU.

No

Does not fit this account this quarter. The X is the point.

Later

Path only. Not live. Do not pitch.

Play summary

Rolled up from the checks so the desk can see the ask this quarter.

Attach

A named project, SKU, MOU, or line at the account. If none, say so.

Unit

The catalog entry this desk leads with on this account — whatever units you defined. (A camera OEM’s happen to be managed, embed, SDK.)

Wedge

The catalog capability that creates differentiation. Mention is not a live SKU.

TCO

Sourced economics only. Catalog hooks or cited public numbers — never invented.

Lane

Who we call, and the ask. Bound to the unit that scored Yes.

Scenarios

oem · direct

Rank accounts for this motion

Will they buy, embed, or consume the commercial unit we sell?

oem · ecosystem

Who should we recruit

Which companies belong on our partner program shortlist?

oem · ecosystem

Which programs we join

Marketplaces, cloud, SI, or OEM programs we attach through — not who we recruit.

oem · any seat

Map a market

Who are the named players, and who is actually buying?

isv · direct

Who is competing with us

Named competitors: what they sell, to whom, and where they are weak.

isv · direct

How do we crush them

Where are they exposed, and what motion do we run this quarter?

isv · any seat

What is on their roadmap

Public signals of where they are heading.

isv · direct

How do we take share

Adjacent markets and accounts we can take from them.

isv · any seat

What is our potential

Size the opportunity honestly. Pass if the TAM is theatre.

isv · any seat

Who might buy us — or who we buy

Strategic fit for an inbound or outbound deal.

agency · direct

Qualify the account

Is this a real meeting, or a polite no?

agency · any seat

Who do we introduce

Right buyer, right motion, this quarter.

isv · ecosystem

Who should we ally with

Complementary ISVs, marketplaces, OEM programs, co-sell — not the rival we crush.

agency · ecosystem

Which partners feed us

Vendors we represent and agencies we attach through. A unit we can keep.

Buy vs. build

Are they more likely to license a component, or staff an equivalent team?

  • Founding year

    founding_date

    Younger firms moving fast tend to buy. Older small firms often build.

    Wikipedia · Crunchbase · company site

  • Headcount

    employees

    Sub-50 with long tenure leans Build. Scale leans Buy.

    LinkedIn · Crunchbase · company site

  • Job openings

    job_openings

    Open engineering seats can mean they will staff instead of license.

    LinkedIn jobs · careers page

  • Technology / OEM partners

    technology_partnerships

    Existing OEM relationships are a Buy tell.

    Company partners page · PR wires · LinkedIn

  • Product leadership

    product_leadership

    CPO leans Build. A PM in a small team leans Buy.

    About / team · press quotes · LinkedIn

  • Developer mix

    developer_ratio

    High engineering share of headcount leans Build.

    LinkedIn · company site

  • Licensing model

    licensing_model

    How they sell (SaaS, perpetual, OEM, hardware) shapes the unit we can attach.

    Pricing page · company site · G2

Growth

Is the company actually expanding, or just noisy?

  • Headcount trend

    headcount_trend

    Sustained hiring is a better growth tell than a press cycle.

    LinkedIn · Crunchbase

  • Open roles vs size

    hiring_intensity

    Hiring intensity relative to headcount separates expansion from replacement.

    LinkedIn jobs · careers page

  • Revenue / ARR signals

    revenue_signals

    Public ARR, filings, or credible press — never invent a number.

    SEC · TechCrunch · company blog

  • Geographic expansion

    geo_expansion

    New offices and regions are a motion cue, not vanity.

    Company site · press · LinkedIn

Funding

Can they write a check this year?

  • Funding history

    funding_rounds

    Raised capital usually means they buy adjacent stack rather than staff it.

    Crunchbase · TechCrunch · Forbes

  • Last round / runway

    last_round

    A stale round with no revenue story is a Watch, not a Pursue.

    Crunchbase · press

  • Public vs private

    listing_status

    Listed issuers have a different check-writing motion than venture shops.

    Company IR · Wikipedia · Crunchbase

  • Profitability signals

    profitability

    Profitable operators buy differently than companies still raising to exist.

    Filings · press · company site

Cloud

Will they consume (and pay for) hosted infrastructure?

  • Current cloud provider

    cloud_provider

    Named hyperscaler is a managed-unit cue. Absence is not a no — it may be embed.

    Job posts · engineering blog · case studies

  • Cloud-native vs on-prem

    deployment_posture

    Self-hosted / air-gapped buyers are an embed motion, not a CPaaS no.

    Product pages · docs · security page

  • Data-residency constraints

    data_residency

    Sovereignty and export-first posture change which commercial unit we lead with.

    Trust center · docs · press

  • Consumption intensity

    cloud_spend

    High usage is a managed-tier tell. Device-first shops often will not pay it.

    Job posts · architecture blogs · partner pages

Reputation

Do they have public legitimacy a partner can stand next to?

  • Review footprint

    reviews

    G2 / Capterra density is legitimacy, not a score to chase.

    G2 · Capterra

  • Named logos / case studies

    logos

    Public logos show who already trusts them — and who we sit next to.

    Customers page · case studies

  • Analyst / press mentions

    press

    Coverage quality beats volume. Ignore recycled SEO pages.

    TechCrunch · trade press · Wikipedia

  • Security / compliance posture

    compliance

    A missing trust page is a risk; a real one is a meeting opener.

    Trust center · security page

  • Enterprise vs SMB

    target_audience

    Who they sell to shapes whether our unit attaches at OEM, ISV, or operator.

    Website · G2 · LinkedIn

Maturity

Is this a real operating company, or a slide deck?

  • Years in market

    years_in_market

    Tenure plus scale separates operators from decks.

    Wikipedia · Crunchbase · company site

  • Product count

    products

    A suite vs a single SKU changes the attach motion.

    Product pages · G2 · LinkedIn

  • Org structure

    org_structure

    Who owns the buy (product, partnerships, engineering) is the first-meeting map.

    LinkedIn · About page

  • M&A history

    ma_history

    Acquirers and acquirees have different check-writing and integration motions.

    Press · Crunchbase · Wikipedia

  • Headquarters

    hq

    Jurisdiction and region change residency, support, and who we introduce.

    Company site · LinkedIn · Wikipedia

Active projects

What can we attach to this quarter? Named work at the account — not a category lecture.

  • Active / named projects

    active_projects

    Products, programs, MOUs, SKUs, or lines a BDM can name in the first sentence. Personnel pages, news, website, and roadmap beat a slogan.

    Company site · newsroom · LinkedIn · trade press

  • Stack hints

    stack_hints

    Codecs, protocols, VMS, cloud, MQTT, on-device AI — the wedge is only real if it matches what they already run or are buying.

    Product pages · docs · datasheets · job posts

  • Public roadmap / news

    public_roadmap

    A live refresh, partnership, or replatform is a timing cue. Stale MOUs are Watch, not Pursue.

    Newsroom · IR · trade press · LinkedIn

  • Who owns the buy

    named_buyers

    Product, partnerships, ODM program, or engineering — the first meeting is a person, not a logo.

    About / team · press quotes · LinkedIn people