I have a VERY long list of things to write about, and any work day for me consists of browsing Twitter, chatting with people, and writing articles, outlines, or taking notes. I do that full time, pretty much.
849 karma · joined October 21, 2012
[ my public key: https://keybase.io/arvidkahl; my proof: https://keybase.io/arvidkahl/sigs/_6k9ClbkSqfdNVPlM7Ar9fo3G32IwgvxozEC0z0bNkY ]
I have a VERY long list of things to write about, and any work day for me consists of browsing Twitter, chatting with people, and writing articles, outlines, or taking notes. I do that full time, pretty much.
Wrapped in a funny story.
I think such a collection of stupid ideas lists would make for a great "anti-cheat-sheet".
I've been to Elixir conferences, and they felt like people were just encouraging each other to build solid software WITH each other. I've not seen this level of camaraderie for other programming language communities.
Elixir devs — and I am super biased here — are a special bunch :)
JUST the front page, it appears.
For a website that has been around so long and has been a fundamental building block of what most of us understand to be a diverse, open, and highly interconnected internet, this is quite close-minded.
People will only give you the benefit of the doubt if they know that you are part of the team — you are a peer. Not a stranger, not a threat, but one of them.
The thing that stands out for me is that involving my (future) readers from day one has been a 100% positive experience. I expected things to be boring or ego-bruising, but this journey has been extremely positive.
I'm fortunate to be deeply embedded in the community I am writing for. Indie hackers and founders are quite supportive of each other, and it shows.
The service periodically checks the original sources and redirects broken links to the archive.org snapshot automatically when the sources fail. Any redirection can be customized or fall back to an author’s website.
The usual problem is that anything that is supposed to prevent link rot itself is prone to rot.
Which is why my SaaS solution has a self-off boarding function: writers can use custom domains for their links and export a fully functional nginx and Apache-based redirection config file at any time. I also have a contingency plan for the next decade, which includes setting up such a low cost redirection server myself.
I needed this service for my own books. So I just built it. Dogfooding is what I recommend to Bootstrapper’s anyway, so I am my first customer.
It’s highly reliable (it’s a 301 forwarding system after all) and very cheap to host.
You can find this at https://permanent.link
While I understand the reasoning behind such an automated disabling, but it probably could be done better. Like delaying the update (and the disabling part) until the user made a choice.
Also very hard to inform users of this issue after it has occurred. Caused us so much trouble. Also a reason we went with the admittedly less safe blanket permission.
Cheers to all the small SaaS businesses out there keeping their services up and running without much of a hick-up all year round.
What surprises me most is the lack of understanding of founder risk. Most negative comments are related to employees not walking away from this exit. It feels to me that many here seem to conflate the inner workings of heavily VC-backed businesses with a slowly and sustainably growing company like Baremetrics. I see a lot of assumptions all over the comments.
I appreciate the discussion, though. It's nice to see people sticking up for employees. But a sub-10-people SaaS that's ALMOST self-funded is not the same as a prospective unicorn.
Gotta say, JSON export alone makes a whole lot of difference with this one though.
I've always found the indie hacker/bootstrapped founder community to be very open and supportive. Many of the people who wrote the guides and articles that I learned lots from have never paywalled their content. If at all, they added some sort of additional product, a course, a book, or consulting opportunities. But the content was always free for those who'd need it most. And that's what I wanted to do as well.
Later in my career, I've worked for more traditional software businesses, but they didn't encourage testing either. It was always an afterthought, and time was better spent on building flashy and fancy new features to pacify customers.
When I founded my first bootstrapped businesses, it was the same thing: things had to be built quickly, almost always as easily scrapped experiments. A SaaS that is well-tested but missed it's market opportunity window was something I didn't want to risk.
Even with the SaaS FeedbackPanda that finally worked out (and which I sold with my co-founder last year), testing was more or less non-existant. We truly tested in production, and trusted the infrastructure and framework choices we made to bear the most of the burden. It worked out for us, and even our acquirer didn't expect much in terms of TDD in the properties they were looking for.
I have the feeling that the concept of rapid prototyping has developed into a cultural phenomenon that expanded into software engineering—and people have adopted to it.
I know of a university teacher who is looking into solving the arduous task of grading without going crazy. I approve of a tool being built to facilitate this.
I am torn on this issue as well: I strongly dislike formal education, with it following a metric of "teaching to the test" and "learning to test instead of retention." I wish that there was more systemic change towards a different way of assessment.
But not for one second will I assume to know what is best for the teachers in that space. If building a pre-grading (which is merely an example here) can help them shave off an hour of tedious work a day, I think it's a valid side project idea. It may even be a valid business idea.
The project that changed my life[1] was an EdTech productivity system that generated student feedback for online teachers working with young students in China. Student feedback as text-only is a horrible way of communicating individualized instruction. Yet we help teachers speed up that process, which allowed them to do one thing: teach more. Be more present in the classroom. Foster stronger relationships.
I would argue that making anything nominally more convenient is a good thing: it removes an inconvenience so that things that matter can take place. No teacher would call teaching inconvenient. Lots of them would call admin stuff very inconvenient.
Again, it's not about "teaching to the test" per see. It's about removing barriers to allow for meaningful, accomplished, and impactful work.
[1] https://thebootstrappedfounder.com/from-founding-to-exit-in-...
I've found one approach work very well with my mentees:
- Figure out which "special interest groups" you are part of beyond software engineering. That can be "aquarium owner", "coffee lover", "morning person", "diligent grandson" — the less technical, the better.
- Among these "niches", find the ones that could benefit from a transfer of technology, like (spitballing here) "teachers who work from home" (education niche) + "automated submission and pre-grading of homework" could work (digital document collection and rule-based checking logic), or "aquarium owner" + "nitrate cycle tracking IoT device" (hardware-enabled analytics) + "optimal light scheduling" (machine-learning-supported recommendation engine).
Do that for all the groups you're part of, and you will find lots of ideas that aren't just "scratch-your-own-itch". They are 'scratch-an-itch-you-understand-and-know-how-to-remedy'.
It's really promising to see that you value the time of the founders you fund so much that you are ready to talk to them in a way that suits them, not just you.
I like this.
Most problem discovery in any market happens through careful qualitative analysis that happens during and after interviews with prospective customers.
Looking at their behavior is a first step to getting a glimpse of what the day-to-day work looks like, and where you as a SaaS could interface with that.
The second step is figuring out customer intent ("what do I want to get done"), problem awareness ("what could be done much better"), pain intensity ("what is unbearable about my work").
Some of those come directly from the prospect, mostly problems where they have high pain and high awareness. Others, you will have to find yourself, such as low-awareness problems. Then, there are problems to dismiss, such as low-pain and non-intent-aligned ones.
To me, a niche represents a group of people you select out of a more general population.
From what you wrote, I understand that we agree that niches don't "exist", they are "defined". That is both a result and a starting point, which makes this whole exercise so hard - it's an iterative approach: you define a niche, you explore their problems, you re-define the niche, explore again, until you have found a critical problem worth solving.
The point is that you can't find problems without communicating with those who have them. Looking won't do. You will need to listen.
- MRR went up a bit: "Great, we're on track"
- MRR went down a bit: "THE END IS NEAR!!!!"
At some point, I understood that it was Loss Aversion Bias [1] at play. Once I reframed MRR movements as something fluctuating and neutral, it lost all anxiety-inducing powers.
So this might actually be fairly neat if the business owner has a reasonable approach to this metric.
What do you think about the list itself?
I never hired. I should have hired. I had alerts waking me at night dozens of times as well. I planned family trips around internet availability. I thought I was needed to solve any problem. That's why I never hired. I thought it would be too much effort to train someone.
Selling the business resolved all these issues at once. Hiring someone to take care of these things for you will allow you to have time to yourself and wind down. I trained my replacement. Turns out other people can do this job.
You don't have to start with the sale. You can start with delegating.
In many ways.
It took us less than two years from founding to exit. I write about it at https://thebootstrappedfounder.com/from-founding-to-exit-in-... . Danielle, my Co-founder, and I did an interview at https://www.sureswiftcapital.com/blog/bootstrapped-saas-foun... as well. Both articles give some insight into the process of selling the company and how we got it to that point.
Our experience was very positive. We had structured our business to be as sellable as possible, even when we didn't intend to sell it. Having documentation and automation in place at every corner made the due diligence and transition phases a joy.
I see a lot of people in the comments here asking for valuation and structural information. In researching the process before we sold, I had the same questions, and never really found reliable answers. It seems that every transaction is inherently unique. All numbers we throw around, MRR, EBITDA, multipliers, they are thrown out of the window once you look at the actual business, it's internal workings and dependencies.
My suggestion for fellow SaaS bootstrappers who want to sell their business: make sure you can hand it over easily, make sure you are not required (to remain part of the operations), make sure your infrastructure is either easily migrated or well-documented.
You will want to negotiate, as value is in the eye of the beholder.
I am currently writing at length about this whole process. I'll release it on the blog before the end of the month.
If allowed me to learn the paradigm of functional programming and build systems quicker than ever before. Combined with the Phoenix framework, I prototyped a tool within a few days that would end up changing my life. I turned it into a SaaS business (called FeedbackPanda) with my partner, and it has been turning my life around for the better.
Thank you Jose for being such a key person in all of that without knowing it. Your insights and determination to leverage new tech combined with a proven software paradigm. Spot on!
Ah, the famous Nuremberg defense. Sorry to invoke Godwin's law immediately, but shifting responsibility away from the people executing the questionable work to the people who either own or consume it is a denial of agency of each and every software professional.
I argue that the workplace of the knowledge worker is not one of blind obedience. Moral reasoning should not be suppressed just because there are other market forces.