nPost Blog

How a startup should leverage a virtual assistant



Tweet this!

rob_wallingRob Walling generously allowed me to reprint this excerpt from his new book, “Start Small, Stay Small: A Developer’s Guide to Launching a Startup” available in paperback and Kindle from Amazon and in PDF and ePub from StartupBook.net.

Rob is one of the most successful “micropreneurs” — creators of small, cash-generating startups frequently sold for cash. He blogs to 10,000 web entrepreneurs at Software by Rob and co-hosts the podcast Startups for the Rest of Us.

Introduction

I receive essentially the same reaction when I mention that I use virtual assistants, and that I recommend them for anyone starting a startup. It’s a mix of shock and excitement.

They’re shocked I’ve been able to pull it off, and excited at the thought that they might be able to do the same. The conversation almost always turns to questions about where to find virtual assistants and how a startup can use one.

This article intends to answer those questions.

What is a Virtual Assistant?

A virtual assistant (VA) is a remote worker hired to complete tasks you should not be doing as the founder of a startup.

These can be research tasks, like finding every tech blogger who blogs about cats, repetitive tasks like creating 100 affiliate links for products in a Word document, or ongoing tasks like monitoring a handful of job boards and posting new jobs to your website.

The term VA has grown to describe any remote contract worker, including people who help with audio editing, video editing, bookkeeping, webmaster tasks, link building, and so on. A VA can be domestic or international, as long as they have a computer and an email account.

Why Should My Startup Use a Virtual Assistant?

startups-for-rest-of-usOutsourcing to a virtual assistant will dramatically reduce the time you spend on administrative tasks, and increase the time you can commit to growing your business.

The value proposition of a VA deals with how you monetize your time. If you monetize it at $50/hour and you can pay a VA $6/hour to handle administrative tasks, this frees up time for you to create real value in your business by developing new features or expanding marketing efforts.

Performing tasks you could pay someone else $6 to accomplish is a foolish use of an entrepreneur’s time.

My VAs have saved me literally hundreds of hours over the past few years.

