- PayPal Website Payments Pro
- Braintree Gateway + Account
- Authorize.net + Merchant Account (add Auth.net's CIM, Braintree's vault, or Recurly if you need vendor flexibility)
|10 or more||$100.00|
|GB||Price Per GB||% of Previous|
|GB||Price Per GB||% of Previous|
|Clients||Price Per Client||% of Previous|
Well, shiver me timbers, but that looks just like the other graphs in the series: same severe downslope with humps in the dark line, same gentle curve with spikes in the lighter line, but no spikes until you hit the 90's.
Now, of course, I'd recommend that 37signals bumps up storage on their Basic plan, with the attendant bumps down the line, but hey, that's just me and my Rule of 80%.
In my last post about startup cash management, smart people like Chris Dixon, Manu Kumar, George Grellas, and the Hacker News cabal all disagreed with my advice to put off incorporation until you absolutely have to.
While there are often investments that should be made upfront, oftentimes new founders and new startups will waste money and time on things that they shouldn't. I sure know I did during my first go-round. Don't make my mistakes. Here are three things you should put off as long as possible:
One of the things that I didn't think about before I started my first startup were all the parts of the infrastructure that weren't product. They've also consistently been the things that other entrepreneurs forget about when they come to me with their "ohmygodIhavethisidea" ideas. They're also vitally important because they allow the founding team to actually execute the pivots you'll need to execute quickly, intelligently, and without sacrificing development of the actual product that you're trying to pivot.
The first part of this infrastructure is the admin panel. This admin panel is what will allow you to do troubleshoot for customer support, engage in administrative actions, and audit your payments in and out of your system without having to mess around with your production database. I cannot impress upon the first-time web entrepreneur just how important it is to have a robust and well-functioning administration system. When you're building your administration system, it is important to make sure that you can disable and delete users, view and change payment regimes, and reset user passwords (because they will invariably not be able to find your reset password form and they *will* e-mail you). If your product takes off and you find yourself bringing on board a business person, they're going to be tasked with support, and you do not want whoever is doing support interrupting engineering to complete basic Level 1 and 2 customer support. If your product really takes off, you may find yourself bringing on board a dedicated support person. If you wait until traction to build out your administration panel, you're going to be ceding ground to the competitors that spring up when they see your traction. Django's admin panel is so well developed that you may not have to build your own, and is a reason to strongly consider the framework if you're familiar with (or interested in) Python. Even as your product pivots, the administrative support tasks generally don't.
Make sure you've built a functional admin panel before you launch.
Make sure you've built (or implemented) a content management system before you launch.
The third part of the infrastructure you need to build is a good metrics dashboard and logger. The standard piece of advice is "pick a few metrics, but log everything". The idea of logging everything when you've decided to focus on just a few Key Performance Indicators (KPIs) can often cause heartburn. But it's relatively simple; build a separate table (or database) that automatically logs all the various things that users do. Don't worry about duplicating writes that you're doing elsewhere in your database. Having a separate table (or better, database) will save ou on reads and JOINs and whatever else when you need to dig in. The one thing the logger needs to do is be *auditable* - that is, you need to be able to say that user_id=8273 did x on page one, then y on page two, then z on page three. These loggers are so important that there are venture-backed startups that exist solely to help other startups collect these logs and make sense of the data they're collecting. The KPIs are, of course, actionable metrics that exist in the aggregate, but the ability to see what any individual user has done will help you troubleshoot, audit, and make hypotheses for new features and functions. Also, one quick note: Google Analytics aren't auditable at the user level nor actionable in helping you make forward-looking hypotheses. Everything in Google Analytics is backwards looking. The product is free as in beer and all-but-free from an engineering cost perspective, which is great. GA does give you the ability to find exception cases and the basic funnel visualizations can be useful for getting conversion metrics up and running quickly, but don't kid yourself - Google Analytics is mostly data porn.
Make sure you build a real metrics dashboard and implement a real logger before you launch.
Ask a QuestionDo Background ResearchConstruct a HypothesisTest Your Hypothesis by Doing an ExperimentAnalyze Your Data and Draw a ConclusionCommunicate Your Results