# DPI advisory

The Centre for DPI is:&#x20;

1. Software neutral: We have no product offering of our own and can provide tech architecture advisory regardless of the software you use.&#x20;
2. Technology neutral: We are happy to support countries regardless of whether they choose open source or private procurement.
3. Financing neutral: We don't provide funding or accept payment for our services. We are philanthropically funded and work on a pro bono basis.&#x20;
4. Government neutral: We are a global team, happy to work with any interested government and have no political alignment.&#x20;
5. Country neutral: Our team spans 5 countries and 3 continents, and we work with global development partners, tech providers, and funders without preference for one over another.

<mark style="background-color:purple;">At CDPI, we are only biased towards one thing: Implementation!</mark>

Whichever country, government, funder, technology and software can help DPI implementation roll out in accordance with best practices, and fast timelines, we are happy to support them and work with them to promote global DPI implementation in the country's best interests.

CDPI has team members who have rolled out DPI projects at scale in their own countries, and continue to do so in various contexts. This includes Daniel Abadie, who oversaw Argentina's verifiable credentials system;Emmanuel Khisa who worked on ID and Payments in Africa, and Pramod Varma, the chief architect of the India Stack.

Any country can approach CDPI (please email <info@cdpi.dev>) to engage with us. CDPI can help share some knowledge and insights on the best practices to adopt while designing their digital transformation journeys to ensure they reach scale in sustainable manners, power public and private innovation, and are able to create interoperable, reusable building blocks with minimal funding and resource constraints.

The engagement with CDPI can be as low-touch or intensive as the country chooses. Since CDPI doesn't undertake any project management, funding, or software offering, the complete control over the engagement remains with the country, with CDPI supporting however the country sees fit.

There are three levels of engagement typically carried out between a country and CDPI. The engagement can progress from one level to the next based on the country's interest and progress.

1. **Conversational:** CDPI informally talks to country representatives to understand the ecosystem, provide broad guidance on the DPI approach, share best practices, and identify powerful +1s to existing initiatives through virtual calls.
2. **Co-Creation:** A country chooses to engage with CDPI on a specific use case or project to collaborate on a detailed strategy note, align stakeholders, and build out the tech architecture through virtual calls that may be accelerated through physical visits if required.
3. **Roll-out Action:** A country is rolling out the DPI pilot or project in line with the advice received from CDPI and its other stakeholders, and needs continued support as they reach scale.&#x20;

For more information on how CDPI can engage with countries, please feel free to reach out to us at <info@cdpi.dev>. To understand how CDPI can provide pre-packaged DPI product, policy, and program management kits for rapid deployment, please see [DPI as a packaged Solution (DaaS)](/initiatives/dpi-as-a-packaged-solution-daas.md).&#x20;


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cdpi.dev/initiatives/dpi-advisory.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
