I have a question - perhaps an idea for a future video? How to handle all the legal stuff and taxes? Do I really need to become a business owner before attempting to launch my first SaaS? I understand the answer strongly depends on the country I live in - but perhaps you could shed some light on the topic from your perspective?
I can’t recall the video, but I do recall Rob mentioning he only handles the legal parts after he’s gotten some paying customers. If you’re in the US, there’s companies that help with legal (Clerky, Stripe Atlas, others)
Obviously this is not legal advice, but I would wait until you are actually making money from your saas before going through the trouble of setting up the legal, banking, tax accounts. Often, your first idea is a flop, and it would be a wasted effort to set all of that infrastructure up only to have to reverse course if it goes nowhere.
Hey Rob, I just want to let you know that I started my B2B startup and I registered a domain and created a notion template in that domain. I don't know anything about frontend but I do know about backend and how it works using Go language. My question is should I learn frontend or use the no-code solution like Tailwind UI for the frontend or should I completely replace coding by being totally dependent on no-code solutions like Webflow, Wix, etc? Note: I don't have a job yet, so it means I don't have a budget for no-code solutions. I have to wait to get a job. Till then I have two ways to either learn frontend or build a community to spread awareness(marketing) and provide the minimum services at least on that notion template. What should I choose now? Thank you
In terms of next steps, I’d suggest you start with this video: ruclips.net/video/pFhVQo0YPyw/видео.html If you are looking to stand up a decent looking landing page to test and see if there is any interest in your idea, Using something like Wix, Squarespace, or even something as simple as Carrd might work temporarily. If you have a programming background, you can probably pick up a front end language, and long-term, that might be a better option than the no-code option listed above.
Yes, as you scale the problems change. Finding product Market Fit may be your #1 priority up to $10K/month. At $100K, you’ve found some product market fit and your focus will move to scaling, infrastructure, team building, etc.
Whatever happens, happens such as you are either formed by nature able to bear it, or not able to bear it. If such as you are by nature formed able to bear, bear it and fret not: But if such as you are not naturally able to bear, don’t fret; for when it has consumed you, itself will perish. Remember, however, you are by nature formed able to bear whatever it is in the power of your own opinion to make supportable or tolerable, according as you conceive it advantageous, or your duty, to do so.
The comment "Unit tests are less vital" really lost him a lot of points in my book. Unit tests are the corner stone of CI/CD. They help keep the code flexible and clean. They avoid unexpected problems and having to hunt for a bug for days. They are vital in SaaS.
I actually do agree with him on that. I think of it as testing especially at this level should be as close to user experience as possible. So e2e an integration makes more sense. Units tests in my opinion are more for the difficult/core parts of the product.
Never meant they aren’t useful! But if someone is considering skipping testing in the name of velocity, then I recommend tests that exercise more of the stack vs isolated parts.
Unit tests make you go faster, not slower, unless you are not used to them or are just learning to use them. Again, I don't think you are using them correctly if that's how you think about them. I never pretended that you said that "they are not useful", I said that they are the corner stone of CI/CD and are vital when you intend to keep your code flexible and clean. What I am saying is that they are a lot more important than you think they are, and you pretty much just confirmed my suspicion about it.
I would only skip unit testing if I am eventually throwing away the code base, as when building a tool that I will only use once or building a prototype that I will throw away before going to production. Or maybe on the front-end if my back is well tested, then I can focus on integration testing on the front.
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
SaaS Marketing Strategies Competitors Are Using To Crush You: ruclips.net/video/vonsIB-Em1M/видео.html
8:54 absolutely agree! Writing integration tests at least for the happy paths is definitely worth the effort!
Thank you for watching.
Thanks for featuring me! :)
Great tips here.
Of course! And thank you!
This Derrick guy should definitely be featured more often. Great stuff 👍
8:40 don’t skin tests
9:30 marketing and customer conversations are crucial
Thank you. I have worked on my SaaS last 3 years, and even now, your advice is actual
I appreciate it!
So much value got from this video, I've learned a lot! Thank you so much!
Happy to hear it! Thank you for watching.
Nice! I was just waiting for a bonus tip in the end :)
Hope you enjoyed it!
You guys are the best! Suuper helpful, keep up the great work :)
Thank you! Will do!
Wow! very helpful,thank you Rob
Happy to hear it! Thank you for watching, Patrick.
I love your content , please keep posting
Thank you, Abdul.
Beautifully said😊
Thank you 🙂
I have a question - perhaps an idea for a future video? How to handle all the legal stuff and taxes? Do I really need to become a business owner before attempting to launch my first SaaS? I understand the answer strongly depends on the country I live in - but perhaps you could shed some light on the topic from your perspective?
I can’t recall the video, but I do recall Rob mentioning he only handles the legal parts after he’s gotten some paying customers.
If you’re in the US, there’s companies that help with legal (Clerky, Stripe Atlas, others)
Obviously this is not legal advice, but I would wait until you are actually making money from your saas before going through the trouble of setting up the legal, banking, tax accounts.
Often, your first idea is a flop, and it would be a wasted effort to set all of that infrastructure up only to have to reverse course if it goes nowhere.
9:33 most important point
Love the visual template you use in your videos, can I purchase that template?
Glad you like it Hector! It’s not something that we have for sale.
I super can relate to the tech stack thing.
Thanks for watching!
Thank you!
Thank you for watching!
Hey Rob,
I just want to let you know that I started my B2B startup and I registered a domain and created a notion template in that domain.
I don't know anything about frontend but I do know about backend and how it works using Go language.
My question is should I learn frontend or use the no-code solution like Tailwind UI for the frontend or should I completely replace coding by being totally dependent on no-code solutions like Webflow, Wix, etc?
Note: I don't have a job yet, so it means I don't have a budget for no-code solutions. I have to wait to get a job. Till then I have two ways to either learn frontend or build a community to spread awareness(marketing) and provide the minimum services at least on that notion template.
What should I choose now?
Thank you
In terms of next steps, I’d suggest you start with this video: ruclips.net/video/pFhVQo0YPyw/видео.html
If you are looking to stand up a decent looking landing page to test and see if there is any interest in your idea, Using something like Wix, Squarespace, or even something as simple as Carrd might work temporarily.
If you have a programming background, you can probably pick up a front end language, and long-term, that might be a better option than the no-code option listed above.
@@MicroConf I have built a notion template and I am working on the programming side and building a community also.
Do you have any content on how founders should manage their first few engineer hires?
run regression packs on staging env before pushing changes to prod😊😊😊
Where do you learn about this stuff ?
How are SaaS for ~$10,000/mo versus ~$100,00/mo different animals? Just by scale to be supported?
Yes, as you scale the problems change. Finding product Market Fit may be your #1 priority up to $10K/month. At $100K, you’ve found some product market fit and your focus will move to scaling, infrastructure, team building, etc.
Whatever happens, happens such as you are either formed by nature able to bear it, or not able to bear it. If such as you are by nature formed
able to bear, bear it and fret not: But if such as you are not naturally able to bear, don’t fret; for when it has consumed you, itself will perish. Remember, however, you are by nature formed able to bear whatever it is in the power of your own opinion to make supportable or tolerable, according as you conceive it advantageous, or your duty, to do so.
2:35 Does anyone knows the background song?
The comment "Unit tests are less vital" really lost him a lot of points in my book. Unit tests are the corner stone of CI/CD. They help keep the code flexible and clean. They avoid unexpected problems and having to hunt for a bug for days. They are vital in SaaS.
Derrick is doing something right. His success is not an accident.
I actually do agree with him on that. I think of it as testing especially at this level should be as close to user experience as possible. So e2e an integration makes more sense. Units tests in my opinion are more for the difficult/core parts of the product.
Never meant they aren’t useful! But if someone is considering skipping testing in the name of velocity, then I recommend tests that exercise more of the stack vs isolated parts.
Unit tests make you go faster, not slower, unless you are not used to them or are just learning to use them. Again, I don't think you are using them correctly if that's how you think about them. I never pretended that you said that "they are not useful", I said that they are the corner stone of CI/CD and are vital when you intend to keep your code flexible and clean.
What I am saying is that they are a lot more important than you think they are, and you pretty much just confirmed my suspicion about it.
I would only skip unit testing if I am eventually throwing away the code base, as when building a tool that I will only use once or building a prototype that I will throw away before going to production. Or maybe on the front-end if my back is well tested, then I can focus on integration testing on the front.