Consider a psuedo-open source project on Github where anyone could make a pull request but only the owners can actually confirm it.
Take that idea and apply it to the website. Instead of being able to see source code progress reports would be made.
So you can then see a sort of developer timestamp.
[Minimum Viable Product] -> [Did This] -> [Did That]
At this point you can actually record these logs and maybe prefer they come with a screenshot. Then you can essentially list how 'alive' the project is based on how complete it was filled out.
Maybe even have a development history page that is public.
This benefits the backer by allowing them to know that their money is being used or that a project is worth backing.
This also benefits the developer as it provides a motivation for some amount of progress in a given time frame, it also opens up opportunities for recruitment by allowing potential team members to be able to catch up with the 'general idea' of what has been done with the product and some guarantee that the project is actually worth their time due to it's aliveness.
Take that idea and apply it to the website. Instead of being able to see source code progress reports would be made.
So you can then see a sort of developer timestamp.
[Minimum Viable Product] -> [Did This] -> [Did That]
At this point you can actually record these logs and maybe prefer they come with a screenshot. Then you can essentially list how 'alive' the project is based on how complete it was filled out.
Maybe even have a development history page that is public.
This benefits the backer by allowing them to know that their money is being used or that a project is worth backing.
This also benefits the developer as it provides a motivation for some amount of progress in a given time frame, it also opens up opportunities for recruitment by allowing potential team members to be able to catch up with the 'general idea' of what has been done with the product and some guarantee that the project is actually worth their time due to it's aliveness.