[Editor's Note: This is especially true for you starting up while still employed where your time is scarce and your existing income should be used to buy more of it.]

Case Study: How I Launched One Month Earlier Using Outsourcing

More than two years ago, my business partner and I discussed launching a hosted version of our ASP.NET invoicing software, DotNetInvoice.

We developed the plan and task list, and estimated the effort at around 160 hours including development time needed to make DotNetInvoice a multi-tenant application. But given the heavy competition in the hosted invoicing software market and the level of effort of the task, it was continually placed on the back burner.

The Shearing
After our initial estimate, every six months for the past two years we’ve revisited the idea of a hosted version until one day in November of last year.

On this day we stopped looking at the hosted version as a new product line, and started looking at it as a market test; to see if we could build enough of a customer base to warrant a major investment in the hosted invoicing market space. With that in mind, things started flying off our “must-have” list.

One large piece we removed was automating sign-up and provisioning of a new hosted installation.

In an ideal world, when a customer wants a new hosted account they would fill out a web form with all of their information and their new hosted version would be ready in 30 seconds. But that amount of automation — given the fact that we have to create a new sub-domain, a new database, and copy physical files — would take a substantial amount of time to develop and QA.

So we tossed it.

Another feature we left on the cutting room floor was the need for a custom purchase page; a page where someone enters their details to make the purchase. In a desperate attempt to bring this entire project down to less than two days work we simply utilized PayPal subscriptions.

Not the optimal approach, but it works quite well for testing out an idea before we invest another day into this project.

Iteration vs. Automation
As a developer, the features we dropped seem like a necessity from day 1. Not automating this process creates the ongoing repetitive work that computers are designed to handle. Manual work — this is what computers are supposed to save us from!

But by getting over the need to automate everything to infinite scale and putting a VA in charge of manually creating new hosted accounts, the time investment to get this feature launched dropped from 160 hours of work to about 10 hours.

I can hear the cries of developers around the world as I write this: “You can’t launch a half-baked solution! You’ll never go back and fix it!”

Most of us have worked in corporate environments where you’re never allowed to go back and refactor code. This burns into our psyche that you don’t want to launch a semi-functioning solution because you’ll never have time to go back and fix it.

But the benefits of being my own boss and being a tiny software company are that I can come back to this anytime. In fact, the day the amount of money paid to my VA for handling this task exceeds a certain amount, I will be very motivated to automate it.

Ideally, by the time I code it up, we’ll have many customers using the platform which means I’ll be working on a product I know is viable, and that’s paying for the time I’m spending to automate it.

Agile Development, meet Agile Business.

Through a bit of outsourcing to a VA, you can get to market with less up-front expense and in dramatically less time than if you try to automate everything.

Had we chosen to automate everything, the worst potential outcome would have been investing 160 hours of time (a huge amount of time for a startup), and then scrapping the whole thing. When you’re working on a small team you can’t afford to throw away that much time.

The Lesson
The lesson is that before you launch your product, think about the processes you can avoid automating.
How about reminder emails? How about monthly billing? Could a human being run a report once a month and send emails or charge credit cards?

This is not the paradigm we typically think of as developers because we’re used to enterprise IT shops where everything has to scale infinitely.

As a startup, you’ll have plenty of time before you need to scale, and you may never need to scale if the idea doesn’t work. Every hour spent writing code is wasted time if that code could be replaced by a human being doing the same task until your product proves itself.

The Two Points When a VA is Most Helpful

There are two key points during the life of your startup where your life will be much easier if you use a virtual assistant (VA):

  1. While proving out your product/market
  2. After your product launch

Let’s look at each one.

Point #1: Developing a Proof of Concept

In the DotNetInvoice case study above, I used a VA to short-circuit my product development time so we could begin to prove out the product’s concept with much less effort than if we had built everything in code.

As I’ve automated pieces of my businesses, I’ve noticed an interesting trend: nearly anything I try to automate is easier to outsource first, then automate down the line once the volume warrants it.

The reason for this is that at any given time you’re likely to have, say 30 tasks on your plate, and you should be trying to remove as many as possible from your task list; both one-time and ongoing tasks.

Out of 30 tasks you might be able to outsource 6 or 8 of them tomorrow if you spend 2-3 hours today writing up the processes. Compare that with automation, which can take a week or more to get each task off your plate since it takes a lot of code to automate a task.

As a startup, one of your advantages is that you move very quickly. You can roll out new features much quicker your competition. And being able to manually process some parts of a task can often reduce your development time by 50-80% which allows you to get the feature out the door and in front of customers.

If customers decide to use it, then you can automate it. If not, you can throw what little time you spent on it away. You develop the minimum required functionality to make the bare bones feature work; nothing more. You scaffold the rest with a human being; your VA.

Then, as needed, you improve the back-end automation iteratively.

Your startup time plummets to near zero even though your maintenance costs are a bit higher since you’re paying someone an hourly rate to handle the task.

But that’s ok, because every task you outsource to someone making $6/hour is a task that frees you up to develop new features and focus on marketing — things that make you a lot more than $6/hour.

In addition, outsourcing provides you with a written process for the task that serves as a blueprint if the time comes later to automate it.

Point #2: After Your Product Launch

The next most important time to use a VA is once your product has launched and you need to begin supporting customers.

Customers make it necessary to put processes in place for marketing, sales, support, and back-end admin tasks. Any ongoing work that can be described in a written process can be outsourced to a VA and save incredible amounts of time for the founders.

If you do not outsource these tasks, they will get in the way of work that’s truly productive for your business.

While most entrepreneurs feel like they need to keep the reins on level 1 email support, level 1 sales questions, manning the live chat window on your website, directory submissions, minor HTML tweaks, keyword research, link building, following up on canceled subscriptions, and running month-end reports, getting these tasks into the hands of a competent VA frees up vast amounts of time that can be spent growing your business.

And the cost is negligible.

Don’t fall into the trap of needing to handle everything yourself. You are now an entrepreneur.

Case Studies

Here are two case studies to give you an idea of how you might use a VA in your own startup, whether serving a core business function or as administrative support.

Case Study #1: Market Research

In 2009, I launched the Micropreneur Academy, a private membership community for startup founders. For the launch event I wanted to contact several bloggers in the startup and microISV space.

I have a list of blogs that I read and quickly added them to my list to send a personal, targeted email to each. I receive enough pitches each month to know that sending a mass email to bloggers doesn’t work.

In the back of my mind, I knew there were other startups/microISV blogs out there that I don’t read, but I didn’t want to spend the time to track them down. More importantly, I didn’t want to spend the time trying to find their contact information. Enter my VA.

I tasked my VA with finding blogs that deal with startups/microISVs and rank in the top 100k in Technorati. The deliverable was a Google spreadsheet containing the blog URL, blogger’s name and blogger’s email.

The final spreadsheet contained 28 blogs. It was up to me to go through each one and become familiar with their content, determine its relevance to my message, and craft a targeted and personal email. Many blogs dropped off the list after a quick glance, but in the end the time saved by delegating this research task to a VA was well-worth my $12.

Case Study #2: JustBeachTowels.com

JustBeachTowels.com was an e-commerce site I purchased with hopes of a high level of automation.

The problem is that beach towel dropshippers are not the most high tech businesses, and none of them offered any kind of API for order placement. All orders had to be manually placed through their web-based shopping carts.

In the early days, I planned to build a screen scraper to pull orders from my database and automatically place them with the four dropshippers I used, but realized the level of effort and QA that would be required for this were substantial and the resulting interface would be brittle due to the screen scraping.

Instead, I assigned a VA to place all of the incoming orders. I never revisited automation due to the lack of ROI on the time it would have taken to build the screen scraping interface.

Running the site using a VA instead of automation saved me time in the long run, as I would never have made back my initial time investment on the 50+ hours required to fully automate the order placement process.

Easing Into a VA

Outsourcing is a learned skill, just like writing code. If you rush into it too quickly, you’ll wind up disappointed with the results. This is most often due to the fact that you don’t yet know how to work with a VA.

One of the plusses of having a VA is that you can ease into them over the course of several months. Since utilizing a VA is a learned skill, you are best to start slowly by finding someone who will work on individual tasks, then move to part-time if needed, and finally to full-time.

These hiring arrangements are described below:

  • Task-based — ($3-10/hour overseas, $12-50/hour in the U.S.) You assign your VA an individual task and give them a deadline and maximum time to spend on the task. Since your VA works for other clients, they are in charge of prioritizing all of the tasks they receive. Task-based VA’s are a great starting point to learn the ropes of delegating.
  • Part-time — ($2-7/hour overseas, $10-$40/hour in the U.S.) Part-time VA’s are dedicated to you for a certain portion of their week (typically 10, 20 or 30 hours). Part-time VA’s are cheaper by the hour than task-based VAs, but you need enough work and experience to keep them busy during the time you are paying for.
  • Full-time – ($1-$5/hour overseas, $8-35/hour in the U.S.) As you might imagine, a full-time VA is a lot of responsibility. While offering the lowest hourly rates, you need 160+ hours of work to keep them busy. If your VA is self-managing, you can lay out tasks a month at a time. If they need supervision, it’s probably not worth bringing them on full-time.

The Steps

The key to learning how to work with a VA is experience. The question is: how can you get started easily and with little risk? The steps are:

  1. Find a VA
  2. Start with a single task and gradually increase the amount of work as you gain comfort
  3. If things don’t work out, find a new VA

When I began outsourcing three years ago I found that when I received the finished product I was elated that I hadn’t spent 3-4 hours doing it. This made me realize how many other tasks I was able to accomplish during that time frame.

Step1: Finding a VA

I’ve had the best results hiring VA’s in the Philippines. This is not to say that the U.S., India, Bangladesh or other countries do not have quality VA’s, but the Filipinos learn English in school, do not tend to be entrepreneurial (thus are less likely to steal ideas), and are culturally service-oriented.

You may find another country to be more compatible with your management style, but after working with 10+ VA’s, I now work almost exclusively with Filipinos. The main exceptions are my audio and video editors in the U.S. and Canada.

In my experience, you will be best off with one of a few choices when looking for a VA:

  1. Task-based VAs
    • Search ODesk under Admin Support -> Personal Assistant or Other.
    • Search Google for “virtual assistants.” Typically the best looking websites are the firms that have their act together.
    • Search Elance under Admin Support -> Admin Assistant.
  2. Part-time VAs
    • Search ODesk under Admin Support -> Personal Assistant or Other.
    • Search Google for “part-time virtual assistants”
  3. Full-time VAs
    • Search ODesk under Admin Support -> Personal Assistant or Other.
    • Search Google for “full-time virtual assistants”

I’ve had positive results and have personally hired a VA using every method listed above.

My current favorite is ODesk.com. I’ve had exceptional luck with them, and their project management tools are helpful in making sure your VA is working on your tasks. Their time clock takes screen shots of the VAs screen at random intervals so you can see the task they are performing.

A Note: Solo vs. Team

Many VA’s work in teams, whether under the umbrella of a single company, or in a loose affiliation.

Solo VA’s tend to be cheaper than team or larger firms.

For recurring work that’s critical to your business, it’s nice to work with a team. You will typically have a primary VA but when he’s on vacation his replacement will step in.

For ongoing work that’s not terribly time-sensitive, I’ve found solo VA’s work out well.

When getting started, my advice is to stick with a larger VA firm. You will pay a little more but you will have more reliability, higher security and will be able to easily find a replacement when you need one.

How to Evaluate a Potential VA

My first piece of advice is to avoid spending too much time worrying about screening your VA before you hire them. In the end, how well they work out depends entirely on how well they accomplish their tasks.

In other words, reliability and the ability to understand your instructions and ask good questions are the key factors. Without hiring someone you can’t get an idea about their reliability; only about their ability to understand and ask questions.

To do that, you need to evaluate their written English (or whatever language you will be working in). This includes hiring U.S.-based VAs; competent written English skills are not a given even for native speakers.

If you’re looking for general help, the only noticeable difference between the 10 VA’s you are screening is their hourly rate and their ability to speak and write English.

If you need specialized work performed, you may have an additional requirement that they also know how to edit audio, for example. In that case, ask for samples of past work and experience doing the exact task you will have them to do.

The best way I’ve found to evaluate English skills is to email back and forth a few times, asking 2-3 basic interview questions. This will be a good indication of how well they will be able to understand your instructions, and their responses are a good indicator of how well you will be able to understand their questions. The best approach is to email with 3-5 VA’s at once to speed up the process.

If you’re working with a VA firm, I recommend requesting someone with excellent written English, and performing the step above with that person. If they don’t live up to your standards, request a new VA and repeat the process.

In the past I’ve asked for writing samples but this has failed me. The problem with asking for writing samples is a VA can easily send something that’s been heavily edited, or a piece written by someone else. During an email exchange you can be certain that you’re catching a true glimpse of their English abilities.

Step 2: The First Task

Properly utilizing a VA is a learned skill. Very few developers will do it right the first time, which leads many who try it to give up after the first attempt. To keep you from falling into this trap, we’re going to look at the best way to delegate, describe and limit tasks in the section below.

After determining your VA has solid English skills, the next step is to send them your first task. You should be able to tell after one task if they are going to work out.

If you’ve never worked with a VA, you should assume they are not technically minded. They will have basic computing skills but are nowhere near techies, so you have to prepare instructions for them as if they were your mom or dad (or at least my mom or dad).

The following is unlikely to work:

Open a command prompt and type ‘ipconfig’

But this should:

In your start menu go to the Run menu, type ‘cmd’ and hit enter. Once the window opens type ipconfig and hit enter.

With that in mind, here is how I suggest you assign your first task:

  • Back everything up before you let them touch production files. It’s unlikely they will be malicious, but they might accidentally break something.
  • Provide detailed instructions in bulleted/numbered format.
  • Screenshots help enormously. Screencasts are even better. I record multiple screencasts each month for my VAs. Jing is perfect for this.
  • Timebox your requests. As an example, let’s say you have twenty blog URLs and you want your VA to find the contact information for each one (whether it’s an email address or a contact page). Provide the list of URLs to your VA and indicate they should work for 1 hour and then update you on their progress. In this manner you can both check if they’re doing it right, and see how long it’s taking them. If it’s taking longer than you think it should, ask how you can help.
  • Assume they are not as fast as you are. If 1 URL takes you 1 minute, assume it will take your VA 5 minutes at first and they will eventually get down to 3 minutes. They will never be as fast as you are. But at $4-6/hour it’s hard to complain.
  • If you have a timeline, spell it out (e.g. “I need these by tomorrow”). If not, let them know you can wait 2 days for the results. They work when we are sleeping so you’ll never get anything the same day.

Step 3: If Things Don’t Work Out, Find a New VA

Finding a VA is about trial and error. I’ve worked through more than 6 VA’s to find the folks I work with today. It’s a similar process when finding a designer, developer, or any outsourcing partner. You can only tell so much from a resume; the best way to evaluate is to try them out, and this means if they don’t work out you should make the decision quickly to find someone new.

It’s critical that you feel comfortable with the person you’re working with. It’s better to cut someone loose early in the relationship before you’ve trained them on the inner workings of your business.

If you’re working with a VA firm it’s easy: simply ask for a new VA and if you can, give a specific reason why the first one did not work out.

If you’re using an individual, head back to your stack of candidates from Elance, Google or ODesk. The odds are low that you will find someone great on your first try. But finding someone great will make a huge difference in the success of your outsourcing effort.

Did you make it this far? Awesome, let’s talk some more.

Let’s continue the discussion in the comments!



Tweet this!

A vote for me is a vote for dipshit businesses everywhere



Tweet this!

Let’s get the self-aggrandizing plea for attention out of the way:

Please vote for my SxSW panel entitled “A Bootstrapped Geek Sifts Through the Bullshit.”

It answers questions like “How do I get the courage to just start when I know so little about what it’s really like at a startup?” and “How do I balance the utility of learning from others with wanting to go my own, unique way?”

Plus it’s ironic; I’m giving advice about how to take advice. You know, like finding a black fly in your Chardonnay. (White flies are harder to see and therefore not ironic, you see.)

OK, now on to the good stuff…

Champion of the dipshits

Michael Arrington wrote an interesting piece today at TechCrunch about how VCs are pissed that great entrepreneurs are taking under $500k of angel money instead of $2m their money.

The real reason they’re pissed is that VCs are increasingly unnecessary to get companies started, both because of inexpensive technology and marketing channels and because there are enough angel investors that founders don’t have to sell the entire farm for ridiculous amounts of cash they don’t really need.

And then, for the few companies that really do need VC-sized investments to take them from product/market fit to explosive growth, by the time they start touring Sand Hill Road their valuations are sky-high; they’ve already got all the trappings of a successful company, the major risks having been removed during the angel round.

All this is explained in clear detail in Paul Graham’s his piece on the future of tech investing — a must-read for anyone interested in financing. He’s is biased, of course, because he leads the 200+ company Y-Combinator incubator, but his predictions have already come true for many founders I know personally.

Of course the VCs aren’t happy about this. This excerpt from the TechCrunch article made me livid:

The VCs, for their part, fight back more quietly. They point out that very few angel funded startups end up very big or interesting. “An entire generation of entrepreneurs are building dipshit companies and hoping that they sell to Google for $25 million,” lamented a venture capitalist to me recently. He believes that angel investors are pushing entrepreneurs to think small, and avoid the home run swings. And you don’t get a home run unless you swing hard, he says. When you play it safe you nearly always lose.

Rather than provide a cogent argument for why founders ought to take VC money anyway, the response is to call the company a “dipshit” and reveal the astounding arrogance that a few founders selling their company for $25m is somehow a failure.

To understand what’s really being said here, you have to replace the word “you” with the actual antecedents.  So: “When you play it safe you nearly always lose” should read: “When founders play it safe VCs nearly always lose.”

But founders often win.

That’s what gets me about this entire attitude — it’s about returns for their fund, not success for the founders. Which is how it should be, understand, because they have a fiduciary duty to their investors, not to the founders of the companies they invest in. It’s OK for them — it’s their job — but it’s not OK for you. “You” being “you, entrepreneur, reading this, the one who matters.”

At last year’s Capital Factory Demo Day, Mike Maples Jr. gave the keynote address. He gave the statistic that only 9% of the companies they invest in succeeded. And his venture firm is considered one of the more successful ones. (By the way, Maples is now doing super-angel deals. Interesting.)

The math is simple: Only one in ten companies need to hit, but it needs to hit big, like 100x the original investment. Of course no one wants the rest to fail, but every one will be pushed into explosive growth, which means strapping a rocket to the back of each one, even if that means the vast majority will just blow apart.

Great for them, bad for the founders.

The last thing they want is for founders to wake up and realize that this isn’t necessarily a good way to build a company. They don’t want you to realize that if you shoot for reasonable, profitable growth, it’s far more likely to work, far more likely to produce a company that not only pays the bills but is a valuable asset, one that you might sell someday for millions of dollars, like I did.

For them, a little, solid company for $25m to Google is dipshit material. For you and me, it’s a life-altering home run.

Until I hear a rational argument for why super-angels, angels, or friends-and-family rounds are worse for founders than a standard A-round from a VC, I’m just going to ignore these emotional, self-serving statements.

And I suggest you do too.

Focus on building a company you’re proud of, not how big and disruptive you can be. Focus on getting to profitability as the greatest measure of success. Focus on selling customers, not selling investors.

And vote for that SxSW panel so I can spread the Good Word to others.  :-)

