You don't need a source inside a competitor's revenue team to know how they sell. The sales motion is baked into every public surface of the product: what the pricing page shows, what happens when you click the main button, what the contract language says, and how much of the docs you can read before you have to talk to anyone. Read five public artifacts in order and you can classify the motion more confidently than most of their own new hires could in month one.
The five artifacts that give it away
Start with the pricing page. Published numbers, visible tiers, a calculator — that's a company that has decided price is not a negotiation. A page that replaces numbers with "Contact us" or "Request a demo" is a company that needs a human in the loop before you see what anything costs, usually because the price varies enough by deal that a fixed number would scare off small buyers or leave money on the table with large ones.
Then look at the buying flow itself. Can you get into a working account with an email and a credit card, or is the only path a form that asks for company size and routes you to a scheduled call? Self-serve signup is a bet that the product can sell itself in one sitting. A gated demo is a bet that it can't, or that the deal size justifies a human closing it.
Contract language is the third tell, often sitting in plain sight in the terms of service or order form: month-to-month with cancellation anytime, versus a minimum term, a minimum seat count, or a master service agreement. Monthly, cancel-anytime pricing means the company re-earns your business every month. Annual-only means they're underwriting risk with a signature, betting on renewal and expansion later.
Fourth, check how much of the product you can evaluate without talking to anyone: public docs, a real changelog, maybe a status page. Companies that publish this material expect technical buyers to self-qualify before a rep ever gets involved. Companies that gate it want a person controlling the narrative through a longer, guided evaluation.
Fifth, the security or trust page. A public page with a SOC 2 badge, a subprocessor list, and a data-residency FAQ exists because buyers with procurement teams keep asking the same six questions, so the company answers them once, publicly, instead of on every call. A thin "we take security seriously" paragraph, or no page at all, usually means nobody's procurement team has demanded one yet.
What the pattern tells you about their business
None of these artifacts is decisive alone. Together, they sketch a business model:
| Signal | Self-serve pattern | Sales-led pattern |
|---|---|---|
| Pricing page | Published, tiered | "Contact us" |
| Buying flow | Signup plus card | Form plus scheduled call |
| Contract | Monthly, cancel anytime | Annual, minimum term |
| Docs | Public, indexed | Gated or thin |
| Security page | Thin or absent | Detailed, with SOC 2 badge |
A competitor in the left column has almost certainly built the product to sell itself: a low average deal size, a support model that leans on documentation instead of headcount, and small teams buying on a card with no purchase order. A competitor in the right column has a sales team owning unit economics, a longer cycle, and customers who expect an implementation partner rather than a checkout page. Crayon and Klue, for instance, are described in buyer guides as sales-led, annual-contract products that don't publish pricing — a pattern that fits the right column, whatever else is true about either.
Selling into the gap
Once you know which column a competitor sits in, the pitch writes itself around what their motion makes painful.
If they're sales-led and you're not, your best prospects are the ones who already resent the process: a buyer who wants to try something this afternoon, not book a fifteen-minute intro call to be told a price. Say so directly in comparison content. "No calls, no demos, the price is on the page" is a real answer to a real frustration, not a slogan.
If they're self-serve and you're sales-led, your opening looks different: buyers who need SSO, a signed data processing agreement, a security review, and one invoice for two hundred seats will bounce off a self-serve competitor's checkout, because that flow was never built for procurement. Lead with the parts of your process built specifically to survive a security questionnaire.
Don't guess at any of this — log the classification like any other competitive fact, with the artifacts and the date you checked them, on a standard template so the next person isn't re-deriving it from scratch. Canopy pulls a competitor's pricing page, signup flow, and reviews into one profile, which turns this classification into a five-minute read instead of six browser tabs.
What this exercise won't tell you is whether the motion is about to change. That's a live read, not a static one, and it deserves its own process. This is just the snapshot you need before you can notice the shift.