Onboarding Flow — Month 1

Good to know: aim for quick wins within a week, two at most. A win is 5–10 pages ranking on page 1, positions 1–5 — achievable even on a brand-new domain; see Part 1 §1.7 Speed-to-rank for why.

1. Research Call (day 1, wk 1): gather key data, clarify assumptions.
2. Strategy Kickoff (day 4/5, wk 1): present strategy, get alignment.
3. Publish (wk 2): first landing pages and blog posts go live; collect data.
4. Collect Data: verify indexing and rankings on Google and ChatGPT.
5. Calibrate: analyze what ranked; plan next month from data.

​

Before project confirmation

• Send out contract
• Send out invoice
• Set up Slack channels
  • <company>-synscribe: direct client communication
  • internal-<company>: internal coordination

​

Before Day 1

• Create the organisation on Synscribe; see how-to: 2.1.1
• Create the client project on Linear
  • Hook the Linear project up to the internal-<company> Slack channel
• Company research on the website (company-explorer skill); see how-to: 2.1.2
• Initialize Pi: set up memory and soul; see how-to: 2.1.1
• Parse the sales-call transcript into a Pi memory file
• Build a product bible (product-bible skill); see how-to: 2.1.2
• Plan horizontal (/uses) and vertical (/feature) landing-page pillars (landing-page-pillar-management skill); see how-to: 2.3.1 and theory: 1.6
• Keyword research to expand the seed keywords (keyword-exploration skill); see how-to: 2.2.1
• Add keywords to the dashboard, tagged Core, Fringe, <month>, Alternative, etc.
• Note key assumptions and questions to clarify with the client

The sales-call transcripts carry most of the strategy. The client usually names focus keywords and areas of interest for month 1, so extract seed keywords from them. Once the client confirms with payment, kick off the background research.

​

Week 1 — Research & Strategy

​

Day 1 — Research Call

• Clarify key assumptions and questions with the client
• Send the client the onboarding checklist:
  • Send competitors (Direct, Incumbent, Adjacent) for verification
  • Send the feature inventory from the product bible for verification; ask for images
  • Request access to: web platform (GitHub / Framer / Webflow / WordPress / …), Google Search Console, PostHog (or set one up; Mixpanel or another analytics platform is fine)
• Update Pi’s memory with the call transcript / material
• Run through Google Search Console for other keyword opportunities

​

Day 2 — Formulate execution strategy

• Generate the landing-page prompt + JSON schema
  • Ask Pi to plan the /uses landing page (the default template usually works)
  • Ask Pi to visualize it in ASCII; iterate
  • Ask Pi to create a sample page
  • Ask Pi to create the landing-page pillar
• Wireframe the landing page
  • Decide static vs dynamic components
  • Get assets from the client, or generate placeholders. Don’t wait on assets
• Pick the first 10–20 landing-page keywords
• Generate the first 5 landing pages (prioritize by the product’s unique edge and cannibalization risk); see how-to: 2.3.2
• Quick quality audit on the landing pages:
  • Primary keyword is the first word of the meta title
  • Primary keyword (or variant) in the meta description
  • Primary keyword is the first word of the H1
  • Primary keyword (or variant) in the first paragraph

• Competitor research
• Keywords listed for blog posts and landing pages
• A single-page wireframe with fake data (Excalidraw)
• A sample blog post
• The month-1 plan (next 3 weeks): typically wk 2 execute pSEO landing pages plus blogs; wk 3 set up PostHog; wk 4 review

​

Day 4/5 — Strategy Kickoff

• Walk the plan and get alignment
• Set a recurring monthly review date on the calendar
  • Add a reminder ≥3 days before to prep review materials and review with Raymond
• Adjust the strategy if needed

• Set up the company featured-image generator; see how-to: Set up image generator 🎥
• Set up refiners (refiner-management). Typical defaults: Brand positioning, CTA, FAQ, TLDR. See how-to: 2.1.7 🎥
• Generate 3 blog posts with the refiners, starting with listicles or BOFU how-tos
• Verify the 3 posts: keyword is high-relevance/high-intent · title contains the keyword · summary mentions the company · CTA present and not overflowing · FAQ present and correct · competitor links removed and company positioned first · all links (incl. CTA) work

​

Week 2 — Publish & Collect Data

​

Day 1 — First blog posts live + pSEO page setup

• Publish the 3 blog posts; see how-to: 2.5.1
• Technical SEO audit (account-quality-control); see how-to: 2.5.2:
  • Canonical link correct · meta title = title · meta description = description · H1 = title
  • Featured image is the OG image (preferred) · OG image title set · table of contents present (preferred)
  • Headings make sense (Ahrefs toolbar > Content)
  • BlogPosting/Article JSON-LD present · FAQ JSON-LD present (future, no FAQ export yet)