Is my argument healthy or too far the other way? When is it right to take VC money right off the bat? Let’s continue the discussion in the comments.



Tweet this!

Yes, but who said they’d actually BUY the damn thing?



Tweet this!

This is Part 3 of the series: 5 lessons from 150 startup pitches.

your-mom-not-test-market

Of hundreds of startup pitches at Capital Factory, almost none had unearthed 10 people willing to say, “If you build this product, I’ll give you $X.”

Meditate on this: Hundreds of people ready to quit their day jobs, burn up savings, risk personal reputation, toil 70 hours per week, absorb as much stress as having a baby (believe me, I’ve done both)….  all without identifying even ten measly people actually willing to pay for what they’re peddling.

Short-sighted, no?

If you can’t find ten people who say they’ll buy it, your company is bullshit.

Aren’t you sick of every startup blogger on Earth badgering you about this? Steve Blank says “get outside the building,” Eric Ries says “seek validated learning,” Sean Ellis says “seek product/market fit,” Drew Houston says “the only way to learn on a $0 budget is to talk to people.”

I say “find ten people who say they’ll buy.” I say “get off your ass and produce hard evidence that customers are in your future light cone.”

But you’re still not listening. You repeat these mantras at Lean Startup Meetings but you’re not doing it.

You’re understandably scared of been proved wrong, especially now that you’re all worked up about the new business idea, and extra especially after you’ve already told friends and family you’re doing this and they’re expecting you to complete your quest.

