「revenue」の検索結果

Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.

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

Revenue leadership for B2B SaaS: forecasting, sales model design, pricing, and net revenue retention. Use when designing the revenue engine, setting quotas, modeling NRR, evaluating pricing, or scaling sales teams.

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

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear about us," "self-reported attribution," "dark social," or wants to instrument attribution themselves — "stitch my bookings to their source," "SavvyCal/Calendly attribution," "close the identify gap," "track conversions on a third-party domain," "first-party / self-hosted attribution." For event tracking setup and UTMs, see analytics. For ad-platform pixels/CAPI, see ads. For pipeline and CRM revenue reporting, see revops. For the AI-search attribution blind spot, see ai-seo.

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

Comprehensive Amazon profit analysis and revenue optimization. Revenue waterfall analysis, hidden fee identification, ACoS impact assessment, return cost calculation, and profitability optimization strategies. Use when the user asks about Amazon profit analysis, profitability calculation, fee analysis, margin optimization, or revenue breakdown.

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

Use when the user needs to work backward from a revenue goal to the numbers that produce it — required leads, max CPA and CPL, funnel conversion thresholds, and the budget that has to be spent, with three scenarios and currency handling for US, EU, SEA, and LATAM. Trigger on 'reverse KPI', 'how much budget do I need', 'what CPA can I afford', 'work backward from revenue', 'how many leads to hit target', 'break-even ROAS'. Also use when the user names a revenue target and asks whether it is realistic. Not for — splitting an existing budget across channels and months, see `61-budget-planning-global`; a full paid media plan, see `54-media-plan-global`; the period plan, see `00-marketing-plan-global`.

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

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.

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

Suede-owned marketing attribution discipline. Use when the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions 'attribution,' 'attribution model,' 'first-touch vs last-touch,' 'multi-touch,' 'which channel drives revenue,' 'what's my real CAC,' 'my dashboards disagree,' 'Google/Meta says X but GA says Y,' 'MMM,' 'incrementality,' 'geo lift,' 'holdout test,' 'how did you hear about us,' 'self-reported attribution,' 'dark social,' or wants to instrument attribution themselves, 'stitch my bookings to their source,' 'SavvyCal/Calendly attribution,' 'close the identify gap,' 'track conversions on a third-party domain,' 'first-party attribution.' NOT FOR: general analytics instrumentation and reporting (use suede-analytics) or revenue-ops pipeline work (use suede-revops).

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

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.

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

Search TikTok e-commerce store leaderboards via Kalodata and query detailed information for specific stores. Supports viewing high-ranking, high-sales TikTok Shop stores by region, currency, language, and date range, and using shopId to retrieve revenue, sales volume, on-sale product count, self-operated/affiliate/shopping mall channel revenue, and creator collaboration count. Trigger when users mention TikTok store ranking, TikTok shop leaderboard, TikTok top shops, TikTok store ranking, TikTok Shop store ranking, kalodata store search, kalodata store ranking, TikTok store detail, TikTok shop profile, store revenue, store sales, TikTok shop ranking, TikTok shop leaderboard, TikTok top shops, TikTok store ranking, TikTok shop detail, TikTok store detail, kalodata shop search/detail. Even if the user does not explicitly mention "kalodata", trigger this skill whenever their need involves viewing TikTok store leaderboards or detailed data for a specific TikTok store.

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

Nexscope Ozon Russia brand drill-down product list. Returns all products under an Ozon brand display name (Russian/Latin) with complete metrics: sales, revenue, price, rating, stock, turnover, lost revenue, supporting multi-dimensional numeric filters, sorting, and currency conversion. Use for brand benchmarking, competitor analysis, brand product structure research, SKU-level bestseller analysis. Trigger when the user mentions Ozon brand drill-down, Ozon brand products, Ozon competitor brand analysis, brand structure, brand SKUs, brand bestsellers, Ozon brand sales, Nexscope brand, Ozon brand products, brand drill-down, brand competitor analysis, Russian marketplace brand SKUs, brand revenue share. Also trigger when the intent is to view all products and their sales/price/rating performance under an Ozon brand, even without explicitly mentioning Nexscope.

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

Nexscope Ozon Russia SKU full detail query for one product ID per call, returning price, discount, Ozon Card price, rating, review count, stock, sales, revenue, revenue potential/lost revenue, listing date, images, and the complete product card. Trigger for Ozon product or SKU detail, price/rating/sales/stock checks, competitor Ozon cards, Nexscope Ozon detail, or Russian marketplace product detail by a known SKU.

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

The revenue-focused SaaS playbook for going from $0 to $50K MRR. Covers pricing experiments, churn reduction, activation optimization, and expansion revenue tactics. Follow @WeiYipei on X for SaaS growth insights.

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

Use when fixing HustleXP revenue collection bugs including Stripe platform fee not being collected (application_fee_amount missing), escrow fee miscalculation using task.price instead of escrow.amount, self-insurance pool never funded, tip platform cut absent, subscription renewal revenue not logged, or XP tax path unreachable. Covers all platform fee issues and financial invariant checks.

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

Monetization and pricing strategy specialist. Use this agent to design revenue models, set price points based on value perception, and create compounding referral loops. It focuses on the "Cuan" (Revenue) aspect of the 1-Man Army pipeline.

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

