МАТЧАСТЬ / AGENCY WORKSPACE / DOCUMENT 37 / 02.09.2026

Agency Workspace

Как превратить «Матчасть» в рабочую систему для PR-, SEO-, SMM-, content-, digital- и GEO/AEO-агентств, которые ведут десятки клиентов одновременно. Документ определяет многоклиентскую архитектуру, pitch-workspaces, client workspaces, delegated access, shared credits, payer/advertiser separation, массовые статусы публикаций, AI Visibility, Next Best Actions, отчёты, white-label, client access, team roles, billing, capacity, audit и границы между агентством, конечным брендом и самой «Матчастью».

Agency ≠ Ownerагентство получает делегированные права, но не становится владельцем entity клиента

Pitch → Clientкороткий аудит prospective client можно превратить в долгий рабочий workspace

One Portfolioодин dashboard для десятков компаний, заказов, отчётов и рекомендаций

Shared creditsединый commercial pool с обязательной привязкой каждой операции к конечному клиенту

1. Главное решение

Agency Workspace становится отдельным коммерческим режимом «Матчасти», а не просто аккаунтом с большим числом пользователей. Агентство получает portfolio-level управление клиентами, pitch workspaces, shared credits, массовые заказы, единый billing, client access, отчёты и Next Best Action queue. При этом каждая компания, публикация, advertiser, billing entity и verification state остаются отдельными объектами.

AGENCY ORGANIZATION │ ├─ Team members ├─ Shared credit pool ├─ Contracts / billing ├─ Pitch workspaces └─ Client workspaces │ ├─ Client entity / brand ├─ Delegated permissions ├─ Experts ├─ Publications ├─ AI Visibility ├─ Search Proof ├─ Reputation ├─ Recommendations └─ Reports CRITICAL: Agency never becomes the client company's entity owner.

2. Почему agency-first важен для «Матчасти»

В ICP уже зафиксировано: 20 хороших агентств, каждое из которых ведёт по нескольку клиентов и покупает публикации/мониторинг регулярно, могут дать платформе больше коммерческого объёма, чем тысячи бесплатных регистраций компаний. Агентство снижает CAC на каждую следующую компанию, повышает repeat и создаёт естественный спрос на bulk workflows.

Для «Матчасти» агентство — не просто customer segment. Это distribution channel + repeat buyer + operator layer.

3. Рыночный benchmark: Profound Agency Mode

В июле 2026 Profound документирует отдельный Agency Mode для организаций, которые ведут несколько брендов. Каждый brand workspace изолирован и имеет собственные настройки, данные и lifecycle. Profound отдельно выделяет short-term Pitch Workspaces и long-term Client Workspaces: prospective клиента можно быстро проаудировать, а после победы в тендере превратить pitch в полноценный клиентский workspace.

Это очень сильный паттерн для «Матчасти»: prospect audit → data-backed pitch → client conversion → ongoing monitoring.

4. Profound: portfolio isolation

Profound подчёркивает, что изменения в одном brand workspace не влияют на другие. Это снижает operational risk при масштабировании агентского портфеля.

Для «Матчасти» cross-client data leakage является критическим security failure: prompt sets, invoices, drafts, reports, discounts, advertiser data и recommendations не должны «протекать» между клиентами.

5. Profound: agency-level credit view

Agency Mode Profound показывает агентству активные workspaces, usage контрактных credits и сроки истечения pitch-workspaces. Admin agency users могут создавать новые pitch/client workspaces, пока доступны contract credits.

Это прямой benchmark для shared credits и workspace quota «Матчасти».

6. Рыночный benchmark: Semrush for Agencies

Semrush в 2026 году делает акцент на multi-client project management, shared workspace, role-based access, white-label reports, alerts, competitor benchmarks и custom dashboards. Enterprise-режим рассчитан на несколько брендов, регионов и команд, поддерживает team governance, audit logs, API, custom prompt tracking и enterprise SLA.

7. Semrush: важный негативный урок

Semrush закрыл старый Agency Growth Kit как bundled product; Client Portal и встроенный CRM были прекращены, а reporting был вынесен в более универсальный My Reports Suite.

Вывод: не строить в «Матчасти» полноценный CRM/Asana/agency ERP. Agency Workspace должен быть узким вокруг нашего продукта: clients, publications, monitoring, recommendations, billing and reports.

8. Agency Workspace не CRM

WE OWN: client workspaces publication pipeline AI/Search measurement recommendations credits billing reports permissions WE DO NOT OWN: sales CRM full task management time tracking agency employees client email inbox general project management accounting ERP.

9. Основная иерархия

Agency Organization Client Account 1 └─ Brand / Company entity Client Account 2 └─ Brand / Company entity Client Account 3 └─ Brand / Company entity One company may: work with different agencies over time Therefore: workspace relationship is temporal, not identity ownership.

10. Agency Organization

agency_id legal/billing profile display name domain verified agency entity optional team roles contracts credit pools workspace limits report branding settings audit.

11. Client Workspace

workspace_id agency_id client_entity_id brand_ids[] billing policy advertiser entity delegation status prompt sets competitors publications reports recommendations team members client guests created_at closed_at.

12. Client entity отдельно от workspace

Organization entity существует независимо. Если клиент прекращает работу с агентством, agency workspace закрывается, а verified entity, public profile и publications остаются.

13. Delegated permission

Client entity owner/admin grants: agency_id scope valid_from valid_to revocable approved_by evidence status.

