AutoGPT

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.

日本語の概要は準備中です。原文の説明を表示しています。

Review pipeline stage age against team rules and identify stalled deals, weak next steps, stale records, and owner actions.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers.

日本語の概要は準備中です。原文の説明を表示しています。

Compare written policies with a named framework's control list and show gaps with evidence.

日本語の概要は準備中です。原文の説明を表示しています。

Track and analyze portfolio company performance against plan. Ingests monthly/quarterly financial packages (Excel, PDF), extracts KPIs, flags variances to budget, and produces summary dashboards. Use when reviewing portfolio company financials, preparing board materials, or monitoring covenant compliance. Triggers on "review portfolio company", "monthly financials", "how is [company] performing", "covenant check", or "portfolio update".

日本語の概要は準備中です。原文の説明を表示しています。

Update, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now/Next/Later view from scratch.

日本語の概要は準備中です。原文の説明を表示しています。

Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan.

日本語の概要は準備中です。原文の説明を表示しています。

Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a partner QBR or business review is coming: grade the quarter against benchmarks, co-draft the agenda, ship the pre-read, land the recap.

日本語の概要は準備中です。原文の説明を表示しています。

Set up a vendor purchase from business need through evidence, approval, renewal, and owner tracking.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user names interviews, user research, a survey, a beta, or a pile of feedback to make sense of: the interview plan with a story opener, or ranked themes led by verbatim quotes with a roadmap verdict on each.

日本語の概要は準備中です。原文の説明を表示しています。

Define each pipeline stage with an entry rule, an exit rule, and required proof.

日本語の概要は準備中です。原文の説明を表示しています。

Draft a press release with the news first, checkable claims, approved quotes, and a boilerplate.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user names an AI feature, an agent, a prompt, retrieval, evals, or model quality work: the scoped spec with a prompt set, a four-rung quality ladder, a scoreboard read over three runs, and the safety gates.

日本語の概要は準備中です。原文の説明を表示しています。

Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B SaaS sales team from scratch or building a lead-qualification framework to improve close rates. Covers the three lead types (seeds/nets/spears), role specialization, the referral-email method, ANUM qualification, and pipeline math. For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user names pricing, packaging, tiers, or discounts, or hands over a price list, competitor pricing, or deal terms: the pricing recommendation with guardrails and mix impact.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user names positioning, messaging, narrative, or value props, or hands over a draft to sharpen: the positioning doc and the message house per audience.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user names an A/B test, an experiment, a growth bet, or a before-and-after read: the plan with one primary metric, guardrails, a computed sample size, precommitted interpretation bands, then the scale-extend-or-kill readout.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user names an exec review, a board update, a steering meeting, or a stakeholder who needs the product story: the narrative spine, a graded scorecard with every number sourced, the roadmap mapped to their goals, risks with contingencies, and asks with owners and dates.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare an internal approval brief for a price or term request, with policy position, business case, risks, give-get, and named approvers.

日本語の概要は準備中です。原文の説明を表示しています。

Draft a procurement decision memo that shows requirements, total cost, evidence gaps, risks, and approvals without selecting or binding.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user names competitors, pricing, positioning, a market read, or battlecard input for the roadmap: the tiered watch list, dated and linked changes, a pricing read taken from real pages, and the differentiation bets it opens.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user names a feature to spec, a build decision, user stories, or acceptance criteria: the PRD with a scope line, stories a tester can check, UX direction at wireframe level, the success metric, and the engineering handoff.

日本語の概要は準備中です。原文の説明を表示しています。

Initialize the productivity system and open the dashboard. Use when setting up the plugin for the first time, bootstrapping working memory from your existing task list, or decoding the shorthand (nicknames, acronyms, project codenames) you use in your todos.

日本語の概要は準備中です。原文の説明を表示しています。