Getting the Most Out of Your Company Unlock Credits

Company unlocks are most valuable when you spend them with intention.

The goal is to reveal the right organizations at the right time, with enough context to decide what to do next. That context might help a maintainer understand adoption, a product team see where users are getting stuck, a community team find important downstream users, or a GTM team prioritize accounts that are already showing real usage.

The common thread is prioritization. Before using unlocks, take the time to narrow the audience you are trying to understand.

Filter first

Scarf gives you a lot of flexibility in how you define a segment before you unlock anything. You can filter down by the project, package, image, documentation path, geography, company size, industry, first seen date, last seen date, growth trend, saved account list, and other attributes that help separate meaningful activity from background noise.

That granularity matters. A broad list of discovered companies can be interesting, but a focused segment is much easier to act on. “Companies using this specific package in the last 30 days” is more useful than “companies that touched anything.” “Organizations from this target list that showed growing usage this month” is more useful than a generic export. For non-commercial users, the same idea applies: a maintainer might care about universities, public-sector organizations, foundations, or important ecosystem projects instead of sales accounts.

The filter is where most of the value gets created. Unlocking a company is much more useful when you already know why it belongs in the segment.

Size the segment before spending unlocks

Once you define a filter, Scarf shows the number of matching companies. That means you can size up an audience before committing unlocks to it.

This is helpful for basic planning. If one segment has 12 companies and another has 1,200, that tells you something before you spend anything. You can compare different audiences, adjust the filters, and decide whether the segment is specific enough to be useful, all without spending unlock credits just to learn whether a segment exists.

This is especially important when you have multiple possible motions. You might want to compare new adopters, companies with repeat usage, companies in a specific region, companies using a particular artifact, or companies already present in a saved list. Seeing the size of each segment helps you decide where more context is likely to be worth it.

Sort before you unlock

After the filter is set, the sorting order matters too.

If you sort the company table by most recently seen, the companies you unlock first are the ones with the freshest activity. If you sort by download volume, the unlocks go toward the companies showing the most usage. Depending on the question, you may want to prioritize first seen, last seen, total downloads, growth, or another signal.

This is a simple but important part of the workflow. Filtering defines the audience. Sorting decides the order in which you spend unlocks inside that audience.

The right order depends on the job. For a time-sensitive follow-up, recent activity may matter most. For roadmap or ecosystem research, total usage may be more useful. For account prioritization, you may want the companies that match your saved list and have the strongest usage signal. The unlock should inherit that priority.

Schedule unlocks when timing matters

Some signals are only valuable while they are fresh.

If you have a segment that matters every week or every month, schedule it. A scheduled unlock workflow can keep the right companies flowing into your process without someone remembering to manually check the table. That makes each unlock more useful because the information arrives while it can still influence what you do next.

For some teams, that means timely outreach. For others, it means knowing which docs are driving adoption, which users may need support, which ecosystems are picking up the project, or which organizations are newly depending on a package.

Keep confidence in the workflow

Signals vary a lot.

Some package activity reflects real product usage. Some is CI. Some is security scanning. Some is a dependency pulled through a build system. Some traffic comes from infrastructure that should be filtered out before anyone draws a conclusion.

The best unlock workflow combines filters, counts, sorting, and timing with a little judgment. You want to know why a company surfaced, how strong the signal is, whether the activity is recent, and whether it fits the segment you meant to investigate.

A practical way to start

Start with one project, package, image, or docs area that matters. Create a filter around the audience you care about. Look at the result count and compare it against a few adjacent segments. Once the segment feels right, sort the table by the signal that best matches your goal, then spend unlocks in that order.

If the segment will matter again, schedule it. A recurring unlock keeps the information timely and turns the segment into a workflow for staying close to meaningful adoption.

For some teams, that next action is outreach. For others, it is better documentation, support, roadmap input, sponsorship evidence, or simply a clearer understanding of where the project is being used.