Contract Wizard Proposal

[DiegoTorresborda]

Submitting Contract Wizard Proposal

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).

If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

• Level 1: Up to $10,000, 2 approvals
• Level 2: Up to $30,000, 3 approvals
• Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

• The application template has been copied and aptly renamed (project_name.md).
• I have read the application guidelines.
• Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
• The software delivered for this grant will be released under an open-source license specified in the application.
• The initial PR contains only one commit (squash and force-push if needed).
• The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
• I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

[Noc2]

Thanks for the application. Here is a link to your previous application: https://github.com/w3f/Grants-Program/blob/master/applications/polkadot-contract-wizard.md The first thing that I noticed is that your costs (FTE, day rate) increased significantly compared to the previous grant. Could you comment on this? Furthermore, did you consider applying for treasury funding (see https://github.com/w3f/Grants-Program#treasury). Once you have a POC, the treasury is a great option to get follow-up funding for the maintenance of these common good tools. Finally, could you clean up the milestone deliverable tables (last rows)? We usually don't support "final testing" or the launch of a product via our grants program. At least "final testing" is not something that we can evaluate and the documentation should always be up to date (regarding finalize documentation) when it's delivered.

[DiegoTorresborda]

Thanks for the application. Here is a link to your previous application: https://github.com/w3f/Grants-Program/blob/master/applications/polkadot-contract-wizard.md The first thing that I noticed is that your costs (FTE, day rate) increased significantly compared to the previous grant. Could you comment on this? Furthermore, did you consider applying for treasury funding (see https://github.com/w3f/Grants-Program#treasury). Once you have a POC, the treasury is a great option to get follow-up funding for the maintenance of these common good tools. Finally, could you clean up the milestone deliverable tables (last rows)? We usually don't support "final testing" or the launch of a product via our grants program. At least "final testing" is not something that we can evaluate and the documentation should always be up to date (regarding finalize documentation) when it's delivered.

Hi!
Thanks for the questions!
Regarding the FTE cost increase, in our initial grant application, we included the direct cost of a Mid-level Developer as a way of showing our support & interest in contributing to this ecosystem. In this case, we used a closer market price.
As for the source of funding, we believe that the source you mentioned would be suitable after implementing this upgrade, which promises to deliver a robust and impactful development tool.
Regarding the final test, we have decided to remove it from the plan.

[Noc2]

Okay. Let me know once you updated the application so I can share it with the rest of the team. But the price increase might be a controversial topic in the committee.

[DiegoTorresborda]

Okay. Let me know once you updated the application so I can share it with the rest of the team. But the price increase might be a controversial topic in the committee.

Certainly!
I have already updated the application, and I appreciate your willingness to share it with the rest of the team. I understand that the price increase may be a sensitive topic for the committee, so please let me know if we have to provide more information to address any potential concerns.
Finally, I want to stress our willingness to continue developing this project, we are open to discussing FTE cost.

[Noc2]

Thanks for the update. As promised, I will share the application with the rest of the team. But I personally won't approve because of the high price at this stage. I also recommend removing the empty rows of the milestone tables.

[DiegoTorresborda]

@Noc2, after careful consideration and taking into account our commitment to delivering a high-quality software solution, we have decided to make some adjustments to the proposal.
We understand the importance of being consistent with our previous proposal, so we decided to adjust FTE Cost.
We aim to create a more focused and manageable plan that aligns with our expertise and objectives. We believe this adjustment will allow us to maximize our efforts and deliver a software solution of exceptional quality within the available resources. We genuinely appreciate your support and understanding in this matter. We are fully committed to the success of this project and are confident that by concentrating our efforts on the core aspects, we will be able to achieve the desired outcomes.

[semuelle]

Thanks for the updates, @DiegoTorresborda. I have reviewed the application again. Could you share any insights into the use of contractwizard.xyz? How many users do you have? How many contracts were created through your tool?

In any case, I noticed that step 2, 3 and 5 are already implemented in the contracts UI. I'm afraid these deliverables (and the remaining deliverables: renaming, shareable links and video tutorials) aren't novel and useful enough to warrant a grant over 87,000 USD.

[DiegoTorresborda]

Thanks for the updates, @DiegoTorresborda. I have reviewed the application again. Could you share any insights into the use of contractwizard.xyz? How many users do you have? How many contracts were created through your tool?

In any case, I noticed that step 2, 3 and 5 are already implemented in the contracts UI. I'm afraid these deliverables (and the remaining deliverables: renaming, shareable links and video tutorials) aren't novel and useful enough to warrant a grant over 87,000 USD.

Thank you for your thoughtful insights and your time in reviewing the application again. I understand your concerns about the novelty and usefulness of the proposed deliverables, and I'm grateful for the opportunity to provide further clarification.
To begin with, we don't currently have detailed user insights or metrics on the usage of contractwizard.xyz since we haven't yet integrated Google Analytics or similar tracking systems into the platform. We've chosen to focus on development and refinement, prioritizing creating a robust and user-friendly tool before beginning promotion. Therefore, the only data we can presently access is through our database and the information users have provided during contract creation. We believe that once the platform is ready for the community, we will be able to collect meaningful and insightful data which will aid in further enhancements.
Your point about Contracts UI is well taken, and we indeed acknowledge its impressive functionalities. We strongly encourage our users to utilize Contracts UI, but we also believe that incorporating these capabilities within Contract Wizard is crucial for maintaining an optimal user experience. The transition between different tools can be a hurdle for users, and we're striving to create a cohesive, single-stop platform that can meet all their needs.
Furthermore, we are firmly of the belief that redundancy in open-source tools is a strength rather than a weakness. It allows for user choice, fostering a vibrant, diverse, and resilient ecosystem. Offering different tools with overlapping features promotes healthy competition, which often leads to better tools in the long run as developers strive to improve upon what's available.
We trust that our explanation provides a clearer perspective on our intentions for the grant funds. We understand the importance of prudent allocation to ensure that the resources are used to deliver real value to the community.