14. Делегирование не ownership

В интерфейсе нельзя писать «Агентство владеет компанией Acme». Правильный термин: «Агентству предоставлен доступ к управлению профилем/публикациями».

15. Какие права можно делегировать

Scope	Что позволяет
PROFILE_VIEW	Смотреть данные и verification state
PROFILE_EDIT	Предлагать изменения фактов
PUBLICATION_CREATE	Создавать drafts/orders
PUBLICATION_SUBMIT	Отправлять в moderation
VISIBILITY_VIEW	Смотреть Search/AI reports
VISIBILITY_CONFIG	Управлять prompts/competitors within policy
REPUTATION_MANAGE	Работать с references/cases/media portfolio
BILLING_USE_CREDITS	Расходовать agency pool на клиента
CLIENT_USERS_MANAGE	Приглашать client viewers/editors

16. Critical entity changes

Legal name INN official domain ownership/control director brand-owner relation Agency can: propose But: high-risk fields need entity verification workflow and/or client confirmation.

17. Agency cannot self-verify client ownership

Даже если agency платит за публикации, payment не делает его владельцем company entity.

18. Client claim flow

Agency creates workspace ↓ existing entity found ↓ agency requests delegated access ↓ client representative confirms ↓ scopes granted.

19. Pre-client pitch exception

For prospect: agency may create PITCH WORKSPACE based only on public data No: profile edit publication claim private client data without authority.

20. Pitch Workspace

Один из самых сильных agency acquisition mechanics.

Agency enters: prospect domain/company Mathchast: resolves entity builds public footprint search baseline AI visibility sample competitors source gaps next actions Output: pitch report.

21. Что Pitch Workspace может использовать

PUBLIC DATA ONLY: company public site Mathchast public entity public media public AI observations public search/market data agency-entered non-sensitive notes.

22. Чего Pitch Workspace не делает

No: claim company edit public profile send publications view private reports reuse other agency data import private analytics represent company as authorized.

23. Pitch lifespan

Default: 7 / 14 / 30 days depending plan At expiry: freeze new runs Keep: snapshot / pitch report according retention policy.

24. Promote Pitch → Client

WIN DEAL Pitch workspace → request client delegation → verify billing/advertiser → CLIENT WORKSPACE Preserve: baseline prompt set competitors pitch report history.

25. Это особенно ценно для Before/After

Pitch baseline может стать реальным pre-contract baseline, если collection method and cohort остаются comparable and client authorizes ongoing measurement.

26. Agency Portfolio Dashboard

CLIENTS Acme Health ✓ AI SoV 22% ↑ 2 recommendations HIGH Credits 3 Next report Sep 12 Beta Health ⚠ 1 publication in review Pricing fact issue Credits 0 Gamma Pitch Expires in 4d.

27. Главная задача portfolio dashboard

Показать «где агентству нужно внимание», а не 40 vanity charts.

28. Portfolio attention states

BLOCKED NEEDS_CLIENT NEEDS_AGENCY NEEDS_EDITOR READY MONITORING RISK OPPORTUNITY NO_ACTION.

29. Agency global queue

TASK/ATTENTION QUEUE: 3 publications need client evidence 2 invoices unpaid 4 recommendations HIGH 1 verification dispute 5 +30 reports ready 2 pitch workspaces expiring.

30. Не делать generic to-do list

Queue состоит только из actions, порождённых системой «Матчасти».

31. Multi-client search

Search by: company brand expert publication invoice report recommendation workspace ID.

32. Agency teams

Agency Admin Account Lead Strategist Editor Analyst Billing Viewer External Client Guest.

33. Role: Agency Admin

manage team workspace creation credit allocation billing overview global settings client invitations report branding audit access.

34. Role: Account Lead

selected clients: view/manage workflow submit publications recommendations reports client communication No: agency billing admin unless granted.

35. Role: Strategist

AI/Search prompt sets competitors Next Best Actions measurement plans reports No: refunds legal entity transfer.

36. Role: Agency Editor

draft/edit collect evidence submit moderation Cannot: approve Mathchast editorial moderation change disclosure refund verification outcome.

37. Role: Billing

credits orders invoices payment documents client billing tags No: content editing verification decisions.

38. Client Guest

Can see: own company only reports drafts/review requests billing if invited recommendations Cannot: other agency clients agency pricing margin agency internal notes shared credit pool totals unless agency chooses.

39. Agency internal vs client-visible notes

note.visibility: AGENCY_INTERNAL CLIENT_VISIBLE MATHCHAST_INTERNAL Never mix.

40. Why this matters

Account manager may write internal commercial notes that must never appear to client/editorial reviewers.

41. Client access model

Option A: agency-only operation Option B: client viewer Option C: client approver Option D: client co-editor Per workspace.

42. Client approval checkpoints

Facts quotes case data publication draft advertiser details monitoring plan report share Agency configures: who approves what.

43. But editorial moderation cannot be bypassed

Client approval means «клиент согласен с фактической частью», not «Матчасть обязана публиковать».

44. Shared Credits

Agency buys pool, then spends credits across authorized clients.

Agency: 10 Publish credits 5 Edit credits Client Acme: reserve 2 Publish Client Beta: consume 1 Edit Ledger: agency pool + workspace attribution + advertiser/client entity.

45. Credit pool data

credit_pool_id agency_id credit_type batch quantity expires_at contract pricing version remaining reserved consumed.

46. Agency shared credits ≠ anonymous credits

