1) Will my project be a priority?
Like many consultants, I prioritize projects against customer need and workload. We can discuss any specific deadlines you may have, but know that if I tell you it will be done at a certain time, it will be done. I include timeframes in all my proposals and it is not in my self-interest to over-extend myself.

2) How does this work? Take me through your customer's typical development process.
Most of my customers come from the web or by referrals. So if you are reading this after finding me on a search engine, you are in good company.
So what happens? I get a call. We discuss your problems, your timeframes, and my fee. If I'm a good fit for needs, it can go one of a few ways.

• Hire me on the spot (over the phone): Some hire me directly for small projects or to test me.
• Request for Proposal (over the phone): You ask me to email you a proposal, as I'm competing with other IT consultants.
• Request for Proposal (after meeting face to face): I meet you at your office location where we can discuss your problem and review your systems. I then write and email you a proposal.

Once you contract with me, I start the work based on the schedule and pricing terms outlined in the proposal. If there are any deviations—like "scope creep"—I always promise to manage your expectations and let you know before moving ahead. No one likes surprise charges.

After the system passes your review, it is installed, tested and users are trained. If everything is satisfactory, I begin any subsequent planned phases of the project.

After payment, I send you the source code. Just a tip regarding anyone you hire—always make sure you get the source code from any developer with which you work. If a developer will not give you the source code as part of his contract, I suggest you run the other way.

3) How long will it take you to build my application?
As you'd surmise, the answer is "it depends" as every job is different and it depends on the depth of your project and its interdependencies. I am up front in my proposals about the timeframe and I do my best to stick to that schedule.

4) Do you offer work on paid "test projects?"
Some customers find comfort in paying consultants for "pilot projects" in which they can test their services before committing to use their expertise for a larger project. I welcome the chance to work with you on pilot projects.

5) After you build it, will my new application do what I want it to do?
I have complete confidence in my abilities to deliver what you need based on what is outlined in our proposal. As the project evolves, you get to look at it and comment. I find this is the best way to weed out any misunderstandings about what an application is going to do, or should do.

6) How easy is installation?
Once the software is ready, I do all installations on-site at a time convenient for your business. I have much implementation experience and since I've already reviewed your systems, this greatly reduces any "surprises."

I often use shortcut icons for end user installations. The end user clicks on the shortcut I've created and installed, and it automatically configures them for the software without disturbing their settings.

Most things go smoothly as planned and if there are any set-backs, trust that I will either work until the problem is fixed or back out of the installation so you are back to where you were before the software installation started.

7) How well will it integrate with my current systems?
Any integration I design is specific to your computing environment. I have a lot of integration experience which helps me foresee any potential problems and mitigate risks.

8) Do work with, or research, 3rd Party Vendors on my behalf?
Yes. I can research new vendors based on your needs or work with existing vendors you may have.

9) What can go wrong?
Not that I'm faultless, but a problem I sometimes encounter is if a customer is not sure of their requirements. Sometimes my point person doesn't have a handle on their own internal processes—and it's hard to put software around a process that doesn't exist the way they thought it did, or a process that is not consistent with too many exceptions. Good processes are key and I find them in better run companies.

10) What if you are "hit by a bus?"
A valid concern and not one some customers like to ask. I always give my customers their software source code and work with viable products that are going to be available for the foreseeable future. This increases the pool of developers available to you for that product and, when you do hire a new developer, that person will have the software code at their fingertips.

11) What kind of support do you offer?
At Bright Network, the majority of our software support requests are handled immediately over the phone, remotely. This saves time and money because I do not physically have to be on site to assist users. If a user calls with a problem, they can click an icon I provide and we can assist them remotely to resolve many support issues that arise. For those support issues that require an office visit and are reachable by car, we respond within the requested 4 hours of the support request, between the hours of 9:00 AM and 5:00 PM Eastern Standard Time, Monday through Friday.

Much of the client support we provide is done remotely using a combination of Terminal Services and remote "desktop takeover software." This access method resolves problems faster and saves clients time and money because I do not have to physically be at their location to assist them, and it is very secure. Plus, the client is the only one who can initiate the connection whenever they need help; I cannot get into their systems without their knowledge.

12) Can I keep the source code you develop?
The source code is yours. I always give my customers the source code at the end of the project. You should question a developer who will not give you the source code. I don't understand that logic. To me, sound the alarms and run—that's not a good relationship.

13) What if I can't find our existing source code for you to work on? Or it's encrypted?
Well, if your code is missing, I can do my own search on your systems for the code. If it is truly missing, then there really is no other choice than to start over anew.

If you have your existing software code but it is encrypted or compiled, we can discuss next steps. Depending on its value to the project, we can attempt to decompile the code. I have done this on other jobs when a developer has "vanished." However, it may or may not work. It is not guaranteed. Read more about handling missing code in my Precise Voting Case Study.

14) How will you behave when something goes wrong?
Calm. If there is a problem, I've probably seen it before and I'm confident in my ability to troubleshoot any issue.

15) What would help me prepare before hiring you or any other consultant?

• Try to define your needs as sharply as you can.
• If you have existing software, know where your source code is, and make sure it's the latest copy.
• Make sure the right person or group of people in your organization are involved in the project. It should include the person(s) who'll be using the software day to day.
• Ask your potential hire the same Q&A questions that I've posted on my website.