Scott AI growth playbook

Replace the stub with a one-screen product homepage that matches the YC description and the docs: the headline "The planning layer for teams that build with coding agents", three short blocks for Sync, Planspaces and PR design review, the one-line install command with a copy button, a docs link and a "Book a team demo" button. Remove the noindex, write a title and meta description, and add a share image and favicon. If shop estimations is a real new direction, give it its own page or domain (idea 21) instead of replacing the page that YC, the docs and the job posts all point to.

The homepage is the one URL every channel shares. A clear headline and a single next step turn visits that the launch, the YC listing and the hiring already create into installs, and let search engines and AI assistants describe Scott correctly. The page is already fast (real visitors pass Core Web Vitals), so the only thing missing is the message.

[ ] H1: The planning layer for teams that build with coding agents
[ ] One line on the problem: coding agents amplify the cost of bad planning
[ ] Three blocks: Sync, Planspaces, PR design review
[ ] Install command with copy button + quickstart link
[ ] Book a team demo button
[ ] Trust center link and SOC 2 line
[ ] Title, meta description, share image, favicon
[ ] Noindex removed; homepage submitted for indexing
[ ] Events: install copy, docs click, demo booked

• The stub is deliberate while the team tests a new direction

  Run the test on its own URL or domain so the product the docs and jobs describe still has a homepage.

• A quick page undersells the product

  Ship the holding page now and a designed page once the Design Engineer starts.

• Your websiteHomepage (fetched twice on November 10, 2026): title "Scott | Shop Estimations", H1 "Scott: we help shops with estimations", and one line, "Reachout to [email protected]". No link to the docs, the app, the install command, a demo, pricing or the team.Source
• PageSpeedMobile test on November 10, 2026: performance 100, accessibility 100 and best practices 100, but SEO 60 because the "Page is blocked from indexing"; no social share image or favicon; 7 requests and 108 KB with no third-party requests. Real visitors pass Core Web Vitals (75th percentile LCP 1.2 s, INP 45 ms, CLS 0).Source
• Y CombinatorCompany page: "The planning layer for teams that build with coding agents"; founded 2025, Fall 2025 batch, team of 3, New York City, status Active, website tryscott.ai.Source
• Y CombinatorLaunch post "Scott AI - Agentic Workspace for Software Spec Design" (122 upvotes): Scott "runs several coding agents side by side to expose their disagreements", shows where they disagree and exports a shareable plan to execution tools. Its calls to action are "Try Scott" (tryscott.ai) and "Apply for access" (www.tryscott.ai/apply), which returned 404 on November 10, 2026.Source
• DocsDocs home: "Sync agent work, share design intent, gather team feedback, and connect planspaces to code." The docs index lists Quickstart, Core concepts, Teams, Documents and versions, Code context, Comments, Reviews and approvals, Sharing, a For You inbox, Team pulse ("design intent, review health, and execution drift"), the agent plugin (Sync, Push, Pull), the GitHub App, PR design review, "The Scott Method" and "The Scott app".Source

Redirect /apply to a live page: either the install quickstart or a short team-access form that books a demo. Then update the launch post's links and check every other link Scott has published (launch, YC page, job posts, social bios) for dead ends.

Someone who clicks "Apply for access" has already decided they want Scott; a 404 loses them at the last step.

• Old applicants expect a waitlist reply

  Say on the page that access is open now and how to start.

• Y CombinatorLaunch post "Scott AI - Agentic Workspace for Software Spec Design" (122 upvotes): Scott "runs several coding agents side by side to expose their disagreements", shows where they disagree and exports a shareable plan to execution tools. Its calls to action are "Try Scott" (tryscott.ai) and "Apply for access" (www.tryscott.ai/apply), which returned 404 on November 10, 2026.Source
• Your websiteHomepage (fetched twice on November 10, 2026): title "Scott | Shop Estimations", H1 "Scott: we help shops with estimations", and one line, "Reachout to [email protected]". No link to the docs, the app, the install command, a demo, pricing or the team.Source