Каждое расходование обязательно связано с конечным client workspace и order.

47. Why

advertising/legal classification;
advertiser identification;
reporting;
unit economics;
client-level cost;
audit;
refund/credit return.

48. Credit allocation modes

OPEN POOL: any authorized account lead can use ALLOCATED: client budgets reserved APPROVAL: spend above threshold needs admin approval.

49. Client budget guardrails

Acme: monthly max 5 credits Beta: max 2 Gamma: requires approval. Agency admin controls.

50. Credits and expiration

Oldest eligible batch first unless contract says otherwise Portfolio dashboard: credits expiring 90/30/7 days.

51. Client cost centers

workspace: cost_center PO number internal agency project ID client contract ref Useful: reconciliation/export.

52. Agency markup

«Матчасть» не обязана знать, сколько agency перепродаёт услугу клиенту. Наш invoice агентству содержит нашу цену; agency's downstream commercial relationship remains external.

53. White-label reporting — важный вопрос

Semrush в 2026 предлагает white-label reports and branded shareable dashboards. Для агентств это стандартная потребность.

«Матчасть» должна поддержать co-branded / agency-branded report presentation, но не скрывать provenance измерений.

54. White-label boundaries

Allowed: agency logo agency colors client logo cover agency contact custom intro Must remain: "Data/measurement by Mathchast" methodology source labels Mathchast publication URLs legal disclosure.

55. Почему не полный invisible white-label

Если агентство может убрать источник methodology and publisher identity, клиенты перестают понимать, откуда взялись метрики и публикации.

56. Recommended mode

CO-BRANDED: AgencyName × Матчасть AI Visibility Report for Acme or: Agency-branded cover "Measurement powered by Mathchast" inside/footer.

57. Client dashboard white-label

P2: custom subdomain/portal branding possible, but core provenance and URLs remain visible.

58. Report templates

Pitch Audit Publication +30 AI Visibility Monthly Search Proof Reputation Campaign Before/After Executive Quarterly.

59. Portfolio report

Agency internal: all clients AI visibility trend critical risks publications shipped credits next actions report status. Not shared to any single client.

60. Client report automation

Monthly: data cutoff generate analyst review optional agency review client delivery States: DRAFT READY_AGENCY APPROVED SENT.

61. Agency edit of report

Agency may add commentary and strategy, but cannot edit underlying metric values or methodology source fields.

62. Report comments

Mathchast data: immutable Agency commentary: editable/versioned Client notes: optional. This preserves: measurement integrity.

63. Pitch Reports

Prospect: Acme Show: public AI presence competitors sources 2–3 gaps example next actions No: claim private/internal data.

64. Pitch → Sales conversion tracking

Pitch created report viewed agency won/lost client workspace promoted first order Agency can mark: WON / LOST / NO_DECISION.

65. Не строим полный sales pipeline

Только outcome pitch workspace, не CRM stages from lead to contract negotiation.

66. Agency onboarding

1. Verify agency 2. Billing profile 3. Invite team 4. Create first client 5. Choose delegated/public pitch 6. Configure credits 7. Create report branding 8. First publication/monitoring.

67. Agency verification

Agency entity: domain legal identity corporate email optional portfolio/site Purpose: security/trust not public badge automatically.

68. Agency directory?

Profound и Semrush развивают partner directories, где verified/certified agencies могут получать leads. Это может стать поздним GTM layer, но не нужно для MVP.

P3: «Партнёры Матчасти» только после появления certification, client references и доказанных results. Не запускать directory как пустой каталог агентств.

69. Agency certification

Future: training methodology knowledge client references successful workflows policy compliance Not: pay fee → badge.

70. Client conflict

Company Acme already delegated to Agency A Agency B requests: pitch public audit okay private access no Client can: grant both or revoke A depending contract.

71. Multiple agencies simultaneously

Entity permission model может поддерживать несколько agencies с разными scopes, но P0 UI should keep it simple and warn client about overlapping rights.

72. No exclusive ownership by default

Agency A: publication scope Agency B: AI visibility scope Possible: if client authorizes.

73. Client changes agency

Revoke Agency A Grant Agency B Entity: unchanged Published assets: unchanged Historical reports: access policy defined Agency A: loses future private access.

74. Historical access after revocation

Agency retains its own billing/order records needed for accounting/audit, but loses client-private current data unless contract/legal retention requires otherwise.

75. Workspace closure

CLOSE: stop monitoring revoke agency scopes preserve orders/reports per retention return/unreserve eligible credits client entity persists.

76. Ownership of reports

Client report: belongs to workspace commercial relationship downloadable by authorized users Mathchast: retains measurement records according terms/privacy Agency: can retain delivered report according client contract.

77. Prompt set ownership

Agency-created prompts may contain proprietary strategy. They should remain private to workspace/agency, while generic anonymized templates may be reused only under clear terms.

78. Private agency notes not training data by default

Do not silently use confidential client strategy as cross-client recommendation input.

79. Cross-client learning

Allowed later: aggregated/de-identified patterns with terms/privacy Not: "Client A's secret prompts recommended to Client B".

80. Agency Prompt Templates

Agency can create: "B2B SaaS RU baseline" "Fintech UK category" "Agency pitch v3" Apply: as starting template per client Each client: creates own prompt set version.

81. Template ≠ linked live prompts

Editing template later should not silently rewrite historical client cohorts.

82. Competitor templates

