Delegated Domain Allocation by Questbook - Arbitrum DAO Grants

I would like to thank all the community members and delegates for reviewing and sharing their comments on our proposal. Without your valuable inputs and feedback, it would not have shaped this way.

Proposal: Delegated Domain Allocation by Questbook

Category : Non-Constitutional AIPs

Abstract

  • We propose Arbitrum DAO to launch Arbitrum grants program with a budget of $1M spread across 2 quarters to fund a wide variety of teams building apps on top of Arbitrum in a transparent manner. Questbook is leading Compound grants program through delegated domain capital allocation model, a community-run grants program
  • We additionally propose that this budget be managed by 4 individuals called Domain Allocators - chosen from the community and by the community. These domain allocators would manage grants for a domain. These domains are strategic areas of focus for which Arbitrum wants to disburse grants
  • The performance of each of these domain allocators will be publicly viewable and auditable using rich dashboards. At the end of the quarter, the Arbitrum community can vote to replace, continue domain allocators or increase budgets for each domain allocator.
  • We (Questbook.xyz) will help facilitate setting up these domain allocators and provide the tooling to run the grants program in an efficient and transparent way. We have previously set up or currently setting up the grants process for Compound, Polygon, Solana, Celo, and Aave.

Motivation
As we continue to experience the depth of the bear market, it is increasingly important for Arbitrum to retain the mindshare of key ecosystem contributors and incentivize builders to build on top of it. Grants program is a great way to attract high-quality builders and grow the ecosystem more quickly. This proposal details the benefit to all the stakeholders involved - token holders, builders and DAO members.

Rationale (Benefits to Arbitrum)

Giving the elected domain allocators the capital and decision-making powers can increase the efficiency of the grants program, without compromising on accountability:

  • Individual expertise instead of collective blindspots
  • Distributed load instead of committee backlogs
  • Accountability instead of diffusion of responsibility

The proposed structure will lead to the following outcomes:

  1. Aligned allocation of funds: By leveraging the Delegated Domain Allocator (DDA) model, Arbitrum DAO can ensure that funds are allocated to projects that align with the domain (selected by the Arbitrum community), promoting efficient and effective use of resources. This approach aligns with Arbitrum’s goal of enabling the distribution of grants and empower the community to build and participate in the future of the Arbitrum.
  2. Increased transparency: The Delegated Domain Allocator approach provides a clear and transparent process for allocating funds, ensuring stakeholders understand the decision-making process and building community confidence. Questbook, a decentralized grant management platform, provides a transparent space for teams to showcase their backgrounds and experience. In addition, Questbook’s reporting features will allow Arbitrum to quickly generate monthly reports on the allocation of funds, with the details for each grant proposal.
  3. Increased accountability: With a dedicated group of stakeholders responsible for allocating funds, the Delegated Domain Allocator approach promotes increased accountability, ensuring that the funds are used effectively and efficiently. Domain allocators can be replaced through a community vote if their performance is not up to the standards accepted by the community.
  4. Lower Turnaround Time (TAT): The Delegated Domain Capital Allocation model will help improve proposals’ turnaround time and overall outcomes for the ecosystem. An example of this is Compound who’s already leveraging the DDA model and has a communication TAT of less than 48 hours. The performance of domain allocators will be measured using objectives and key results (OKRs) to ensure goals are achieved efficiently and effectively.

  1. Strong Brand Recognition : The Delegated Domain Allocator model will play a crucial role in boosting developer engagement with Arbitrum, as well as forming strategic partnerships with important ecosystems to jointly fund grants in mutually beneficial areas.

Specifications
The program structure focuses on having community members as domain allocators. Arbitrum DAO will be required to set a budget of $1M to be disbursed by 4 domain allocators and for committee compensation. Each domain allocator will be elected by the community. Interested community members can self-nominate themselves to be considered for becoming a domain allocator. The domain allocator for each domain will be selected via a community-wide Snapshot vote. Domain allocators will run their domain on-chain for full transparency. The data and performance across key metrics will be visible to the community in order to evaluate the domain allocator’s performance.

The disbursement of the grant will take place on-chain from a multi-sig wallet for each domain controlled by the program manager & the domain allocator. The domain allocators will approve or reject proposals based on their evaluation. The program manager will then coordinate with the Arbitrum team and the community to ensure that the proposal is aligned with Arbitrum’s roadmap before making the disbursal. The sole purpose of the multi-sig is to make sure capital is not being siphoned. However, the allocators are encouraged to make independent decisions in consultation with the Arbitrum team regarding the approval of the proposal based on their expertise.

