TractionScout is a growth operating system for products and apps. It helps founders, product teams, and growth operators bring evidence from different systems into one project, decide what deserves attention, and turn that decision into work they can review, ship, and measure.
The project can combine product behavior, acquisition, revenue, search, store, social, advertising, and operational signals. The sources available to a particular project depend on its connected providers and deployment. See Connecting your data sources for how to check support before setup.
How the operating loop works
Connect evidence. Bring in useful signals and inspect their source, freshness, coverage, and limitations.
Choose the next move. Scout uses the project's business context and evidence to identify likely bottlenecks and prepare hypotheses, experiments, content, creative, code candidates, or provider actions.
Review and execute. Prepared work keeps its evidence and approval state. Reading data, staging work, publishing, changing budgets, and rolling back changes are separate capabilities.
Measure the result. Review what happened against the work's measurement plan. Useful outcomes and corrected interpretations can inform later decisions through project memory.
Finishing an action does not establish that it improved growth. A report should make the observation window, source limitations, and evidence for the conclusion clear.
Where to begin
Start with one product and one question, such as whether a change in activation coincides with a change in subscriptions. Connect the evidence needed to investigate that question and review the proposed next step before expanding the workflow.
Read Getting started for onboarding, or Agent CLI and MCP for working from an external agent. The managed service guide explains where to find current access, pricing, and privacy information. TractionScout is under active development, so available capabilities and setup requirements may change before a stable release.