# \[Temp Check\] Implementation of an RFP Framework for Service Provider Engagements

**URL:** <https://governance.aave.com/t/temp-check-implementation-of-an-rfp-framework-for-service-provider-engagements/14643>\
**Category:** General\
**Created:** [August 26, 2023, 5:51am UTC](https://governance.aave.com/t/temp-check-implementation-of-an-rfp-framework-for-service-provider-engagements/14643 "2023-08-26T05:51:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![kpk](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/kpk/32/14763_2.png) [@kpk](https://governance.aave.com/u/kpk)\
**Post date:** [August 28, 2023, 6:50pm UTC](https://governance.aave.com/t/temp-check-implementation-of-an-rfp-framework-for-service-provider-engagements/14643/3 "2023-08-28T18:50:12Z")

</div>

We support this initiative, which we see as an obvious evolutionary step towards an effectively managed DAO.

As @benhoneill pointed out, passively waiting for Service Provider proposals to dictate what’s in the DAO’s best interest doesn’t seem the most efficient way for conducting community-wide strategic planning, let alone fostering market-driven price/SLA discovery mechanisms.

In our opinion, it should be the other way around: the community should decide on the most compelling topics/areas of focus to invest in based on the available budget and optimise for short-term ROI.

Today, the DAO is currently allocating its Service Provider budget to the following areas:

- **Technical Development:** maintenance, improvement, and support of the multiple components that comprise the Aave ecosystem’s architecture (e.g. Aave v2/v3; Governance v2/v3; Safety Module; GHO; GSM; UIs; etc.), including the launch of these on new chains ([BGD](https://app.aave.com/governance/proposal/?proposalId=71); [Aave Companies](https://app.aave.com/governance/proposal/?proposalId=98));
- **Grants:** community-led grants program, focused on growing an ecosystem of contributors within Aave through funding ideas, projects, and events that benefit the ecosystem ([Aave Grants DAO](https://app.aave.com/governance/proposal/145/));
- **Security:** smart contract auditing, as well as specification development for the Aave protocol ([Certora](https://app.aave.com/governance/proposal/?proposalId=114); [Sigma Prime](https://snapshot.org/#/aave.eth/proposal/0x099a932f4e11a07b462f91257d2e5e899df25f6f43547644c681ac5addb38a9d));
- **Risk Management:** risk assessment and risk parameter recommendations to optimise capital efficiency Vs insolvency risk and liquidations ([Gauntlet](https://app.aave.com/governance/proposal/?proposalId=133); [Chaos Labs](https://app.aave.com/governance/proposal/?proposalId=113));
- **Governance:** Coordination of Aave governance discussions, development and submission of Snapshot votes & AIPs, and collaboration with Delegates and Stakeholders ([ACI](https://app.aave.com/governance/proposal/?proposalId=202));
- **Protocol and Ecosystem Development:** Support the onboarding of strategic assets to the Aave ecosystem, push for product innovation and improvement (e.g. GHO; Safety Module), and foster the expansion of the protocol to new chain ecosystems ([ACI](https://app.aave.com/governance/proposal/?proposalId=202));

The end of [Llama’s Service Provider Agreement](https://app.aave.com/governance/proposal/?proposalId=104) will leave a void that will need replacement (even if not necessarily for the entire scope). This is the perfect opportunity to execute differently and potentially avoid the pitfalls that led to the [unexpected reduced stream](https://governance.aave.com/t/arfc-cancel-llama-service-provider-stream/14137/58?) for Llama’s last two months: an undesired outcome both for the DAO and for the Service Provider.

We’d be keen to know the opinion of more experienced Delegates, especially the ones involved in this domain e.g. @MarcZeller; @fig; @Kene_Anode.

---

_[View the full topic](https://governance.aave.com/t/temp-check-implementation-of-an-rfp-framework-for-service-provider-engagements/14643)._