Request for Proposals (RFP)
How the Carrot ecosystem sources new methodologies — RFP types, lifecycle, and evaluation process.
What is an RFP?
A Request for Proposals (RFP) is a formal call in which the Carrot Foundation invites experts, developers, and organizations to submit proposals for a specific challenge, build a solution, or contribute to the platform ecosystem. Think of an RFP as a bridge between a need identified by Carrot (or the market) and the talent available in the community.
The RFP mechanism is central to Carrot's mission because it reflects three principles:
- Transparency — Public criteria and a documented process ensure every participant has the same information.
- Meritocracy — The best proposal wins, regardless of who submits it.
- Community engagement — The community participates actively in building the platform.
Who can participate?
Any individual or organization can participate in a Carrot RFP, provided they meet the eligibility criteria defined in each call.
To preserve impartiality, community members eligible for deliberative governance processes cannot serve as evaluators on RFPs to which they have submitted a proposal.
RFP types
Not all RFPs are the same. Each type is designed for a specific kind of contribution — the type determines what is expected from the proponent, which documents to submit, and how the proposal will be evaluated.
| Type | Name | Description |
|---|---|---|
| A | Problem-solving | Carrot identifies a problem or question and invites the community to propose approaches, analyses, or conceptual solutions. The focus is on idea quality, not immediate execution. |
| B | AMC Project | An Advance Market Commitment funds the construction of infrastructure — composting facilities, collection systems, or recycling chains. The proponent presents a full implementation and delivery plan. |
| C | MvF Build | A call to translate a validated scientific methodology into an operational Methodology Verification Framework. The proponent must demonstrate domain mastery and the ability to structure the artifacts the Carrot platform uses to execute the methodology. |
| D | MvA Build | A call to implement an approved MvF as code. The deliverable is the MvA (Methodology Verification Application) — the software that performs digital verification on the platform. Requires a completed MvF as a prerequisite. |
| E | Technology Solution | Development of a feature, tool, or integration for the Carrot platform. The deliverable is functional, tested, and documented code. |
| F | Open | Reserved for calls that do not fit other types. New categories may emerge as ecosystem needs evolve. |
Evolving types
New RFP types may be created as new needs arise in the ecosystem. Carrot reserves the right to create or revoke types at any time, always respecting processes already in progress.
Type dependencies
Some RFP types have natural dependencies. For example, a Type D (Methodology Verification Application (MvA) Build) can only be opened after a Type C (Methodology Verification Framework (MvF) Build) is completed, because the code needs an approved framework as reference. Similarly, a Type B (AMC Project) can generate subsequent Type C, D, and E needs — when an infrastructure project requires a new methodology to be operationalized and technology tools to function on the platform.
When reviewing an RFP, check whether it references dependencies on prior or concurrent calls.
Lifecycle
Every Carrot RFP follows a standardized lifecycle with 10 phases, ensuring each call goes through the same preparation, engagement, evaluation, and execution stages regardless of type.
- Conception — Carrot (or the market) identifies the need that originates the RFP and defines its initial scope.
- Structuring — The RFP is drafted with scope, eligibility criteria, expected deliverables, timeline, and evaluation matrix.
- Publication — The RFP is published and the community is notified. From this point, the document is public.
- Submission — Proponents prepare and submit their proposals within the established deadline.
- Triage — Proposals are checked against eligibility criteria. Those that do not meet minimum requirements are disqualified.
- Evaluation — Eligible proposals are scored individually by independent evaluators using the weighted criteria matrix.
- Selection — Proposals are ranked by final score and the evaluation committee makes a decision.
- Contracting — The selected proponent negotiates final terms and formalizes the agreement with the Carrot Foundation.
- Execution — Work proceeds according to the agreed timeline, with periodic oversight by Carrot.
- Closure — Deliverables are verified, work is formally accepted, and lessons learned feed future calls.
Key periods
Each RFP defines its own timeline, but two periods deserve special attention:
Q&A period — Between publication and the submission deadline, there is a window to submit questions. Answers are consolidated in a public FAQ available to all proponents. No privileged information is provided individually.
Submission deadline — Non-negotiable. Proposals received after the deadline will not be considered under any circumstances. We recommend submitting at least 24 hours early.
Alternative entry channels
Although the RFP is the preferred mechanism, the ecosystem also accepts methodologies via strategic partnerships and direct initiative. In these cases, the proponent submits the proposal directly to Carrot, which evaluates relevance and quality using the same criteria applied to RFPs — preserving integrity, auditability, and ecosystem alignment requirements. The difference is that partnerships and direct submissions are evaluated on individual merit, without competition between proposals.
For practical guidance on participating in RFPs, see the RFP Participation Guide.
RFP Participation Guide · Methodology Lifecycle · Methodology Ecosystem