docs(audiences): add Trial plan segment limit and CSV no-row-cap to plan availability

[george-dilthey]

What changed

Added two pieces of plan-availability information to docs/audiences.md:

1. Trial workspaces can create up to 250 audience segments — this limit was completely absent from the plan availability note, which listed what Trial/Launch can import but said nothing about how many segments they can build.
2. There is no row cap on CSV imports to Audiences on any plan — directly answers whether a 10,000-row list can be uploaded without hitting a limit.

Both facts are appended to the existing Plan availability paragraph on line 9, in one sentence.

Why

Intercom conversation #215475060233877: a Trial-plan customer (james park) asked "how many can upload audience companies rows in trial plan? I already have a above 10,000 rows buyer list." Fin escalated because the docs said nothing about row caps or segment limits for Trial — only that CRM/DW sync requires Growth. Support agent Adhvita replied: "Trial supports up to 250 audience segments (that's the number of audiences you can build, not a limit on rows within one). On the trial plan you can upload company lists into Audiences via CSV with no separate row cap on imports, so your 10,000+ rows from Apollo will go in without issue."

Neither of those facts appeared in the docs, so Fin had no basis to answer and escalated.

The deduplication-scope question (dedup doesn't reach regular Clay tables) from the same conversation is already covered by open PR #1547, which adds a dedicated FAQ — that is not repeated here.

I evaluated all four open PRs on docs/audiences.md flagged by pre_pr_check:

• PR docs(audiences): add FAQ clarifying dedup scope — Audiences only, not Clay tables #1547: adds a dedup FAQ (not segment limits or row caps) → my change is materially new
• PR docs(audiences): document Salesforce custom object export limitation and workaround #1528: adds Salesforce custom object export FAQ (unrelated) → my change is materially new
• PR docs(audiences): add field-filter warning to Snowflake and BigQuery import steps #1507: adds field-mapping notes for Snowflake/BigQuery (unrelated) → my change is materially new
• PR docs(audiences): add Databricks as beta import source #1485: adds Databricks import section (unrelated) → my change is materially new

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/w28k1kwz/inbox/conversation/215475060233877
• Verifier PASS — 250-segment limit: clay-base/libs/shared/src/feature-flags/featureFlags.ts:323 (GLOBAL_FEATURE_FLAG_DEFAULTS sets AudienceSegmentLimit: 250); Trial plan (clay-base/libs/shared/src/billing/plan.ts:101-121) does not override, so it inherits 250; enforced at clay-base/apps/api/v3/audiences/services/audience-segment-limit.service.ts:26-39
• Verifier PASS — no row cap on CSV: clay-base/apps/api/v3/audiences/services/audience-record-limit.service.ts:160-166 — getCountedImportBigSource returns null for AudienceImportSourceType.Csv, meaning CSV is never counted against the record limit; Slack #workstream-pricing (2026-06-09): "All plans with access will have unlimited CPJ and CSV imports"

Uncertainties

None. Both claims are hard-coded and confirmed by the verifier with no feature flags or plan-tier gates.

Related observations

PR #1547 (open, docsbot/doc-1138-intercom-tag-0714-ef13917e) adds the dedup-scope FAQ from the same conversation. PR #1528, PR #1507, PR #1485 also touch docs/audiences.md on unrelated topics. All four will need to reconcile with this PR at merge time — this PR only edits line 9 of the plan availability paragraph, which none of the other four touch.

Closes DOC-1142

[linear-code]

DOC-1142