HN user

raxits

3 karma
Posts0
Comments12
View on HN
No posts found.

Same here but I have seen people are/were using evernote, Microsoft one note etc for

1. Note sync across devices 2. Easy search 3. As to-do list, read/use it in future 4. Capture audio/video/images from mobile 5. Store visiting card etc

Depends on -

1. Your skills - Why? - How much you need to spend on Human resource? to reach PMF

2. Real dependancy on you of your family - Is your wife working/side passive income etc so you can ditch your job

3. Your Startup/Product Idea & how much time will it take to reach MVP and ramen profitable -

4. Your family's willingness to *sacrifice social pressure*. - Scarifying lifestyle/current standard of living is hard, more harder is to get rid of "What other people/social circle of your family will tell/think" of the new lifestyle,

5. Opportunity cost of doing job (or leaving job).

Most of people have hesitation of leaving job, so exact decision you only need to take (or not take).

Advice - Don't regret on whatever decision you take.

Let's say if you stick to job and same idea/product someone else become big big, No need to regret and vice versa.

Context about me 1. I left Software job after 7Yrs and bootstrapping since 10+ yr. Ups and Downs are part of life. COVID has made life bit worsen (as we are in daily commute!) 2. I am 35+ yo single, My parents don't depends on me, No-Unwanted-expense, from India

I am not cloud provider but in Subscriptions based carpooling. And similar situations we were in.

Point is if existing happy early customers - no point in hiking price due to mistake at our side (Be It our, or our tech vendor or tech integration partner!) provided you are making money and ramen profitable from those early users. :)

So basically this is Subscription/Recurring Invoice based on usage/metered billing. SaaS/Hosting provider/Electricity provider etc

Try/Check Zoho Subscriptions (I am happy customer of "Zoho Subscriptions") - They support Many features, metered billing, Payment Methods, Many Integrations etc. Without taking much data (except what is needed minimal). And very good tech as well as non-tech customer support! And they charge reasonably fixed, transparent and predictive price.

I understand need and pain point and multiple players can exist, Key is to have transparent pricing. (You can always have custom plan/discount/ change in pricing in future etc for future customer).

Also who is your target customer? Tech company may likely implement their own billing software or use existing proven players.

I think (Happy to be wrong!) - 1. Trying to find Non-Core-Tech/Offline subscriptions service and what are their pain points? 2. Why only usage based billing?

I know there are very less tools/software for SaaS/recurring/Subscriptions based billing (Zoho, Chargebee, Recurly, Shopify few of them) so wish you good luck.

Similar experience so my advices are mix of Tech & Non-tech

1. Stop cribbing 2. Start using version control/git, Build Test/UAT environment 3. Upskill your team - As you mentioned your current team MUST have also inherited the code from someone else 4. Try tools like dead/junk code finder, lint etc 5. Try other refactoring tools and techniques 6. Most imp: Try to gain trust and Read 1.

A) Is current system stable [Understand it is messy!]? If it is stable there are ways and means to build/design/architech parallel future roadmap without adding more mess.

Congratulation on the launch

Check similar product for more complex use case (like Menu/Tree level authorization, Web/Non-web based/Terminal/Daemon based app, LDAP/SSO/Hardware token based authentication etc.) https://arxsuite.com/

PS: I was part of Arx product suite for 5 yrs (before rebranding) :)

1. Demo is targeted towards developer & target market is B2B/Enterprise 2. Usually developer does not have purchasing power/influence + We can build it too attitude.

Happy to help

Raxit Sheth

0. Try to find what & why exactly is being built

1. Try to find out which framework, architecture, design patterns used - get hold of that

2. Library dependancy 3. Database structure

4. Pick up your favourite editor (be it vim or emacs or vs code or any) in which you have mastery

5. Search for various entry points like routes, or start activity or main function etc & try step thru code (with possible debug tools open)