[keeganquigley]

Thanks for the application @DiegoTorresborda, and for answering the questions. A few additional questions/comments:

• I'd suggest removing the "renaming" of the product out of milestone 1, as any rebranding would fall under marketing which is not something that is covered by the grants program.
• For deliverables 2 & 3 in M1, we usually ask for mockups to be provided upfront as part of the application. What kind of mockups are you aiming to produce here?
• Educational content is not something that we typically fund, so you could also remove the series of video tutorials from M2, and reduce the scope/price accordingly.
• Finally, how do you intend to ensure the long term sustainability of the project? Will you go for alternative sources of funding after this?

[DiegoTorresborda]

Thanks for the application @DiegoTorresborda, and for answering the questions. A few additional questions/comments:

• I'd suggest removing the "renaming" of the product out of milestone 1, as any rebranding would fall under marketing which is not something that is covered by the grants program.
• For deliverables 2 & 3 in M1, we usually ask for mockups to be provided upfront as part of the application. What kind of mockups are you aiming to produce here?
• Educational content is not something that we typically fund, so you could also remove the series of video tutorials from M2, and reduce the scope/price accordingly.
• Finally, how do you intend to ensure the long-term sustainability of the project? Will you go for alternative sources of funding after this?

Hi @keeganquigley! Thank you for your feedback and suggestions. We appreciate your insights and have made some adjustments based on your points.

Regarding the rebranding aspect, we understand that marketing-related activities are not covered by the grants program. However, we firmly believe that rebranding our product is essential for its long-term success. Therefore, we have decided to undertake the rebranding process independently and cover the associated costs ourselves.

For deliverables 2 and 3 in Milestone 1, we apologize for not including mockups upfront in the application. Our UI/UX team is currently conducting a comprehensive usability research, which goes beyond the creation of basic mockups, and we are confident that research will lead to a great UX as we delivered on the grant we alredy delivered. We believe that this research will greatly enhance the user experience and justify the pricing for these deliverables.

We acknowledge your point about educational content not typically falling within the scope of funding. Consequently, we have removed the series of video tutorials from Milestone 2. However, we still believe that creating such tutorials is crucial for promoting adoption and facilitating users' understanding of our tool. Therefore, we have decided to bear the costs associated with producing these tutorials ourselves.

Regarding the long-term sustainability of our project, we are committed to exploring alternative sources of funding beyond the initial grants. One avenue we are considering is participating in programs like Astar's Dapp Staking, which could help us secure the necessary resources to keep the tool operational. By diversifying our funding streams, we aim to ensure the sustained development and availability of our product.

Once again, we appreciate your valuable input and have taken your suggestions into account. We remain dedicated to delivering a high-quality solution and are open to further discussion on any other aspects of our proposal.

[semuelle]

Thanks for the updates, @DiegoTorresborda. However, M1 currently consists mainly of mockups, a detail that we expect to be in the application already, for over 25,000 USD. I'd suggest moving D1.3 to M2 for 50k and removing M1 altogether.

FYI, https://www.contractwizard.xyz/ currently returns 502.

[semuelle]

pinging @DiegoTorresborda

[Noc2]

I'm closing this because of inactivity. Let me know if I should reopen it.

[DiegoTorresborda]

I'm closing this because of inactivity. Let me know if I should reopen it.

Please, reopen! I was on holidays!

[DiegoTorresborda]

Thanks for the updates, @DiegoTorresborda. However, M1 currently consists mainly of mockups, a detail that we expect to be in the application already, for over 25,000 USD. I'd suggest moving D1.3 to M2 for 50k and removing M1 altogether.

FYI, https://www.contractwizard.xyz/ currently returns 502.

The proposal is updated according to your feedback. Everything is allocated into a single milestone and the price is updated to 52.5k.

[Noc2]

Thanks for the updates. Could you clean up the deliverable table? For example, remove the last row and move the number to the first column.

[CLAassistant]

All committers have signed the CLA.

[Noc2]

Thanks for fixing it. Could you sign the latest version of the terms and conditions again? After this, I'm happy to go ahead and share it again with the rest of the team.

[DiegoTorresborda]

Thanks for fixing it. Could you sign the latest version of the terms and conditions again? After this, I'm happy to go ahead and share it again with the rest of the team.

Signed!

[keeganquigley]

Thanks for the changes @DiegoTorresborda looking forward to the next phase.

[github-actions]

Congratulations and welcome to the Web3 Foundation Grants Program! Please refer to our Milestone Delivery repository for instructions on how to submit milestones and invoices, our FAQ for frequently asked questions and the support section of our README for more ways to find answers to your questions.

Before you start, take a moment to read through our announcement guidelines for all communications related to the grant or make them known to the right person in your organisation. In particular, please don't announce the grant publicly before at least the first milestone of your project has been approved. At that point or shortly before, you can get in touch with us at [email protected] and we'll be happy to collaborate on an announcement about the work you’re doing.

Lastly, please remember to let us know in case you run into any delays or deviate from the deliverables in your application. You can either leave a comment here or directly request to amend your application via PR. We wish you luck with your project! 🚀

[keeganquigley]

Hi @DiegoTorresborda how is milestone 1 coming along?

[DiegoTorresborda]

Hi @DiegoTorresborda how is milestone 1 coming along?

Hey!! We are about to finish the fine-tuning development & testing. Most likely next week we will deliver the milestone. 💪