The grants committee and the Arbitrum community shall evaluate the performance of each domain and domain allocator using publicly available data. The outcomes could be as follows:

  1. Change the domain
  2. Change the allocator/program manager
  3. Change the budget

Active community members can also initiate a no-confidence motion to initiate a review off-cycle. This can be initiated by one of the active delegates on Snapshot. The program manager can coordinate this, if the situation arises, along with the active community members. The unused funds from every domain will be returned to the treasury at the end of the quarter.

Product Screens

Invite proposals to your grants program

Anyone from the community can view and comment on the proposals

Invite community members to review proposals based on an evaluation rubric

Make milestone-based payouts directly from the multi-sig

Track the performance of the grants program

Steps to Implement
Arbitrum Grants Committee

The program will consist of

  1. A Program Manager
  2. 4 Domain Allocators

A Grants SAFE, with 4/6 multi-sig, between the program manager and 4 domain allocators will be setup. We will then have 4 SAFEs for each of the domains with a 2/2 between the program manager and the specific domain allocator.

The funds for the grants program will flow from the treasury into the Grants SAFE. This SAFE will hold the funds related to the grants budget and committee compensation. Funds that will be disbursed to the proposers will reside in the domain-level SAFEs. The program manager will be responsible to update the community about approved proposals and their details through bi-weekly community calls and reports over discord.

We have identified the following domains based on our thorough research and the feedback from the Arbitrum team and community.

Domain Credentials Needed Why it is relevant
Gaming Experience in game development or a deep understanding of Web3 gaming industry. This will help Arbitrum encourage more developers to create innovative gaming experiences and thus onboard new users to its ecosystem
Developer Tooling on NOVA Core contributor to Arbitrum and popular L2s in Web 3 This will help Arbitrum build essential infrastructure, tooling for Arbitrum Nova
New Protocol Ideas Core contributor to Arbitrum protocol This will encourage more contributors to propose and run experiments for improving the Arbitrum protocol
Education, Community growth and events Experience in builder community growth and technical bootcamps This will help Arbitrum attract quality builders through community growth activities such as education courses, bootcamps, hackathons and sponsoring events

Domain Allocator Roles & Responsibilities:

The following will be the roles and responsibilities of the selected domain allocators.

  1. Time commitment per week: Maximum of 25 hours per week for the program manager and 15 hours per week for the domain allocator, which might vary based on the number of applications. The program manager will ensure that the workload is evenly distributed

  2. Program Manager:

    1. Communication:

      1. Work with the Arbitrum team and the elected domain allocators to create and list out the necessary RFPs
      2. Identify key areas and relevant ecosystem partners who will co-fund grants alongside Arbitrum
      3. Create marketing content for communicating RPFs to the builders
      4. Coordinate between Arbitrum team and the community regarding cohort announcement and funding requirements
      5. Communicate the information regarding approval/rejection of proposals to the Arbitrum community regularly
      6. Attend community calls, actively participate in the community forum, and keep the community updated and take their feedback on the program
      7. Regularly update the progress of the grants program to the Arbitrum community over Discord and community calls
      8. Bi-weekly reporting of key metrics of the grants program and progress each selected project such as:
      Metric Details
      Names and summary of accepted proposals Total number of proposals that have been accepted by each domain allocator along with the proposal summary
      Grant Amount Disbursed Names of the proposal that have been awarded a grant amount along with the proposal summary and grant amount
      Milestone Completion Rate Each team should have a clear set of milestones and deliverables that they need to achieve. Program manager will share the status on milestone completion for each project
      User Engagement Number of users onboarded by a grantee onto their project
      TVL TVL (if applicable) of selected projects
      Project Completion Rates Number and names of projects who have completed all milestones
      Growth in community engagement Measured by number of followers of the project across different social media platforms, Discord community members
      External Funding Number of projects that have raised follow on capital after getting a grant from Arbitrum
    2. Grants Program:

      1. Source good-quality proposals from developer communities
      2. Sign the transactions for the approved projects
      3. Ensure a quick turnaround time for proposers regarding their proposal decision
      4. Coordinate between the domain allocators to ensure that the workload is evenly distributed and take their feedback consistently
  3. Domain Allocator:

    1. Review proposals received for their domains based on the rubrics set by the domain allocator
    2. Reject/Approve proposals and coordinate consistently with the program manager
    3. Source applications by reaching out to developer communities in their network
    4. Discuss program improvements with the other domain allocators and program manager during scheduled meetings.

