Does this sound familiar?

"All of our developers are working on the core product. We don't have the resources to experiment with this."

"We need to build out the next version of our product. We have no one in house who knows how to do this."

"We acquired funding and have proven our concept. Now we need to expand our MVP into a solid V1."

"Hiring takes a long time. It does not make sense for us at the stage we are in."

What do you do?

You hire a contractor. They skip the discovery phase - they just want to get to work. Everyone is excited. Work gets done, everything is going well. Then you review the work.

Things just don't make sense. You know your customers would never use the payment screen in that way. And why the hell do you have three different types of modals across the board? Okay, you chalk it up to quick iterations - "We just had to get this done" you say.

Your team then goes to add a new feature a few months down the road. The code is a mess - it barely works. You end up having to refactor everything that was done costing your team financially and using up time you could have bene shipping new features.

You wish you had just hired someone to work in house.

In a perfect world...

You work with someone who understands how to balance the competing concerns of product development. Responsibility to customer, responsibility to business, and responsibility to developer.

Your users are delighted and you delivered the quality features they want. You reduced cost and generated revenue by delivering value quickly and iteratively. You minimized technical debt by having quality, maintainable code.

The work makes sense. The UX is clean and follows the steps your customers would expect. The UI is consistent, errors are handled gracefully. Most important - when a user first signs on, the blank slate experience is fantastic. Your customers know exactly how your product will look and function without having to spend weeks or months work in it only to discover, its not what they want.

You go to add a new feature a few months later. Your developers already know whats going on. They had an onboarding with the contractor prior to work was wrapped up. You refer to the documentation for complex processes. There is a visual guide to information flow. The code is clean, extending it is a joy.

You think working with a contractor is the best decision you made.

Im no unicorn BUT...

I have been working with startups like yours for the past three years. Startups are unique. I have made mistakes in the past and learned what works, and what doesn't when it comes to working with you.

I know how to break down your endless feature list and get you to focus on your mvp. I have designed, built and shipped products from start to finish. This puts me in a unique position where I understand the full product cycle and can work with your team at any point in the game.

I don't just dive in and get to work. I take the time to understand your goals, what your customers pain points are, and what your roadmap looks like. I help you wireframe, design and prototype new ideas to quickly validate if they will work or not. When all the stars align, I help you develop your product. I focus on balancing moving quickly and writing clean, maintainable code.

If you are thinking "Edward, you literally have read my mind" while you have read through this - take some time to explore a few teams I have partnered with in the past.