One Startup A Day launch

Worked example throughout: RegLyr (Reg Layer). Substitute your project’s name/files.

​

Naming & domain

• Pick a name for the new project
  • Try to ensure the .com exists
  • Modifiers like tryName.com / getName.com are fine to keep the name short
  • Not trademarked / not confusable with adjacent companies
• Buy the domain
• Set domain auto-renewal OFF

​

Wisp setup (blog)

• Create the blog on Wisp
  • Billing: use SYNSCRIBE100OFF on the team plan (add 10 users)
  • Create the API key (Wisp > Settings > Team > API keys)
  • Get the blog id (Wisp > Setup)
• Set up the Wisp connector in Synscribe

​

Sniper repo — environment

• Set up the sniper env:
  • NEXT_PUBLIC_WISP_BLOG_ID = the blog id from above
  • SYNSCRIBE_ORG_ID = the Synscribe org id (from the URL)
  • SYNSCRIBE_API_TOKEN = create at Settings > Features > Add new
  • NEXT_PUBLIC_POSTHOG_KEY = create a new PostHog org under sam@synscribe.com, copy the project token
  • Copy the rest of the MAIL env vars from 1Password (.env for Zero to Launch)
• Set up the dev environment: pnpm i then pnpm dev

​

Keyword research & site design

read product bible, then list all the keywords in db, rank in order of importance
(see 2d keyword labelling framework). Give me top 5 and top 10 keywords to describe us.
remember to use customer language instead of founder speak.

• Save top 5, top 10, top 50 to memory
• (optional) Visualize the keyword groupings:

build out a dendrogram by grouping the keywords by proximity. I want to see the various
root keywords and how they expand down (to be more specific)

read product bible, then using the landing page management skill, help me plan the vertical
'feature' landing page pillar. Each page should map to an item on the feature inventory.

• Ensure the keyword doesn’t optimize for the horizontal keywords; the goal here is to go deep into one feature
• Ask for a sample page, e.g. give me an example of how the '[Feature Name]' page content could look like

​

Styling & customizing the homepage

• Export the research artifacts from Pi into the project’s ./project folder:
  • Product bible · Homepage copy · Core keywords
• Prompt Claude (plan mode) to read them and customize site.json:

ok now change the project to another company called [Name] ([expansion]). Read these files
and customize the site.json. You will want to explore how it is used to configure the project
sitewide.

  [project]/project/[client]-product-bible.md
  [project]/project/[client]-homepage-copy.md
  [project]/project/[client]-core-keywords.md

• Replace branding images: src/app/icon.png, public/logo.png, public/logo-full.png

​

Known issues with the sniper repo (fixes)

• Wisp blog id hardcoded; connect it to the env:
  • In Claude Code: seemed like the wisp blog id was hardcoded and not using NEXT_PUBLIC_WISP_BLOG_ID. connect it to use the env
  • Follow up: remove siteJson.blog.blogId entirely
• PostHog not tracking page views; debug
• Contact form does not track visitor context; wire the journey trace (2.6.2)

​

Blog content creation

• List all the links before creating refiners (Contact/demo link, sign-up link); see refiners
• Generate 5 blogs, read through, and check the links:
  • No broken links
  • Blog reads OK