Fasttrak

Fasttrak is the URL-to-positioning-playbook orchestrator. Paste a public landing page URL, wait a couple of minutes, and you walk away with a project, two ICP candidates, positioning artifacts, a full draft (above + below the fold), a preview audit on the draft, a fresh audit on your live page, and an AI-generated narrative comparing the two.

It’s the same workflow Projects, drafts, and pages describes — just compressed into a single orchestrated run instead of click-by-click.

The 3-phase flow

Phase	What happens	You wait	You do
1. Context	Scrape the URL, extract a brief, generate 2 ICP candidates, generate positioning for ICP #1	~30s synchronous	Nothing — the orchestrator runs to a “needs review” pause
2. Review	The flow halts. You see the brief, both ICPs, and ICP #1’s positioning.	Until you click	Pick the ICP and strategy you want; optionally add a competitor URL for comparison
3. Draft + audit + compare	Generate ATF + BTF, run a preview audit on the draft, run a fresh live audit, generate the compare narrative	~60–90s	Nothing — wait for completion

The pause between Context and Draft+audit is deliberate. The cheapest moment to redirect is after you’ve seen what the LLM inferred but before committing 8 more audit-units to draft generation. If the brief came back wrong or the wrong ICP is in slot #1, swap before you spend.

What it produces

When the run completes you have:

A project with the scraped brief, both ICP variations, and your chosen ICP’s positioning artifacts (UVP, positioning statement, differentiators)
A draft scoped to the chosen ICP — ATF (headline + subheading + CTA) and BTF (features, FAQ skeleton)
A preview audit on the draft (treats the draft copy as if it were live and audits it)
A live audit on the original URL (so you have a fresh baseline, even if you’d already audited the page recently)
A compare narrative between the two — “Headline appeal moved 6→9 because the new version names the buyer’s role explicitly; ICP alignment moved 4→8 because the BTF now addresses the inferred persona’s top pain point”
A linked landing page — if you started Fasttrak from a Page workspace, the page row is auto-linked to the new draft so future audits trail behind the comparison

Cost — 10 audit-units

Fasttrak charges 10 audit-units up front, regardless of which phases run successfully. That covers the live audit, the preview audit, and the LLM cost of context + draft + compare generation. If a phase fails (e.g., scrape couldn’t load the page) you don’t get a refund — the audit-units paid for the work that did run. Re-running starts from scratch.

→ Audit-unit budgeting: Plans and pricing

When to use Fasttrak vs. build from scratch

Use Fasttrak when you have a live page and want a working positioning draft fast — to benchmark against, to seed the manual workflow, or to ship as a v0 you’ll iterate. The output is meant to be a starting point, not a finished page.

Build from scratch when you don’t have a live URL yet, when you want to control which positioning framework drives the statement (Fasttrak picks one for you), or when the page you’d start from is so off-brand that scraping it would seed bad context.

The two paths converge — Fasttrak produces the same project + draft shape the manual workflow does. You can refine, regenerate, and edit everything afterward.

Plan availability

Fasttrak is on every paid plan (Solo Founder, Team, Business). Free doesn’t include it.

Failure modes

A few things can go wrong, and they all surface in the orchestration row in Orchestrations → Fasttrak:

Scrape failed — the URL didn’t load (heavy JS, anti-bot wall, 404). Re-running won’t help; you have to point Fasttrak at a different URL.
LLM hiccup mid-phase — rare; the orchestration row shows which phase died and you can retry from the failed step rather than re-paying 10 audit-units.
Plan downgrade mid-run — if you downgrade off a Fasttrak-eligible tier between Phase 1 and Phase 3, the run pauses with a “plan no longer supports Fasttrak” message.