Agency reusable competitor logic: manual list category rules But each client: locks competitor set for Before/After.

83. Bulk imports

P1: CSV clients CSV prompts CSV media URLs CSV experts Validation: entity resolution duplicates permissions errors.

84. Bulk publication creation

Allowed only as draft/order setup, not bulk autopublish.

Upload: 5 client briefs System: 5 separate publications 5 moderation workflows 5 advertiser records 5 legal classifications.

85. Never bulk-relax moderation

Agency volume does not create a bypass lane around editorial policy.

86. Agency SLA

Possible: priority support batch intake dedicated account contact capacity reservations Not: faster because fewer checks.

87. Reserved editorial capacity

Agency commits: 20 credits/month Mathchast may reserve: capacity units Useful: predictability Needs: Doc 30 capacity model.

88. Agency volume pricing

Potential: 10–20% discount for committed volume Only if: support/acquisition economics justify and quality remains same.

89. Agency plans — product hypothesis

Plan	Для кого	Что отличает
Agency Starter	2–5 clients	Shared credits, multi-client dashboard
Agency Pro	5–20 clients	Pitch workspaces, co-branded reports, advanced monitoring
Agency Scale	20+ clients	Committed volume, API/exports, SSO later, custom SLA

Не утверждённый прайс; конкретная monetization проверяется в Doc 38/GTM interviews.

90. Charge for seats?

Не делать seats главным revenue axis на старте. Agency value растёт от clients/workspaces/usage, а не от числа сотрудников.

91. Suggested pricing axes

commercial: publication credits monitoring workspaces prompt/run scope reporting pitch workspace quota agency volume commitment secondary: extra users enterprise governance.

92. Why not unlimited clients

Каждый active monitoring workspace создаёт real AI/search API cost and support load.

93. Pitch workspace credits

Agency plan includes: N active pitch audits/month or: pitch credits Converted to client: pitch credit partly/fully credited against paid setup later.

94. Clever acquisition mechanic

Можно дать агентству дешёвый/limited pitch audit, который автоматически превращается в первый baseline клиента после продажи.

95. Pitch abuse prevention

Limits: active pitch count prompt count run frequency duration public data only Prevent: using free pitch as perpetual monitoring.

96. Agency Client Setup

Step 1: company/domain Step 2: Pitch or Authorized Client? Step 3: entity resolution Step 4: brand/product Step 5: goals Step 6: competitors/prompts Step 7: team/access Step 8: billing/credits.

97. Default separation by client

Each workspace has: own: prompt sets competitors reports recommendations billing attribution media portfolio experts notes files client users.

98. Organization-level resources

Shared: agency team credit pool templates report branding contracts global billing audit plan limits.

99. Some Profound workflows are org-level, not isolated

Profound notes that certain Enterprise workflows/content/agent capabilities are organization-level and accessible across pitch/client workspaces. Для «Матчасти» это useful warning: by default, client-sensitive data must be isolated; org-level shared automation should use templates/config, not raw client data.

100. Global agency templates safe

Safe: report layout prompt template workflow role preset Risky: raw answers client facts private briefs unpublished content.

101. Agency audit log

workspace created delegation granted user invited credit reserved order created prompt changed competitor set changed report shared client access revoked refund manual adjustment.

102. Cross-client data access alert

Security monitoring should treat forbidden workspace access attempts as high-priority events.

103. Data scoping in backend

Every private object: organization_id workspace_id scope Authorization: server-side never trust frontend filters.

104. Row-level security?

PostgreSQL RLS can be considered as defense-in-depth for workspace data, but application authorization and tests remain mandatory.

105. Workspace IDs in analytics

AI run Search report publication order recommendation document all: workspace_id client_entity_id.

106. Public content does not become private

Published article: public platform object Workspace: holds management/report relation After agency revoked: article remains public.

107. Drafts are private

Draft access: workspace role only Mathchast editorial authorized client Other agency clients: never.

108. Files/evidence isolation

Contracts case evidence verification docs images reports storage path/key: workspace-scoped access signed audit.

109. White-label PDF leak prevention

Generation worker must receive one workspace dataset, not broad agency dataset with client name substituted at render time.

110. Client-level encryption keys?

Not needed MVP. Strong application isolation + object permissions + encrypted storage. Enterprise customer-managed keys later only if demanded.

111. SSO

P2/Enterprise: SAML/OIDC domain enforcement SCIM later MVP: secure email auth/MFA.

112. MFA

Agency Admin/Billing should require MFA; large portfolios create much bigger blast radius.

113. Agency offboarding employee

Remove user → revoke all workspace sessions → preserve actions/audit → reassign open items.

114. Client-side revocation

Client revokes agency → immediate permission removal → running private jobs stop → active public publications unaffected → billing items preserved.

115. Agency takeover dispute

Two agencies claim client Mathchast: does not decide by invoice size uses client/entity control evidence from Verification policy.

116. Advertiser / payer / subject separation

Agency Workspace must enforce this trio on every commercial order.

Payer: Agency LLC Advertiser: Acme LLC Subject: Acme Product X Operator: Agency user Publisher: Mathchast.

117. Legal classification per publication

Agency volume: cannot use one advertiser ID for all clients Each: correct advertiser/entity contract/reporting fields.

118. Agency billing statement

Monthly: Client Acme: 2 Publish 1 Visibility Client Beta: 1 Create Agency: total fees credits documents.

119. Client internal billing visibility