Compensation :
The grant budget will be $1M with $200k for each domain. The committee compensation will be $200K for 4 domain allocators and one program manager for 6 months. Note that this is the proposed budget. All unused funds from every domain and committee compensation will be returned to the treasury. The compensation for Domain Allocators and Program Managers has been factored into this overall proposed budget. Please find below its details.

P.S

  1. We are inviting applications for all domain allocator roles. Once this proposal passes through Snapshot, we will create a separate forum post for the nomination of domain allocators. Delegates and community members can self-nominate themselves under the post for two weeks. After the nomination period, a snapshot vote will be conducted.

Conclusion

What does success look like?

  • Objective
    • The prime objective of this model is to have domains that align with Arbitrum’s priorities. This way the contribution of the projects as part of the grants program is directly adding value to the DAO and the token holders.
    • Increase in the number of builders, proposals, and funded projects
    • Number of partners who are co-funding grants alongside Arbitrum in mutually beneficial areas
    • Increase in the homegrown leadership to run grant programs (measured by the number of people running grant programs)
    • Increase in the community members’ participation to keep grant programs accountable (measured by the number of people looking at the dashboard and participating in the program)
    • Diversity in projects being funded across technologies, geographies, and demographics, to name a few. We encourage the community to regularly review the project domains during Arbitrum’s community call
    • Increased engagement in builder community’s
      • Discourse
      • Discord, Telegram
      • Social media (Twitter, Reddit)
      • GitHub
  • Subjective
    • Improved community involvement in the grants program
    • Strengthened builders’ sentiment towards Arbitrum
    • Enhanced Arbitrum’s brand recognition in builder circles

KPIs

  • Each domain allocator is required to work alongside program manager and come up with domain-specific rubrics similar to the following in order to evaluate the proposals. If the identified rubrics are not in line with the domain or Arbitrum’s roadmap, anyone from the community can openly suggest changes or question them on the forum
Score 0 1 2 3 4
Developer Reach No project developer team. No developer attraction. No dev team. Small attraction plan (1 to 5 devs). Yes team dev. Yes team dev. Small attraction plan (1 to 5 more devs). Yes team dev. Big attraction plan (+5 more devs).
Developer Commitment No commitment attraction Mercenary commitment attraction (stays until benefits end) Commitment attraction (1 to 3 months ) Commitment attraction (1 year) Commitment attraction (3 year)
Developer Quality* Project does not have a reasonable chance to attract high-quality devs Project has a possibility of attracting high-quality devs Project has a reasonable possibility of attracting high-quality devs and/or has high-quality devs Project is likely to attract high-quality devs Project is highly likely to attract high-quality devs
Likelihood of success Clear flaw in design that cannot be easily remedied Difficult to see the project continuing for more than a year Reasonable chance that the project has intermediate-to-long-term success (+1 Year) Project is likely to generate long-term, sustainable value for the ecosystem Project has substantial likelihood to generate long-term, sustainable value for the ecosystem
Grant size Grant size significantly outweighs projected benefit Grant size is considerably larger than expected benefit Grant size is proportional to expected benefit Expected benefit outweighs grant size Expected benefit meaningfully exceeds grant size
Team assessment Team does not substantiate ability to deliver on plan Team does not show significant ability to deliver on plan Team shows reasonable ability to deliver on plan Team shows significant ability to deliver on plan Team exceeds what is required to deliver on plan
Milestone Assessment Milestones do not significantly hold proposer accountable Milestones are unlikely to hold proposer accountable Milestones are reasonably likely to hold proposer accountable Milestones are significantly likely to hold proposer accountable Milestones are very likely to hold proposer accountable
Demo included (binary yes/no) No demo included Demo included
Score -2 -1 0 1 2
Discretionary Factors (comment required)**
  • Total number of proposals received, number of proposals received for each domain, number of proposals funded, turn around time to take a decision and for disbursal, milestone and project completion rates
  • The program manager will share reports and conduct AMAs once every two weeks to ensure transparency and accountability.
  • We welcome any suggestions for additional qualitative or quantitative metrics not included above
  • Questbook product is a decentralized on-chain grants orchestration tool. Anyone from the community can view the data and create custom dashboards using the on chain data relevant to Arbitrum Grants Program in a permissionless manner.

