> For the complete documentation index, see [llms.txt](https://committees.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://committees.docs.intersectmbo.org/intersect-budget-committee/committee-meeting-notes/2026-meeting-notes/budget-committee-weekly-meetings/august-3rd-2026-budget-comm-minutes.md). # August 3rd, 2026 Budget Comm Minutes ### Budget Committee Weekly Meeting — August 3rd, 2026 **Date:** August 3, 2026\ **Time:** 13:00 UTC **Attendees:** Megan Hess (Chair), Kristijan Kowalsky (Vice Chair) Eric Helms (SCATDAO), Fanny Wijaya, Rodrigo Pacini, Christina Gianelloni (SME), Simo Simovic (Acting Secretary) **Quorum:** Confirmed (5 of 10 voting members present) *** ## 1. Opening Simo Simovic opened the meeting, confirmed quorum, and welcomed attendees. The primary agenda item was to review the results of the 2026 Budget Process retrospective survey and discuss how the committee should use the feedback to inform future improvements. *** ## 2. Review of the Budget Process Retrospective The committee reviewed the initial results of the retrospective survey, which received 20 responses from community members, proposal submitters, and DReps. Overall, respondents indicated strong support for maintaining a structured budget process, with an average importance rating of 4.65 out of 5. The survey identified **Adoption & Utility** and **Community & Ecosystem Growth** as the highest priorities for future budget cycles. Respondents also highlighted opportunities to strengthen future processes through clearer review criteria, stronger proposal requirements, measurable KPIs, milestone-based reporting, conflict of interest disclosures, and improved accountability. Most respondents expressed a preference for beginning the 2027 Budget Process during **Q4 2026**. *** ## 3. Survey Representation and Community Feedback The committee discussed whether the survey results were sufficiently representative to guide future recommendations. Members agreed that, while the responses provided valuable insights, the sample size was too small to accurately reflect the views of the broader ecosystem. It was also noted that several responses came from committee members themselves, introducing potential bias. To improve the quality of the retrospective, members agreed that additional feedback should be collected from a broader range of stakeholders, including DReps, governance action submitters, proposal vendors, and organizations that participated in the 2026 Budget Process. *** ## 4. Expanding Stakeholder Engagement The committee agreed that targeted outreach would provide more meaningful feedback than relying solely on a publicly available survey. Members discussed coordinating direct engagement with DReps, proposal submitters, vendors, and other ecosystem participants. In addition to extending the survey period, the committee supported using workshops and one-to-one conversations to gather qualitative feedback that could complement the survey results. A shared tracking document will be created to coordinate outreach efforts and consolidate feedback received across committee members. *** ## 5. Planning for the 2027 Budget Process The committee discussed several external developments that may influence planning for the next budget cycle, including ecosystem organizational changes, broader governance developments, and regulatory uncertainty. Members agreed that stakeholder feedback collection should continue; however, it would be premature to develop formal recommendations for the 2027 Budget Process until there is greater clarity regarding the Board's expectations and the committee's future role within the budget process. *** ## 6. Actions and Next Steps The committee agreed to continue expanding the retrospective effort before developing recommendations for the 2027 Budget Process. The following next steps were identified: * Identify which DReps have already completed the retrospective survey. * Coordinate targeted outreach to DReps, proposal submitters, proposal vendors, governance action participants, and other ecosystem stakeholders. * Create a shared tracking document to coordinate outreach activities and capture stakeholder feedback. * Extend engagement through workshops, community discussions, and direct conversations in addition to the survey. * Obtain access to the retrospective survey data and supporting documentation to enable continued management of the feedback process. * Continue monitoring ecosystem developments while awaiting further strategic direction from the Board before preparing recommendations for the 2027 Budget Process. --- # 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://committees.docs.intersectmbo.org/intersect-budget-committee/committee-meeting-notes/2026-meeting-notes/budget-committee-weekly-meetings/august-3rd-2026-budget-comm-minutes.md?ask=&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.