motherduck-pricing-roi
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_questionfeature 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
references/PRICING_ROI_PLAYBOOK.mdfor workload-to-cost mapping, publicly safe talking points, ROI framing, and what not to promise
Related Skills
motherduck-connectwhen the pricing discussion depends on connection-path choicesmotherduck-security-governancewhen compliance, residency, or commercial controls affect ROImotherduck-build-cfa-appandmotherduck-build-dashboardwhen the economics depend on the application architecture
More from motherduckdb/agent-skills
motherduck-security-governance
Explain MotherDuck security, governance, and access-control patterns. Use when a security_compliance_owner, technical_owner, or application_builder is asking about residency, access boundaries, service accounts, isolation, sharing, or governance posture.
48motherduck-query
Execute DuckDB SQL queries against MotherDuck databases. Use when running analytics, aggregations, transformations, or any SQL operation. Covers query best practices, CTEs, window functions, QUALIFY, and performance optimization.
44motherduck-build-data-pipeline
Design an end-to-end MotherDuck pipeline. Use when choosing raw, staging, and analytics boundaries, bulk ingestion paths, transformation sequencing, publication targets, or whether DuckLake is actually required.
44motherduck-ducklake
Decide when DuckLake is the right MotherDuck storage pattern. Use when evaluating fully managed DuckLake, BYOB, own-compute DuckLake access, data inlining, object-storage layout, or file-aware maintenance instead of native MotherDuck storage.
44motherduck-create-dive
Create, edit, manage, share, or embed MotherDuck Dives. Use when the work involves Dive authoring, live React + SQL components, MCP get_dive_guide, useSQLQuery, local preview, version history, Dives-as-code, required resources, team sharing, or embedded Dive sessions.
44motherduck-share-data
Create and manage MotherDuck data shares for zero-copy data distribution. Use when sharing databases with team members, other organizations, or making data publicly available.
44