Track the performance of the grants program

Anyone from the community can track the number of proposals, funding available for builders for a particular domain, and accepted proposals from the Homepage.

About Questbook:

Questbook’s role in Arbitrum’s Grant Program

  • Saurabh from Questbook will be the program manager. Thereafter, the program manager will be elected from the community. Saurabh was previously working very closely with the Program manager of Polygon, where he facilitated the disbursement of approximately $1 million in grants. Saurabh has received a grant from IoTeX to establish their grant program, and he works closely with the Program Manager of Compound Grants Program 2.0. Saurabh has spoken to more than 100 builders and teams over the last 6-8 months and understands what it takes to make a grant program successful - from both program manager and builder perspectives.
  • Questbook Grants tool will make sure the workflows are systematic and transparent.

Product Flows

  1. Posting a grant - Link
  2. Reviewing and Funding Proposals - Link
  3. Settings - Link
  4. Communicating with Builders - Link
  5. Funding Builders - Link

Credentials

  • Questbook (YC-W21) is a decentralized grant orchestration tool, currently being used by Compound, Polygon, AAVE, Celo & Solana Ecosystem
  • Saurabh from Questbook will be the program manager. Thereafter, the program manager will be elected from the community. Saurabh was previously working very closely with the Program manager of Polygon, where he facilitated the disbursement of approximately $1 million in grants. Saurabh has received a grant from IoTeX to establish their grant program, and he works closely with the Program Manager of Compound Grants Program 2.0. Saurabh has spoken to more than 100 builders and teams over the last 6-8 months and understands what it takes to make a grant program successful - from both program manager and builder perspectives.

Questbook Product Compensation:

  • We are willing to share the tool for free with Arbitrum Grants Program
  • However, for any specific ask from the grants team, to run the process more smoothly, we charge for the additional features based on the development overhead.

Timeline
We welcome any comments on our proposal from the Arbitrum community and would love to seek suggestions/answer any questions. At the end of 2 weeks and after incorporating feedback from the community, we will post the proposal on Snapshot for community voting for an additional 7 days. One this proposal is passed, community members will self nominate themselves on a different forum post. Subsequently, domain allocators will be elected by the community members from the pool of nominees through a Snapshot vote.

25 Likes

We have worked with Questbook serving as a domain allocator in Compound’s Grants program and have found Questbook to be great to work with. They are very communicative, open to feedback from the community, and provide a great service to DAOs.

Their dashboards create full transparency with on-chain records of grant submission, discussion, review, and milestone-based disbursements. Additionally, they work with each Domain Alloocator (DA) to create rubrics that help to create a standardized way to evaluate grants. The concept of Domain Allocators ensures someone is held accountable for each grant distributed and therefore ensures all grants are thoroughly vetted. Additionally, the ability to remove these DAs after 3 months helps to prevent collusion.

We support the idea of a pluralistic grants program as we believe this will help the DAO reach true decentralization. However, we think Questbook would be a great piece to the grants puzzle and could be easily and quickly implemented to kick off a grants program while the pluralistic framework is still being designed.

My only recommendation would be for the community to examine the domains Questbook has mentioned and discuss/suggest if they think there are others that could be more suited for Arbitrum such as a DeFi domain, a domain focused on protocol integration, or anything else the DAO can think of.

18 Likes

Good news, My only recommendation would be for the community to examine the domains

8 Likes

I like good news​:heart::heart::heart::heart:

3 Likes

I can support this idea, especially at a low level entry to start it out and give it a try to gauge results.

9 Likes

I was personally on Compound Grants Program 2.0 as the multi-chain domain allocator and on Optimisms DeFI Committee A in S2, and will outline some of my thoughts below.

We saw Optimism seasons go through an iteration cycle to reach their current program, where it’s 3 for builders and 5 for growth. A total of 8 + 1 Grant lead to cover 2 broad areas rather than domains. Here is a quick summary of their journey.

  1. Phase 1: Everyone with $OP tokens voted
  2. Phase 2: Committee provided recommendations & $OP token holders voted
  3. Phase 3: Committee votes ($OP not used for grant allocations anymore)

