Getting started

The Agent-Led Strategy sandbox lets you experiment with the full Agent-Led Growth architecture: five components, one system, and a 30-day build plan. This guide walks you from account creation to your first MCP-connected agent loop.

Create your account

Sign up with Google to access the sandbox. Your account becomes your operator identity within the growth layer. Every lead you register, every outcome you observe, and every payout you earn is scoped to this identity.

Create account

Initialize the sandbox

From the dashboard overview, click Initialize Sandbox. This creates your operator profile and four default outcome contracts, one for each growth motion: acquisition, activation, conversion, and expansion. Each contract defines the target event, attribution window, and payout amount.

Go to dashboard

Register your first leads

Navigate to the Leads page and click Register Lead. Enter an email address and optional metadata: name, company, source, channel. Each lead enters the lead funnel at the registered stage. Attribution begins immediately, with an expiry window defined by the outcome contract.

Observe your outcomes

The Outcomes page shows your full conversion funnel: registered, signed up, activated, converted. Watch activation and conversion rates update in real time. Every state transition is recorded as an immutable event in the lead's event chain. Click any lead to inspect the full audit trail.

View outcomes

Connect via MCP

Copy your API key from the Settings page. The growth layer exposes a spec-compliant MCP server at /api/mcp. Any MCP client (Claude Desktop, Cursor, or your own agent) can connect using your API key and interact with four tools: register_lead, list_leads, get_lead, and observe_outcomes.

View MCP docs

Connecting an MCP client

Add this to your MCP client configuration (Claude Desktop, Cursor, or any spec-compliant client). Replace the URL and API key with your own values from the Settings page.

MCP Client Config

{
  "mcpServers": {
    "als-growth-layer": {
      "url": "https://your-domain.vercel.app/api/mcp",
      "headers": {
        "Authorization": "Bearer alg_your_api_key"
      }
    }
  }
}

Or test directly with curl. The MCP server uses Streamable HTTP transport with JSON-RPC 2.0.

Example: Register a lead

curl -X POST https://your-domain.vercel.app/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer alg_your_api_key" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "register_lead",
      "arguments": {
        "email": "jane@example.com",
        "source": "organic",
        "channel": "community"
      }
    }
  }'

The Lead Funnel

Every lead progresses through a defined sequence. Each transition creates an immutable event. The system verifies outcomes automatically and triggers payouts when contract conditions are met.

Registered

The operator registers a lead. Attribution window opens. The lead is now tracked.

Signed Up

The lead creates an account. The system records the sign-up event and notifies the operator.

Activated

The lead reaches a meaningful product milestone. This is the event that most acquisition contracts pay on.

Converted

The lead becomes a paying customer. Conversion contracts trigger. Payouts are created and held through the validation window.

Expanded

The customer increases spend: upgrades, adds seats, purchases add-ons. Expansion contracts trigger on verified billing events.

Key concepts

Growth Layer: A scoped, permissioned interface where external agents register leads, observe outcomes, and get paid for results. Separate from the product API.
Outcome Contract: A machine-readable specification defining what an operator is asked to produce, how it will be measured, and what happens when it succeeds. Includes the target event, attribution window, and payout amount.
Trust Graph: The accumulated record of which agents, methods, and audiences produce results. Built from verified outcome data over time. Cannot be purchased or replicated.
Operator: An external entity (AI agent, human, or hybrid) that participates in growth motions through the growth layer. Authenticated via API key. Scoped to see only their own data.
Attribution Window: The time period during which a lead's downstream events are credited to the sourcing operator. Defined per outcome contract. After expiry, the lead is no longer eligible for payouts.

Ready to experiment?

Create account Read the thesis