[argonaut]

In what "domain" is your product idea? (without revealing too much, obviously). For example: a collaboration tool. Or an e-commerce subscription site. Etc...

I would go for Python + Django. Avoid Google App Engine. There are big gotchas with using Django and GAE. You essentially have to throw out the Django ORM because Google places restrictions on what SQL queries you can use (for scalability reasons, none of which are your concern for an MVP or even a moderately sized startup). You can avoid this using Google Cloud SQL, but then you have to use MySQL. PostgreSQL is recommended by most of the Django community. You are better off using something like Heroku (which has great documentation). You can either use Twitter Bootstrap (maybe tweak the defaults with something like Jetstrap), or use a template off themeforest or woothemes. If you use a theme, you'll have to tweak the HTML to make them work with Django's templating.

The problem with Wordpress is that unless you're doing a plain vanilla ecommerce site or some other limited choices, there are many kinds of MVPs you would not be able to build with it. Not to mention that you would be rewriting everything eventually if you use Wordpress.

Using meteor and node.js cover different product use cases (real-time apps or apps with a lot of connections). So it depends on your product. Keep in mind that meteor is not mature yet.

[bdcravens]

If you're willing to spend some money on plugins, you can pretty far with WP (WP-Member, Gravity Forms, etc)

Zapier makes it easy to wire together a bunch of services if you want to build up functionality fast.

Myself, I'm building my MVP's these days with Bootstrap + Rails + Heroku, and when I need to step up the design a bit, I'm leaning on WrapBoostrap and Designmodo. That said, I think it's extremely possible to build an MVP (emphasis on Minimum, as it should be) and write very little code.

[v3rt]

The app is basically a service for ordering/dispatching couriers/deliverypeople, so it's definitely real-time(ish) - the core functionality is for users to be able to order a delivery (with real-time cost estimate) and for human dispatchers to be able to process the deliveries through a private portal. At the bare minimum I could honestly just do it through a basic form that sends emails to a dispatcher account, so I might do that for an MVP (didn't know that term before), although that would be a very, very temporary solution. You guys have suggested a ton of useful options, so I'm going to have to spend some time just reading up and seeing what would be a good approach. Thank you for the help, everyone - it's been really useful information, and I'd appreciate it if anyone has more to add as well.

[argonaut]

That's not really realtime. Realtime is a chat app - i.e even a delay of 10 seconds is too much. Realtime is a multiplayer game with 1000 users all at once. I'm afraid I was a little vague when I said realtime. Node.js is for concurrent realtime. Meaning it's good for a product where you have thousands of users that need to be connected all at the same time all communicating with one another.

Your app seems like a fairly standard SaaS app. The cost estimate is only "real-time" in the sense that there is some data that is crunched on the server before it's served up to the user. Users just deal with a form and they punch in their data, and then that data is shown to couriers. That's pretty standard CRUD and you don't need anything fancy. Node.js is really cool, but you're going to be a lot more productive and you're going to have a much easier time by sticking to a standard, mature web framework like Django (or Rails).

Are you fluent in Javascript, PHP, or Ruby? If not, that's even more of a reason to stick with Python and Django, because you can literally start learning Django and have your MVP up by Monday.

[v3rt]

I am (or was, a couple of years ago) fluent in Javascript/AJAX and PHP so I could definitely hack something together with that, but Django sounds like a cool technology to learn as well.