Agency chooses whether client guest sees Mathchast invoice/credit cost. Default: client sees service status, not agency wholesale commercial terms.

120. Closing docs

Mathchast: documents with agency payer Ad/compliance: stores final advertiser Client downstream invoice: agency responsibility.

121. Refund credit flow

Client order rejected → credit returns to agency pool or allocated client pool according original source batch Audit: workspace + order.

122. Agency monthly close

Credits: opening purchased reserved consumed returned expired closing Orders: by client Reports: delivered Invoices/docs: status.

123. Agency performance dashboard

Not only money: publications shipped median moderation time AI reports completed high recommendations acted client workspace health credit utilization.

124. Client success signal

For each client: last action next action measurement status renewal/monitoring state Useful: agency account management.

125. Renewal hint

«Monitoring ends in 7d» okay. «Client likely to churn 83%» not needed before real retention data.

126. Agency Next Best Action queue

HIGH: Acme security case Beta pricing correction Gamma external media gap Filters: client action type priority evidence due owner.

127. Assign recommendation

Agency strategist assigns: Account Lead / Client User Status: reviewing accepted briefing executing measuring.

128. Keep comments focused

Recommendation can have comments/activity; no need for general chat channels.

129. Agency templates for briefs

Agency may add: tone client questionnaire internal approval step Mathchast retains: required evidence editorial fields measurement fields.

130. Client approval before order?

Config: agency can spend independently or client approval required Useful: different contracts.

131. Spend approval thresholds

Any order: allowed > 20k: agency admin Create+Publish: client approval Custom research: both.

132. Compliance cannot be delegated away

Даже если agency/brand approved, Mathchast legal/editorial checks remain.

133. Bulk reporting

Generate: 20 monthly reports Each: own data cutoff own methodology own client branding Agency: review queue.

134. Agency report status view

Acme READY Beta DATA_DELAYED Gamma NEEDS_ANALYST Delta SENT Echo CLIENT_VIEWED.

135. Read receipt

P1: report viewed/downloaded event useful for account management, respecting privacy.

136. Scheduled reports

Monthly Quarterly +30 publication +60 Agency: can schedule within available monitoring plan.

137. Report consistency

Agency custom comments cannot overwrite core Mathchast numbers. White-label does not mean editable metrics.

138. Export formats

PDF CSV share link XLSX later API P2.

139. White-label PPTX?

P2 if agencies repeatedly request it. Not core MVP.

140. API future

GET workspaces GET publications GET reports GET recommendations GET metrics POST draft/order POST report comment POST external execution No: force publish override moderation verification outcome.

141. Webhooks future

PublicationPublished ReportReady RecommendationHigh PaymentFailed VerificationNeedsAction CreditLow.

142. Slack integration future

Agency workflows may value alerts, but build after core email/in-app. Do not require Slack for MVP.

143. Agency email digest

Weekly: 3 client risks 5 reports ready 2 credits expiring 4 high opportunities 1 pitch expiring [Open workspace]

144. Prospect audit workflow

Create pitch ↓ 24–48h-ish data collection depending connector ↓ review ↓ export pitch report ↓ agency presents ↓ won? YES → promote NO → archive.

Profound currently documents 24–48 hours to populate pitch/new prompt data; Mathchast timing depends on our own collection design.

145. Pitch report must disclose data limitations

Prospect report is observational public-data audit, not claim that agency already manages brand.

146. Pitch report branded by agency

Agency logo prospect logo "Audit prepared by Agency using Mathchast measurement" Data source/method: visible.

147. Pitch report commercial CTA

Suggested next: verified profile publication monitoring Agency controls: its proposal Mathchast: does not insert retail prices if agency wholesale workflow.

148. Wholesale vs direct pricing

Agency commercial agreement can have its own rate/credits. Client-facing public website prices should not automatically appear inside co-branded agency report.

149. Channel conflict

Mathchast should not use agency-provided client data to directly upsell the agency's client behind its back while delegated relationship is active.

150. Partner protection principle

Agency-sourced client: respect agency channel Mathchast may: send product/system notices required legal notices Commercial direct outreach: according explicit partner agreement.

151. What if client independently contacts Mathchast?

Commercial policy needed. Product must preserve data rights and permissions regardless of channel agreement.

152. Agency client portability

Client should not become hostage to agency. Verified entity and public publication history remain accessible/claimable by company.

153. Agency intellectual property

Agency-owned: private notes custom prompt templates report commentary internal strategy Client-specific work: rights per contract Mathchast: platform data/methodology according terms.

154. Data deletion

Delete workspace request: respect legal retention billing/audit client entity/public content measurement terms Do not: cascade-delete public company or published pages.

155. Client private data minimization

Agency Workspace should not encourage uploading whole CRM/export when a 10-row case evidence form is enough.

156. Enterprise security questionnaires

Later: DPA subprocessors data retention MFA/SSO audit backups incident policy Prepared in Docs 41–42.

157. Multi-region clients

One client workspace may have: RU brand program US program EU program Separate: prompt cohorts competitors regions reports.

158. Sub-brands/products

Client: Acme Inc Brands: Acme Acme Cloud Acme Secure Workspace: portfolio can track entity-specific visibility.

159. Do we create one workspace per product?

Default one client organization workspace with brand/product programs beneath. Separate workspace only if permissions/billing/team isolation genuinely require it.

160. Program object later

program: brand/product region goal prompt sets competitors reports campaigns.

161. Keep MVP simpler

