Best PBX to use with call center cloud software.

I consult with clients who are looking for the right outsourcing situation all the time, and the best way to get started is to figure out what kind of outsourcing partner will be the best 'fit' for your needs. After that, it's easy to find out where that type of outsourcing partner/contractor/freelance hangs out and pick a winner. Try writing up some notes about things like: 1) You mentioned you had a small budget - how small? If your budget is $1500 your options are going to be very different than if it's $25,000. Both of those could be considered 'small budgets' in the right context, so try to put a number out there. 2) You also mentioned that you wanted 'good quality, clean code'. What does this mean and are you willing to pay for that? If you are building an MVP and are really short on funds, you might have to use a less senior developer/team and take the risk of getting sloppier code - but sometimes with an MVP that's ok! If you are building a production app, that's a different story. 3) What is your technical and management expertise? Can you create specifications and manage a developer on your own (not easy to do)? If so, you can save money by using a freelancer, etc. If you are very non-technical and will need PM support, you might consider a small group or agency. 4) What does 'website development' involve, in your vision? Design? Copywriting? QA? Server migration and admin? ui/ux? 5) What is your tolerance for going offshore? You will hear lots of people saying that offshore teams all suck, and lots of people saying that they did it and it went fine. Like most software projects, there is a high failure rate but lots of success with offshore. You can save a ton of money, but you can also take a bath so you need to consider whether you are up to the challenge or not - going offshore takes much more patience, attention, documentation, etc. but it can work. 6) What are the skills/tech that you will need? It's best to get a team that is great at the skills you need. If you want a ruby site, hire a ruby shop. If you want a augmented reality site, find a team that is great at that. Watch out for the generalists :) By thinking through questions like the above, you can change your statement from "Where do you go for outsourcing website development" to something like this: "I am looking for an outsourcing partner who would be interested in a 15k-20k project that will be build in python. This application will be evolved into our production app so the quality must be good. I am a good project manager and will work with the developer on the requirements/spec side, and help test. We will need application/db design and development, server administration, and technical support but all design, content, copy, ui/ux will be provided. We will consider offshore teams but you must have excellent spoken english." When you expand your 'what we're looking for' paragraph, the whole search for outsourcing partner gets much easier! If you like, feel free to give me a call and share your 'vendor profile' with me and I can help point you in the right direction.

Most of my friends use www.wordpress.org and http://member.wishlistproducts.com/ to create their membership sites. Hope that helps.

Go for Wordpress initially. -- Custom website will delay your launch plans considering all factors. -- Wordpress can be used to meet your requirements from day 1. -- Once you have enough visitors and decided the revenue model + business objective plan for a customized website to be developed from scratch.

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.