I think the concept is "MC" (of MVC) as a service, you should make this more clear. This is difficult, because the people who need this the most are also the people how know the least about structural design patterns.
It is unclear to me, how the products are inserted and how payment processing works. From a technical innovators perspective this is not the main feature, to the end-user it is. You should show the developer how his customers can insert products.
I am not sure if your target audience (someone who knows Python and Jinja2) is a good fit. Seems like someone who nows HTML+CSS and a bit of PHP would need the service more. I would therefore use terms these people would understand and offer technologies they understand (drop the command-line fu, offer FTP-Upload or even Web-based Upload etc).
The pricing is unclear. I imagine Boutique + Pricing + Storage add up to the Basic Price. You should drop the prices in the second table and use a syntax like "first x GB included (additional cost x GB cost x $)".
It is unclear to me, how the products are inserted and how payment processing works. From a technical innovators perspective this is not the main feature, to the end-user it is. You should show the developer how his customers can insert products.
I am not sure if your target audience (someone who knows Python and Jinja2) is a good fit. Seems like someone who nows HTML+CSS and a bit of PHP would need the service more. I would therefore use terms these people would understand and offer technologies they understand (drop the command-line fu, offer FTP-Upload or even Web-based Upload etc).
The pricing is unclear. I imagine Boutique + Pricing + Storage add up to the Basic Price. You should drop the prices in the second table and use a syntax like "first x GB included (additional cost x GB cost x $)".