Having Your Software Idea Built

If you're lost about how to turn your software idea into software - then you're not alone. Nearly every client I have, who has an great idea for software, doesn't know the steps to take to make it happen. But take heart - with a few key guidelines, and the common sense you already have, you're going to fly through this process.

Here are the primary questions I get asked:

Should I even tell you my idea? What if you steal it?

Building software is all about trust. It's like having your kitchen redone - you're trusting the contractor is going to do a great job, leave the house clean, and not give you a bill for twice what you had planned for. So, the first order of business is to find someone you trust. This means:

- Talk to them. Have a conversation, get to know them. If it doesn't feel right talking to them, take that as a strong hint.

- Ask for references. Sample work is a good first start, but it's often hard to judge what a programmer actually did. And heck, what looks good on the surface may be an awful mess behind the scenes. The best solution? Talk to people who actually worked with the programmer.

Were they reliable? Easy to talk to? How do they take criticism?

- Have the programmer sign a Non-Disclosure Agreement (NDA). An NDA is a nice, extra protection, that says you're serious about protecting your idea. Feel free to get your lawyer involved, or just grab a template off the web (one you've read, thoroughly, of course.)

This process is all about trust - if it doesn't feel right, move on to another programmer.

How much should it cost?

That depends. Creating software will cost money. Perhaps not a lot of money. And to some, $20,000 is pocket change, while to others $20 is a big sum.

Having software built is kind of like buying a car. You can spend anywhere between $5,000 and $50,000 to buy a car - and on one level, they will do the same thing. Get you from point A to point B. Obviously, the $50,000 car will get you there more comfortably.

You should, at a minimum expect to spend thousands.

The price of the project will be a combination of budget plus what you want to accomplish.

Two key pieces of advice I give my clients:

Pay a fixed price - Whatever amount you pay, the last thing you need to worry about are surprises. If the programmer gets stuck on something, and he definitely will, you don't want to see a big spike in your invoice. So yes, even if the price is hard to swallow - get it fixed, so that once it's decided, it's done and you can relax about it.

Plan to grow your software - Your goal should be to find the smallest, version 1.0 of your software that you can build that still captures your idea. Removing feature after feature takes work and discipline. But the benefits are many, including: reduced cost, faster time to market, a chance to test the programmer on a smaller job before trusting them with a big job, and a chance to change your product direction if things don't go as expected.

The goal should be to come up with a price everyone is happy with and everyone feels like they got great excellent value. If you're not feeling this, stop the relationship and move on.

What happens when the software is built?

It's the Ideas2Executables policy that you own the software we build for you, and you can do anything you want with it. Sell it, take it to another programmer, throw it in the trash - whatever you want. This is, I believe, the most fair and simplest way to deliver software, and I highly recommend you find this arrangement.

Knowing that you can always take your software and go elsewhere will provide you with a key advantage, should it become necessary.

Those are the primary questions I get asked. Have another? I'd be glad to address it, drop me a line at questions@ideas2executables.com.

Here are some ground rules that I think are ideal for programmers and clients (that's you) to follow:

Programmers:

- Do not share the client's idea with anybody without getting permission. Not even mom.

- Provide frequent status updates of the project

- Provide versions of the software as the software is being built. This is critical, you want to see the software take shape to make sure it's on the right track.

- Provide early feedback if a feature isn't going to be possible or will require excessive work

- Hit your promised dates. At the very least, provide very early warning if a date isn't going to be possible to hit

- The only kind of surprises your clients should have are good ones

- Give the client the benefit of the doubt

Clients:

- Provide specific and constructive feedback

- Document any details you want included in the project, before the price has been agreed upon

- Make sure there is an electronic paper trail for every decision and agreement. E-mail works great for this. So can instant messenger, provided logs are saved.

- Pay on time

- Software will have bugs - that's just how it is. Help the programmer find them, and get rid of them.

- Give the programmer the benefit of the doubt

Have other ground rules to suggest? I'd love to hear them, drop me a line a questions@ideas2executables.com

OK, by now you've figured I'm pretty passionate about building software. Yeah, it's true. So, let's talk- you can give me a call at (270) 747-4253. I'd love to hear about your idea, and get you started on your way.

If you want to learn more about me, you're welcome to check out my company's website. You can even check out my personal blog if you want.

Yeah, those two links pretty much sum up everything you need to know about Ben Simon.