HackerTrans
TopNewTrendsCommentsPastAskShowJobs

bramkrom

no profile record

Submissions

Maven.com Product Breakdown

medium.com
1 points·by bramkrom·5 years ago·0 comments

How to Set Up Veracode in a Large Azure Project

community.veracode.com
1 points·by bramkrom·5 years ago·0 comments

comments

bramkrom
·5 years ago·discuss
Sorry, totally missed this. In case it's still relevant: Stages were all before 500k revenue. So maybe the very successful ones did have their mvp built by someone else, but I just didn't encounter them. As far as proper hand-off concerns - yes, I've seen companies usually deal professionally with their hand-off. That's what their reputation depends on. But the idea of the MVP is not necessarily the product - it's more the first attempt at seeing if you can solve something. Next steps are usually hard to follow up. Seeing as you just do the minimal, you leave out so many things that later on it's just hard to improve on it. I'd want my co-founder to be part of all the initial learning, and so would rather stay put in my job and find a passionate co-founder first before having someone build the mvp. good luck!
bramkrom
·5 years ago·discuss
What worked for me (oversimplified): 1. Find an interest you're excited about and/or spend a lot of money in (climbing). It'll be easier creating something of value for yourself. 2. Write down what could be improved there. Problems you run into. Solutions you use that suck, or chose not to use because they suck. Build your problem understanding. (developing climbing technique and staying hyped) 3. Find others who're interested in this space. (fellow climbers) 4. Build your problem understanding. Ask them what is challenging, frustrating or annoying for them as climbers. Ask them what they've tried or are trying and what they like/dislike. 5. Come up with a solution. Make something super small. A landing page that explains your idea. A brochure. Something ideally that you can make within a week. A day's even better. 6. Show your solution to people you'd consider customers. Ask them for feedback about how they think this could solve their problem. (for me I came up with an online program, designed a landing page with google sheets and showed it as if it was an actual website. Climbers gave me feedback that they wanted to know more about the practical way of learning - exercises, etc) 7. Repeat step 5&6 until you have confidence this is worth building. Then you've got your idea you're asking for. Congrats. You've ended up at the hardest point: figuring out how to execute on your idea and get all the parts right and figuring out how to sell and market it.
bramkrom
·5 years ago·discuss
Writing from the Netherlands so advice might differ per country. I've worked with about 5 startups who had at least a part of their product built externally. There are three outcomes from your MVP being built externally: 1. It works, which for the moment is great. So you ignore the product and focus on mkt & sales. Because you need revenue. 2 years down you realise you need to start improving stuff, but find yourself limited because you can't change the code and don't really understand how anything works. Then you need to spend couple months raising funds to rebuild the product OR finding a technical founder. Quite the momentum killer. Not so great. 2. The result from your MVP (assuming you're using it to test something) is meh - mediocre, maybe, perhaps. People like this but don't like that. This has the biggest odds of happening. The thing that sucks here is that the learnings are probably your own, because the agency would ask you to pay way more if they'd be involved in all the user testing etc, because that's how their business model works. Translating them to your agency again has the odds of miscommunication or misinterpretation, which is why YCs credo is 'talk to users, write code' - just because you probably need to run through this feedback loop 5-10 times before you get it right. So, outcome also not so great. 3. Your initial target customers tell you the MVP really doesn't do the job and you either end up abandoning the MVP or starting to look for another problem to solve with it. Also really not outcomes you're looking for.

So yes - experience with hiring agency - all negative.

Given you're asking for an MVP I'd suggest you make it smaller. There are tons of ways to learn about your customers' problem and whether you can solve it for them without writing code. We've built landing pages using Keynote which we then tested with customers, ran entire processes that were supposed to be automated manually, and even prototyped a machine learning algorithm by manually coming up with our best guesses for a users' search query. Because the purpose wasn't scientific validation, the purpose was learning. All these three we built in a day. For more: https://hackernoon.com/the-mvp-is-dead-long-live-the-rat-233... http://paulgraham.com/ds.html