But jeez people, you’re not even trying. And worse, you’re inventing lame excuses for why you’re not trying.

Full power to forward shields y’all, I’m coming for you.

“I’m scratching my own itch. Since I’m my own target customer, I already know what to build.”

Oh! I didn’t realize your typical customer is observant enough to recognize monetizable pain, creative enough to invent products, able to convince others to work for free and invest money and time with you, and passionate enough to quit her job to pursue unproven ideas.

Fooey! By definition, if you’re a startup founder you’re explicitly not your customer.

“Scratching your own itch” is how all three of my companies started, but it’s only that — the start. It’s the spark of inspiration, not the strategy. It’s the grain of sand tickling the oyster, not the pearl.

Look! Smart people agree:

“Be a user of your own product. Make it better based on your own desires. But don’t trick yourself into thinking you are your user.”  Evan Williams, founder Blogger & Twitter

“If the VP of Engineering thinks the target customer is just like him/her, you’re doomed.  If the VP of Marketing thinks the target customer is just like him/her, you’re doomed.”  Cranky Product Manager

“Our customers did a lot of stuff that I would never do. We think differently. We solve our problems differently. We have different needs and wants. Repeat after me: You are not your customer.”  Eric Ries, Lean Startup leader (repeating a conversation with a startup founder)

In fact I challenge you to find one founder of a real business who thinks “I’m the customer” is the only market validation you need.

