Not sure what you are asking excatly.
A library like next-intl does wht you describe. Just the other way around, e.g: /locale/slug
That's the setup it requires to do other localization taks like rewriting slugs, language switching, middleware, alternate href headers and so on

We are using next-intl for that but the issue we have right now is that the client wants that [company] before the locale as that part will be dynamic. I’m not sure if it will be possible to create a static param that represents the slug. I was wondering if there is a way to put the slug before the localization

only via rewrites imo. You'd have to keep next-intl structure, so

[locale]
  [company]

Disable Locale Prefixes all together

export default createMiddleware({
  // ... other config
 
  localePrefix: 'never'
});

And rewrite the paths in the middlware
But i dont know that sounds stupid writing it

Is there a way to inject the slug to the locale ? Instead of having it like what you explain above something like [company/locale]