What are your best resources and advice to structure and build a business that can fully run without the owner?

I feel your pain — I've been there several times in a couple of my companies. Each situation ended up being unique, and had to be handled differently. I think there are a few things to consider before you make your decision: -- 1. What is in your cofounder's way? Is you cofounder being held up by a lack of clarity? Lack of motivation? Lack of autonomy? One of my past cofounders was very good at getting the job done, but didn't naturally have the skill to lay out tasks in a manageable way. To get around this, I worked with the whole team (4 people) to write up process documentation that removed the need to "figure out what to do next" that was tripping up this cofounder. -- 2. What job was your cofounder brought on to complete? And is it being completed? One of my companies brought on a cofounder simply to give us a marketing platform — he had a huge online audience — but he did nothing else. At first, this caused tension; once we had specifically laid out who was on the team and for what purpose, it was easier to identify where responsibilities lay. -- 3. Is your cofounder capable of doing the job? One of the more painful ordeals I've gone through in business is bringing on a good friend, then realizing that — despite his talent and intelligence — he just wasn't able to perform the job I'd hired him for. His skills were better suited for a different job: he needs hands-on management; he works better with repetitive tasks that don't require big-picture thinking; he lacks assertiveness and confidence, which were critical for the management-level role he'd been hired to do. After I tried to clear everything in his way, it became clear the company couldn't survive if he remained on the team. I had to lay him off. -- 4. Do you just simply not like the way this cofounder works? In one of my startups, there was a cofounder who I didn't know all that well, but he had amazing industry contacts and domain knowledge. However, once we started working together it became clear that we had VERY different working styles. He drove me completely nuts with (what seemed to me to be) a very ADHD-style of planning, with projects starting and being dropped and then coming out of nowhere with a call at 21:00 to discuss something critical that would be forgotten tomorrow. I'm sure I drove him nuts, too. So eventually we ended up selling that company — it was that or shutter it — because we knew there wasn't a chance we'd be successful if we continued as we were. -- Working with other people is tricky in general. Our instinct is to assume that we're the best workers on the planet and everyone else is incompetent, an idiot, a slacker, or all of the above. Usually it's a combination of an organizational-level lack of clarity, poor communication, no processes, and (sometimes) plain ol' we-don't-see-eye-to-eye-on-things-ness. Hopefully that helps. Feel free to get in touch if you'd like to hear specifics on my situations, or if you'd like any help devising a strategy for resolving your cofounder trouble. Good luck!

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.

Pardot is the easiest to learn and then execute. Will take your team the least amount of time to provide managed email marketing & automation services to your client. Naturally you'll want to bill fixed rates.

The existing answers are good, and I agree with most of the price ranges that are mentioned. There is a huge range in rates and they are most affected by the region and the type of organization you are dealing with. For example, a small shop in E. Europe that is exceptional in Ruby and has professional management, great communication skills, and the ability to work agile (for real) is going to cost in the high 30's. A company in the same region but with less mediocre communication skills will get you into the 20's, but it won't be the same experience. In India, it's similar but the entire price range is a bit lower. In order to understand how much you should pay, we use a simple approach like this: - we figure out what kind of client you are. are you a bootstrapped startup? are you techy? can you manage it from your end? Do you have time to take on a lot of QA? are you experienced with this? - knowing your client profile we can determine what kind of vendor will be successful with you. if you are an experienced client, have outsourced before, and know the ins and outs of software development you can work with freelancers, boutique shops, etc. if you are inexperienced with software and haven't managed this kind of thing, we might look for more of an agency type shop that will provide really good PM and awesome communication, etc. If you are pretty experienced and going long-term, you might consider an ODC model, too. - Knowing the type of client you are and thus, the type of vendor you need allows us to recommend a region and specific development shops for you. When we know what/where we're looking for, it becomes easy to answer that magic question ,'how much should I pay?'. This is basically the process that our entire business is based on :) Check out this video series that explains the process in more detail (complete with 2014 pricing numbers). Good luck, and feel free to reach out if you need any help choosing that perfect development shop. They are out there.

The number one would be shipping product (or anything really) out in front of a customer. If you can't work together to get something done fast, that is usually a huge indicator that somethings wrong. That usually means your values or mission aren't aligned.