“There are millions of potential customers, so it doesn’t matter what only ten of them think. I need to just start; later I can survey and learn something statistically significant.”

If there are millions, it’s trivial to find ten. If you can’t find even ten, then either there’s not millions or those millions aren’t interested in you.

Businesses don’t start with millions of customers, they start with one, then ten, then a hundred, and then a thousand. But most don’t get past ten.

If you haven’t gotten ten to at least say they’ll buy, where do you get your hubris to proclaim that thousands actually will buy?

“My customers can’t understand mock-ups. I have to build it first.”

You shouldn’t need screenshots or PowerPoints to convince someone in your target market that what you’re doing is compelling. If your concept is so esoteric that you can’t describe it in 30 seconds at a cocktail party, it’s either too complex or you don’t understand it yourself.

Even if I concede that some folks can’t grok mock-ups, remember that your first customers will by definition be early-adopters who are OK with alpha software. If you can’t find a few of those and get them excited about your product, maybe your product isn’t exciting.

“I suck at sales/marketing; I need to build a product so compelling it sells itself.”

The world is filled with decent products that make no money. You know this!

Oh fine, you want empirical evidence? Here’s a list of the top 100 Twitter clients, and here’s some more. Now:

  • How many do you suppose are decent pieces of software that basically work?  (My guess: 80%)
  • How many do you suppose produce any revenue?  (My guess: 5%)
  • How many do you suppose produce enough revenue that, after hosting and marketing expenses, they result in a profitable company where the owner doesn’t need a day job?  (My guess: <1%)

