Yeah, the requirements should also be clear - or at least clear before any sort of implementation starts. Defining the requirements is a large part of what our consultants do and the more experienced ones know how to ask questions to get perspectives of people other than the "stars". Takes months usually to get things to where us developers can get started on anything. We've built some hella cool shit for some customers but then you look at the git history and realize that it took the customer over a YEAR to go live. They must've easily invested six figures getting this ERP just right for their needs. Automatic imports from other software they use, lots of customizations, including some brand new in-erp apps. They're loving it so far. But you don't get this without considering a bunch of people's needs.
boonhet
at this point everyone knows
Yea I reckon most people don't know. Terminally online people know. In your average household, Amazon is prolly considered trustworthy.
Something something when old men plant trees whose shade they knew they won't sit in
Such a simple quote, yet so much wisdom.
It's because you're supposed to customize them, not use as-is. We've had a lot of happy customers. Some send us gifts! But for the first year or maybe even couple of years, you probably pay more to your partner for implementation, customizations and advice than to the ERP developer for licensing.
ERPs aren't for every company, different ERPs work best for different companies and different partners themselves have their own specializations. The one I work through (used to work for, but now I have my own company and just contract for them), does small to medium sized production companies. Think 5-200 employees usually. The ERP we work with is meant to cover every imaginable use case - which is why it doesn't have enough depth. We add a bunch of stuff that isn't there OOTB, sometimes remove things in default modules, etc.
But first you NEED an ERP partner to make the most of it. At ours the CEO is also the biggest salesman. He's not afraid to tell you if he doesn't think it's a good fit. A bad partner will still try to sell you and that's going to end up in disappointment for everyone.
Not for president Musk.
If he's under investigation there, he'll probably never visit Canada again.
It might also surprise you to learn that Dacia is actually a large French conglomerate.
They've been fully owned by Renault for more than two decades.
They might but only if they're building something new for their entire range.
Discord has a single point of registration though.
You can see the same communities from lemmy.world and lemm.ee, more or less. But the average user doesnt know that. They get confused. People are stupid. Sad, I know, but also true.
I'm not Canadian even, just a car enthusiast :)
The automotive industry in Canada would take a large hit I reckon.
But given that a lot of these are US companies working in Canada, maybe that's for the better. I'm not Canadian so my opinion is irrelevant anyway. Likely some people will lose their jobs and that sucks.
Odoo actually. You more or less can't use all the features, there's too many. That doesn't mean it's the best ERP, it just tries to be a true generalist, which means it needs lots of customizations usually.