Add a robots.txt that allows crawling and points to a sitemap, a sitemap listing the homepage and the main product pages, and homepage and footer links to the docs' top pages. Check that the docs have their own sitemap and that docs pages link back to tryscott.ai.

Search engines and AI assistants find and trust pages through links and sitemaps; connecting the main domain and the docs lets queries like "coding agent planning tool" reach Scott.

• Docs pages compete with the homepage for brand searches

  Give the homepage the brand title and the docs page titles their topic.

• #1 Put the coding-agent planning product back on tryscott.ai: the homepage now says "we help shops with estimations" and blocks search engines

• Your websiteSite check (November 10, 2026): /robots.txt and /sitemap.xml return 404; no pricing page, blog, newsletter, careers page or social profile links; 0 Hacker News mentions and no news in the last 30 days. Change tracking shows the homepage headline moved from "Coding Agent Plan Mode with Super Powers" to "Scott: we help shops with estimations"; the domain was registered in October 2025.Source
• PageSpeedMobile test on November 10, 2026: performance 100, accessibility 100 and best practices 100, but SEO 60 because the "Page is blocked from indexing"; no social share image or favicon; 7 requests and 108 KB with no third-party requests. Real visitors pass Core Web Vitals (75th percentile LCP 1.2 s, INP 45 ms, CLS 0).Source
• DocsDocs home: "Sync agent work, share design intent, gather team feedback, and connect planspaces to code." The docs index lists Quickstart, Core concepts, Teams, Documents and versions, Code context, Comments, Reviews and approvals, Sharing, a For You inbox, Team pulse ("design intent, review health, and execution drift"), the agent plugin (Sync, Push, Pull), the GitHub App, PR design review, "The Scott Method" and "The Scott app".Source

Put the install command in a copyable block at the top of the homepage, with "Run scott sync and ask what your agents did this week" under it, and the list of supported agents. Add a 30-second clip of sync producing the first answer. Mirror the block at the top of the docs home.

Developer tools win when the first useful result comes quickly; showing the exact command and the result removes the guesswork about setup.

• Teams wary of piping a script to the shell

  Link the script source and offer a package-manager alternative.

• #1 Put the coding-agent planning product back on tryscott.ai: the homepage now says "we help shops with estimations" and blocks search engines