Comparing that to QB DDA program, means that there are 4 people who handle each domain. Domains are more specific so it’s different to Optimism “Areas” but it would be interesting to see whether it is worth having additional people handling a domain, i.e. 2 domain allocators for Gaming.

Even though it comes at a higher admin cost, this helps increase the knowledge held by the domain allocators and reduces the likelihood of one person acting as the barrier to entry. Admin costs for CGP 2.0 were much lower than expected, so it might be feasible to add additional allocators without additional funding.

I am an advocate for the QB tool and believe it tackles a lot of issues that both grantees and DAOs face in hosting a grant program such as opaqueness and lack of accountability within grants programs. Still, it would be interesting to see DDA program can be explored further with multiple allocators.

I believe the following domains are suitable for the initial two quarters as they tackle different areas that will help the Arbitrum ecosystem grow. These domains can be examined after the first or second quarter.

4 Likes

This is an interesting idea. I like that the cost of redundancy short term is worth a long-term benefit of holding context and making gatekeeping more difficult.

3 Likes

Thanks QB for the proposal.

Could you please offer some statistics and links on how the DDA program was able to help achieve the mission of the DAOs which have adopted the program? To be specific, I’d like to hear how the distributed funds were able to quantifiably help the DAOs in achieving their mission?

6 Likes

Hey @Ceazor and @Yuhana, Thanks for the kind words and appreciate your support

8 Likes

Hi @Matt_StableLab and @Aleksandr. Thank you for your kind words and for sharing your feedback. We welcome the Arbitrum community to provide their feedback on the proposed domains. We are open to incorporating their suggestions and making adjustments based on their input. Furthermore, I will actively participate in all upcoming community calls to seek feedback and input from the Arbitrum community.

7 Likes

Hey @Bobbay, thanks for sharing feedback and your valuable experience both as a CGP 2.0 domain allocator and as an Optimism DEFI Grants Commitee member. We are open to exploring different versions of DDA model based on the impact of the proposed model after the first or the second quarter.

I appreciate your support for the QB tool and its capacity to tackle problems related to lack of transparency and accountability in grant programs.

8 Likes

Hi @jengajojo, thanks for sharing your comments and thoughtful questions. The purpose of the DDA model is to help Arbitrum DAO achieve the following:

  1. Aligned allocation of funds: Using the DDA model, community elected domain allocators of CGP 2.0 have funded 29 high quality proposals aligned with its roadmap

  2. Increased transparency: The Delegated Domain Allocator approach provides a clear and transparent process for allocating funds, ensuring stakeholders understand the decision-making process and building community confidence. Questbook, a decentralized grant management platform, provides a transparent space for teams to showcase their backgrounds and experience.

  3. Increased accountability: Each domain in CGP 2.0 is managed by a community elected domain allocator. These DAs are required to source and fund the best proposals while being accountable to the community and proposers. CGP 2.0 Domain allocators may be replaced through a community vote if their performance is not up to the standards accepted by the community

  4. Turnaround Time (TAT): We’ve maintained a communication TAT of less than 48 hours through the DDA model. Please find below some of the metrics related to CGP 2.0 which is being managed through the DDA model.

Sharing some feedback from the builders of the CGP 2.0

Here is the impact created by 3 months of Compound Grants Program:

  • Total Proposals Received 75
  • 29 proposals approved [38.6%]
  • 15 applications first milestone completed
  • 2 2nd milestone completed
  • 1 3rd milestone completed.
  • The total amount of funds committed*
  • Protocol ideas and dapps by allthecolors: $247K
  • Security tooling by Michael: $100K
  • Multichain Strategy by Bobby: $62K
  • Dev Tooling by Madhavan: $22K
  • Total amount of funds disbursed*
  • Protocol ideas and dapps by allthecolors: $144K
  • Security tooling by Michael: $0K
  • Multichain Strategy by Bobby: $25K
  • Dev Tooling by Madhavan: $16K

Let us know if you have any other questions or concerns.

9 Likes

I don’t see the need to wait till after the first or second quarter. There is no harm in employing a hybrid version of this program now if we have suitable candidates. The DAO can decide whether they want one or two DDA for each domain via a poll.