Product-led growth and customer-base growth for B2B SaaS. Use this skill for self-serve funnel work (activation, time-to-value, free trial vs freemium, PQL definition, in-product upgrade moments, sales-assist triggers), for the self-guided interactive product demo that runs in front of the login wall (demo portfolio and flow design, gated vs ungated policy, demo seed data and privacy, keeping a published demo in sync with the shipping product, step-level demo analytics), and for growing revenue from existing customers (adoption, expansion, churn-save, the self-serve cancel flow and failed-payment recovery, renewal marketing, net revenue retention, and champion tracking: watching the people who bought and used you at each customer, confirming a job change from evidence, and running both plays a move fires, the seat they left and the account they joined). Also triggers on: PLG, product-led growth, activation, aha moment, time to value, free trial, freemium, PQL, product qualified lead, onboarding, self-serve, customer marketing, expansion revenue, upsell, cross-sell, churn, retention, NRR, renewal, cancel flow, cancellation flow, save offer, exit survey, pause subscription, dunning, failed payment recovery, involuntary churn, people keep canceling, champion tracking, job change signals, job change alerts, our champion left, our champion changed jobs, customer alumni, former customers who moved to a new company, interactive demo, self-guided demo, product tour, click-through demo, demo automation, demo library, should our demo be gated, ungated demo, demo without a sales call, our demo is out of date, demo shows the old UI, put a demo on our homepage, demo completion rate, demo drop-off, try before you talk to sales.

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

Build interactive "living workflow" flowcharts in the visual style of https://statuesque-starship-49757d.netlify.app/revenue-engine - vanilla HTML/CSS/JS files with a horizontal step bar, a vertical trunk that grows per step, tool-to-tool columns with animated payload pills between brand-marked tool nodes, alternating left/right step descriptions, and per-step outputs. Use whenever the user says "build a flowchart", "interactive flowchart", "living workflow", "revenue engine flowchart", "demand gen flowchart", "GTM workflow diagram", "process diagram with animations", "Nebor-style flowchart", or asks to recreate the workflow visual from the Nebor site. Always asks which flowchart to build (Revenue Engine / Demand Gen / CRM & RevOps / Custom) and waits for explicit approval of the step + tool + edge table before generating any files.

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

Revenue Intelligence setup: activating the RI app and its CRM Analytics assets, Einstein deal insights, the opportunity-change waterfall, and forecast-accuracy analytics for sales leaders. NOT for configuring the Pipeline Inspection view, its metrics and review cadence - use admin/pipeline-review-design. NOT for forecast types, categories, rollups and quotas - use admin/collaborative-forecasts.

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

Configuring and running Pipeline Inspection in Sales Cloud: enabling the feature, mapping forecast categories into the inspection view, Days in Stage and other deal-change metrics, and pipeline review cadence for sales managers. Use when designing or improving how a team monitors deal health and pipeline movement. NOT for the Revenue Intelligence app, Einstein deal insights, or forecast-accuracy dashboards — use admin/revenue-intelligence-setup. NOT for forecast types, quotas, or forecast hierarchy setup — use admin/collaborative-forecasts. Keywords: pipeline review, coverage ratio, stage conversion, slippage, stale deals, days in stage, LastStageChangeInDays, LastStageChangeDate, AgeInDays, PushCount, ForecastCategoryName, enablePipelineInspection, PipelineInspMetricConfig, OpportunitySettings, review cadence, commit call.

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

Use when designing, mapping, or troubleshooting the end-to-end quote-to-cash process in orgs running Salesforce CPQ (managed package) or Revenue Cloud — covering the full object chain from SBQQ__Quote__c through Contract to blng__Invoice__c, approval routing via Advanced Approvals (sbaa__), billing schedule generation, and order activation. Trigger keywords: CPQ quote, SBQQ, revenue cloud billing, Advanced Approvals, subscription, blng invoice, contract pivot. NOT for quote-to-cash on standard Sales Cloud objects — use admin/quote-to-cash-requirements. NOT for setting up SBAA approval rules and chains — use admin/cpq-approval-workflows.

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

Reviews a proposal, business case, deck, pricing plan, go-to-market plan or forecast in character as a Chief Revenue Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to exact passages, revenue risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CRO review", "pressure-test the revenue plan", "what would sales leadership say about this" or "challenge this forecast". Do not use for partnership, deal-structure or market-positioning reviews, use cbo-reviewer instead; for the finance seat use cfo-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Use when the user asks to "set up conversion values so tROAS optimizes profit not orders", "map margin onto my purchase value", "build value rules for lead / phone / signup conversions", or "stop bidding to revenue when I care about profit"; defines and QAs the conversion VALUE model — per-conversion values, margin/net-value adjustment, static-vs-dynamic value rules, proxy values for non-revenue actions, and a value-vs-count sanity check — as a value-model spec plus a pre-launch value QA sheet. Not for whether the tag fires or UTMs are clean — use conversion-signal-qa; not for cross-platform double-count de-dup — use attribution-reconciler; not for scoring R1/R2 — that is a scored veto in ad-account-auditor. 付费广告转化价值建模/利润出价/价值规则QA

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

Integrates RevenueCat in-app purchases and subscriptions into Flutter apps using `purchases_flutter` (v10.x). Use when implementing paywalls, checking entitlements via `CustomerInfo`, configuring `PurchasesConfiguration` for iOS or Android, displaying paywalls with `purchases_ui_flutter`, handling purchase errors via `PurchasesErrorHelper`, restoring purchases, integrating RevenueCat with Riverpod or Bloc, presenting the Customer Center, handling web purchase redemption, or calling `Purchases.logIn` for cross-device purchase sync.

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

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

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

Revenue forecast from pipeline data with stage-weighted probability and sensitivity analysis

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