P0: one main brand per client workspace + optional tracked products. Program layer P1/P2.

162. Publication ownership in agency flow

Author: client expert/company Operator: agency Publisher: Mathchast Sponsor/advertiser: client entity if applicable Never: agency shown as author unless it actually authors.

163. Agency-authored content

If agency genuinely authors: author can be agency/person subject client Still: commercial relationship disclosed correctly.

164. Agency internal draft attribution

created_by agency user content_author public editorial contributors Separate fields.

165. Client fact approval

Agency operator should be able to request structured fact approval from client without giving the client access to other workflow/admin areas.

166. Approval links

Secure client guest: review claims approve quotes upload evidence comment No need: full account initially if invite flow can be secure.

167. But critical changes require account verification

Magic link approval okay for bounded draft claim; entity ownership transfer requires stronger authentication.

168. Agency content calendar?

Не строить полноценный календарь SMM. Можно показывать publication due/publish/report dates внутри Mathchast workflow.

169. Timeline view

Sep 4 publish Acme Sep 7 baseline report Beta Sep 10 client approval Gamma Sep 12 +30 report Acme Useful: operations not general content calendar.

170. Agency capacity view

Agency commitments: 12 publications this month Mathchast slots: 8 scheduled 4 waiting evidence Credits: 15 remaining No: fake exact editor capacity exposure unless contractual.

171. Order batching

Agency chooses: 5 approved drafts Checkout: one agency payment 5 order items 5 client workspaces 5 moderation workflows.

172. Batch invoice

B2B agencies will value one invoice/package rather than five card payments.

173. But one invoice ≠ one publication object

Invoice: 50,000 Orders: Acme #1 Beta #2 Gamma #3... Each: own refund/state/legal classification.

174. Agency package commitment

20 publish credits 5 visibility workspaces 10 pitch audits Contract: 12 months Dashboard: usage by client.

175. Underutilization

Agency sees: unused credits expiring inactive clients Next Best: not automatically "spend all" but operational reminder.

176. Do not design for breakage

Revenue model cannot depend on agencies forgetting credits.

177. Agency analytics economics

Track: revenue discount support time active clients credits consumed monitoring cost reports CAC retention By agency account.

178. Agency LTV

Agency LTV should be measured on contribution, not gross top-line, because large discounts/support can make a big account unattractive.

179. Concentration risk

Top agency revenue share Top 5 share Warn: if one agency >25–30% long term strategic dependence rises.

Threshold is internal risk hypothesis, not accounting rule.

180. Agency client churn

Agency lost one client: workspace closes Agency account: continues Track: net client workspaces per agency.

181. Agency health metrics

active client workspaces pitch → client conversion publications/client monitoring attach recommendation action rate report delivery credit utilization.

182. Agency activation

Activated if: ≥2 client workspaces and ≥1 paid order and/or ≥1 monitoring report within onboarding period.

183. Why 2 clients

If agency only uses one client, it has not yet validated the multi-client product value.

184. Agency North Star candidate

Monthly active client workspaces that complete: measure → recommendation → action per agency.

185. Pitch conversion KPI

pitch created → pitch report ready → client won → workspace promoted → paid order.

186. Do not claim causality

If agency wins client after pitch report, Mathchast cannot claim it caused the sale. Track association/usefulness.

187. Client satisfaction

Ask agency: report usefulness workflow friction client understanding recommendation quality billing friction. Not: generic NPS only.

188. MVP onboarding interviews

20 agencies: How many clients? Who buys? How do they report? How many brands/user? Need white-label? Who approves? How bill clients? Current AI tools? Current publication workflow? Biggest repetitive manual work?

189. Agency segments

Segment	Need
PR agency	Media portfolio, publication, reports, reputation
SEO/GEO agency	Search Proof, AI prompts, gaps, before/after
Content agency	Briefs, publication workflow, measurement
SMM/digital	Client management, content proof, cross-channel reports
Integrated agency	Everything + governance/billing/API

190. Wedge agency

Первый wedge: PR/content/SEO/GEO agencies with 10–50+ active B2B/tech clients and an existing recurring content/reporting workflow.

191. Anti-ICP agencies

link builders dofollow resellers mass guest-post brokers "100 articles/month no moderation" fake review agencies guaranteed ChatGPT sellers → reject / low priority.

192. Agency value proposition

«Ведите публикации, Search Proof, AI Visibility и следующие действия по всем клиентам в одном месте — с общей оплатой, отдельными клиентскими пространствами и отчётами, которые можно отдавать заказчику.»

193. Pitch value proposition

«Соберите AI/Search аудит потенциального клиента до встречи, покажите конкретные пробелы и после выигрыша не начинайте измерение с нуля.»

194. Agency reporting value

Instead of: manual screenshots 8 tools PowerPoint copy-paste Mathchast: normalized data client workspace co-branded report next action.

195. Product packaging hypothesis

Agency Workspace: base organization feature Paid usage: credits monitoring clients pitch audits Premium: co-brand scheduled reports advanced permissions API SSO dedicated capacity.

196. Don't charge twice for basic client separation

Multi-client isolation is core agency functionality, not luxury enterprise add-on.

197. Client viewer pricing

Likely free/low-cost within reasonable limits. Charging per client viewer can discourage transparency and collaboration.

198. Additional agency seats

Can become secondary monetization above included seats, similar to market practice, but not primary launch driver.

199. Pitch workspace monetization

