# Why do we need DaaS?

Challenges of Current DPI Implementation that DaaS Seeks to Address

The ground realities of implementation vary not just from country to country, but also by region. Yet a few common challenges in DPI rollouts persist across contexts: 

1. An <mark style="color:red;">**inherent friction between need and speed of rollout:**</mark> the need for the DPI is urgent for people, but there are often challenges in speed of implementation.
2. The <mark style="color:red;">**local capacity**</mark> to architect and build minimalist technology infrastructure solutions may be low or vary at different levels of government.
3. There may be <mark style="color:red;">**funding or budget gaps**</mark> for execution (not just for the new software systems but also for compute/hardware).
4. <mark style="color:red;">**Procurement cycles**</mark> may be long and tedious to kickstart progress. There are multiple hoops to jump through before a country can even test out the DPI block through a pilot. Some of these are shown below, indicating the complexity countries often face: many have a selection process to identify the team that would eventually craft the RFP to identify a final system builder.

<figure><img src="https://lh7-us.googleusercontent.com/27MGCm4rMwhzKxMl7U3SiaudlOsuBAMwKXDQv6iWeMhUttzmKF5LkszYsudv1aCPbN9nC4gMej3SW9tDv6uLzxuTaT4VelKuVbWtKw9ThDzexHRR08IqIQorupjTR9X9_l5bP9f_aeCHVYIq2Qa7ejM" alt=""><figcaption></figcaption></figure>

<mark style="background-color:green;">**These execution pains are real!**</mark> Initial planners are often unable to anticipate the exact system requirements eventually needed in nationwide infrastructure. They feel the need to anticipate and prepare for all eventualities, which is an extremely time-consuming process and often doesn’t yield results. The future is constantly evolving. The DaaS framing helps maintain focus on the current context while simultaneously allowing future innovations to be extensible in the future with minimal changes to its foundational protocols and systems. Creating optionality is a powerful strategy for large-scale digital projects.

In many countries there is no <mark style="color:green;">**demonstrated proof of success**</mark> to show others that the <mark style="color:green;">**DPI approach will work at an unprecedented scale**</mark> when applied to a specific use case, in that context, and for those outcomes. A DaaS phase one implementation rollout can help establish this conviction.&#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-as-a-packaged-solution-daas/why-do-we-need-daas.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.