Developers are a different beast, and the advice here may not apply to anyone who is not a developer and is a normal human being.
Pick an idea you have used. When you start a startup one of the persistent problems you face is that you don't relate to the problem. If you are not a parent, its almost impossible to relate to any conversations that parents have about their troubles. You just don’t. This lack of empathy in a startup setting adds up to a huge disadvantage and will never allow you to be fully confident in what you are doing. 2. Pick an idea you have already paid for: If you have ever paid for a service, think very carefully about that. Can you code it yourself if you give yourself a few months? It is because developers don’t pay for shit. If an app forced you to do that, then there must a real need for that app.
3. Don’t pick something that needs a pretty UI: My product Proxies API is an API. I can get away with almost no UI. It is such a relief that I don’t have to work with a designer. I find that I am 4 to 5 times faster when I don’t have to deal with UI stuff.
4. Don’t pick anything that you need in-person sales for. Marketing is a developer’s friend. I realized this only later in my life. In-person sales are very weird for the developer personality. My advice. Don't do it. Learn how to market instead.
5. Pick something that is a self-serve model: People signup for a trial and decide to pay or not pay based on their trial experience. This is a beast that you can conquer. You don’t want to be going around talking to actual humans. It is not for us.
6. Try writing: If you can code and write, you will win the world. The whole success of Proxies API is based on constant improvements to code and a little bit of consistent writing over time.
7. Keep it real: Be clear on your motivations. I know that developers are not motivated by the prospect of making millions. But they are excited by the promise of financial freedom. So I was clear on my motivations when starting Proxies API — I didn’t want it to make me millions. I wanted it to give me financial freedom by earning what I earned in my day job. I didn’t need a penny more. By being clear about it, you are not living someone else’s life but your own, and it will give you the necessary fuel to keep going.
Have fun.
The author is the founder of Proxies API the rotating proxies service.
This article originally appeared here: https://www.proxiesapi.com/blog/Tips-For-Developers-Who-Want-To-Build-A-SAAS-Startup.php
https://www.proxiesapi.com/assets/img/steve.jpg
https://www.proxiesapi.com/assets/img/customer1.jpg
https://www.proxiesapi.com/assets/img/customer3.jpg
https://www.proxiesapi.com/assets/img/customer4.jpg
Makes me question if the customer reviews or even the customers themselves are real.
Logos, customer reviews, etc. are just tricks.
The way the person's head is framed in the shot is pretty much identical most of the time and kind of a tell on its own.
Other tells:
- steve.jpg: The skin above the top rim of his glasses has some repetition/distortion.
- customer1.jpg: Distortion in the hair, most noticeable at top left. Mouth looks fake too.
- customer3.jpg: I didn't notice anything significant, but it just looks like an image taken straight off TPDNE. Do "vibes" count?
- customer4.jpg: The teeth merge into each other.
Probably the biggest giveaway is that the faces are all positioned identically in each photo, but there's something else that juuuust quite doesn't look real. Maybe some of the faces just seem a little bit more androgynous than anyone I ever see in real life. There's something about them that sits just on the edge of the uncanny valley.
Our friend Steve has something going on with the left hinge of his glasses.
Customer1 has an interesting right ear.
Customer3 has very asymmetrical earrings.
Customer4 has a bulge where the left earring would normally be, and the right hinge of their glasses is crooked.
"customer1.jpg" and "steve.jpg" lol
Maybe sometimes it feels a bit much to ask to use someone's review and also ask for a photo of them.
It is somewhat disingenuous but I don't think I mind too much if they are legit customer reviews.
I don't believe that these testimonials are real.
[2] see the Our customers feel it section
I’d say: if you want to be successful, push yourself. All of these things are skills that can be learned.
I frequently find that I reach the “I give up” ceiling very quickly when I try to push myself on most things. I reckon it’s because I can be quite impatient and intolerant towards frustrations.
And what are your thoughts on talent? Sure, most skills can be learned, but the rate of learning can vary and time is limited. How worthwhile is it to learn something if you know you might be slow at it and the skill plateau is probably not too far off? Do you normally aim for good enough for those skills you did learn but don’t think you can be an expert on them?
I try to spend time learning things that interest me personally, and when that happens to overlap with things I deal with at my day job, great. If not, oh well.
I don't really consider how long it might take to learn something if it's interesting to me, and I tend to dive pretty deep, even if I don't get to "expert" level. I figure if I need to become an expert in a thing, that'll come with time.
I'm shit at it, but the mantra I tell to myself is: "remember when you were a kid? These are other kids that play with the same toys as you. Just talk about the toys and how to make toys more fun. Same enthusiasm!".
Just stay away from the mindset of "convincing people". Nobody likes being convinced to do something.
The problem is: this kind of "nerd talk" that you are enthused about often comes across as awkward in particular to business-minded people.
In other words: I can perfectly understand why many developers have bad experiences with talking to people: too different interests and thus quite a lot of bad experiences in the past.
edit: example: one such industry is selling big expensive machines and/or software to run them.
The only thing I'll differentiate in my thinking from the OP advice is consider thoughtfully how well you are served by diarizing your development process and how much more can come from thinking in reverse from the customer perspective.
The post would have had more merit if they left their startup’s name out of it, e.g. only on their profile page.
The way I understand Stripe Tax is that it will give you a huge list of sales like:
$210 paid from a company in the USA
$123 paid from an individual in France
$300 paid from a company in Japan
...
And then you are supposed to do the right thing with that list.Is that true?
Do you pass that giant list to your tax accountant and they fill all the correct paperwork?
What if some of those sales mean you have to pay taxes directly to the country in which the buyer is? You deal with that countries government directly then?
When you are doing low revenue numbers like this guy under 100-200K per year its hardly ever relevant.
A lot of countries and states don't claim sales tax to international countries under a certain treshold: 30 - 100K per year. (if you are selling to consumers would actually be a waste to charge sales tax)
The EU is different, but if you are in the EU relatively easy to comply with.
Use paddle or revin instead of stripe or use stripe with quaderno or with stripe tax.
Stripe tax doesn't work too well yet imho but it may end up getting there
They charge 5% per transaction.
I would expect that MoR's have their own set of issues. As they become the seller. So they are liable for the product quality, safety etc.
So I don't think signing up and working with them will be very easy. Especially if your product is not as standardized as an ebook or something.
So if you use those, I would love to hear about your experiences. What you sell, how the signup was and how the relationship with them is going.
Last time I looked at the Paddle signup flow, I already had two issues I could not resolve:
- What product category my product falls under. None of their categories seemed to fit.
- How to sign up before the site is live. Paddle wants to look at the site. So do you have to build a dummy that works up until the point where the user buys something and then it says "Sorry, we are still looking for a payment solution"?
Paddle only replied with nonsensical semi-automated messages to my questions. And when I answered and asked for a real answer by a human, I never got a reply.
How long did it take you to hit that number? Many of us devs want to do SAAS but don't understand what's a reasonable amount of time to expect until we can get "ramen profitable".
Probably quite long but I had a lot of stuff to set up to get the product automated (and I did barely any marketing, basically just wrote a couple random blog posts for SEO).
> It's not allowed for us to publish your app in our own developer accounts
I've published apps for others in my developer account
I suggest adding your site link to your HN bio, as it might be of interest to some HN people.
You - being the future SaaS startup developer.
For frontend engineers, should the advice be the opposite: "Pick something that needs good UI/UX"?
If you're a UX person and have access to a pool of people to do user testing with: pick something that needs good UX
Those two are somewhat at odds with each other, and neither is really the job description of a typical frontend engineer (though of course some frontend engineers are good at one or both)
"Don’t pick something that needs a pretty UI": What if I'm really skilled in UI dev and have a good visual eye? Or a friend happy to do some free mockups?
"In-person sales are very weird for the developer personality": there is no one developer personality, I wouldn't rule this out at all.
"You don’t want to be going around talking to actual humans.": this is almost never going to work for a startup. Actually talking to people (users, clients, integration partners) is probably the most important thing you can do as a founder.
> 1.. you don't relate to the problem
Yeah, it's like being blind. "Why do people buy that thing?" is a question I barely get answer confidently
> 2.. because developers don’t pay for shit
It's getting worse. These folks always demand open source alternatives, self-host. Sometimes, the moral of story is "I want your free labor no matter how your family is doing"
> 3.. Don’t pick something that needs a pretty UI:
Super related here. When I realized my product value is literally UX/UI, it's like the end of the word because there's no many HCI solutions at all. It's always hard to use for any target, techie, non-techie, it's hard still.
> 4.. Learn how to market instead.
Developers try to do marketing is like trying to do self-surgery, ones just can't
> 5.. You don’t want to be going around talking to actual humans
I ended up shitting on a customer because he thought he knew problems (my app trying to solve) more than I do, but I'm confident he didn't know shit.
> 6.. Try writing
Yeah, this is part of content marketing. It kinda sucks to me though, lots of content marking is just for sake of marketing, doesn't bring much knowledge.
> 7.. Keep it real.
The most real sad thing is going back to working for corp.
Also, be prepared to fail a lot before you succeed...your first solution might not go anywhere...your tenth one might not either...but your eleventh product...who knows?
Not sure what you're referring to by "writing" here. Blogging? Writing marketing copy?
How has that experiment been working out?
Customer feedback is the most valuable resource for a starting company. Understand what brings value to your customer, and understand what the pain points are. Where do they get stuck trying to use your product or service?
Apply what you learn from customer feedback. This is also a feedback loop on the improvement cycle of your product, as you should observe a drop in customer service requests once an improvement has been applied.
With every improvement cycle, the product should bring more value and less friction to the customer. This will make marketing so much easier as you now understand the customer's pain points, and you have a product that solves just that. Do it right, and the product will basically sell itself (you still need marketing though).
Yes, in most cases, they're not making millions, but who needs millions anyway? If you can buy food, pay rent, and support your family with a product that you made with your own hands, wouldn't that be nice?
This is what my site https://microfounder.com is exactly about: "It's possible for a solo developer to build a profitable microstartup to pay the bills and live life on their own terms."
AND you got me interested! Definitely noted, thanks for sharing!
How do you market your software-product? with small budget..?