OperatorOne

Design, run, and audit Stage3 Iterate on product capability for OperatorOne. Use when asked to convert Stage1 metrics and Stage2 feedback priorities into experiment backlogs, rollout plans, policy-driven decisions (ship/iterate/rollback/park), learning logs, and cross-team iteration handoffs; or when asked to bootstrap Stage3 contracts/config, enforce guardrails, and verify strict reproducibility.

Implement and operate Stage2 Process feedback capability for OperatorOne. Use when asked to build, run, audit, or deliver feedback processing from ingestion through prioritization and closed-loop tracking; generate Stage2 feedback scoreboards/alerts/weekly snapshots; create operations_to_product/marketing/sales handoffs; enforce strict reproducibility; or migrate from simulated feedback adapters to live sources.

End-to-end Stage3 conversion execution for op1_sales. Use when asked to convert early customers, move leads from interest/discovery into pilot and paid start, generate close-motion playbooks, track pilot onboarding and TTFV, process conversion signals (commitment/paid/lost), produce conversion scoreboards, or run reproducible conversion audits.

End-to-end Stage2 send outreach pipeline for op1_sales. Use when asked to send outreach, run follow-up sequences, generate outreach dispatch packs, approval-gated dispatch batches, process outreach replies, enforce suppression/frequency controls, or roll up outreach outcomes into handoffs/sales_to_operations.json.

Implement and operate Stage1 tracking for OperatorOne operations (traffic, signups, revenue). Use when asked to build, run, audit, or deliver this capability; bootstrap contracts/adapters; generate Stage1 scoreboards and weekly KPI snapshots; enforce data quality and reproducibility; or migrate from simulated signals to live analytics/billing sources.

Build and refresh Stage1 prospect-identification outputs for op1_sales. Use when asked to identify prospects, rank ICP segments, show top prospects, or generate evidence-backed lead queues from OperatorOne handoff data (marketing_to_sales, opportunity_records, reddit_signals).

Run and operate OperatorOne Marketing Stage3 launch-campaign orchestration in shadow/review mode. Use when asked to launch campaigns without auto-posting, convert Stage2 approved assets into campaign packets, generate UTM attribution maps, route campaigns into launch_ready/watchlist/hold, validate Stage3 output integrity, or sync campaign launch status to marketing_to_sales handoff.

Run and operate OperatorOne Marketing Stage2 content publishing in shadow/review mode. Use when asked to publish content without auto-posting, generate Stage2 drafts from Stage1 SEO outputs, apply manual approve/revision decisions, verify queue integrity, or update marketing_to_sales handoff statuses.

Run and audit OperatorOne Stage1 marketing SEO shadow experiments across input sync, context index, keyword graph, experiment synthesis, and Ready/Hold/Drop queueing. Use when asked to run SEO experiments, execute 1/2/3 validation rounds, verify reproducibility, or summarize queue and scoreboard outputs for op1_marketing.

Execute full Stage-3 landing capability for op1_product (Mode C): resolve opportunity/scope/evidence gates, generate landing package + landing-specific page spec, run contract/semantic tests, and (optionally) deploy via build pipeline.

Discover startup opportunities from market signals and user pain evidence. Use when generating idea longlists, collecting corroborated problem evidence, mapping target segments, and producing Stage-1 opportunity records.

Score and prioritize startup opportunities with an explicit weighted framework. Use when selecting which Stage-1 opportunities should advance into MVP design (Stage 3).

Create landing-page-ready product handoff using Mode-C contract gates (opportunity selection, scope boundary, evidence traceability) and write output for marketing consumption.

Convert a selected Stage-2 opportunity into a testable MVP blueprint with strict scope boundaries, pricing hypothesis, success metric, and kill criteria.

Build and deploy simple web products with a robust, adapter-driven framework (project spec -> page spec -> scaffold -> deploy -> smoke/page-strategy/business tests). Use when implementing or operating `Build & deploy simple web products` for `op1_product`, especially when the same harness must support multiple business project types.