What growth hack is best for a SAAS startup looking to attract eBay sellers?

Obviously, they do the fundamentals well. Good brand. Good experience. Good word of mouth. Good PR. Etc. Etc. But after my interview with Ryan Graves, the head of Global Operations at Uber (https://www.growthhacker.tv/ryan-graves), it became clear that they are operationally advanced and this is a huge part of their success. I'll explain. Uber isn't just a single startup, it's essentially dozens of startups rolled into one because every time they enter a new city they have to establish themselves from essentially nothing (except whatever brand equity has reached the city ahead of them). This means finding/training drivers, marketing to consumers, and building out local staff to manage operations for that city. This is where Ryan Graves comes in. He has a protocol of everything that must be done, and in what order, and by who, to ensure the best chance of success in a new city. So how has Uber grown so fast? Essentially, they figured out how to grow in one locale and were relentless about refining their launch process to recreate that initial success over and over in new cities. No plan works for every city, and they've had to adapt in many situations, but it is still a driving factor for their success.

It depends on a number of factors but I'd boil it down to two key things to start: 1) What is your real cost to provide a free plan or trial? 2) Who exactly is your customer and what are they used to paying and who and how do they pay today? When you say "online workforce marketplace" it sounds as though you're placing virtual workers. If that's the case, or if you're paying for the supply side of the marketplace, the question is how much can you subsidize demand? Depending on where you're at in the process, I'd also question how much you can learn about the viability of your marketplace by offering a free version, assuming again, that free is actually a real cost to you. I was part of a SaaS project that started charging people for early access based mostly on just a good landing page (we clearly stated they were pre-paying) and were amazed at the response. I've also run a SaaS product that offered free trials and realized that the support costs and hand-holding and selling required to convert from free trial to paid wasn't worth it, this despite the product's significant average ARR. You might be better off providing a "more information" sign-up form (to capture more leads) and let them ask for a free trial while only showing your paid options. I've been amazed at the lead capture potential from a simple "have questions? Click here and we'll contact you" This is all the generalized advice I can offer based on the limited information I have, but happy to dive-in further if you'd like on a call.

Most Software as a service vendors generally don't book annual deals except in highly specialized cases. Most customers prefer to be able to cancel/change anytime they choose. Also, deals done "offline" end up actually often being more trouble than they are worth to administrate especially for a $2988 ticket. Generally, companies don't view prepaying for SaaS products a year in advance as a "convenience" (to them) so if the debate is internal (not customer driven), I'd set this debate aside until it's requested by the customer. Most customers will request a discount to pre-pay annual service. Happy to talk this through with you in a call, to work through the specifics of your situation in more detail.

Whenever you assign them a task, break down the task into small chunks. Make the chunks as small as you can (within reason, and to the extent that your knowledge allows), and tell your devs that if any chunks seem large, that they should further break those chunks down into bite size pieces. For instance, for the overall task of making a new webpage, _you_ might break it down as follows: 1) Set up a database 2) Make a form that takes user email, name, and phone number and adds them to database 3) Have our site send an email to everyone above the age of 50 each week When your devs take a look at it, _they_ might further break down the third step into: A) Set up an email service B) Connect it to the client database C) Figure out how to query the database for certain users D) Have it send emails to users over 50 You can keep using Asana, or you could use something like Trello which might make more sense for a small company, and might be easier to understand and track by yourself. In Trello you'd set up 4 columns titled, "To Do", "Doing", "Ready for Review", "Approved" (or combine the last two into "Done") You might want to tell them to only have tasks in the "Doing" column if they/re actually sitting at their desk working on it. For instance: not to leave a task in "Doing" overnight after work. That way you can actually see what they're working on and how long it takes, but that might be overly micro-manager-y At the end of each day / week when you review the tasks completed, look for ones that took a longer time than average (since, on average, all the tasks should be broken down into sub-tasks of approximately the same difficulty). Ask them about those tasks and why they took longer to do. It may be because they neglected to further break it down into chunks as you had asked (in which case you ask them to do that next time), or it may be that some unexpected snag came up, or it may be a hard task that can't be further broken down. In any case, listen to their explanation and you should be able to tell if it sounds reasonable, and if it sounds fishy, google the problem they say they encountered. You'll be able to get a better feel of their work ethic and honesty by how they answer the question, without worrying as much about what their actual words are. Make sure that when you ask for more details about why a task took longer, you don't do it in a probing way. Make sure they understand that you're doing it for your own learning and to help predict and properly plan future timelines.

Here is a link to a basic model - http://monetizepros.com/tools/template-library/subscription-revenue-model-spreadsheet/ Depending on the purpose of the model you could get much much more elaborate or simpler. This base model will help you to understand size of the prize. But if you want to develop an end to end profitability model (Revenue, Gross Margin, Selling & General Administrative Costs, Taxes) I would suggest working with financial analyst. You biggest drivers (inputs) on a SaaS model will be CAC (Customer Acquisition Cost, Average Selling Price / Monthly Plan Cost, Customer Churn(How many people cancel their plans month to month), & Cost to serve If you can nail down them with solid backup data on your assumption that will make thing a lot simpler. Let me know if you need any help. I spent 7 years at a Fortune 100 company as a Sr. Financial Analyst.