Conclusion: If your goal is a business (not a hobby), building charming, novel software isn’t enough.

You and I know you have the ability to build cool new software. We agree that will be fun and exciting. But that’s not going to create a business.

Writing code is what you love, so you myopically decide that’s what you’ll do. But what you should do is just the opposite: Attack the part of the business you’re least sure of, you’re least qualified for.

If you’re still not convinced, think of it as project risk management. In a big software project do you tackle the high-risk, ill-defined stuff first, or do you postpone that to the end? Obviously you address the unpredictable stuff first — most of the project risk is due to the unknown, so the earlier you can sort out uncertainty the more time you have to deal with the consequences.

I’m making the same argument, except the “high-risk unknown” is “everything that’s not code.” Your code will be good enough; it’s the other stuff that will probably sink your ship — unable to find customers or unable to convince the target audience they should open their wallets.

No sense in postponing it.

“My friend/brother/co-worker/dentist thinks it’s a great idea.”

Your mother thinks you’re smart and good-looking, but that doesn’t mean I do.

It doesn’t matter what non-entrepreneurs think because they’re not versed product/market fit, squeezing blood from evanescent budgets, and using Facebook for advertising instead of sharing the latest FailBlog movie.

In fact it only barely matters what real entrepreneurs think, because they’re not expert in your problem domain, they might have outdated notions, they might be biased against certain ideas and technology, and they carry baggage from good and bad experiences (due as much to timing and luck as anything else).

