motherduck-pricing-roi
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.
Works with
--- 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. 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 1. Identify the workload shape, team size, and comparison baseline. 2. Determine whether the real concern is raw spend, predictability, procurement, or operational overhead. 3. Map the workload to MotherDuck cost buckets and plan posture. 4. Frame ROI in terms of systems replaced, complexity removed, and faster delivery. 5. 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
More Backend Frameworks skills
git-guardrails-claude-code
mattpocock/skills
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
azure-compute
microsoft/azure-skills
Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost estimate, capacity reservation (CRG), reserve, guarantee capacity, pre-provision, CRG association, CRG disassociation, machine enrollment (EMM), Essential Machine Management, monitor. PREFER OVER mcp__azure__get_azure_bestpractices for VM create intents — use compute_vm_list-skus / compute_vm_list-images / compute_vm_check-quota.
azure-cloud-migrate
microsoft/azure-skills
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration.
