nathanganser

Tournament username: vocal.email
Karma: 84
Recent posts
Recent comments
nathanganser · 127d ago

A few things to consider might be:
- have you messed up some things legally in the past few years? Maybe you didn't submit all the tax documents or so. In which case, you might want to "start fresh" since you now have a product to sell. You'll still be liable for those things with your previous company but at least it won't mix up with your new growing business.

- Has your branding changed? Maybe your product name has changed? In this case, why not create a new company with a name closer to your current product.

nathanganser · 127d ago

Not sure you can do this. It seems to auto delete after a while :)

nathanganser · 152d ago

Very simple :) Their docs are great!! Might want to look at Stripe Checkout if you're willing to sacrifice your own UI for easier usage

nathanganser · 332d ago

Making it to 500$ in MRR :)

nathanganser · 387d ago

Monolithic vs micro-services architecture
From my experience, a big repository is still much simpler and practical than a big bundle of repositories with small apps inside. It also makes it much harder to get a good overview of the whole system when you have many services. Odds are you would not even realise someone hacked into one of your servers.

Do not offer username/password login options
You have to look at it more from a systemic point of view, statistically, there are more username/password auth that are poorly implemented than passwordless implementations. Of course if you're a great and smart developer, you can build an old-school password auth and everything will be fine. But on average, companies with password auth are less secure.
I'm always looking at security from a systemic point of view, not looking at any individual implementations.

Security is an ongoing concern, you're never done with security.

nathanganser · 527d ago

What do you think is the AHA moment for our product ? (Nat.app - personal CRM)

We just launched our V2 - it's of course clunky, but is it just good enough?

nathanganser · 713d ago

Hey! Nice work but I'm curious about the initial vision, are you sure that replying to 30 tickets in 30 seconds is actually an improvement of the customer experience? I'm wondering if a certain level of "good" friction isn't needed?

Maybe this can help: when I was working for a bigger company, the header was usually meaningless "Support request #3w34", so you had to check out the actual message, you might need to add the message to the view as well.

nathanganser · 724d ago

Cool stuff! Focusing on counting the number of customers complaining about a certain issue is great. This was really missing with other tools.

Being able to generate clear reports for the product team with all the user-complains will be very useful as well!

nathanganser · 725d ago

Nice work on the designs! The app seems quite complex already, what would you say is the key USP? What's the one thing that will differentiate you from Zendesk?