DESK NOTE / 001 · METHODOLOGY EXAMPLE
From governance decision
to opportunity.
The difference between a promising headline and a useful lead is the evidence connecting a decision to work someone can actually apply for.
About this sample
This is an original demonstration of our research method. It is not a current opportunity listing, a completed client engagement or a claim that funding is available. An actual brief would include dated findings and source links for the specific organizations in scope.
1. Separate the stages
Proposal, approval, procurement and payment describe different events. A treasury balance alone does not establish that a team has a budget for your service.
| Stage | Evidence to look for | What it does not establish |
|---|---|---|
| Proposed | A governance post with a defined request. | Approval, funding or an invitation to apply. |
| Approved | A final decision and its implementation conditions. | That money remains available or vendors are being recruited. |
| Open | A current request, application route and stated eligibility. | That a particular applicant qualifies or will be selected. |
| Paid | A payment record linked to the correct recipient and purpose. | That the work was completed or that another contract is available. |
2. Build the evidence record
For each potential opportunity, record the organization, original source, request, budget status, application deadline, eligibility, contact route and last-checked date. Add a separate field for facts that remain unconfirmed.
Use primary documents wherever possible. Treat an unanswered question as an uncertainty to resolve, rather than filling the gap with an assumption.
3. Establish fit before recommending action
- Capability: Can the provider demonstrate the work requested?
- Eligibility: Are there location, identity, experience or other requirements?
- Economics: Does the potential engagement justify the application and delivery effort?
- Payment: Are the denomination, milestones, acceptance criteria and payment route clear?
- Availability: Is the request still accepting applications, and who can confirm that?
4. Reconcile governance with activity
Spending analysis should connect the decision, the disclosed wallet, the transaction and the stated purpose. Identify internal transfers separately so they are not counted as expenses twice. Label fees and refunds, and keep token quantities separate from any chosen fiat valuation.
A wallet address does not prove the identity of a person. A token transfer does not, on its own, prove that an invoice has been settled. Customer records or direct confirmation may be necessary.
5. End with a next step
A useful brief ends with a specific action: apply through the stated channel, request eligibility clarification, monitor a decision, or rule the opportunity out. The deliverable should say what is known, what remains uncertain and why the proposed next step follows.
Primary-source starting points
The documents below illustrate governance and procurement mechanisms. They are background references, not recommendations to apply or assertions that a program is currently open.
- Arbitrum: RPC service-provider procurement framework — an example of a defined provider application process.
- ENS: service-provider program proposal — an example of funding tied to ecosystem services.
- Safe: infrastructure documentation — a starting point for understanding supported transaction data access and its limits.
What a tailored engagement can include
An agreed research question, an evidence table, concise findings, a list of unresolved questions and recommended next steps. The number of organizations, depth of review, timing and fee are agreed before work starts.