The only thing that matters is that people are willing to give you money! Business “experts” can argue all day long that it makes no sense to buy shoes over the Internet, but as long as people give Zappos $1 billion per year, it doesn’t matter what experts say.

When ten people say they’ll give you money if you build this thing, that’s the only validation that counts.

What else?

What other excuses have you heard? Which excuses are you using now? Leave a comment and continue the conversation.



Tweet this!

Bending over: How to sell to large companies



Tweet this!

This is a guest post by Steve Hanov, who blogs about programming and startups.


For a micro-ISV, selling to big businesses can be more lucrative than selling to consumers. Instead of making a few dollars per sale and hoping for thousands of sales, you sell to only a few customers, and charge much higher rates. But the rates are high for a reason. It takes more time and money to sell to businesses, especially the big ones.

Legal Issues

Consumers rarely read software license agreements. Most corporate customers don’t read them either, but some have legal departments that must approve any agreement that the company makes, no matter how small. Your EULA will be examined with the same fervor as a billion dollar acquisition.

The license agreement’s primary purpose, then, is to get past the customer’s legal team quickly, because they stand between you and a sale. It helps if it is fair and well balanced at the start. That way, if they add crazy one-sided terms, you can negotiate without sounding unreasonable.

Some terms that you may be asked for:

  • “If you go out of business, we get all of your source code.” The request is common. The customer sees it as an insurance policy in case a smaller supplier disappears, and the assurance it provides may be so important that they are unwilling to drop it. Source code escrow services will hold on to your source code for a fee (hint: get the buyer to pay). Opt for a more informal arrangement if they don’t specifically ask for this service.

    [Editor's Note: When this has come up I've always used the same line: "We're happy to put code in escrow.  You set up the escrow agent and bear all costs."  Every time this policy was accepted without a fight, and never did a customer actually set up the escrow!]
  • “If someone sues us over your product, you have to pay our legal costs.” Indemnification is also a standard clause that is difficult to get removed. If you can’t stomache any risk of personal bankruptcy, incorporating your micro-ISV is a must.

    [Editor's Note: Incorporating isn't enough because usually lawsuits with small companies name the primary owners as well as the company. You also need an umbrella insurance policy for yourself. You have to allow the indemnity clause, but your lawyer can help you craft words that ensures, for example, that damages cannot be greater than the money the customer spent, or that they can seek damages only if the customer themselves are successfully sued for damages, and not just that they got sued at all.]
  • Support details. Are you going to be providing free technical support for this product in perpetuity? I hope not.
  • “What happens if the product is defective?” It’s only fair to offer a full refund if the customer is not satisfied.

A good software license agreement that you can re-use in a variety of situations can cost anywhere from $1000 to $5000. It pays to shop around.

[Editor's Note: Most small companies start by copying a EULA from a similar company, possibly even a competitor.  That's a copyright violation, but perhaps you can use it as a guide with a lawyer of your own.]

Quotes

A quote looks just like an invoice, except that it has an expiry date. Sixty days ought to be long enough for the client to make a decision, even if the whole department goes on consecutive vacations.

Even if you publish your prices on your website, many companies require a formal quote anyway. This is a document they can put in their system, not something fleeting and changeable like a website.

Make sure you get this right; if your eventual invoice deviates from the quote they’re going to scream bloody murder.

Evaluation Version

The purchasing process can take a long time, so you might be asked to provide an evaluation version while the details of the sale are worked out. It is unclear whether the customer acknowledges any of your license terms during the evaluation period, so the product should have a time limited expiry and other technical measures to ensure compliance.

