LinkedIn marketing for Dynamics 365 partners
Microsoft is winding Dynamics GP down, and Business Central ships two major releases a year. We interview the consultants handling both and publish their thinking on LinkedIn for finance and IT leaders in the UK and US.

“I just wanted to share that I’ve been really impressed with the work Alex is producing for several of our UK partners. The approach around multi-touch, multi-channel campaigns and the focus on more targeted, high-quality content is clearly delivering strong results.”

Results from our last three ERP success stories
Organic LinkedIn activity only, measured in LinkedIn Page Analytics.
For partners selling Business Central, Finance and Supply Chain
Microsoft partners earn from implementations, GP migrations, apps that extend Dynamics 365 and consultants placed on projects. Each of those businesses needs its own story on LinkedIn.
Finance directors still on GP; IT managers; Operations directors; Wholesale distribution; Professional services; Assembly and manufacturing
Business Central services partners
Implementations for small and mid-sized firms, GP migrations and the twice-yearly update cycle.
Finance and Supply Chain partners
Dynamics 365 Finance and Supply Chain Management programmes for organisations beyond the SMB bracket.
ISVs
Apps that extend Business Central or Finance and Operations, sold through Microsoft’s marketplace.
Dynamics staffing firms
Placing Business Central and Finance consultants on implementation and support projects.

Why Dynamics 365 partners lose momentum on LinkedIn
Three problems we keep finding, each one from a real client engagement.
Posting happens when someone has time
No cadence, no content plan and no quality control.
Every channel tells a different story
LinkedIn, sales collateral and event materials say slightly different things, so your delivery strength never comes through.
Technical buyers tune out marketing
IT directors and senior decision-makers are wary of anything that reads like a sales pitch.
Your Dynamics 365 LinkedIn, run by one team
One team plans, writes, designs, publishes and reports, so your consultants stay on delivery.
Pillars built on your Dynamics services
GP migrations, Business Central go-lives, release wave readiness and the apps or support plans you sell.
Writing from consultant interviews
We interview your consultants and write the posts. Nobody on your team has to draft anything.
Design: carousels and visuals
Carousels and graphics designed to a professional standard, with optional video where it adds value.
Publishing and reporting
Scheduling, a monthly report and a quarterly review of what to change.

Recent work for ERP consultancies
Each sample shows who it was for and what it was for.

Case study carousel

Thought leadership post

LinkedIn article banner

Consultant profile
Our latest win for an ERP consultancy
Structured marketing programme for a specialist IFS implementation partner
Strong delivery and IFS expertise weren’t reflected in the firm’s marketing. LinkedIn, sales collateral and event materials told slightly different stories, and there was no publishing schedule, approval process or reporting.
Four Dynamics 365 posts worth drafting first
These are proposals. GP migration stories suit a Business Central practice; a Finance and Supply Chain team would swap them for its own programmes.
What moving from GP to Business Central involves
Microsoft has published end dates for GP support. Your consultants explain data, customisations and timing for finance teams still on GP.
Getting ready for each Business Central release wave
Major updates land every April and October with a five-month update window. Show customers how you test extensions before it closes.
Where Copilot in Business Central saves time
A consultant walks through bank reconciliation or sales line suggestions with Copilot, and shows where human review still matters.
Business Central or Finance and Supply Chain?
A plain comparison of when a growing company stays on Business Central and when Finance and Supply Chain Management fits better.
Your first 90 days
Your consultant signs off every technical claim before anything goes live.
Kickoff and consultant interviews
We learn your services, your buyers and the projects worth talking about.
Content pillars and the first month’s calendar
You approve the plan before anything is written.
Writing and technical sign-off
Your nominated consultant checks the technical claims in every post.
Publishing at the agreed cadence
Set by your scope. One ERP consultancy we work with posts twice a week.
Monthly report and quarterly review
What moved, what to change and next quarter’s topics.

