Client Onboarding Proposal

Client onboarding proposal

Produce the document an agency brings to the start of a client relationship: an honest read of where the client stands across SEO, AI search, and social — and a clear, scoped plan for what the agency will do. It pairs SE Ranking analysis (organic + AI visibility, competitive gaps, site health) with Planable's view of the client's current social performance.

Positioning. This is an onboarding / early-engagement proposal, not a cold pitch. It assumes the client's social pages are already connected in the Planable workspace so their real performance can be analysed. (Without that access, the social section can't be produced from data — only the SE Ranking side.)

Prerequisites

• SE Ranking MCP connected (Data API for research + audit; a project is optional, and an existing finished audit can be reused via PROJECT_listAudits instead of crawling).
• Planable MCP connected, with the client's workspace and connected social pages available.
• The user provides: client domain + brand, market/country (default us), 2–4 competitors, and the Planable workspace. Optionally the engagement goals (e.g. lead gen, brand, local).

Connector health check

Before doing anything else, verify both MCPs are reachable:

• SE Ranking: call DATA_getSubscription. If it fails or returns an auth error, stop immediately and tell the user:

  "The SE Ranking connector isn't responding — please reconnect it before we continue. Setup guide: https://seranking.com/api/integrations/mcp/"

• Planable: call list_workspaces. If it fails or returns an auth error, stop immediately and tell the user:

  "The Planable connector isn't responding — please reconnect it before we continue. Setup guide: https://help.planable.io/hc/en-us/articles/27538577098780-How-to-connect-Planable-MCP-to-your-AI-tools"

Only continue to the process steps below once both calls return a successful response.

Process

1. Scope the proposal

Confirm the client domain, competitors, the Planable workspace, and what the engagement is meant to achieve. Verify the workspace actually has the client's pages connected (list_pages) and check get_workspace_details for hasAnalytics — this gates the social section.

2. SEO + AI-search analysis (SE Ranking)

• Organic footprint: DATA_getDomainOverviewWorldwide + DATA_getDomainKeywords — traffic, top terms, trajectory. Highlight striking-distance terms (high volume, position 11–30) — they're the fastest wins.
• Competitive gaps: DATA_getDomainCompetitors + DATA_getDomainKeywordsComparison — what competitors capture that the client doesn't (discard junk/off-brand terms).
• Site health: reuse an existing audit (PROJECT_listAudits → getAuditReport) or run DATA_createStandardAudit → DATA_getAuditReport — health score and the issues holding pages back.
• AI visibility: DATA_getAiSearchBrand to resolve the brand, then DATA_getAiSearchOverview and DATA_getAiSearchLeaderboard vs competitors (query the leaderboard narrowly — see the ai-search skill's timeout note).
• Demand for content: DATA_getKeywordQuestions + DATA_getRelatedKeywords — proof there's an audience to win.
• Separate findings into quick wins (low effort, near-term) and strategic plays (higher effort, compounding).

3. Social baseline (Planable)

• list_pages(workspaceId) — the connected channels.
• get_page_metrics_summary(workspaceId, pageIds, startDate, endDate) — account-level reach: audience (followers), total page impressions, and engagement rate. This is the size-of-presence number.
• get_post_metrics_summary(workspaceId, pageIds, startDate, endDate) — published-content performance in the window (impressions/engagement of the posts). These two impression figures are different scopes (page reach vs post reach) — report them separately and don't add or conflate them.
• get_post_metrics(workspaceId, pageIds, ..., limit: 5) — current top posts (what already resonates).
• list_posts(workspaceId, ...) — current cadence and how much is actually scheduled vs idle.
• Read it as a baseline: cadence, engagement rate, platform mix, and the obvious gaps.