> I think it would need the backing of something like ycombinator, techcrunch or techstars

That's a bad mindset, imo, and probably just a distraction. If it's such a great idea that you think it is, build it and acquire users.

I think it's worth glancing at https://www.ycombinator.com/resources/ - but I think more people use this as an alternative to building things and getting users.

Saying "just build something people want" is reductionist well past the point of being useless, it's almost actively insulting. Customer acquisition is the death of almost every failed company.

Bootstrapping is tough for tech, because the curve is usually exponential. If you were selling lasagna, you could easily make $1000 profit the first week, and bootstrapping is easy.

With tech, it's quite common to spend a year trying to get to $1000/week, and then make $30k/week the next year.

You also have to consider competition. There are many kinds of ideas. Making a Tinder for X might not have too much competition, but if you do something that Google/Amazon/Facebook is building, you'll get crushed if you move too slowly.

This is usually where venture backing comes in - investors are happy at getting good returns, and you're happy at skipping years of consulting, etc to pay the bills.

Don't spend too much time negotiating or optimizing; you're aiming for 3300% annual growth and a 20% better deal isn't worth your time. Paul Graham/Viaweb started at 10% for $10k. (http://www.paulgraham.com/ycstart.html) It seems unfair, but it was still a good deal for both sides.

my advice is - go with backend as api and separate frontend. define the api(protobuf+swagger plugin, not raw anonymous json because you will get lost in fluid schema later on and with 10+ routes you will go crazy without schema) and strict interfaces. so you know how data will flow. just pure basics, not all the functionality you have in your mind/vision. avoid DRY, copy code all over the place, go with kiss and most importantly YAGNI. use tech you know, not what is fancy right now.

then proceed to implement it in the fastest way possible. the end result should be a MVP with the worst code you can imagine. I myself have never been able to execute it, unfortunately. Each programmer strives for perfection which in this stage means time wasted not delivering the end product. I am certain that this way, no matter the size of the project, you should be able to produce something usable within 3 months.

You WILL be struggling with authN but mostly authZ(unsolved problem) so go for the simplest solution you can think of.

Next important thing is to do a monolith first. NO EXCEPTION. Forget microservices or SOA at this stage. I too fell into this trap and kinda keep repeating this mistake over and over. People like to use too much abstraction. Just brute-force it.

Then make sure you run one single VPS. No cloud, not kubernetes, no docker, nothing. Run it as close to metal as possible without any infra mumbojumbo fancy scheduler...tech..whatnot. And avoid cloud VPS. Look at OVH, Hetzner, DO or whatever. Just not cloud VPS because they are crazy expensive. Don't go for bare metal just yet(and avoid cloud altogether, it will bankrupt you in the long run, bare metal is where it's at).

Once you get the MVP up and running, look for first paid customer(s) and listen to their feedback. That feedback is free and no one else can give you better information than actual users. Also don't bother promoting the project on forums looking for people to test it for free. That is a dead end, trust me. Spend few bucks on some basic presentation page and some ads. Most notably it should be immediately clear on the website what your product does. I'd say 80% of companies these days fail at this horribly.

When you take payments, always upfront and annually will be better than monthly.

Once you get there, let us now :)

Good luck soldier.

I’m curious to learn more. Reach out to me at [email protected] if you want to chat.

So yeah I would reach out but I also don't really want to disclose any details until I've got something running and hopefully users using it. Of course there are NDA's but I've always wondered if those are worth anything.

Thanks for the response either way, appreciate the offer.

Is your idea building "Tinder for job search"?

I don't say that to discourage you. Quite the opposite. If you're passionate about it, do it. As others have said, at the end of the day, it's quite a simple formula: build X, get people to use X.

Even more simply, "solve problem Y for lots of people".

But this one feels different... and no it's not 'tinder for job search', I was just trying to use something to compare my idea market/space, etc without giving away anything (I'm paranoid that way).

I have bootstrapped a few apps... most notably a signup system to manage pick-up hockey games... I knew writing it it was a niche 'product' and didn't expect to make any money off of it and mostly just wanted it to cure a bunch of personal pain points of running pick-up/drop-in hockey games. Truthfully I thought I could get rinks to adopt it but after meeting with 3 rinks all owned by local muni's that idea fizzled out quickly. I did get one privately owned rink to use it (and they still do and love it), so it's fine, I make a little off it every few months (like 50-100 bucks) and it made/makes running my skates a breeze so all good.

Which is why I am trying to avoid that same fate... aka if I bootstrap this idea, there is no way I'm going to be able to get the level of users to compete with a Linked-In or a Tinder. To me that requires something like Ycombinator getting onboard and throwing their weight and resources behind it.

So I guess I'm saying I am pretty realistic about this idea... it's not a rink management or drop-in/pick-up management type thing that is very limited in the scope/scale. That idea never had the potential of truly blowing up.

This idea is more like a linked-in, tinder, facebook, instagram, giant, massive, holy fuck type of idea... and yeah ideas are a dime a dozen, but to me that's only true when that idea is coming from a friend, an uncle, a buddies wife... aka someone that doesn't really know how to qualify an idea like this.

I think I have my decision though, I feel that apply for Ycombinator is the right way to go; I'm convinced it's that level idea, that warrants that level support to get it to world domination levels.

Thanks for the reply.

My bigger challenge is whether to try to find 2 people to partner with, and if so who/what roles that would be. I know generally speaking solo founder startups are less likely to be picked up. Debating bringing on a designer or maybe a mobile dev(s) (I do back-end/db/web so I have that covered).

For example, if the TAM isn’t there, you can execute as well as you want, but you can’t increase the physical limit on number of customers.

I should've been a bit more clear... On the list of things that are important, having a "good idea" is near the bottom ... unless you're lumping in market validation, timing, total addressable market, etc. into "good idea". In this case, I wasn't. Those are all on the list of things that need to be considered though, and to me, fall directly in line with "execution", rather than "idea".

Again, this is just the way I see it, and it's mostly a semantic argument. But to me, "Idea" is like the hypothesis, and problem statement. "Execution" is proving that out by building a really good product and iterating on it, along with analyzing TAM and PMF. If you're better at the "execution" component, you're going to find more success. Especially if you're good at doing that portion quickly and reliably and can cycle through several "ideas". Therefore, ideas are a dime a dozen (in my opinion).