Should you code yourself if your idea is actually great?

[genesisk5]

I know it's all about action, not the idea and
nobody is interested in your idea unless you prove traction.

but if you genuinely think that your idea for a SaaS is
really great to a point where you think the company hired
to make an MVP of it might get to have an urge to steal it,

should you still remind yourself that nobody is interested
in your idea and delegate to the company or can it actually
be that you better code yourself to protect your idea?

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[Subsonic]

I know it's all about action, not the idea and
nobody is interested in your idea unless you prove traction.

but if you genuinely think that your idea for a SaaS is
really great to a point where you think the company hired
to make an MVP of it might get to have an urge to steal it,

should you still remind yourself that nobody is interested
in your idea and delegate to the company or can it actually
be that you better code yourself to protect your idea?

the company could just steal your idea after you made the mvp and published it anyways.

If you have a concern like this you can always sign a contract with the company that forbids them from stealing your idea.

That would include a nda and non compete together with some other specific legaly binding therms for the working relationship.


Remember that you can always ask chatgpt for solutions to problems like this.

 

[srodrigo]

I know it's all about action, not the idea and
nobody is interested in your idea unless you prove traction.

but if you genuinely think that your idea for a SaaS is
really great to a point where you think the company hired
to make an MVP of it might get to have an urge to steal it,

should you still remind yourself that nobody is interested
in your idea and delegate to the company or can it actually
be that you better code yourself to protect your idea?

I'm a code monkey, so I'm biased. Use at your own risk:

I'd recommend, in this order:

1. Partner with someone who can build an MVP. Good luck with this though, as the big chunk of the initial time investment relies on that person and I would personally not build someone else's idea for revenue share, unless it looks great (but there are also great snake oil sellers, so I'm careful with this).
2. Try using a no-code tool. I'm unaware of the details that I'm sure these tools miss, but some people have successfully built some MVPs, so worth looking.
3. Learn how to code yourself. This has many benefits: being employable on a high-paying skill (should you need it), being able to prototype your ideas without limitations, etc. The main con is the time investment to get decent at it. But hey, tech is still not easy despite the great tools that are simplifying it.
4. Find cheap labor and pray that you don't get a piece of crap and you wasted your money.
5. Pay a fortune for an actual developer who knows what they are doing.

Good luck.

 

[Andy Black]

I know it's all about action, not the idea and
nobody is interested in your idea unless you prove traction.

but if you genuinely think that your idea for a SaaS is
really great to a point where you think the company hired
to make an MVP of it might get to have an urge to steal it,

should you still remind yourself that nobody is interested
in your idea and delegate to the company or can it actually
be that you better code yourself to protect your idea?

Could the MVP for a Software-as-a-Service offering be a Service? Can you provide a more expensive DFY service and use the revenue to start building tools so you can provide the service better?

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[SEBASTlAN]

No one is stealing your idea buddy

 

[genesisk5]

I'm a code monkey, so I'm biased. Use at your own risk:

I'd recommend, in this order:

1. Partner with someone who can build an MVP. Good luck with this though, as the big chunk of the initial time investment relies on that person and I would personally not build someone else's idea for revenue share, unless it looks great (but there are also great snake oil sellers, so I'm careful with this).
2. Try using a no-code tool. I'm unaware of the details that I'm sure these tools miss, but some people have successfully built some MVPs, so worth looking.
3. Learn how to code yourself. This has many benefits: being employable on a high-paying skill (should you need it), being able to prototype your ideas without limitations, etc. The main con is the time investment to get decent at it. But hey, tech is still not easy despite the great tools that are simplifying it.
4. Find cheap labor and pray that you don't get a piece of crap and you wasted your money.
5. Pay a fortune for an actual developer who knows what they are doing.

Good luck.

That was a great food for thought. thanks a lot.

 

[genesisk5]

No one is stealing your idea buddy

Correct. after posting this I did some research and was reminded of that. my head is always leaking..

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[genesisk5]

Could the MVP for a Software-as-a-Service offering be a Service? Can you provide a more expensive DFY service and use the revenue to start building tools so you can provide the service better?

I've decided to go this route. coding alone in house is inefficient. I'm ditching this now.