Getting started

Begin with a public product URL and a concrete growth question. A useful first project has a clear outcome, enough evidence to investigate it, and an owner who can review proposed work.

Set up a project

Setup has three steps.

1. Your product. Open TractionScout signup and paste a public website, App Store, or Google Play link. Adding what you want to improve is optional; Scout asks in the workspace if you skip it.
2. Your account. Sign in with an enabled provider or create an account with email, and review the access shown beside it. During the alpha this is a free place with no payment card. The project is created here, and Scout starts reading your public pages right away.
3. Connect data. Optional. Install web tracking for your site and connect sources such as Search Console or Stripe. Each card says what it unlocks and what access it needs. The operating mode at the bottom of this step sets what Scout may prepare or execute; change it there or later in the workspace. Open your workspace whenever you like and add sources later under Configure → Data Sources.

After setup, review the discovered Business Context and correct the product description, audience, goals, and assumptions before relying on them for recommendations. The setup card in your workspace tracks tracking verification, your first connected source, and your first question to Scout.

Make the first question answerable

Choose a focused investigation: trial activation, Search Console clicks, or acquisition channel activation. Each guide specifies the evidence and a way to reproduce a baseline before proposing a change. Use the project's existing measurement definitions and preserve your selected outcome.

For a product with PostHog and Stripe, a first question might be: “How did activation and subscription activity change over the same period?” Connect the relevant project and account, run their initial synchronization, and check the reported coverage before asking Scout for a readout.

Keep the time window and denominators explicit. Missing data is a limitation to investigate; it should not be interpreted as zero activity. If two metrics move together, the report should distinguish that observation from evidence that one caused the other.

Review any proposed follow-up in the action queue. Confirm the intended outcome, supporting evidence, scope, and measurement plan before approving consequential work. After execution, inspect the result and record what was learned so the next run has that context.

See Connecting your data sources for prerequisites and readiness checks. Review pricing and privacy for the current commercial information and project data controls.