TractionScout
FeaturesScout AI

Scout, the AI that reads all of it and asks before it acts

Scout compares your numbers across every source, explains what may be in the way, prepares the change and checks whether it helped. It remembers what worked and works with your own agents through MCP.

Get startedTry the demo workspace

Scout, the TractionScout AI assistant, explaining what changed for a sample product and suggesting next steps
Scout open on the sample product’s home, with its readings and notes. Sample data, no account needed. Open it full screen

What you can do

  • Evidence first

    Scout separates what the data shows from what still needs checking, and says when a finished task is not yet proof of more customers.

  • Prepares the work

    Copy, content, a code change, a post or a campaign, ready for you to review in Work.

  • Separate permissions

    Reading data, preparing a draft, publishing and changing a budget are separate permissions. Approvals stay with you.

  • Memory you control

    Scout remembers what worked per project, from experiments, assets, posts and alerts. Review, approve and retire memories in Activity & Memory.

  • Automations

    Work Scout repeats hourly, every 6 or 12 hours, daily or weekly, with a record of what came of each run.

  • MCP and Agent CLI

    Connect Claude Code, Codex or any MCP client with the open-source Agent CLI. Read-only by default, and external execution is always blocked.

What Scout does

Scout is the AI inside TractionScout. It reads every source you connect, from analytics and search to payments, social and email, and works through a growth question the way a careful analyst would:

  1. compare the numbers along your funnel,
  2. explain what may be getting in the way, keeping what the data shows apart from what still needs checking,
  3. prepare a change: copy, content, a code change, a post or a campaign,
  4. check afterwards whether it helped.

A finished task is not treated as proof of more customers or revenue. Scout says when the evidence is not in yet.

You stay in control

Reading data, preparing a draft, publishing and changing a budget are separate permissions. Everything Scout prepares appears in Work, where you review, approve and follow each growth action. Reading your analytics never gives Scout permission to post or spend.

Memory that you curate

Scout keeps a memory per project, built from evidence such as experiments, assets, social posts and alerts. In Activity & Memory you can review, approve and retire what it remembers, see what it made, and check the health of scheduled work.

Automations

Automations are work Scout repeats on a schedule, hourly, every 6 or 12 hours, daily or weekly, with a record of what came of each run. You choose what happens when a previous run has not finished. Scout's notes can reach you as browser notifications.

Bring your own agents with MCP

The open-source Agent CLI (tscout, AGPL-3.0) connects Claude Code, Codex or any MCP client to your projects. The download is verified with a checksum and has no dependencies. The default mode is read-only; a review-staging mode lets agents stage work for your approval. External execution is blocked in every mode, and credentials, approvals and budgets stay on the server.

Set it up with Agent CLI and MCP, or see an example in Connect a coding agent or script.

Questions

Will Scout post or spend money on its own?

No. Reading your analytics does not give it permission to publish content or change a budget. Those actions need the right connection and follow the approval rules you set.

Can I use my own AI agent?

Yes. Install the Agent CLI and connect any MCP client. It works with the same projects and permissions, while credentials, approvals and budgets stay on the server.

Which AI model does Scout use?

The model and AI budget are set per project in AI & Billing settings. Provider usage may cost extra depending on your plan.

Ask Scout on your own product

What is holding back sign-ups this month, and what should I try first?

Start with this question

Your question is carried into setup. Review it, connect the data you need, and send it to Scout when you are ready.