Options: included N/month pay-per-audit credits Best pilot: include limited quota to drive agency acquisition.

200. Agency portfolio export

CSV: client workspace state credits used publications AI metrics next action report date No: cross-client private raw answers unless agency authorized.

201. White-label governance

Report brand config: agency logo accent contact intro footer Immutable: methodology source attribution legal disclaimers publication URLs measurement provider Mathchast.

202. Enterprise audit log

Filter: user client action date financial permission publication report Export: CSV later.

203. Agency notifications

Immediate: critical client incident payment/refund verification dispute Daily/weekly: recommendations reports ready credits low pitch expiry.

204. Avoid alert flood

Portfolio-level deduplication and severity grouping are mandatory.

205. Agency mobile?

Responsive web sufficient MVP. Complex multi-client work is desktop-heavy.

206. Technical multi-tenancy

organization workspace resource Authorization: user membership + workspace role + entity delegation + resource policy.

207. Permission evaluation

Can user X edit profile Y? 1. user active? 2. agency member? 3. workspace member? 4. delegated scope PROFILE_EDIT? 5. field allowed? 6. entity verification policy? 7. not frozen/disputed?

208. Client entity freeze

Takeover/dispute: freeze high-risk edits Agency still: view reports work drafts until resolved.

209. Security test matrix

Agency A user: cannot fetch Agency B clients Agency A Acme user: cannot fetch Beta private data unless assigned Client Acme guest: cannot see agency pool or other clients Revoked user: all access denied.

210. Bulk endpoint security

Bulk exports are high-risk because one bad filter can leak an entire portfolio. Require strict authorization + audit + pagination/scoped query.

211. Data export watermark?

Enterprise later. Not core.

212. Public company entity conflict

Agency tries to create duplicate Acme Entity resolver: find existing → link workspace Do not: create parallel "agency Acme".

213. Duplicate brand prevention

Same entity resolution from Doc 19 applies to agency onboarding.

214. Agency client group

Holding: 3 legal entities 5 brands Workspace setup: group view later MVP: one primary organization with related brand entities.

215. Portfolio-level brand rollup

P2. Need clear entity rollup rules, especially for SoV.

216. Billing per advertiser

Agency pays one package but legal reporting stores: which advertiser used which publication. No anonymous pooled advertiser.

217. Reporting source access

Client can click: Mathchast methodology exact publication source URL prompt evidence where permitted White-label: does not remove evidence.

218. Agency comments on AI answers

"Client says old pricing fixed" → note → create correction action → remeasure Useful: context, not metric overwrite.

219. Client-provided external execution

Agency earns article elsewhere → add URL → media portfolio → watched source → before/after annotation.

220. Agency cross-channel campaign

Mathchast case external media client site update social distribution Campaign object: annotations measurement plan Report: campaign-level change.

221. Campaign object P1

campaign_id client goal interventions[] start/end measurement plan notes report.

222. Do not build campaign budget planner

Campaign object exists only to group interventions and measurement.

223. Agency reputation workflow

Agency can: invite references collect case confirmation add media URLs manage client response drafts Cannot: fake reviews approve own verification remove negative review.

224. Trust & Safety independence

Large agency account does not gain moderation privileges in reviews/reputation.

225. Agency review invitation templates

Neutral default fixed Agency can brand intro lightly Cannot: "Please leave us 5 stars" or suppress negative option.

226. Client identity in invite

"Acme, represented by Agency X, invites you through Mathchast..." Clear: who requested.

227. Agency renewal path

Monitoring client active monthly reports delivered recommendations acted → recurring workspace renewal Publication credits: separate.

228. Do not bundle everything into one giant annual plan immediately

Transactional-first remains valid. Agency can combine credits + recurring monitoring after usage is proven.

229. Agency trial

Pilot: 1–2 pitch workspaces 1 client workspace limited report no card required perhaps Goal: show multi-client value.

230. Trial abuse

domain verification agency email workspace limits no repeated same prospect limited prompt/run quota.

231. First 10 agency pilots

Target: PR/GEO/content agencies 5–30 clients Give: concierge onboarding Observe: pitch use client setup credits reports approval permission pain.

232. Pilot success signals

Agency creates ≥2 clients uses ≥1 shared credit creates ≥1 pitch delivers ≥1 report returns next month asks to add more clients.

233. Strongest product-market signal

Агентство само приводит второго и третьего клиента без отдельной продажи со стороны «Матчасти».

234. Weak signal

Agency loves pitch demo, but never converts prospect/client into paid workspace.

235. Agency unit economics

Revenue: credits monitoring premium features Variable: AI runs editorial support reports onboarding Contribution: per agency and per client workspace.

236. Concierge support trap

Одно agency account может создать 20x support load. Need self-service workspace templates before scaling.

237. Support levels

Starter: standard Pro: priority Scale: named success manager only if contract contribution supports.

238. Dedicated agency strategist?

Can be premium service, not included by default in software-like plan.

239. Agency documentation

Quickstart Roles Pitch mode Client delegation Credits Reports White-label Publication workflow AI methodology Billing Offboarding.

240. Agency Academy later

Useful for partner certification/GTM once methodology stabilizes.

241. Competitor benchmark summary

Pattern	Profound	Semrush	Mathchast decision
Multi-client workspaces	Strong agency mode	Multi-project	Core
Pitch workspace	Yes	Pitch/market data workflows	Core differentiator
White-label reporting	Agency focus	Strong	Co-branded P1
Client CRM	Not central	Old client portal/CRM discontinued	Do not build
AI visibility	Core	Core	Core
Publication marketplace/workflow	External workflows	Content tools	Mathchast-owned moat
Verified entity/reputation	Limited vs our model	Limited vs our model	Mathchast moat