Ascension vs the alternatives
Pick the option you’re weighing up and see the difference side by side.
What our ERP clients say
"Alex has been instrumental in supporting our social media campaigns and marketing materials. He is great to work with and is always looking for new ways to develop content and ideas, with a clear drive to make sure our marketing and brand stand out."
“Substantial traffic increase across all media platforms and increased leads.”
“Pleasure to work with. Responds promptly, and always happy to listen to the team for our feedback to get the required finished article.”
“Agile and smart thinking to quickly achieve outstanding outcomes and tangible results.”
Three ways to run LinkedIn with us
A monthly retainer, scoped to the services you need. Commitment is agreed at scoping.
Strategy & Direction
A LinkedIn plan and templates. Your team does the posting.
Done With You
We create the content with your team’s input.
Your Dynamics 365 questions, before the first call
Answered honestly, before your first call.
Yes, by treating Microsoft’s timeline as planning information rather than a countdown. Microsoft has published separate end dates for GP product support and, later, for security patches, and a post quotes them only after your consultant confirms they still stand. A finance director still on GP needs to know what that means for their year-end, their integrations and their budget cycle, not to be told the sky is falling. Posts can set out the options your consultants actually recommend, such as a phased move to Business Central or a check on whether Finance and Supply Chain Management fits better, and the order of work that makes sense. A nominated consultant checks every date and migration claim before scheduling, so nothing overstates urgency, quotes a timeline you would not commit to in a proposal or contradicts what your account managers are telling customers. Useful formats include a carousel explaining the published dates and what each means in practice, a consultant’s short video on which historical data can stay behind, and an approved story from a customer who has already moved. Each points to a next step that matches your offer, such as an assessment.
Each April and October release can change screens, features and Copilot capabilities, and tenants then have a five-month window to take the update before it is enforced. That rhythm is useful content in itself: customers want to know what is coming, what to test and whether their extensions will survive. We plan release posts after your team has tried the update in a sandbox, interview whoever did the testing and write up what customers should switch on, what can wait and what to check in their own extensions. The draft goes back to that consultant for approval, so feature names and screenshots match what customers will see. If a capability is still in preview or limited to some regions, the post says so plainly. The preview period opens a month before each major version, in March and September, which gives your team time to explore what is coming. A post written then positions you as the partner who looks ahead rather than reacts. Partners who manage many tenants can explain how they schedule updates across a customer base without disrupting month end.
It can, with separate pillars and different interviewees. App content speaks to the business problem the app solves, the people who use it every day and how it fits inside Business Central or Finance and Operations. Services content speaks to implementation, support and your team’s judgement. Mixing them in one post confuses both readers and can make the app look like a route into consultancy, or the reverse. We interview your product owner about use cases and customer feedback, and your delivery lead about projects, then give each a regular slot in the calendar. Marketplace listings and programme benefits are confirmed with you before we mention them, and integration claims are approved by the person who knows the code. Where your app holds certified status through Microsoft’s ISV programmes, we use the exact wording you are entitled to, never more. Demonstration content works well here: a short, captioned screen recording of a common task often explains an app faster than any description. Industry apps for wholesale distribution or professional services, where Microsoft says Business Central is mainly used, are natural subjects.
Both, where your scope covers leadership profiles, because they do different jobs. A practice lead’s profile suits opinion and lessons learned: why a distributor stayed on Business Central rather than moving to Finance and Supply Chain, what went wrong on a GP data migration and how the team fixed it, or what a release wave changes for finance teams. The company page suits release news, events, hiring and approved customer stories, and gives buyers somewhere to check you are substantial. We write in each person’s voice from interviews, so profile posts do not read like rebadged company announcements. Each extra profile adds to the price, so we agree with you which ones are worth it. Staffing firms are a special case: consultants’ profiles can show depth of Business Central or Finance experience, while the company page focuses on the projects and roles you fill, without naming end clients who have not agreed. Practice leads who speak at user groups or Microsoft events can repurpose their talks into short posts.
LinkedIn Ads are optional and sit on their own budget. They can help if you want a GP migration guide or a Business Central webinar in front of finance leaders at a defined list of companies, since organic reach alone will not guarantee those people see it. Ad spend is outside the retainer, and so is outbound messaging. If you want direct outreach to named GP customers or prospects, the Outbound LinkedIn ICP Campaign handles that as a separate engagement, so organic content, paid promotion and outreach can support each other while each is scoped on its own terms. When paid and organic run together, we keep the messaging aligned, so a finance director who sees an ad and then visits your page finds the same argument made in more depth. Registrations and downloads from paid campaigns should go straight to your sales team for follow-up rather than sitting in a spreadsheet.
Yes, as long as each post ties back to a business result rather than the tooling. Microsoft’s Business Applications designation covers Dynamics 365 and Power Platform together, so buyers already expect partners to work across both. The strongest posts pick one process, such as approvals that used to travel by email or a report finance rebuilt every week, and show how an app or automation removed the manual step. Your maker or solution architect explains it in an interview; we write it for an operations or finance reader and design a simple before-and-after visual. Licensing, connectors and data access are easy to describe loosely, so your nominated consultant confirms those details before anything is published. Power Platform then becomes a supporting pillar next to Business Central rather than a separate brand.
Further reading for Microsoft partners

How to market ERP software without sounding like every other consultancy

Why your ERP consultancy isn’t getting inbound enquiries

LinkedIn content strategy for ERP consultancies with long sales cycles
Plan your GP migration content with us
Bring a rough count of customers still on GP and the Business Central services you sell. We’ll sketch a first month.