Reseller / channel
They sell our unit through their motion. Enablement and margin, not a rip-and-replace.
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.
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.
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.
Our unit
Catalog row that scored Yes or Qualify — product, service, or feature.
Their product
The SKU that stays. Adjacency, not displacement.
Project
A named line at them. If none, say so.
Gap
Why that project is open now.
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.
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
Direct packets
Ecosystem packets
They sell our unit through their motion. Enablement and margin, not a rip-and-replace.
They introduce. We close. No SKU this quarter.
Registered deal. Both names on the account. Outflow to CRM as a partner-sourced opp.
Their product × our unit, technically. The sit is an integration type. The motion is the alliance.
Joint demand: solution brief, webinar, field story. Packet is the product this week.
We sit in their catalog, or they sit in ours. Listing is the wedge.
They ship our unit under their name or in their device. Same synergy as an OEM desk — alliances owns the program.
They deliver us into accounts they already own. We do not steal the relationship.
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.
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.
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.
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.
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.
In the list. No human motion yet.
Outreach sent or first touch.
A conversation happened.
Engineering or product in the room.
They asked for a packet or use-case.
They named an incumbent or alternative.
Eval is on the table.
In field. Outcomes live here.
Parked. Not a pass.
Date and purpose required.
Do not touch. Outflow as do-not-contact.
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.
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.
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.
They ship a device. You license the runtime that sits inside it.
Hunt · OEM / Product · Head of modules / hardware · Partnerships / BD
You run the control plane. They consume it. Not an embed.
Hunt · VP Cloud / Ops · Head of Product · Partnerships
They keep the application. You sit in a layer they will not staff.
Hunt · CTO / VP Engineering · Head of Product · Partnerships
You sell the product. They are a rival, a partner, or a buyer.
Hunt · Head of Product · Partnerships · CTO
You sell the device. Software is the attach, not the camera you displace.
Hunt · Product / hardware · Partnerships / BD · Sales engineering
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
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.
Licensed into their binary or device. They keep the product.
They call us. We are a service, not a library in the box.
We sit inside their application as an extension they list or load.
Adjacency via a rail they already speak — MQTT, ONVIF, RTSP, not a new SKU.
Webhooks, streams, fan-out. The leak is compute or idle video, not a camera.
We operate next to their on-prem or device stack. Only if they named a gap they will not staff.
They ship our unit under their name. Access and capacity still our commercial rules.
No technical attach this quarter. A meeting, not a runtime.
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.”
This catalog row is in play at a named project.
Possible — confirm a project, stack, or MOU before a SKU.
Does not fit this account this quarter. The X is the point.
Path only. Not live. Do not pitch.
Rolled up from the checks so the desk can see the ask this quarter.
A named project, SKU, MOU, or line at the account. If none, say so.
The catalog entry this desk leads with on this account — whatever units you defined. (A camera OEM’s happen to be managed, embed, SDK.)
The catalog capability that creates differentiation. Mention is not a live SKU.
Sourced economics only. Catalog hooks or cited public numbers — never invented.
Who we call, and the ask. Bound to the unit that scored Yes.
oem · direct
Will they buy, embed, or consume the commercial unit we sell?
oem · ecosystem
Which companies belong on our partner program shortlist?
oem · ecosystem
Marketplaces, cloud, SI, or OEM programs we attach through — not who we recruit.
oem · any seat
Who are the named players, and who is actually buying?
isv · direct
Named competitors: what they sell, to whom, and where they are weak.
isv · direct
Where are they exposed, and what motion do we run this quarter?
isv · any seat
Public signals of where they are heading.
isv · direct
Adjacent markets and accounts we can take from them.
isv · any seat
Size the opportunity honestly. Pass if the TAM is theatre.
isv · any seat
Strategic fit for an inbound or outbound deal.
agency · direct
Is this a real meeting, or a polite no?
agency · any seat
Right buyer, right motion, this quarter.
isv · ecosystem
Complementary ISVs, marketplaces, OEM programs, co-sell — not the rival we crush.
agency · ecosystem
Vendors we represent and agencies we attach through. A unit we can keep.
Are they more likely to license a component, or staff an equivalent team?
Younger firms moving fast tend to buy. Older small firms often build.
Wikipedia · Crunchbase · company site
Sub-50 with long tenure leans Build. Scale leans Buy.
LinkedIn · Crunchbase · company site
Open engineering seats can mean they will staff instead of license.
LinkedIn jobs · careers page
Existing OEM relationships are a Buy tell.
Company partners page · PR wires · LinkedIn
CPO leans Build. A PM in a small team leans Buy.
About / team · press quotes · LinkedIn
High engineering share of headcount leans Build.
LinkedIn · company site
How they sell (SaaS, perpetual, OEM, hardware) shapes the unit we can attach.
Pricing page · company site · G2
Is the company actually expanding, or just noisy?
Sustained hiring is a better growth tell than a press cycle.
LinkedIn · Crunchbase
Hiring intensity relative to headcount separates expansion from replacement.
LinkedIn jobs · careers page
Public ARR, filings, or credible press — never invent a number.
SEC · TechCrunch · company blog
New offices and regions are a motion cue, not vanity.
Company site · press · LinkedIn
Can they write a check this year?
Raised capital usually means they buy adjacent stack rather than staff it.
Crunchbase · TechCrunch · Forbes
A stale round with no revenue story is a Watch, not a Pursue.
Crunchbase · press
Listed issuers have a different check-writing motion than venture shops.
Company IR · Wikipedia · Crunchbase
Profitable operators buy differently than companies still raising to exist.
Filings · press · company site
Will they consume (and pay for) hosted infrastructure?
Named hyperscaler is a managed-unit cue. Absence is not a no — it may be embed.
Job posts · engineering blog · case studies
Self-hosted / air-gapped buyers are an embed motion, not a CPaaS no.
Product pages · docs · security page
Sovereignty and export-first posture change which commercial unit we lead with.
Trust center · docs · press
High usage is a managed-tier tell. Device-first shops often will not pay it.
Job posts · architecture blogs · partner pages
Do they have public legitimacy a partner can stand next to?
G2 / Capterra density is legitimacy, not a score to chase.
G2 · Capterra
Public logos show who already trusts them — and who we sit next to.
Customers page · case studies
Coverage quality beats volume. Ignore recycled SEO pages.
TechCrunch · trade press · Wikipedia
A missing trust page is a risk; a real one is a meeting opener.
Trust center · security page
Who they sell to shapes whether our unit attaches at OEM, ISV, or operator.
Website · G2 · LinkedIn
Is this a real operating company, or a slide deck?
Tenure plus scale separates operators from decks.
Wikipedia · Crunchbase · company site
A suite vs a single SKU changes the attach motion.
Product pages · G2 · LinkedIn
Who owns the buy (product, partnerships, engineering) is the first-meeting map.
LinkedIn · About page
Acquirers and acquirees have different check-writing and integration motions.
Press · Crunchbase · Wikipedia
Jurisdiction and region change residency, support, and who we introduce.
Company site · LinkedIn · Wikipedia
What can we attach to this quarter? Named work at the account — not a category lecture.
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
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
A live refresh, partnership, or replatform is a timing cue. Stale MOUs are Watch, not Pursue.
Newsroom · IR · trade press · LinkedIn
Product, partnerships, ODM program, or engineering — the first meeting is a person, not a logo.
About / team · press quotes · LinkedIn people