[Editor's Note: It's impossible to be strict with an evaluation timeline. There are counter-arguments to the following (and please leave those in the comments), but in my experience big companies move slow regardless of how much of a hard line you want to have with the evaluation period.

However you can still use the timeline to your advantage. Still have a time limit, then when they inevitably need more time, you have an excuse to say things like, "Well I could try to get permission to extend the deadline, but I need to tell my boss something. Is there progress on getting the sale done? Are there any technical barriers we need to remove?" In other words, gain information about what they're doing and at least secure another step forward in their purchasing process.]

Purchase orders

You and the end users of your software have patiently waited for five months for the company’s legal team review your license. Now, the signed copies have been faxed (yes, faxed!) back and forth. At last, they’ll click on that Paypal button on your order page…

Think again. Once a large business has agreed to buy your product, you are expected to send it to them for free. They do not have to pay you a dime until they feel like it. Instead, they will send a purchase order — a document saying they intend to pay eventually.

The good news is that purchase orders are a legally binding promise to pay you, after all of the terms have been fulfilled. Here is a diagram to illustrate the procedure:

Click to Edit on WebSequenceDiagrams.com

If you are lucky, they will use PDF files for the purchase order and invoice. But you will probably have to send and receive some more faxes.

[Editor's Note: "Waits exactly 29 days" is optimistic. Often they pay much later than the stated deadline. Yes you can try to impose late fees, but good luck collecting on those. Probably not worth your time anyway.

Another mistake I made early on was to send invoices before the PO (Purchase Order) was received. Invoices that don't include a valid purchase order are automatically rejected.]

“Please read this 100 page document about our invoicing process.”

Sometimes, after everything is agreed, you’ll be asked to perform some kind of insanely complex invoicing procedure. The instructions are laced with stern, upper case warnings that if the invoice doesn’t follow the proper format, lacks item category labels (found in document B), or is submitted during the wrong hours, it will be ignored.

If you have priced your product appropriately it will be worth it to spend a few hours to learn their codes and procedures. If the price is too low, you can try your luck and (politely) ask if there are any other options. (Do not mention why!)

[Editor's Note: Companies with complex purchasing procedures are also used to spending more for software. It's OK to ask about what their purchasing process is like before you send the original quote. If it sounds complex, it's appropriate to add extra charges to deal with it. However, mask it as something like "installation support" and not "coping with your ridiculous payment system."]

“We will release the funds after you provide your US social security number.”

US customers will sometimes ask for a Taxpayer Identification Number (TIN). If you are not a US taxpayer, you don’t need one. Once you point this out, they may be okay with it, or they will ask you to fill out a US form W-8BEN and send it to them. The form is scary because it states that your “income” will be subject to a 40% withholding tax. Don’t worry: the purchase price is not “an amount subject to withholding”, and sellers do not need to start doing US taxes (if they aren’t already). Some US businesses feel that they must keep this form on file for all suppliers, and it’s easier to comply than argue. Here’s some more information.

[Editor's Note: In the US there's never a reason to give out your SSN.  Instead, get an EIN (Employer Identification Number) from the IRS. This is what will appear on all your legal forms with customers as well as your corporate tax returns. You don't need to incorporate first.]

“We only pay using Bankers’ Scrolls made from papyrus”

Many companies have a policy against using Paypal. It’s best to use an old fashioned check if you can. You can suggest, but never insist on a method of payment. Money is money! Some international customers only use bank transfers. If so, call your bank for the information that you need to provide them, and expect about $30 of the payment to go to fees.

[Editor's Note: Smaller banks often have ridiculous multi-hop procedures for accepting international wires. If you must use a smaller bank (e.g. maybe a smaller one offered you a bigger line of credit), still have a working account at a bigger bank for things like international transactions.]

Resellers

Imagine you are asked to buy some software from, say Adobe.

  1. You go to their web site,
  2. try to find the link to buy,
  3. figure out how to pay,
  4. get to the checkout page,
  5. then stop and search Google for “adobe coupon codes”,
  6. go back to step 1
  7. keep refreshing your email for the link,
  8. download the software.
  9. Keep of record of the receipt somewhere.

Now imagine you have to do this for 1000 different items, at 1000 different web sites. It gets to be a very large job. Some companies have outsourced their procurement to resellers.

A reseller is simply an intermediary who pays you and provides the software to their client. It’s also their job to ask for a discount, but there is no need to provide one. They have been told to acquire your product, and have already been paid a fee as a percentage of your price.

[Editor's Note: Never never never never give these guys a discount! Was that clear enough?  :-)

They might go down easy or they might use sleazy hard-sell tactics to get you to lower your price. Some will even say they have the power to block the sale. That's not true; they don't get their useless, stinky paws on the order until it's already approved.]

Keep smiling (in public)

Selling to big companies can be frustrating. Throughout the process, it is important to stay professional and pleasant. Sometimes, it may appear that your customer is trying to screw you. Even if they are, is your job to be jovial, point it out, and assume that it is a simple oversight. It makes no business sense to throw money away because of a rude email.

What else?

What other techniques do you have? More stories from the field? Leave a comment and join the conversation.



Tweet this!

hosting