When I’m hired onto an existing project, I’m often surprised to find that costly decisions were made early on in the process without insight from someone with sufficient technical knowledge to avoid costly mistakes. Everyone must live with these high level decisions (unless there is enough funding to absorb the cost of back-tracking). I’m surprised by how many times I see this major mis-step. How do we avoid it ? Consult early!

Technical Partner

Most often, the entrepreneurs driving a new project are not programmers, and thus are searching for that elusive “technical partner”, to help guide them through the murky, technical maze of web development. This is a fantastic idea. In fact, this article is aimed at making that easier. Here are a few misconceptions that entrepreneurs have about what they need from a technical partner:

There might be other requirements specific to the project. We need someone who is expert with Technology X. Once you start piling up this laundry list of requirements, we start to understand how people can get impatient and plow headfirst into projects without any expert, technical guidance. Alternatively, some become mired in “analysis paralysis”. Waiting for the arrival of the technical partner before making big decisions.

When dealing with tech, trying to understand what is happening can feel like “black magic”, so having trust in your advisor is key. Having a personal friend or someone invested in the project act as the technical partner is an understandable impulse.

Technical Consultant

To side-step the problems of finding the technical partner and still get that early, technical guidance, I am going to suggest working with a consultant. This may feel scary. And to make matters worse, this article is not going to solve the question of “how do I find someone I can trust ?” Earning trust is something that takes time. And in terms of finding someone, I don’t have anything beyond the obvious suggestions: Ask your technical friends. Friends of friends. Network. Etc…. I don’t have much to add to that conversation. However, we can (and will) discuss how to offset the risk of working with someone who (let’s face it), does not have 100% of your trust…. yet.

Let’s address the number one concern:

I need someone who is invested in the project (emotionally and maybe even financially) to get good advice.

Technical advice can be given without knowing too many details about the business domain. I’ve worked on dozens of websites and they all have had common technical structures, even though the content of each site has been vastly different. If this is a hard pill to swallow (But OUR site is completely unique!), I suggest you ask some of your programmer friends about it. I’m only talking about the technical structure here, not the content of the site.

Let’s talk about some big advantages to working with consultants as a sort of temporary, technical partner.

Consultants have wider perspective and are skilled at being resource efficient. More often than not, consultants must work as the programmer who is writing code, etc…. and also fill other roles that might not be for a smaller company. It’s no secret. Larger, more “corporate” companies, can end up being a bit wasteful in their spending. Startups and smaller companies are not afforded this luxury. Consultants, who work with these smaller companies, understand this fact.

Consultants have experience working on Minimal Viable Products (MVP) projects. We won’t go into depth here about what MVP means here. Chances are, if you are looking for a technical partner, you are in the very early stages of your project. Normally getting an MVP should be the first milestone.

Another unexpected benefit to working with consultants is that they are exposed to more people in the web development business than a traditional, “compartmentalized programmer.” It’s not surprising that consultants are likely to work on more projects than the traditional programmer, and therefore meet more people. If you develop trust with your consultant, they can be very useful in helping you find long-term or additional developers once your business takes off!

Mitigating the Risks

As mentioned previously, there is no magic trick to finding someone. Once you have some candidates, the following suggestions won’t prevent you from making mistakes, but hopefully they will prevent mistakes from growing into full-fledged catastrophes.

Work Incrementally

This is the same advice I have for working directly with someone who is writing code for you. Even if the consultant is only offering advice, start with something really small. You’d be surprised how often solving a small, easy task can be accomplished in a number of ways. Each decision has future implications. So start small! Paying a consultant for a few hours is certain less risk than sending a consultant off to plan out a complex task. You might find you don’t like working with this person. Or perhaps they are flashing some red flags…

Look for advice, not answers

Consultants should give people options. There is never a perfect answer. Each decision has pros and cons. A good consultant should understand this truth. I would be wary of someone telling me:

Get a Second Opinion

Or third or fourth if you have some serious qualms about your technical decisions / options. This might sound like an unnecessary cost, but again, mis-steps early in the planning can be exponentially more expensive later on.

Congrats for making it to the end of the article. If you are at that critical stage of your project, why not invest in the long term chances of success ? Consult early!