Can you use Twillio as a smart routing business phone solution?

I've been developing web and iPhone apps for a while and I usually recommend to first use the provided sharing mechanisms. They provide great flexibility and as well don't require your app to request permissions on external networks. Using the iOS SDK sharing components will also save you precious development time. The most important part is the content that will be shared. On that side, make sure all the content has a unique URL, and can be properly consumed on all plateforms, desktop and mobile. Pay a particular attention to the head meta tags of those pages. Open graph and Twitter tags are not optional anymore and help driver a better visibility on the networks your content is being shared onto. Don't forget to track with an appropriate analytics tool how your users use the sharing module. Then you can evaluate the pertinence of building something custom.

HelpScout, ZenDesk or Desk.com. HelpScout (help desk software) would be a great start – less options but even when I ran a 6 person customer support team (with over 500 emails a day), we never needed the complex features of Desk.com. Have one person create 'saved replies' to quickly answer your customers in a cohesive voice and with consistent responses. (However, encourage your entire team to inject some of their personality!) This seems like a huge task, but if they dig through their sent emails, it can be done pretty quickly. Good luck!

Instead of repeating the wisdom of others, I'll link to it below. Here is a great blog post on hiring your first salesperson: http://tomtunguz.com/when-to-hire-a-salesperson Also, Mark Suster has written a ton of great post on his blog about startup sales. http://www.bothsidesofthetable.com/on-selling/

I've helped lots of SaaS companies improve their onboarding processes over the years, but I just published my best (high-level) piece on doing this right: http://sixteenventures.com/customer-onboarding The bottom line is (though I suggest reading the entire article) you need to know what success looks like for your customer - what their Desired Outcome is - and then reverse engineer the steps necessary to get there. Going through that process will reveal the steps necessary to get them to that Desired Outcome outside of the product; we're not talking about functional steps within the product yet. Map this out using flow charts, line lists, mind map, white board, etc. The tool isn't important as much as doing this right. Now, once you understand the process required to move them from Step 0 - deciding to take action to reach their desired outcome to Step z - achieving their (at least initial) Desired Outcome, you can start laying out, designing, and building the in-product processes necessary to achieve those success milestones and ultimately, their Desired Outcome. You should then peg your email (or other lifecycle messaging) flow to those success milestones (rather than doing a timed follow-up), where each message is sent like this: "have they done this milestone? yes, then send this message to get them to the next one." Since each user and customer will achieve success on their own cadence, it's best to not have a timed autoresponder sequence but to actually trigger based on milestones reached. The good news is that this is relatively easy to do given the availability of lifecycle messaging services. See this post for more on this topic: http://sixteenventures.com/email-follow-up-sequence Hopefully this helps, but if you want more details or - more importantly - want to figure out how to apply this thinking directly to your situation, request at least a 15-minute call with me.

Yes, a consistent sales process is vital so that you know where you are. You also want to know why you lost some orders and won others--I was over a decade into my career before I realized I had no idea why. And that's what lead to the change. You need to understand your numbers. You need to know what the process steps are, and how to proceed to the next one--or let the opportunity die if it should (hint: if you're trying to turn every prospect into a client, you're doing it wrong.) And you must have your fulfillment process dialed in, which at present with the description of murky data-gathering and pricing it sounds like you do not. Loads of info my my blog at http://www.salestactics.org Let's discuss specifics on a call.