Frequently Asked Questions

Since I get asked these questions a lot, I've compiled them here to save you some time.

What is your development process?

You can read all about my product development process right here.

How long will it take to build an MVP for my startup?

First, read about my development process to get a background on how Agile development works.

The short answer

Minimum: 2 weeks. Maximum: the amount of time it takes you to truly understand your customers’ problems.

Some clients of mine have taken 1 month to launch an MVP, others over a year.

Why the difference in time?

The first set realized that testing a product with real customers as quickly as possible is the only way to know if you have a product with potential for success.

The second set insisted on perfection, so they spent a long time polishing a piece of software that they hadn’t even proven would solve their customers’ problems.

You want to be like the first set, and I can help you do this.

The detailed answer

Your MVP isn’t a product we can design and conceive of with absolute certainty at the beginning of your project.

Getting to your MVP is a process, which requires constant feedback from customers, and iterative refinement of the product in response to that feedback.

Think of building an MVP as a series of science experiments.

You start by proposing a simple solution to your customers’ problems (the hypothesis), then you show the solution to your customers to test if it is the correct one (the experiment).

If you manage to find a solution immediately, that’s great! But more often than not, it will take several experiments before you find a solution that truly helps your customers.

The faster you can run experiments, the faster you’ll reach a solution that works.

That solution is your MVP.

Essentially, the MVP is the end point on a journey to understanding your customers’ real needs.

So how quickly you reach the MVP stage depends primarily on how quickly you can understand your customers problems, not on speed of development.

In fact, if you test the most important aspects of your solution first, it’s theoretically possible to have an MVP in under 3 weeks!

Example MVP development time line

Because I follow an Agile development process, we will begin your project by prioritizing the features that you hypothesize will be most important to your customers.

I will then build the most important features of your app first, so that your customers can extract immediate value from your product, and you can test your hypothesis as quickly as possible.

The first week

During the first week of work, I set up the development environment, prepare tooling, select hosting infrastructure, choose a base software stack, etc.

This “set up” phase is essential to building your product, but you probably won’t see much in terms of results here. That comes in week 2.

The second week

The second week is the first Agile sprint, where your product begins to take shape.

By the end of the week, you’ll have an ultra-simple yet functional product that you can show to customers, to gather feedback and check if you’re on the right track.

Third week and beyond

Of course, how useful the product will be at this point will depend on your customers, the complexity of the solution you proposed, and most importantly, how well you understood your customers’ needs before the sprint started.

Most likely, more sprints will be needed to refine the product to move it closer to solving your customers true problems.

But if you plan things correctly, each week you’ll have something you can test with your customers, and you’ll always be moving ever closer to your MVP.

Eventually, your customers will let you know when you’ve got something they actually find useful enough to pay for.

Apply to work with me, and we can discuss the time line of your product in more detail.

What kind of problems can you help me solve?

Basically any technical problem your business is having.

Some examples:

Getting Started

  • How do you test your business idea without building anything?
  • How do you build your Minimal Viable Product (MVP) without wasting money?
  • What features should you put into your MVP? What should you leave out?
  • What tech stack should you use? What are the risks and opportunities associated with a particular stack?
  • How do you build a product road map to keep your team on track while building your product?

Team Building

  • What professionals will you need to hire to best solve a particular problem? Is it the right time to hire?
  • How do you properly screen and hire potential team members?
  • Should you outsource to freelance contractors or hire employees?
  • How do you avoid being ripped off by freelance developers and designers?
  • Why is your current development team unreliable? Why are they constantly missing deadlines?

Increasing Revenue

  • How can you leverage your user data to increase sales?
  • Should your team code their own solution to a problem, or use a SaaS product or third-party solution?
  • How do you reduce costly bugs in your project?
  • How do you avoid delays during development?
  • How do you raise money to fund development? What are the best options at each stage of your business?
  • How much should you budget for each stage of your business? How can you save money?

Managing Growth

  • How can you attract more users to your platform, or keep them from leaving?
  • How do you reduce on-going server and infrastructure costs?
  • How can you make a sluggish platform website feel more responsive?
  • Is it the right time to scale?
  • How do you scale up from where you are now?
  • How do you properly test UI or marketing changes without disrupting users?

Apply to work with me and we can figure out a solution to your problems.

Will you work for equity?

Generally, no, I will not work for equity alone.