I am going to sell saas subscription in the europe, and it is like easiest way to handle all the taxes and legal requirements via merchant of record.
I know there are exists Paddle and Lemon Squeezy.
My question: what should I choose? may be there some other better MoRs exists.
Please share your experience.
So I have saas with 3 tiers of pricing.
I need to understand what flow of transition from trial to paid plan would be less painful and convert more. Here is few variants I see, and if you could, please give your opinion about variant will work the best for saas, or may be you could suggest your own.
It is b2b. I plan to have direct sales, but still there is an option for self sign up.
Variant 1:
User selects pricing plan right after registration and start trial.
We require credit card but not charging until end of trial. And we charge it automatically after trial ends. In this case user has to cancel its subscription to not being charged.
IMHO: At first glance, this seems to be the most brazen and unpleasant method.
Variant 2:
User selects pricing plan, start trial but credit card not required until he decide to buy a subscription. Also user is free to switch between plans during trial, to compare capabilities.
IMHO: More loyal relaxed way to give user a chance to try product and decide what plan fits his needs.
Variant 3:
Right after registration user get trial plan automatically (no credit card required), crafted specifically for trial, so some capabilities are disabled (like custom domain, or white label), but user can try all other features freely, similar to max plan. After trial ends - user has to decide what plan he wants to use. At this point he enters card, and start paid subscription.
IMHO: this is my preferred variant as it feels like customer centric, where we allow to check everything before he makes a decision. No need to think about plans, and customer can focus on solution. One caveat exists if he used more resources than his plan allows - but it is not a problem. system will restrict further resource adding until he remove used resources to match the limits.
What do you think?
So I see the badge
while having active paid subscription. And it is not 7 days, it is 6. For me it looks like a data not synchronized somewhere. OK.
I thought to report the situation to get fixed, to avoid confusion and overpay for no reason.
But when you open Help > Submit Bug Report... - you got redirected to youtrack site, where you can't "continue as guest" it just doesn't work.
So that forcing you to create an account, then submit a ticket.
It always wondered me, why company that have all required information about me and my system still want me to create another new account on another their platform for just doing a small thing.
Jetbrains knows my login, my license, my os, my hardware and all kind of version numbers.
Why is it so hard to provide simple window for adding bug report details and submitting it in place instead of adding me more work to do?
I constantly hear, that people using hive of ai agents to do a software development. Like, running them in parallel and some how combining results into working application.
So my question is - how do you organise your workflow with multiple agents running at the same time, when human has limited attention and decision making energy? if I need to review every output of every agent that delivered some piece of work, how can I be sure that i accept right solution?
What is your flow? Do you bother with review?
When you check person's profile, do you care about articles and comments that person have? Lets imagine person has articles related to his skills, and he describing real problems and how he was soling them.
Is this valuable for you, or you just looking for specific keywords in recent activity (jobs responsibilities)?
Please, post answer only people who hired on linked in.
P.S: HR/Recruiters skip this topic, as it is clear that for your technical articles doesn't show much.
As far as I recall, no one used to set their status to “open for work”. it was probably seen as a sign of weakness in an employee's market. The situation has changed significantly now.
In your opinion, should one set this status, or is it still a sign that a professional is not in demand?
Currently I am integrating react-i18next library to enable different languages in my app ui.
As I understood from the documentation i18next suppose to have all translations inside language files, that are loaded on demand. But IMHO from DX point of view, such organization is not very convenient.
I assumed that it would be much more intuitive to keep translations along with components themselves. For example:
Component /
Component.tsx
Component.module.scss
Component.i18n.json
But as per documentation - such translation file should be loaded separately. having many components such approach would require too many http requests to work. But from DX - i think it is the best. Also having namespace to Component it can be t('title') instead of t('Component.title').
But again, seems to be this is my fantasy, and i18next not supposed work like that.
So the questions:
- is it possible to have described flow in production, compiling scattered i18n.json files into single translation file and use it for i18next?
- if not, what approach do you use now?
- if you would start i18n from scratch on your project, what would you change?
Thanks.