Building Your First App: What No One Tells You Before You Hire a Developer
Most founders don’t realize their software project was already in trouble before they hired anyone. The mistake happens much earlier in the gap between having an idea and knowing what you are building. Instead, you can avoid this costly mistake by making decisions before you ever reach out to a developer.
Decision 1 – Scope before Team
Most founders can describe what they want their application to do in broad strokes, but broad strokes are not enough for a developer to build from. Make sure that the requirements for your application are clearly laid out so that the scope of the project is well defined. Requirements are one of the main inputs used by development teams to ensure they are building the right functionality. Scope also enables founders to map out what they want built so there are no surprises when the application rolls out.
Decision 2 – Build, Buy, or Integrate
Custom code is expensive and often the most complicated option for founders. A good use of time is ensuring that there is not already a product on the market that meets the needs of the business owner. Oftentimes a good off-the-shelf product will rapidly enable new value for a business and avoids the costly development option. Integrating products already in use is often a low-cost option that owners don’t think about. Focusing on the end-result of the project will help define the work needed.
Decision 3 – Who should build it
There are several options founders use to complete software projects: freelancers, agencies, offshore developers, or in-house. The complexity of the project and familiarity with software will often drive this decision. The right answer depends on timelines, budgets, and on-going support needs after launch. Owners should avoid making decisions based on the most confident pitch.
Decision 4 – What does ‘done’ look like
If you can’t explain what the feature should do when it’s complete, then your developer will not be able to either. Vague requirements produce vague results, and you won’t know your project is off track until you’ve already paid for the wrong thing. Building out clear criteria that explains when a feature is complete will enable developers to build the right functionality.
Decision 5 – Who is accountable for the delivery
Most founders assume the developer will surface any problems when they arise. Developers assume founders know exactly what they want. When those assumptions collide six months into a project, everyone loses. Someone needs to make sure that what is being built matches what was agreed to and that person is not your developer.
Answering these five questions before you hire anyone is exactly what a Pathfinder Assessment is designed to do. By the time you talk to a developer, you already know what you’re building, what it should cost, and how you will know when it’s done.
If you are a founder getting ready to build yourfirst piece of software, then reach out for a free 45-minute call. No pitch,just a plain assessment of where you are and what the next step might be.