• DocsQuickstart: install with one command (curl -fsSL https://tryscott.ai/install | sh), run "scott sync" and open the URL it prints; works with five named coding agents "and other supported agent sessions"; pushing a thread creates a planspace with a shareable app.tryscott.ai/workspace URL; the GitHub App works best with access to all repositories; Scott says it is SOC 2 compliant, does not persist repository contents and fetches code into ephemeral sandboxes only when needed. No page in the docs mentions pricing, plans or seats.Source
• Your websiteHomepage (fetched twice on November 10, 2026): title "Scott | Shop Estimations", H1 "Scott: we help shops with estimations", and one line, "Reachout to [email protected]". No link to the docs, the app, the install command, a demo, pricing or the team.Source

Add a "What sync sends" section: the fields uploaded, what is stripped (keys and tokens, environment files), how long it is kept and who can see it. Ship a simple exclude list (by project path or session) and a dry-run flag that prints what would be uploaded. Link it from the homepage install block and the trust center.

A clear answer and a dry run let a cautious developer try Scott without a security review, and give the lead who does the review the document they need.

• Excluding too much weakens answers

  Show which excluded sessions would have helped and let users opt back in.

• DocsSync: reads local coding-agent sessions from the last 14 days and "uploads the relevant context to Scott"; the page does not describe what is excluded or redacted, or how to opt a session out.Source
• DocsQuickstart: install with one command (curl -fsSL https://tryscott.ai/install | sh), run "scott sync" and open the URL it prints; works with five named coding agents "and other supported agent sessions"; pushing a thread creates a planspace with a shareable app.tryscott.ai/workspace URL; the GitHub App works best with access to all repositories; Scott says it is SOC 2 compliant, does not persist repository contents and fetches code into ephemeral sandboxes only when needed. No page in the docs mentions pricing, plans or seats.Source

Publish tryscott.ai/security in plain HTML: SOC 2 status and report request, what the GitHub App can access and why it asks for all repositories, no persisted repository contents, ephemeral sandboxes, what sync uploads (idea 5), subprocessors and contact. Link it from the homepage, docs footer and the trust center.

Repository access is the biggest ask Scott makes; a readable answer shortens security review and shows up when buyers research.

• Claims overstate the audit scope

  Use the exact wording from the SOC 2 report.

• #5 Publish exactly what "scott sync" uploads, with an exclude list, before teams ask

• Trust centertrust.tryscott.ai is a Vanta trust center; read as page text it shows only the title "Scott AI Trust Center", with no certifications, policies or subprocessors.Source
• DocsQuickstart: install with one command (curl -fsSL https://tryscott.ai/install | sh), run "scott sync" and open the URL it prints; works with five named coding agents "and other supported agent sessions"; pushing a thread creates a planspace with a shareable app.tryscott.ai/workspace URL; the GitHub App works best with access to all repositories; Scott says it is SOC 2 compliant, does not persist repository contents and fetches code into ephemeral sandboxes only when needed. No page in the docs mentions pricing, plans or seats.Source

Publish a simple page: Free for one developer (sync, private planspaces), Team per editor seat (shared planspaces, reviews and approvals, PR design review), and Enterprise (idea 19). Make Commenter and Viewer seats free so reviewers never block adoption. Show a monthly and yearly price and a "book a demo" for larger teams.

Published prices let a team lead start without a sales call, and free reviewer seats match how planspaces spread: one author, many reviewers.

• Pricing too early limits learning

  Keep a generous free tier and revisit after one quarter.

• #1 Put the coding-agent planning product back on tryscott.ai: the homepage now says "we help shops with estimations" and blocks search engines

• DocsTeams and concepts: a planspace combines a chat, a living document, source context, comments, reviews, approvals and members; roles are Owner, Editor, Commenter and Viewer; reviews have pending, in progress, approved and rejected states. Nothing on invitations, seats or billing.Source
• Competitor researchRivals' own homepages: Traycer, "The <Nerve Center/> for Agentic Coding", a free open-source desktop app with a team plan at $16 per user a month billed yearly ($20 monthly) and 19 coding agents supported; Kiro, "Specs capture what you meant before code is written and verify results after"; CodeRabbit, "The future isn't writing code. It's reviewing it.", with 17K customers, 6M repositories and a claim to be the most installed AI app on GitHub.See the research Source
• Your websiteSite check (November 10, 2026): /robots.txt and /sitemap.xml return 404; no pricing page, blog, newsletter, careers page or social profile links; 0 Hacker News mentions and no news in the last 30 days. Change tracking shows the homepage headline moved from "Coding Agent Plan Mode with Super Powers" to "Scott: we help shops with estimations"; the domain was registered in October 2025.Source

Write three fair pages: Scott and Traycer (plan and approve vs run agents side by side), Scott and Kiro (works with the agents you already use vs one environment), Scott and CodeRabbit (checks PRs against the approved design vs code quality, and how they work together). Each has a short table, a "use both" section and the install block.

Buyers search for alternatives and comparisons once they know the category; clear pages also teach AI assistants where Scott fits.

• Claims about rivals go out of date

  Date each page and cite the rival's own page.

• #1 Put the coding-agent planning product back on tryscott.ai: the homepage now says "we help shops with estimations" and blocks search engines

• Competitor researchRivals' own homepages: Traycer, "The <Nerve Center/> for Agentic Coding", a free open-source desktop app with a team plan at $16 per user a month billed yearly ($20 monthly) and 19 coding agents supported; Kiro, "Specs capture what you meant before code is written and verify results after"; CodeRabbit, "The future isn't writing code. It's reviewing it.", with 17K customers, 6M repositories and a claim to be the most installed AI app on GitHub.See the research Source
• DocsPR design review: "The planspace URL is the contract between design intent and execution." Scott asks "Does this implementation match the design intent the team reviewed?", posts a GitHub comment on architectural alignment, missing requirements and drift, and links back to the planspace. It only runs when a PR includes a planspace URL and does not block merges or add a required status check by default.Source

At the end of the first sync, show three suggested threads (largest, most recent unfinished, most debated) with a one-click "push to planspace and invite a reviewer". Track time from install to first shared planspace and first review as the activation measure.

A concrete next step on the user's own work beats a blank prompt, and the first reviewer invite starts team adoption.

• Suggestions surface private work

  Pushing stays opt-in and private until the user shares.

• #4 Make the install command the main button, with a "first answer in five minutes" promise

• DocsQuickstart: install with one command (curl -fsSL https://tryscott.ai/install | sh), run "scott sync" and open the URL it prints; works with five named coding agents "and other supported agent sessions"; pushing a thread creates a planspace with a shareable app.tryscott.ai/workspace URL; the GitHub App works best with access to all repositories; Scott says it is SOC 2 compliant, does not persist repository contents and fetches code into ephemeral sandboxes only when needed. No page in the docs mentions pricing, plans or seats.Source
• DocsSync: reads local coding-agent sessions from the last 14 days and "uploads the relevant context to Scott"; the page does not describe what is excluded or redacted, or how to opt a session out.Source
• DocsTeams and concepts: a planspace combines a chat, a living document, source context, comments, reviews, approvals and members; roles are Owner, Editor, Commenter and Viewer; reviews have pending, in progress, approved and rejected states. Nothing on invitations, seats or billing.Source

On a planspace opened by someone without an account, add a light frame: "Reviewed with Scott: plan your next agent task the same way", one-click sign-in to comment, and after their first review a prompt to install and sync their own sessions. Count invites per active user and reviewer-to-author conversion as the loop's health.

Collaboration tools grow through the people invited to collaborate; the reviewer arrives with context and a reason to come back.

• Authors dislike branding on their work

  Keep it small and let paid teams turn it off.

• DocsQuickstart: install with one command (curl -fsSL https://tryscott.ai/install | sh), run "scott sync" and open the URL it prints; works with five named coding agents "and other supported agent sessions"; pushing a thread creates a planspace with a shareable app.tryscott.ai/workspace URL; the GitHub App works best with access to all repositories; Scott says it is SOC 2 compliant, does not persist repository contents and fetches code into ephemeral sandboxes only when needed. No page in the docs mentions pricing, plans or seats.Source
• DocsTeams and concepts: a planspace combines a chat, a living document, source context, comments, reviews, approvals and members; roles are Owner, Editor, Commenter and Viewer; reviews have pending, in progress, approved and rejected states. Nothing on invitations, seats or billing.Source

Add an optional "design drift" status check teams can make required, a short comment footer ("Plan linked with Scott: see the approved design"), and a gentle nudge on unlinked PRs in connected repositories: "No plan linked. Push your agent thread to Scott." Report how many PRs are linked per team as a usage measure.

Required checks make a tool part of the workflow, and PR comments put the product in front of the whole team every day.

• Nudges feel like spam

  Off by default, one per PR, easy to mute.

• DocsPR design review: "The planspace URL is the contract between design intent and execution." Scott asks "Does this implementation match the design intent the team reviewed?", posts a GitHub comment on architectural alignment, missing requirements and drift, and links back to the planspace. It only runs when a PR includes a planspace URL and does not block merges or add a required status check by default.Source

Send a Monday email per team: plans approved and shipped, PRs where drift was caught, reviews waiting longest, and one suggested next plan. Include a forwardable summary for the engineering manager.

A weekly digest brings people back and makes the tool's value visible to whoever approves the budget.

• Empty weeks look bad

  Skip the send when nothing happened and suggest a first plan instead.

• DocsDocs home: "Sync agent work, share design intent, gather team feedback, and connect planspaces to code." The docs index lists Quickstart, Core concepts, Teams, Documents and versions, Code context, Comments, Reviews and approvals, Sharing, a For You inbox, Team pulse ("design intent, review health, and execution drift"), the agent plugin (Sync, Push, Pull), the GitHub App, PR design review, "The Scott Method" and "The Scott app".Source
• DocsPR design review: "The planspace URL is the contract between design intent and execution." Scott asks "Does this implementation match the design intent the team reviewed?", posts a GitHub comment on architectural alignment, missing requirements and drift, and links back to the planspace. It only runs when a PR includes a planspace URL and does not block merges or add a required status check by default.Source

Turn the method into a short essay on tryscott.ai: the problem, the four moves (sync, push to a planspace, review and approve, pull into execution and check the PR), and a worked example. Put a summary on the homepage and post the essay where engineering leaders read.

A named method gives people a way to talk about the problem and a reason to link to Scott, and it sells the product's workflow without a demo.

• Reads as a sales pitch

  Make the method useful even without Scott.

• #1 Put the coding-agent planning product back on tryscott.ai: the homepage now says "we help shops with estimations" and blocks search engines

• DocsDocs home: "Sync agent work, share design intent, gather team feedback, and connect planspaces to code." The docs index lists Quickstart, Core concepts, Teams, Documents and versions, Code context, Comments, Reviews and approvals, Sharing, a For You inbox, Team pulse ("design intent, review health, and execution drift"), the agent plugin (Sync, Push, Pull), the GitHub App, PR design review, "The Scott Method" and "The Scott app".Source
• HiringTwo open roles on Y Combinator's job board: Product Engineer ($140K-$250K, 0.50%-2.00% equity) and Design Engineer ($140K-$250K, 0.50%-1.50%), New York or San Francisco, new grads welcome. The posts' thesis: "Coding agents amplify the cost of bad planning"; agents write far more code while teams still review and align on intent at the same pace.Source

Each week, publish one short post: a real task (from Scott's own work or a team that opts in, anonymized), the two or three designs the agents proposed, where they diverged and which choice the humans made and why. Post it from the founder accounts and the company account, and collect them on a page on tryscott.ai.

Concrete design debates are shareable, show the product without a pitch, and build an audience that the site currently lacks.

• Exposing customer code

  Use Scott's own work or written opt-in with anonymization.

• Y CombinatorLaunch post "Scott AI - Agentic Workspace for Software Spec Design" (122 upvotes): Scott "runs several coding agents side by side to expose their disagreements", shows where they disagree and exports a shareable plan to execution tools. Its calls to action are "Try Scott" (tryscott.ai) and "Apply for access" (www.tryscott.ai/apply), which returned 404 on November 10, 2026.Source
• Your websiteSite check (November 10, 2026): /robots.txt and /sitemap.xml return 404; no pricing page, blog, newsletter, careers page or social profile links; 0 Hacker News mentions and no news in the last 30 days. Change tracking shows the homepage headline moved from "Coding Agent Plan Mode with Super Powers" to "Scott: we help shops with estimations"; the domain was registered in October 2025.Source

Publish or polish a public GitHub Marketplace listing for the Scott GitHub App: one-line value ("Check every PR against the design your team approved"), screenshots of a drift comment, the permissions and why, and a link to the security page. Add a "Works alongside your code review bot" line so it is a complement, not a swap.

Developers look for tools where they will use them; a listing with clear permissions and a distinct promise turns browsing into installs.

• Installs without a planspace see nothing

  Show an install screen that leads to sync and the first push.

• #6 Add a plain-text security page on tryscott.ai, since the trust center reads as just a title to search engines and AI assistants

• DocsPR design review: "The planspace URL is the contract between design intent and execution." Scott asks "Does this implementation match the design intent the team reviewed?", posts a GitHub comment on architectural alignment, missing requirements and drift, and links back to the planspace. It only runs when a PR includes a planspace URL and does not block merges or add a required status check by default.Source
• Competitor researchRivals' own homepages: Traycer, "The <Nerve Center/> for Agentic Coding", a free open-source desktop app with a team plan at $16 per user a month billed yearly ($20 monthly) and 19 coding agents supported; Kiro, "Specs capture what you meant before code is written and verify results after"; CodeRabbit, "The future isn't writing code. It's reviewing it.", with 17K customers, 6M repositories and a claim to be the most installed AI app on GitHub.See the research Source

Package the plugin for each supported agent's official or community directory, with a two-line description and a link to the quickstart. Publish a "Supported agents" page on tryscott.ai with setup per agent, and add agents in order of user demand.

Directory listings put Scott in front of developers at the moment they are extending their agent, and a supported-agents page answers "does it work with mine?" before they leave.

• Directory rules change often

  Keep one owner and review listings quarterly.

• DocsQuickstart: install with one command (curl -fsSL https://tryscott.ai/install | sh), run "scott sync" and open the URL it prints; works with five named coding agents "and other supported agent sessions"; pushing a thread creates a planspace with a shareable app.tryscott.ai/workspace URL; the GitHub App works best with access to all repositories; Scott says it is SOC 2 compliant, does not persist repository contents and fetches code into ephemeral sandboxes only when needed. No page in the docs mentions pricing, plans or seats.Source
• Competitor researchRivals' own homepages: Traycer, "The <Nerve Center/> for Agentic Coding", a free open-source desktop app with a team plan at $16 per user a month billed yearly ($20 monthly) and 19 coding agents supported; Kiro, "Specs capture what you meant before code is written and verify results after"; CodeRabbit, "The future isn't writing code. It's reviewing it.", with 17K customers, 6M repositories and a claim to be the most installed AI app on GitHub.See the research Source

Build one public example planspace from Scott's own work (for example, how PR design review was planned): the agent thread, the document versions, comments, an approval, and the linked PR with its drift comment. Link it from the homepage as "See a real planspace".

Seeing a finished example answers "what would my team get?" in a minute, without asking for repository access first.

• Example goes stale

  Refresh it with each major release.

• #1 Put the coding-agent planning product back on tryscott.ai: the homepage now says "we help shops with estimations" and blocks search engines

• DocsTeams and concepts: a planspace combines a chat, a living document, source context, comments, reviews, approvals and members; roles are Owner, Editor, Commenter and Viewer; reviews have pending, in progress, approved and rejected states. Nothing on invitations, seats or billing.Source
• Your websiteHomepage (fetched twice on November 10, 2026): title "Scott | Shop Estimations", H1 "Scott: we help shops with estimations", and one line, "Reachout to [email protected]". No link to the docs, the app, the install command, a demo, pricing or the team.Source
• HiringTwo open roles on Y Combinator's job board: Product Engineer ($140K-$250K, 0.50%-2.00% equity) and Design Engineer ($140K-$250K, 0.50%-1.50%), New York or San Francisco, new grads welcome. The posts' thesis: "Coding agents amplify the cost of bad planning"; agents write far more code while teams still review and align on intent at the same pace.Source

Define six events (homepage visit, install command copied, first sync, first planspace, first approved review, first linked PR) with a source tag, and one weekly chart by cohort. Use a privacy-friendly, first-party setup so the page stays fast and no session content is collected.

A three-person team has to pick one fix at a time; a funnel shows which step to fix first and proves whether each idea in this playbook works.

• Tracking worries privacy-minded developers

  Count events only, never session content, and say so on the security page.

• PageSpeedMobile test on November 10, 2026: performance 100, accessibility 100 and best practices 100, but SEO 60 because the "Page is blocked from indexing"; no social share image or favicon; 7 requests and 108 KB with no third-party requests. Real visitors pass Core Web Vitals (75th percentile LCP 1.2 s, INP 45 ms, CLS 0).Source
• DocsQuickstart: install with one command (curl -fsSL https://tryscott.ai/install | sh), run "scott sync" and open the URL it prints; works with five named coding agents "and other supported agent sessions"; pushing a thread creates a planspace with a shareable app.tryscott.ai/workspace URL; the GitHub App works best with access to all repositories; Scott says it is SOC 2 compliant, does not persist repository contents and fetches code into ephemeral sandboxes only when needed. No page in the docs mentions pricing, plans or seats.Source
• DocsTeams and concepts: a planspace combines a chat, a living document, source context, comments, reviews, approvals and members; roles are Owner, Editor, Commenter and Viewer; reviews have pending, in progress, approved and rejected states. Nothing on invitations, seats or billing.Source

With customer opt-in and full anonymization, publish a twice-yearly report: share of linked PRs with drift, the most common kinds (missing requirements, new dependencies, changed abstractions), how much drift is intentional, and how approval before execution changes the rate. Release the method openly and offer teams their own benchmark.

Original data earns links, press and conference talks, and makes Scott the reference for a problem every engineering leader is asking about.

• Too little data at this stage

  Start with Scott's own repositories and a small opt-in cohort, labelled as such.

• Customer privacy

  Aggregate only, with written opt-in.

• #11 Use the PR comment as distribution: an opt-in "design drift" status check and a link back to the planspace

• DocsPR design review: "The planspace URL is the contract between design intent and execution." Scott asks "Does this implementation match the design intent the team reviewed?", posts a GitHub comment on architectural alignment, missing requirements and drift, and links back to the planspace. It only runs when a PR includes a planspace URL and does not block merges or add a required status check by default.Source
• HiringTwo open roles on Y Combinator's job board: Product Engineer ($140K-$250K, 0.50%-2.00% equity) and Design Engineer ($140K-$250K, 0.50%-1.50%), New York or San Francisco, new grads welcome. The posts' thesis: "Coding agents amplify the cost of bad planning"; agents write far more code while teams still review and align on intent at the same pace.Source
• DocsDocs home: "Sync agent work, share design intent, gather team feedback, and connect planspaces to code." The docs index lists Quickstart, Core concepts, Teams, Documents and versions, Code context, Comments, Reviews and approvals, Sharing, a For You inbox, Team pulse ("design intent, review health, and execution drift"), the agent plugin (Sync, Push, Pull), the GitHub App, PR design review, "The Scott Method" and "The Scott app".Source

Package an Enterprise plan: SSO and SCIM, audit logs for every sync, push, pull and PR review, repository and session scoping, data retention settings, a data processing agreement and a named contact. Sell it through demos to engineering organizations that already allow coding agents, starting with existing teams that are growing.

Planning and design approval matter most in large teams, which pay more per seat, and security controls are what turn a team pilot into a company rollout.

• Enterprise work slows the core product

  Build only what a signed or late-stage deal needs.

• #5 Publish exactly what "scott sync" uploads, with an exclude list, before teams ask
• #6 Add a plain-text security page on tryscott.ai, since the trust center reads as just a title to search engines and AI assistants
• #7 Publish pricing: a free single-developer tier and a per-seat team plan

• DocsQuickstart: install with one command (curl -fsSL https://tryscott.ai/install | sh), run "scott sync" and open the URL it prints; works with five named coding agents "and other supported agent sessions"; pushing a thread creates a planspace with a shareable app.tryscott.ai/workspace URL; the GitHub App works best with access to all repositories; Scott says it is SOC 2 compliant, does not persist repository contents and fetches code into ephemeral sandboxes only when needed. No page in the docs mentions pricing, plans or seats.Source
• Trust centertrust.tryscott.ai is a Vanta trust center; read as page text it shows only the title "Scott AI Trust Center", with no certifications, policies or subprocessors.Source
• DocsSync: reads local coding-agent sessions from the last 14 days and "uploads the relevant context to Scott"; the page does not describe what is excluded or redacted, or how to opt a session out.Source

Build a free web tool on tryscott.ai: describe a task (or paste a public repository URL), two agents draft plans, and Scott shows the key divergences side by side. The result ends with "Turn this into a planspace for your team", which leads to install and sync. Rate-limit it and require sign-in after the first run.

A free, instantly useful tool gets shared and indexed, and every result is a natural starting point for a planspace.

• Usage costs climb

  Cap free runs and require sign-in after the first.

• Distracts from team features

  Reuse the existing planning engine; no separate product.

• #1 Put the coding-agent planning product back on tryscott.ai: the homepage now says "we help shops with estimations" and blocks search engines

• Y CombinatorLaunch post "Scott AI - Agentic Workspace for Software Spec Design" (122 upvotes): Scott "runs several coding agents side by side to expose their disagreements", shows where they disagree and exports a shareable plan to execution tools. Its calls to action are "Try Scott" (tryscott.ai) and "Apply for access" (www.tryscott.ai/apply), which returned 404 on November 10, 2026.Source
• Your websiteSite check (November 10, 2026): /robots.txt and /sitemap.xml return 404; no pricing page, blog, newsletter, careers page or social profile links; 0 Hacker News mentions and no news in the last 30 days. Change tracking shows the homepage headline moved from "Coding Agent Plan Mode with Super Powers" to "Scott: we help shops with estimations"; the domain was registered in October 2025.Source

Decide in writing which product tryscott.ai is for. If estimations is a test, give it its own domain or a /shops page with its own headline, example estimate and sign-up, and keep the planning product on the homepage. If it replaces the planning product, update the YC page, the docs and the job posts together so every channel tells one story.

One domain, one audience, one promise: each product gets a page that converts, and neither confuses the other's visitors or search results.

• Splitting focus across two products

  Set a date to review the test and stop the weaker one.

• #1 Put the coding-agent planning product back on tryscott.ai: the homepage now says "we help shops with estimations" and blocks search engines

• Your websiteHomepage (fetched twice on November 10, 2026): title "Scott | Shop Estimations", H1 "Scott: we help shops with estimations", and one line, "Reachout to [email protected]". No link to the docs, the app, the install command, a demo, pricing or the team.Source
• Your websiteSite check (November 10, 2026): /robots.txt and /sitemap.xml return 404; no pricing page, blog, newsletter, careers page or social profile links; 0 Hacker News mentions and no news in the last 30 days. Change tracking shows the homepage headline moved from "Coding Agent Plan Mode with Super Powers" to "Scott: we help shops with estimations"; the domain was registered in October 2025.Source
• Y CombinatorCompany page: "The planning layer for teams that build with coding agents"; founded 2025, Fall 2025 batch, team of 3, New York City, status Active, website tryscott.ai.Source

Add /careers with the thesis, what the team is building (sync, planspaces, PR design review), the two roles linking to the YC posts, and how the team uses Scott to plan its own work. Link it from the homepage footer.

Engineers who would join are also the users Scott wants; a careers page that explains the product serves both, and gives candidates the site they will check first.

• Page goes stale after hires

  Keep a general "we're always talking to engineers" line.

• #1 Put the coding-agent planning product back on tryscott.ai: the homepage now says "we help shops with estimations" and blocks search engines

• HiringTwo open roles on Y Combinator's job board: Product Engineer ($140K-$250K, 0.50%-2.00% equity) and Design Engineer ($140K-$250K, 0.50%-1.50%), New York or San Francisco, new grads welcome. The posts' thesis: "Coding agents amplify the cost of bad planning"; agents write far more code while teams still review and align on intent at the same pace.Source
• Your websiteSite check (November 10, 2026): /robots.txt and /sitemap.xml return 404; no pricing page, blog, newsletter, careers page or social profile links; 0 Hacker News mentions and no news in the last 30 days. Change tracking shows the homepage headline moved from "Coding Agent Plan Mode with Super Powers" to "Scott: we help shops with estimations"; the domain was registered in October 2025.Source