Objectives

• Maximise value from funding - The team are looking to not use the funding to pay themselves for the work they've completed. All contributors input to the project is recorded for the future and can be compensated at a later date with a salary if the project is successful. The pool of funding would instead be allocated to other tasks to speed up the development and improvement of the site.
• Give value before receiving - An initial focus will be to maximise value provided to the community regardless of the funding received. Execution has started on the project and will continue before voting.
• Fair compensation - We want to strike a balance between not asking for much but also not under compensating the amount of effort that will go into this project. As part of the fair compensation objective a future aim is to support people working on the project full time if the project is valued enough amongst the community.

Costing break down notes

Hourly rate x Estimated time

To keep the budgeting simple we're using an hourly rate multiplied by the estimated time in weeks to complete a given proposal. Each proposal has a development roadmap to highlight some of the main tasks and a time allocation break down is given below.

Rough time allocation breakdown

Naturally it is difficult for the break down to be exact. However the intention of the breakdown is to highlight some of the areas where resources will be spent to execute the proposal. Over time with more recorded input this breakdown can become more accurate and based off of data for future proposals.

Initial deployment dates

The proposals have initial deployment dates added. These dates do not mean the budget has been depleted at this stage. Further research & analysis, development, maintenance and collaboration & marketing can happen after any initial deployment.

Time allocation breakdown

• Research & analysis (10%)
• Product and design (15%)
• Development (45%)