• Fix all non-optional findings
• Create a Linear ticket for deferred tasks (human-only tool)
• Re-audit to verify fixes
• Manually index the 3 posts on GSC; see how-to: 2.5.3

• Set up the pSEO template on the client’s site, starting with /uses/<slug> before the hub page
  • Set up export from the landing-page pillar (JSON for code frontends, CSV for CMS like Webflow/Framer/WordPress); see how-to: 2.3.4
  • Export the pillar data and map the page to it
• Ship the first 5 pSEO pages
  • Get top-5 and top-10 keywords (keyword-research-planning)
  • Publish the top 5
• Technical SEO audit on pSEO pages (as above, plus): FAQ JSON-LD must be present; (hub page) all elements DOM-readable but can be hidden
• Fix issues and re-audit
• Submit the 5 pSEO pages to GSC for indexing
• Verify sitemap.xml contains the posts and landing pages
• Submit the sitemap to both GSC and Bing Webmaster

​

Day 2 — GSC verification + ops + IndexNow

• Search all targeted keywords from day 1; try a few variants
• On ChatGPT, search the targeted keywords and capture every response featuring client pages
• Screenshot and highlight ranked pages
• If more than 5 different pages are ranking (ideally across more than 5 terms), share in the client Slack to celebrate
• Publish more blog posts (per schedule)
• Publish all remaining landing pages
• Index the landing pages and posts on GSC (index as many as you can; track the backlog)
  • Create a Linear ticket for the indexing backlog
• Ask the BPO teammate to help publish on the schedule you define in #bpo; see roles: 3.14
  • If it’s a new flow, record a Loom showing them how
• Set up IndexNow for the site and run it for all existing pages; see how-to: 2.1.5 🎥

​

Day 3 — GSC verification (day-2 check)

• Re-check keywords (Google + ChatGPT) from days 1–2
  • More than 5 different pages ranking: share with client
  • Fewer: raise with Raymond (diagnostics below)
• If fewer than 5 pages are ranking, run diagnostics and save to Notion:
  • Log domain DR · GSC indexing status of published pages · site:<url> for each page · Bing Webmaster index status
  • Share findings with Raymond (medium priority)
• Evaluate recovery actions (with Raymond): footer internal links to hub and specific LPs · announcement/listicle post on Wisp · press release announcement · Medium post · other link-building. See 3.9 and 3.10

​

Day 4 — Quality Gate

STRICT: if we don’t have >5 pages on Google/ChatGPT by now, get Raymond’s attention immediately (high priority). This is achievable even for brand-new domains. See 3.6 Quality Gate.

​

Week 3 — Analytics Setup & Monitoring

​

Day 1 — Set up PostHog

• Get a PostHog account (team’s or register + invite them)
• Install PostHog on the site
• Turn on session recording; verify (disable ad-block to test)
• Set up actions to track:
  • Soft conversions: click demo, click sign up
  • Conversion events: form submission, account setup (optional)
  • Hard conversion: payment (optional)
• Set up the Pages with AI Traffic insight (SQL below)
• Set up the Sitewide Conversion Funnel to baseline conversion
• Set up a pillar-based conversion funnel for each content pillar (blog, uses, feature, …)

​

Day 3 — Check in on PostHog

• Verify data is collecting
• Observe early results in Pages with AI Traffic
• No data: debug (exception flow; loop Raymond in, medium priority)

​

Week 4 — Review Prep & Calibration

​

Day 1 — Start preparing review materials

• Celebrate the wins; congratulate the client
• Debug internally what could be better; note action items for next cycle
• If you notice SOP gaps, raise them and update the SOP
• Prepare proposals for the coming months: additional keywords · the /feature pillar (vertical LPs) · adjustments to existing content · better attribution · other opportunities

​

Reference — PostHog: Pages with AI Traffic (SQL)

SELECT properties.$current_url AS page_url, count() AS event_count
FROM events
WHERE event = '$pageview'
  AND (
    properties.$referrer LIKE '%chatgpt.com%'
    OR properties.$referrer LIKE '%perplexity.ai%'
    OR properties.$referrer LIKE '%claude.ai%'
    OR properties.$referrer LIKE '%gemini.google.com%'
  )
  AND timestamp >= now() - INTERVAL {variables.number_of_days} DAY
GROUP BY page_url
ORDER BY event_count DESC

Add Number of Days as a variable for it to work. This insight is central to how we prove AI-answer-engine traffic. See Part 1 §1.2 and §1.10 Attribution.

​

Reference — external tools (human-only, not via Pi)

​

Next / Related

• 3.2 Monthly planning flow: every cycle after this one opens here.
• 3.6 The Quality Gate: the Month-1 ranking checkpoint this flow builds toward.
• 3.7 Preparing client-review material · 3.8 Running the client review: the Week-4 review.
• Part 1 §1.7 Speed-to-rank: why the quick win is achievable.