242. Что входит в MVP

P0: Agency organization multi-client workspaces strict workspace isolation agency roles client guest/viewer delegated entity access shared credit ledger client attribution per order portfolio dashboard publication status queue AI/Search report access Next Best Action queue basic pitch workspace pitch → client promotion batch invoice/order attribution basic report branding audit log client offboarding/revocation.

243. P1

co-branded scheduled reports pitch quotas/credits prompt templates bulk CSV client approver role report comments weekly digest campaign object reputation workflows credit budgets agency-specific pricing report share links external execution URLs.

244. P2

API webhooks SSO advanced permissions program/sub-brand layer white-label portal agency exports advanced batch workflows client analytics connectors custom SLA automated billing integrations.

245. P3

partner certification agency directory/leads SCIM advanced enterprise governance portfolio recommendation optimization cross-client anonymized benchmarks partner co-marketing.

246. Что не входит в MVP

Не строим	Почему
Полный CRM	Не core; Semrush уже показал риск bundle sprawl
Asana/ClickUp replacement	Лишняя product surface
General SMM calendar	Не задача «Матчасти»
100% invisible white-label	Разрушает provenance/methodology
Agency ownership of client entity	Неверная identity model
Bulk moderation bypass	Quality/legal risk
Shared advertiser identity	Legal/data error
Unlimited monitoring clients	Real variable cost

247. Acceptance test: second client

Agency user assigned Acme only tries Beta private report Expected: 403/denied audit event Portfolio admin: can see both.

248. Acceptance test: client guest

Acme client user: sees Acme report approves quote Cannot: see agency credits Beta wholesale prices internal notes.

249. Acceptance test: entity delegation

Agency requests Acme domain change Scope PROFILE_EDIT exists But: official domain critical field Expected: verification/client confirmation not instant update.

250. Acceptance test: pitch

Agency creates prospect workspace without client permission Allowed: public audit Blocked: profile edit publication private data After client confirms: promote to Client Workspace.

251. Acceptance test: shared credits

10 credits Acme reserves 2 Beta consumes 1 Ledger: remaining 7 reserved 2 consumed 1 all attributable.

252. Acceptance test: refund

Acme publication rejected reserved/consumed credit returns according billing rule to original agency pool/batch Beta unaffected.

253. Acceptance test: white-label

Agency PDF: agency branding yes Still visible: Mathchast methodology data sources publication URLs legal disclosures.

254. Acceptance test: revocation

Client revokes agency Immediately: private access stops future monitoring authorization ends open critical actions freeze/reassign Remain: public publication entity billing audit.

255. Главный экран MVP

MY AGENCY CLIENTS 12 PITCHES 4 CREDITS 18 NEEDS ATTENTION • Acme — client evidence required • Beta — +30 report ready • Gamma — HIGH pricing fact issue • Delta — 2 credits expire in 30d NEXT OPPORTUNITIES • Acme security case • Beta external-media gap • Echo profile verification [Create client] [Create pitch]

256. Главная коммерческая формулировка

«Матчасть для агентств — один рабочий кабинет для внешнего присутствия всех клиентов: публикации, AI/Search monitoring, проверяемые отчёты, следующие действия и единая оплата — при строгом разделении клиентских данных.»

257. Второй ключевой message

«Создайте pitch-аудит до встречи с потенциальным клиентом, а после сделки превратите его в постоянный monitoring workspace без потери baseline.»

258. Решение документа

Утвердить Agency Workspace как отдельную multi-tenant organization layer. Агентство управляет несколькими изолированными client workspaces, получает shared credits, billing, reports, portfolio dashboard, Next Best Action queue и pitch-workspaces. Company/entity ownership не передаётся агентству: доступ всегда delegated, scope-based, temporal and revocable. Prospective clients можно анализировать в public-data Pitch Workspace без права редактировать entity или публиковать от имени компании; после подтверждения клиента pitch promotes into full workspace and can preserve baseline. Shared credits живут на agency ledger, но каждое reserve/consume привязано к client workspace, order, advertiser and entity. Reports могут быть agency/co-branded, но Mathchast methodology and provenance cannot be hidden. Client users видят только own workspace and never wholesale pricing/internal notes unless explicitly allowed. Agency roles, audit and cross-client authorization are core security features. P0 deliberately excludes CRM, generic project management, unlimited clients and moderation bypass. Главный moat агентского режима: agency can move client from pitch → verified entity → publication → Search/AI Proof → Next Best Action → repeat while keeping all data and billing organized in one portfolio.

259. Что этот документ разблокирует

Mathchast_37 Agency Workspace → Mathchast_38 Sales/GTM: first 100 clients → Mathchast_39 Brand/design → Mathchast_40 Technical architecture → Mathchast_41 Security/privacy/backups → Mathchast_42 Monitoring/SLA/incidents → Mathchast_43 MVP scope & roadmap

Источники исследования

Agency roles, scope model, shared-credit architecture, pitch limits, co-branded-report policy, plan concepts, portfolio states, permission rules, channel-protection principles and P0/P1/P2/P3 scope are project decisions of «Матчасть». Competitor research is used as product-pattern evidence, not as a requirement to reproduce vendor implementations.