> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/extension-framework/case-studies.md).

# Case Studies

The following case studies show the Extension Framework in action across two production applications. Their purpose is to make one point concrete: the framework is domain-agnostic. The resource model, the ticketing system, the skill-driven execution engine, the RBAC, and the cost management system are all shared infrastructure. What differs between applications is only the policy model — the resource taxonomy — and the skills that encode each domain's operational logic.

The two applications covered here could not be more different. One automates cloud infrastructure: VPCs, Kubernetes clusters, IAM roles, and workloads. The other automates sales demand generation: prospect cohorts, ICP qualification, and outreach sequencing. Both were built on the same CaaS platform, using identical framework mechanics. A team that understands how one application works can read the other and recognize every pattern immediately.

## The Pattern

The table below maps the same conceptual framework elements across both domains. Every column is the same object — only the domain-specific label and content change.

| Concept          | DevOps                  | SalesOps                       |
| ---------------- | ----------------------- | ------------------------------ |
| Resource         | Network                 | Account                        |
| Spec             | Region, CIDR, AZs       | Company name, website          |
| Skill            | CloudFormation template | ICP qualification criteria     |
| Provider / Scope | AWS credentials         | Apollo API                     |
| Result           | VPC ID, subnets, SGs    | Signal verdicts, leads         |
| Status           | Provisioning → Ready    | Processing → Complete          |
| Cost tracking    | Per resource            | Per account ($0.636 example)   |
| Dependency       | Cluster needs Network   | Engagement needs Qualification |
| Troubleshooting  | Track Status → Ticket   | Track Status → Ticket          |

Two completely different operational domains, one framework, one platform. See the [AI-Native DevOps Platform](/docs/extension-framework/case-studies/devops-platform.md) case study for a detailed walkthrough of cloud infrastructure automation, and the [AI-Powered SalesOps](/docs/extension-framework/case-studies/salesops-platform.md) case study for demand generation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/extension-framework/case-studies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.