Big News: FounderDating is joining OneVest to build the largest community for entrepreneurs. Details here
Latest Notifications
You have no recent recommendations.
Name
Title
 
MiniBio
FOLLOW
Title
 Followers
FOLLOW TOPIC

Question goes here

1,300 Followers

  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur

Should I launch MVP with poor code base or rebuild & launch?

We are building personal finance website for Latinos.

In order to test our idea we decided to build an MVP/prototype using wordpress to shorten development time and cost.

I recently hired a new development team as prior engineer quit and was noticed that the code was not up to par. We have been operating without a CTO given that our technology is simple (to the likes of a credit card comparison site) and thought we could build MVP while taking the time to find the right CTO.

The new development team is suggesting to build from scratch because:

  1. They estimate it might take them two months to build from scratch and estimate it could take them just as long to finish wordpress work.
  2. They are afraid a lot of bugs and issues will surface as they finish work on wordpress. The site would not be good to launch to public as some users could have a poor experience.

The new development team comes highly referred from other startup CTOs and they would be equity partners so economic interests are aligned (no true incentive to try to gain a few extra thousands from us...I hope).

I am approaching this more from a business perspective. Even if the site is not code perfect but operates decently I want to launch to determine product market fit and save time and money.

Some users could have a poor experience but want to validate the idea. Thoughts?



52 Replies

Michael Brill
6
0
Michael Brill Entrepreneur
Technology startup exec focused on AI-driven products
If you trust your new technical team and you said:

  1. They estimate it might take them two months to build from scratch and estimate it could take them just as long to finish wordpress work.

..then you're not going to get to market faster with your existing crappy code. If you truly trust your team, they've already made the decision to rewrite it because finishing the existing code doesn't get to market faster.

It doesn't sound like you really trust them though.
Danny (Duc) Duong
3
0
Danny (Duc) Duong Entrepreneur
Lead Software Engineer at Platphorm
I would go with rebuilding from scratch. Honestly, developers hate to continue to work on a mess created by others. When they are not happy, they will not be productive.

I bet you already have all the UI design, database schema, workflow,... Rebuilding should be quick, probably less than 2 months if you have a good team. (I'm talking about normal MVPs though, I don't know how big your MVP is)
Dan Meier
12
1
Dan Meier Entrepreneur
Reinventing Manufacturing Management Software
In my experience, development teams, no matter how good, are typically lousy at estimating project duration. My rule of thumb has been "estimate and triple" -- I get my developers' best "gut instinct" estimate, then triple it to get a realistic project duration. (Don't, however, let your developers know you've tripled their estimate, else they'll take even longer!) This has consistently resulted in "real-world" estimates that are pretty close without spending a ton of time analyzing project design and architecture to get a better, more informed estimate.

One more thought. Developers -- particularly the best ones -- tend to have a "not invented here" mentality. The code is crap if they didn't write it. They may well be right. However, if you're always re-writing everything (because developers come and go), you'll never release anything. Particularly for an MVP, "good enough" is the key consideration. You need to get feedback from your customers, and the sooner the better. There will always be time to "optimize" the code later...if you have a viable product.
Bill Lennan
26
0
Bill Lennan Entrepreneur • Advisor
Red Rope Social
Launch now!

I've done more new launches than I can count.
Every time we had known issues.

We also had a boatload of business hypothesis - of which a significant portion were ultimately found to be incorrect.

You can spend the time and money to write great code wrapped around bad business assumptions and that's just a loosing game.

You can always do an invite only launch - start with 100 people. See what works, what breaks, what they completely miss.

I love elegant code - but all the elegant code in the world won't save you from a bad business hypothesis.
David Albert
2
0
David Albert Entrepreneur • Advisor
Founder & Principal at GreyGoo
It depends on the extent of the issues and bugs. I agree with Bill that things don't need to be perfect, but launching with something unusable is going to hurt you more than help prove out your model.

If that's the outcome you fear, as someone who has been through this numerous times in working with and consulting start-ups, build from scratch. You'll likely regret it if you don't. Obviously that's my advice from just the information from your post and an accurate recommendation would require true due diligence, but 9 times out of 10 just licking your wounds and rebuilding is the best route. We've had startups launch with bad code, had early wildfire success and ended up creating a bad reputation and pissed off customers because they couldn't patch the mess fast enough once they had paying users.
Jake Carlson
3
0
Jake Carlson Entrepreneur • Advisor
Software Development Manager at Oracle
Maybe I'm missing something, but exactly how close to complete is this project? Devs always want to write everything from scratch and make it their own (I'm speaking as a dev). If there is hardly any code written, let them. As other have said there is value in making them happy, as they will be much more productive that way. If it's close to completion, this is not the right move. Have them slog on and finish it up, learn from the MVP, *then* build from scratch when you have learned enough to make it worth it.
Edward M. Yang
3
0
Edward M. Yang Entrepreneur
Managing Partner at Firecracker PR
Perfect is the enemy of good.

If I remember correctly from Lean Startup by Eric Ries, it advocates validating a product idea as early as possible, regardless how polished or finished it is.
Stephen Packer
0
0
Stephen Packer Entrepreneur
Lead Developer at Lettuce Box LLC
I agree with the other comments: If you can afford it (time and money), I'd suggest going with the new dev team's suggestion on rewriting it. If they inherit the code (that they consider bad code), every fix and feature will be slower because they have to either refactor bad code along the way, or they have to work around code that they don't know/like and hope they don't break anything.

Conversely,if they're going to be the ones maintaining and adding new features, it'll go much smoother if they are the architects of the code base.

Perhaps a middle-ground would be to soft-launch with what you have, and allow the dev team to start working on a version 2.0. A lot can be learned from even a buggy application. When 2.0 releases, then the big marketing pushes can begin.

Danny (Duc) Duong
2
0
Danny (Duc) Duong Entrepreneur
Lead Software Engineer at Platphorm
I had a comment above and want to add:

Your prior engineer left and said the quality is sub par, it's the red flag.

If your MVP has too many issues and crashes frequently, how would you know if users don't like your idea or give up because of the inconvenience. MVP doesn't need to be perfect, but needs to be usable.
David Albert
8
0
David Albert Entrepreneur • Advisor
Founder & Principal at GreyGoo
"Perfect is the enemy of good."

Absolutely agree--but the principles of Lean Startup are to launch with an MVP, not code that is buggy, sluggish or unstable. There's a difference between polished and finished vs. buggy--the latter risks turning people off depending on the severity of those bugs. That's the judgment call you really have to make.
Join FounderDating to participate in the discussion
Nothing gets posted to LinkedIn and your information will not be shared.

Just a few more details please.

DO: Start a discussion, share a resource, or ask a question related to entrepreneurship.
DON'T: Post about prohibited topics such as recruiting, cofounder wanted, check out my product
or feedback on the FD site (you can send this to us directly info@founderdating.com).
See the Community Code of Conduct for more details.

Title

Give your question or discussion topic a great title, make it catchy and succinct.

Details

Make sure what you're about to say is specific and relevant - you'll get better responses.

Topics

Tag your discussion so you get more relevant responses.

Question goes here

1,300 Followers

  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
Know someone who should answer this question? Enter their email below
Stay current and follow these discussion topics?