Installed-base aftermarket
Prioritize which existing customers are due for service, parts or upgrades.
High priorityA PERSONAL POINT OF VIEW FOR GED · NORFIELD RETHCEIF
Unlock aftermarket and cross-sell revenue across GED, Norfield and Rethceif. Connect customer intelligence to IFS with Microsoft Dynamics 365 and AI — and prove the opportunity in 90 days.
01 / THE COMMERCIAL THESIS
GED has spent years building an installed base of industrial automation customers. Every one of those accounts represents aftermarket service, parts, upgrades and cross-sell potential — but most of it is invisible to the sales team because it lives in IFS, not in a CRM that sellers actually use.
The opportunity is not replacing IFS. It is adding a revenue intelligence layer — Dynamics 365 Sales, Dataverse and Copilot Studio — that surfaces the installed base, scores it for cross-sell and aftermarket propensity, and gives sellers a prioritized, AI-assisted list of accounts to act on this week.
Integrate, don't replace. IFS runs the business. D365 + Copilot grows it.
02 / WHAT WE KNOW VS. WHAT WE WOULD TEST
Every claim in this proposal is labeled. We separate what is verifiable from what we would validate during the pilot.
GED operates in industrial automation. IFS is a recognized ERP platform used by industrial and manufacturing companies. Microsoft Dynamics 365, Dataverse and Copilot Studio are commercially available Microsoft products.
Jason Wickman brings 25+ years in CRM consulting and Microsoft field experience, including 12 years at Microsoft, and has built a Microsoft account intelligence platform for cross-sell and aftermarket discovery.
GED's installed base contains significant untapped aftermarket and cross-sell revenue that CRM and AI can quantify, prioritize and activate through seller workflows.
D365 + Dataverse + Copilot Studio can integrate with IFS to surface installed-base data without replacing the ERP, delivering revenue impact in weeks rather than the quarters an ERP migration would require.
Verified facts are based on public information and Jason's documented background. Working hypotheses would be validated during discovery and the 30-60-90 pilot. No confidential GED data is referenced in this proposal.
03 / 15 INDUSTRY CRM USE CASES, PRIORITIZED
A prioritized CRM and AI use-case library for industrial automation — each one configured to GED's IFS environment, installed base and sales motion. Priority reflects estimated value, feasibility and time-to-impact.
Prioritize which existing customers are due for service, parts or upgrades.
High priorityScore accounts for adjacent product fit using CRM + ERP data.
High priorityUnified view of account health, pipeline and service history.
High priorityAI model flagging at-risk accounts before renewal.
High priorityAutomate service case routing and parts ordering from CRM.
High priorityCopilot-assisted quoting from IFS product data in D365.
Medium priorityAI-suggested account prioritization for sales reps.
Medium priorityAutomated capture, scoring and routing of inbound leads.
Medium priorityUnified customer record across sales, service and ERP.
Medium priorityConversational AI for reps to query accounts and IFS data.
Medium priorityPredict aftermarket revenue from installed-base age and mix.
Medium priorityAutomated renewal reminders and opportunity creation.
Medium priorityAI-assisted scheduling for service and aftermarket visits.
FoundationalSurface parts demand from CRM service cases to IFS.
FoundationalAutomated weekly scorecard: pipeline, aftermarket, attach.
FoundationalPriority assignments are Agilidy's proposed starting point based on industrial automation patterns. Actual priority would be validated against GED's commercial data, IFS configuration and sales process during discovery.
04 / THE ARCHITECTURE
Three layers. The ERP runs the business. The CRM and data layer unifies the customer view. The AI layer makes sellers faster and smarter. No rip-and-replace.
Conversational AI for sales, service and aftermarket.
Unified CRM and customer data platform.
Stays in place. Integrated, not replaced.
Architecture is a proposed pattern. IFS integration depth, Dataverse schema and Copilot Studio scope are defined during discovery. No GED system architecture is assumed or referenced.
05 / A HYPOTHETICAL INTERACTIVE EXAMPLE
Adjust the sliders to see how account intelligence could prioritize the installed base for aftermarket, cross-sell or churn prevention. This is a hypothetical illustration — not a GED forecast.
AI prioritizes which installed-base accounts are most likely to buy service, parts or upgrades.
Hypothetical illustration. Active rate × AI uplift % × average deal size. Uplift percentages (aftermarket 18%, cross-sell 12%, churn 8%) are illustrative assumptions, not GED-specific or industry-benchmarked. Actual results depend on installed-base quality, data completeness, IFS integration depth and sales execution.
EXAMPLE / CUSTOMER 360 + COPILOT SALES AGENT
Jackie Morrison is a senior account executive at Norfield. Her Teams Copilot agent watches her accounts 24/7 — proactively alerting her to opportunities, drafting personalized outreach, and tracking follow-through so nothing slips. See the full Customer 360 experience for Great Lakes Windows & Doors: $8.4M revenue, 42% share of wallet, $11.6M whitespace, GED/Norfield/Rethceif opportunity propensity, a 30-60-90 day account plan, and the Copilot agent in action.
Where Great Lakes spends across Norfield, GED, Rethceif and other suppliers
Estimated untapped annual revenue from products this account does not yet buy direct
estimated annual whitespace
AI-predicted likelihood of engagement within 90 days, by brand
The Copilot agent watches account signals 24/7 — alerting Jackie to opportunities, drafting personalized outreach, and tracking follow-through so nothing slips.
This mockup illustrates the kind of account intelligence and AI-agent experience a D365 + Dataverse + Copilot Studio layer could deliver on top of an existing ERP. Account name, revenue, share-of-wallet, whitespace, propensity scores, Copilot alerts, drafted emails and accountability tasks are entirely hypothetical. No real customer, GED, Norfield, Rethceif or MSouth data is used or implied.
06 / THE 30-60-90 PILOT
Deliverables: commercial baseline + prioritized use-case backlog + D365/Dataverse foundation + IFS integration plan. Gate: agree the pilot scope and success measures.
Installed-base coverage · AI-prioritized accounts acted on · Aftermarket attach rate · Cross-sell pipeline · CRM adoption · Copilot assistant usage · Pipeline movement vs. baseline
Proposed delivery scope. Revenue targets are agreed after baseline discovery. Pilot results are reported as verified outcomes, separate from projected impact.07 / WHY JASON
I'm Jason Wickman, founder of Agilidy. I bring 25+ years at the intersection of customer strategy, revenue and Microsoft technology, including 12 years at Microsoft and experience building a CRM business that was acquired.
I have built a Microsoft account intelligence platform to support account research, cross-sell discovery and targeted engagement. For GED, I would apply that asset to the installed base, configure the 15-use-case library against IFS, and personally lead the pilot alongside the sales and service teams.
I work with a handful of clients, personally leading the work. The engagement can expand or transition to a permanent hire with a documented handoff.
More about Jason08 / THE PROPOSED FRACTIONAL ENGAGEMENT
An initial 90-day pilot to stand up the D365 + Dataverse + Copilot Studio foundation on IFS, deliver the first five AI use cases, and prove aftermarket and cross-sell impact against a measured baseline.
Commercial terms and capacity agreed after discovery. Fractional or contract-to-hire structure available by mutual agreement. This is a draft proposal; no engagement has been agreed.
CRM + AI strategy, use-case prioritization, D365/Dataverse/Copilot Studio configuration, IFS integration design, account intelligence, cross-sell and aftermarket play design, pilot delivery, executive reporting and handoff.
GED sales and service leaders own their teams; IT owns IFS and infrastructure; product owns the roadmap. Microsoft partner and specialist resources are scoped where needed.