As @DisruptionJoe highlighted, it makes gatekeeping more difficult. It also reduces the likelihood of preferential treatment.

4 Likes

Thinking on it, it makes sense to keep the program as similar to CGP2.0 as possible due to success we have seen with it. As you said we can explore multiple allocators in the future, but right now let’s stick with one allocator.

In support of the program as it is and look forward to seeing this getting implemented :slight_smile:

3 Likes

Thank you Bobby for the kind consideration and the apt response. Sharing the learnings from the experience of setting up Polygon and Compound Grants Program to throw some more light on this aspect.
In the context of single vs multiple domain allocators:

  • The decision-making has to be unambiguous. What if there are scenarios where one domain allocator approves the project and the other doesn’t? This opens up the possibility of applications falling under the “no-result” category,
  • The decision-making has to be quick while being decentralized. The concept of choosing one domain allocator for the community is to strike the balance between speed and decentralization Having more than one DA for the same domain, increases the TAT - the current process ensures 48 hours of TAT. We also feared a potential friction between the domain allocators during a disagreement, hence we have a very clear distinction of the scope of the domains and the decisions of the domain allocators.
  • Single Point of Contact: The communication to applicants is very clear right now at CGP because the domain allocator is the single point of contact for their proposals. Didn’t want to disturb this approach, while it was working.
  • One of the strongest learnings we had from evaluating some failed grant programs was the diffusion of responsibility and reduced accountability, wanted to absolutely avoid that.

Just to be clear, we are with you. We need multiple allocators given enough individual budgets, and clear scope of their domains and decisions. As you said, it is best to evaluate this approach in the future after accommodating learnings from this quarter too. :+1:

10 Likes

I would be in support of this proposal, as well as the Pluralist proposal this is tied to. In reading through the OP, some of the comments, as well as some discussion with Saurabh it sounds like the a solid solution to decentralized grant funding.

My only real question would be on the score rubric. It sounds like each of the four domains would have a separate rubric to grade off of. Based on:

Each domain allocator is required to work alongside program manager and come up with domain-specific rubrics similar to the following in order to evaluate the proposals.

My thought would be we’d want to maintain a consistent rubric across all the domains to be fairn across projects of different types. I’m assuming in your past experiences with other DAOs, having separate rubics per domain was a benefit over a standardized one per DAO? Mostly just curious to get a little more detail on that — your experiences and thoughts on those two methods of determining a rubric.

Otherwise, I don’t really see a reason to not at least give this project a shot for 6 months and then reassess it’s success.

6 Likes

Hey, thanks for supporting the proposal. I completely agree with your points. Having a standardized rubric across all domains could be more fair, but having domain-specific rubrics could also allow for more nuanced evaluation of proposals. From my experience with other DAOs, having separate rubrics per domain has been helpful in ensuring that proposals are evaluated on their specific merits and that domain experts are able to provide input on proposals within their area of expertise. Ultimately, I think it will depend on the specific needs and goals of this DAO, but I think it’s definitely worth discussing further.

14 Likes

Hi Saurabh! Thank you for making such a comprehensive, detailed proposal with a suitable budget and clear objectives. SEED Latam’s team supports this proposal - Questbook has shown to have extensive knowledge plus they have a good track record.

One thing that could be discussed a bit further, as some have mentioned before, is the Domains we choose, for example, we could have one dedicated to Arbitrum Orbit instead of dev tooling only for Nova or maybe one to support the development of Account Abstraction on Arbitrum - which could go in hand with this proposal. These are just some thoughts tho, and we’re open to see what others might have in mind - especially considering that these domains aren’t meant to last very long and could be used to support short term goals.

18 Likes

Hey @cattin, thank you to the whole Seed Latam team for supporting the proposal. I appreciate your feedback and suggestions! This proposal is tied to @DisruptionJoe’s Proposal and would be one of the Pluralistic grants programs. I appreciate your suggestion about having different domains, and we are open to exploring different domains that may align with the DAO’s short-term goals. Account Abstraction can also be included in the new protocols, dApps, and ideas domain. When we have the nomination period for the domain allocators, we can conduct a poll to determine which four domains should be funded, allowing the DAO and community to vote. We will take your suggestions into consideration. Please let us know if you have any other thoughts or ideas.

18 Likes

A quick update on how we are approaching the collaboration between Questbook and Plurality Labs.

7 Likes