How We Bootstrapped Our SaaS Startup to Ramen Profitability

Tracking feature requests is a huge pain for most companies. A few pieces of feedback after dealing with this for years:

The Customer Support teams of your customers are going to be one of the main channels for capturing feature requests. We use Zendesk and have custom fields for categorizing and sub-categorizing requests along with a brief description. We do this so that the PMs don't have to read the entire Support ticket if one sentence is about the feature request out of 10 pages of text. If you could build an integration with Zendesk and other major ticketing tools that tie support tickets directly into your product it'd be an easy way to get your customers to have a huge influx of important data.

Sales will also provide lots of feature requests as they are also talking to many customers. You have to make this as seamless and as easy as possible otherwise they won't use it. Setting up a Salesforce integration is probably your only way to do that.

Tracking feature requests for strategic customers need to be treated differently than for other customers. There needs to be a system to categorize tickets by customer cohorts. If you can tie ARR, deal-breakers or other metrics to feature requests, that will help PMs prioritize them.

For your customers, publicly exposing feature requests is a double-edged sword. You're going to capture a lot of feedback. Some of it is good, some is bad. Not taking action on customer feature requests can build negative sentiment in the community.

Sales funnel feedback: I want to know what this will look like on my website to my users. That screenshot on the top isn't quite enough--I'm not sure which parts of that are my website and which are your widget. Is your widget always a big brick like that, or does it collapse into a little icon (like intercom + others)? Why not just put the actual widget on your homepage?

So I started the trial setup, but I bounced at step 1/3. Didn't want to write 5 feature ideas. And I still don't know what it'll look like on my site.

(Small side thing: I wanted to use the sample "board" name that you gave, but I couldn't just hit enter--I had to re-type it into the text field.)

Good luck! Looks interesting, from what I can understand so far.

Congratulations on your early success and thanks for sharing your story. It's inspiring and I love your storytelling style. I don't think people realize that it takes awhile to get everything started and your timeline/decisions clearly show that.

It's also a great product for us but as a fellow bootstrapper, the price range is out of our reach at the moment. We will be looking into when get more scale.

We're building a simple CRM tool that tracks calls, meetings and all kinds of details for companies. It would be interesting if you already have an API available that we can integrate with.

If you're ever in Edinburgh/Glasgow, be happy to take you and your significant other out for a coffee/beer.

Interesting post! About living nomad, is there any pain points regarding the management of the company from anywhere?

I read the post linked[1] in this blog post which talks about day to day life, even if work-life balance can be tough, it must be awesome for you guys! But what about administrative paperwork or hurdles (IRS, legal mail, and whatnot)? Was there anything different due to the fact that you guys are digital nomads?

[1] https://blog.canny.io/building-startup-digital-nomads/

S!=aS. I can't think of many instances where I'd pay a recurring fee for the use of a piece of code. Code to me is an end-product, meaning, I buy it then I own it in perpetuity. I still have my copy of XP from the Paleozoic era but it's still mine and if I choose, I could spin it up. I can only think of two instances where I'd agree S[is]aS; signing up for a full class, and buying tickets. I thought both of these were clever ideas but I'd still be hard pressed to agree to pay anybody else for this "service."

That said, hat's off to those of you who make this work.