Three years at a partner doesn't always mean three years of growth
Sometimes it's year one, three times over.
I see it a lot with D365 consultants, and it's usually not their fault.
The obvious pushback: no two rollouts are the same. True. Every client has its own config, its own integrations, something you haven't hit before. A tenth Finance build will still teach you things the first nine didn't.
But that makes you broader, not more senior.
What's usually missing is the level above: solution design, architecture, running the build yourself instead of delivering someone else's design. A lot of people never get handed that step.
It's rarely a deliberate plan. You're good at Finance delivery, so that's the work that keeps coming your way. Whether that's the partner protecting delivery or just nobody thinking about your progression, the effect on you is the same.
I'm not saying walk out the door.
If the work genuinely gets harder each time, more ownership, a bigger say in how it's built, then stay. You're getting somewhere.
But if it's the same job with a different client's name on it, that's worth noticing, because nobody at the partner is going to point it out for you.
Two years from now, will you be more senior? Or just more experienced at the same thing?
I work with Microsoft Partners, ISVs and end users across the US, helping them build permanent and freelance teams across the Dynamics 365 ecosystem.
If you'd like to compare notes on the market or discuss your hiring plans, I'd be delighted to connect.
