Can Linear Customer Requests Weight Feedback by Revenue Without Salesforce?

Yes, you can weight Linear customer requests by revenue or tier without the Enterprise plan or the Salesforce integration. The Customer Requests filter and sort UI that lets you "segment and filter projects by request volume, customer tier, or revenue" ships on every plan, including Free. What's actually gated to Salesforce, and Salesforce is an add-on to Linear's Enterprise plan, is the automatic sync that keeps those tier and revenue fields populated for you.

Without that sync, the fields still exist on every Customer record. You just have to fill them in yourself, one of three ways: type the numbers in by hand when you create the customer, pull them in automatically through the Intercom integration (which populates the same Revenue, Tier, and Size fields Salesforce does), or push them over Linear's API. None of those three require Enterprise. What none of them do is keep the numbers current on their own the way a live CRM sync does.

What's gated, and what isn't

Linear's pricing page draws the line cleanly once you look at the actual feature table instead of the marketing copy. Customer Requests, including its revenue and tier filters, is listed as a Core feature on every plan, from Free through Enterprise. Salesforce sync sits only on Enterprise, sold as an add-on to that plan with its own license cost on top of the seat price. Business gets Zendesk and Intercom as included integrations; Salesforce isn't one of them at any tier below Enterprise.

That split matters because Salesforce isn't the only thing that can populate a Customer's Revenue, Tier, and Size fields. Linear's own customer-requests documentation says those fields "will be automatically populated if you use the Intercom integration, or can be filled when creating customers manually," and that any attribute left unmapped can have manual edits enabled for it, with the note that "attributes will always be editable via the Linear API regardless of this UI-specific setting." So a team on Intercom for support gets a second free path to the same data Salesforce would otherwise sync. A team on HubSpot, Close, or nothing in particular gets the manual path, where someone opens each Customer record and types in a tier by hand.

What that manual path looks like at real volume

Bramfield builds payroll software for employers who run mostly hourly workforces, and its product team tracks every request that comes in through Linear's Customer Requests feature. Once volume picked up, engineering started asking a fair question before triaging anything: which asks were coming from paying accounts worth protecting, and which were coming from trial signups who'd churn regardless of what shipped.

Nobody at Bramfield had ever set up Salesforce. Billing ran through Stripe and the CRM was HubSpot, so the operations lead, Priya Ramesh, did the honest thing available to her. She added a Tier field to Linear's customer records, set each one to Starter, Growth, or Enterprise by hand, and asked account managers to flag her when an account moved between tiers.

Priya, in the #product-ops Slack channel: Can whoever owns the Calloway Health account bump their tier to Enterprise in Linear? They just signed the annual contract.

That held up for about six weeks. Then a request came in tagged to three separate customer records for the same company, because a support rep, an AE, and Priya herself had each created a Customer entry on their own, and two of the three were still marked Starter from before the upgrade. When a director asked which open requests came from accounts worth more than $50k a year, nobody could answer without cross-referencing Linear against a HubSpot export by hand, and the export was already a month stale by the time anyone ran it.

Three failure points that show up as volume grows

The manual approach isn't wrong, it's just bounded by who remembers to update it. In roughly this order, three things tend to break first:

• Duplicate customer records. Nothing in Linear stops two people from creating separate Customer entries for the same company, and nothing merges them automatically once that happens.
• Stale tiers. A tier set at signup doesn't update itself at renewal, expansion, or downgrade, so the field silently drifts away from what's actually being billed.
• A second source of truth. The moment revenue data lives in HubSpot or Stripe and tier data lives in Linear, someone owns keeping the two in sync, and that job usually isn't anyone's actual job.

None of that is a reason to avoid Linear's Customer Requests feature. It's a reason to be honest about the cost of "weight by revenue" without a sync in place. That cost is an ongoing manual process that degrades under volume, the same way any spreadsheet-adjacent workaround does.

Attaching revenue automatically, without a Salesforce contract

This is the gap Modem fills, and we build Modem, which is reason enough to read the rest of this section with that in mind. Modem connects to Stripe directly, matching billing customers to the people and companies behind every piece of feedback, so a topic in Modem carries live plan and revenue context without anyone typing a tier into anything. For teams that do run Salesforce, Modem's Salesforce integration pulls accounts, contacts, opportunities, and users in as read-only context on top of that, no Enterprise Linear plan required on either end. Either source, or both together, feeds the same context graph.

From there, Modem's Linear integration creates or links issues with that context already attached. An account's revenue and plan sit next to the quote that generated the request, whether the request came in through Slack, a support ticket, or a sales call. Linear's own revenue and tier filters still work exactly as documented once the data's there; Modem is just one more way to keep the fields current without a dedicated CRM sync or a person doing it by hand. Pricing follows the same shape regardless of team size, with unlimited users on every plan and usage billed pay-as-you-go beyond what's included, not a per-seat Enterprise contract.

For teams already comparing dedicated revenue-weighting tools against the DIY route, the six best tools for prioritizing feedback by revenue lays out the tradeoffs across the category, not just Modem's corner of it.

The cheap fixes that hold up for a while

If Bramfield's situation sounds familiar and a CRM integration isn't in this quarter's budget, three unpaid changes fix most of the drift. Merge duplicate Customer records in Linear the moment you spot them. Put tier updates on the same checklist as the contract renewal process so they're not a separate step anyone forgets. Enable manual edits on the Tier and Revenue attributes so account owners can correct them directly instead of asking someone else to. That gets a small team most of the way there. Past a few hundred customer records, the syncing problem stops being a discipline problem and starts being worth automating, whether that automation is Salesforce, Modem, or something else that reads your actual CRM.