Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

motherduck-pricing-roi

Estrellas49

Forks3

Actualizado13 de julio de 2026 a las 15:16

Explain MotherDuck pricing and ROI tradeoffs. Use for any pricing, cost, billing, plan-comparison, instance-sizing, chargeback, or budget question — when an economic_buyer, technical_owner, or analytics_lead asks about spend, budget guardrails, workload cost drivers, plan fit, vendor cost comparisons, or whether MotherDuck is worth adopting.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

motherduckdb

motherduckdb/agent-skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de presupuestoOperaciones empresariales y financieras·SOC 13-2031

Explorador de archivos

2 archivos

SKILL.md

readonly

name	motherduck-pricing-roi
description	Explain MotherDuck pricing and ROI tradeoffs. Use for any pricing, cost, billing, plan-comparison, instance-sizing, chargeback, or budget question — when an economic_buyer, technical_owner, or analytics_lead asks about spend, budget guardrails, workload cost drivers, plan fit, vendor cost comparisons, or whether MotherDuck is worth adopting.
argument-hint	["workload-or-pricing-question"]
license	MIT

Pricing and ROI

Use this skill when the user is asking whether MotherDuck is financially sensible for their workload, team, or project. This is a workflow skill focused on cost framing, not implementation detail.

Source Of Truth

Always verify current numbers, plan limits, and feature entitlements against the live public pricing page before answering.
If the MotherDuck MCP ask_docs_question feature is available, use it first for pricing-related documentation lookups.
Use the live pricing, Hypertenancy, and Trust & Security pages for exact commercial framing.

Default Posture

Do not hardcode pricing numbers unless you have verified them in the current turn.
When quoting numbers, include the verification date and the public source you checked.
Separate storage, compute, and operational complexity in every answer.
Map workload shape to cost shape before comparing vendors or plans.
Treat many pricing questions as risk, predictability, or procurement questions rather than purely technical ones.

Workflow

Identify the workload shape, team size, and comparison baseline.
Determine whether the real concern is raw spend, predictability, procurement, or operational overhead.
Map the workload to MotherDuck cost buckets and plan posture.
Frame ROI in terms of systems replaced, complexity removed, and faster delivery.
Call out what still needs live pricing-page or sales confirmation.

Open Next

Read references/PRICING_ROI_PLAYBOOK.md for workload-to-cost mapping, publicly safe talking points, ROI framing, and what not to promise

Related Skills

motherduck-connect when the pricing discussion depends on connection-path choices
motherduck-security-governance when compliance, residency, or commercial controls affect ROI
motherduck-build-cfa-app and motherduck-build-dashboard when the economics depend on the application architecture

Más de este repositorio

mismo repositorio

motherduck-build-cfa-app

motherduckdb/agent-skills

Design a MotherDuck-backed customer-facing analytics app. Use for embedded analytics, multi-tenant SaaS reporting, or product analytics for external users -- whenever the decision depends on per-customer isolation, backend routing, service-account boundaries, read scaling, or Hypertenancy-style patterns.

2026-07-1349

motherduck-build-dashboard

motherduckdb/agent-skills

Build a live MotherDuck dashboard as a Dive. Use when composing one shareable KPI, trend, and breakdown story over existing MotherDuck data, especially when the result should stay a saved workspace artifact rather than a full application.

2026-07-1349

motherduck-build-data-pipeline

motherduckdb/agent-skills

Design an end-to-end MotherDuck data pipeline. Use for ETL/ELT workflows -- choosing raw, staging, and analytics boundaries, bulk ingestion paths, transformation sequencing, dlt/dbt integration, publication targets, or whether DuckLake is actually required.

2026-07-1349

motherduck-connect

motherduckdb/agent-skills

Connect to MotherDuck from any application. Use when setting up database connectivity via the Postgres endpoint (recommended), pg_duckdb, native DuckDB API, or JDBC. Covers connection strings, authentication, SSL, and environment variable configuration.

2026-07-1349

motherduck-create-dive

motherduckdb/agent-skills

Create, edit, manage, share, or embed MotherDuck Dives — live React + SQL dashboards, charts, and data apps saved in the workspace. Use for any dashboard, chart, KPI display, or data visualization over MotherDuck data, and for Dive authoring mechanics such as get_dive_guide, useSQLQuery, local preview, version history, Dives-as-code, required resources, team sharing, or embedded Dive sessions.

2026-07-1349

motherduck-create-flight

motherduckdb/agent-skills

Create, schedule, run, and debug MotherDuck Flights — Python jobs that run on MotherDuck compute. Use whenever someone wants to create a flight, schedule a Python script or recurring job on MotherDuck, set up scheduled ingestion from Postgres, dlt sources, S3, BigQuery, Snowflake, or APIs, refresh aggregates or transformations on a cron, or operate flights with get_flight_guide, create_flight, run_flight, flight logs, secrets, schedules, and versions.

2026-07-1349

name	motherduck-pricing-roi
description	Explain MotherDuck pricing and ROI tradeoffs. Use for any pricing, cost, billing, plan-comparison, instance-sizing, chargeback, or budget question — when an economic_buyer, technical_owner, or analytics_lead asks about spend, budget guardrails, workload cost drivers, plan fit, vendor cost comparisons, or whether MotherDuck is worth adopting.
argument-hint	["workload-or-pricing-question"]
license	MIT

Pricing and ROI

Use this skill when the user is asking whether MotherDuck is financially sensible for their workload, team, or project. This is a workflow skill focused on cost framing, not implementation detail.

Source Of Truth

Always verify current numbers, plan limits, and feature entitlements against the live public pricing page before answering.
If the MotherDuck MCP ask_docs_question feature is available, use it first for pricing-related documentation lookups.
Use the live pricing, Hypertenancy, and Trust & Security pages for exact commercial framing.

Default Posture

Do not hardcode pricing numbers unless you have verified them in the current turn.
When quoting numbers, include the verification date and the public source you checked.
Separate storage, compute, and operational complexity in every answer.
Map workload shape to cost shape before comparing vendors or plans.
Treat many pricing questions as risk, predictability, or procurement questions rather than purely technical ones.

Workflow

Identify the workload shape, team size, and comparison baseline.
Determine whether the real concern is raw spend, predictability, procurement, or operational overhead.
Map the workload to MotherDuck cost buckets and plan posture.
Frame ROI in terms of systems replaced, complexity removed, and faster delivery.
Call out what still needs live pricing-page or sales confirmation.

Open Next

Read references/PRICING_ROI_PLAYBOOK.md for workload-to-cost mapping, publicly safe talking points, ROI framing, and what not to promise

Related Skills

motherduck-connect when the pricing discussion depends on connection-path choices
motherduck-security-governance when compliance, residency, or commercial controls affect ROI
motherduck-build-cfa-app and motherduck-build-dashboard when the economics depend on the application architecture