yes, you can. why not?

Maybe a 1 year subscription? How much traffic do you have?

Consider reading more about OKRs: en.wikipedia.org/wiki/OKR it's a good way to set realistic goals when you run a business.

Hey Sarup, there is one story that may be interesting to you:
www.indiehackers.com/intervie…
amplifr.com/

It looks like their situation was similar to yours.
TL;DR they looked at what features were used the most and removed everything else. Only then scaled it.

Hey Shabrina. Maybe that helps:

blog.ycombinator.com/getting-…
www.upbeatpr.com/
500.co/pr-for-startups-the-ar…

Have never tried it myself (yet), but it looks like there are solid SaaS solutions which help you with lean PR services.

I would consider another pattern, Swizec. There is one, which is actively used by D3.js. Basically you create an object and then each instance method returns that object back. This way you can create a neat chain of settings without any ugly config objects or time consuming DSL. Example: instance = new Instance(); instance.setMemory(300).setStorage(1000).setMemoryAlertThreshold(0.8).start(). There is no context of what you work on, but hope it helps.

What tool are you using? Probably a way to go could be using Segment.io. By using Segment or (Analytics.js) you won't depend on a specific tool. Anyway, you could treat every new signup as a trial user unless proved the opposite. So you call new user a lead. Then you register a purchase event when it happens. Purchased/Leads would be the conversion you are looking for. Heap, Mixpanel allow you to do so.

Look into these options:
osome.com/
stripe.com/atlas
www.clerky.com/
www.earthclassmail.com/

You can implement any service you want fully on serverless unless you need to use Websocket (then you'd need to combine serverless API with a traditional server). To avoid race conditions you can look into transaction locking (ex: in Postgres): stackoverflow.com/questions/4… or you can set flags with a Redis caching layer. The reason why you should always close your DB connections is that functions create a new connection on each invocation. Considering that it's infinitely scalable, we get a bottleneck at the DB level. So your database solution should be ready to handle thousands of connections at the same time.

I've tried many. Heap analytics is the most convenient for me. No need to track events manually. Good stuff.