Get the answer before you buy the platform.

Strategy & Advisory is paid advisory work that produces a structured assessment of your HCM environment and the strategic decisions ahead of you, delivered as a gap-analysis deck your team can use internally or share with implementation partners. Unlike operational pillars (Implementation, Optimization, Managed Services, Integration) which execute specific work, Strategy & Advisory analyzes where you are, identifies gaps between current state and where you need to be, and produces clear recommendations with effort estimates and decision criteria.

The work typically covers HCM platform fit assessment, organizational readiness for change, integration architecture analysis, and operational gaps that affect strategic options. The output isn't a generic best-practices document. It's specific to your environment: your platforms, your industry, your team's capabilities, your current pain points, and the decisions you're actively facing.

The deliverable is yours once the engagement completes. RJR doesn't tie advisory work to downstream implementation commitments. Some clients use the deck to inform vendor selection conversations, some take it to their board for funding, and some use it to scope internal work. The flexibility matters because strategic decisions about HCM platforms typically involve stakeholders, timelines, and considerations that extend beyond what any single implementation partner can address.

Strategy & Advisory makes sense when you have decisions to make before execution work begins. Common signals: you're evaluating HCM platforms but haven't committed; you have an HCM platform but aren't sure whether to optimize it, replace it, or restructure how you use it; you're integrating M&A acquisitions and need to decide on platform consolidation strategy; or you have internal disagreement about strategic direction that needs an external assessment to break the tie.

Going straight to Implementation makes sense when the strategic decisions are already made. You've selected your platform, you have executive alignment on scope, and you're ready to execute. Adding Strategy & Advisory in front of a clear implementation just adds time and cost without changing the outcome.

Going straight to Optimization makes sense when you have a platform running, you know what's broken or underperforming, and you need execution work rather than analysis. The exception is when "what's broken" isn't clear and the team is stuck in workarounds without diagnostic visibility. In those cases, Strategy & Advisory can produce an honest assessment that turns vague pain into a prioritized fix list.

The honest signal: if you can articulate what you need done in operational terms, you probably don't need Strategy & Advisory. If you can articulate the symptoms but not the strategy, that's the engagement.

The gap-analysis deck is structured to support specific decisions rather than generic education. The standard sections include: current state assessment (what platforms, integrations, processes, and operational patterns exist today), gap analysis (specific gaps between current state and what your strategic objectives require), recommendations organized by priority (typically high-impact-near-term, strategic-medium-term, and infrastructure-long-term), effort estimates for each recommendation, and decision criteria your team can use when evaluating options.

Specific examples of what shows up: which platform modules you're paying for but not using, which integrations are creating operational debt that won't scale, which manual workarounds reflect underlying configuration problems vs. which reflect genuine business policy gaps, where your reporting capabilities fall short of what your team actually needs, and how your current operational structure constrains or enables specific strategic options.

The deck is built to be presentation-ready for executive audiences. Clients use it for board funding discussions, vendor selection conversations, internal alignment sessions, and budget planning. The format anticipates that the audience won't have RJR available to interpret it — every recommendation includes enough context that someone reading the deck cold can understand what's being recommended and why.

The most common decisions Strategy & Advisory engagements inform fall into four categories. First, platform-level decisions: should we stay on UKG, migrate to ADP, evaluate Workday, or run multi-platform? When should the migration happen? What's the realistic effort and disruption? Second, scope-level decisions: which modules should we deploy or expand? What's the priority order when we can't do everything at once? Where does the highest-leverage work actually live?

Third, operational decisions: should we hire internally, engage Managed Services, or some combination? How do we structure the HR/IT/payroll team to support the platform we're operating? What gaps in current capability need to be addressed before the next strategic phase? Fourth, integration decisions: which adjacent systems should we connect? What's the right architecture for the integration landscape we're growing into? Where does iPaaS make sense vs. native vs. custom?

Less commonly but importantly: M&A integration strategy (how do we merge HCM environments from acquired entities?), divestiture planning (how do we cleanly separate HCM operations when business units split off?), and major regulatory shifts (how do we restructure to handle changing compliance requirements at scale). These engagements tend to be larger and more complex when they happen, but the framework is similar — assess current state, identify gaps, produce decision-quality recommendations.

Vendor pre-sales discovery and Strategy & Advisory both produce assessments, but they're built for different purposes. A vendor's pre-sales discovery exists to support a specific outcome: helping you commit to that vendor's platform. The discovery is genuinely useful, often free or low-cost, and the people running it are knowledgeable. But the deliverable is shaped by the vendor's product portfolio, and the recommendations naturally lean toward what that vendor can deliver.

Strategy & Advisory is a paid engagement where the deliverable is yours, structured to support your decisions rather than a specific vendor outcome. The recommendations might point toward expanding your current platform, switching platforms, running multi-platform, doing nothing for 12 months while you fix data quality, or something else entirely. The output isn't constrained by what RJR sells, because clients are free to take the deck and implement with anyone they choose.

The honest framing on RJR's positioning: when a client engages through their existing UKG or ADP relationship, the assessment works within that platform context rather than recommending a switch. That's not advisory bias; it's recognizing that platform decisions involve more than what an external assessment can fairly recalibrate mid-engagement. If you want a platform-agnostic evaluation that may recommend switching, that's a different scope worth scoping at the outset rather than expecting it to emerge from a partner-introduced engagement.

The right participants depend on the scope, but Strategy & Advisory engagements consistently benefit from involving three groups. First, executive sponsors who own the strategic decisions: typically CHRO, CFO, COO, or CIO depending on whether the focus is HR, finance integration, operations, or technology architecture. Without an executive sponsor, recommendations land in a void where nobody has authority to act on them.

Second, operational owners who understand current state in detail: HR operations leaders, payroll managers, HRIS analysts, integration architects. These participants surface the operational reality that high-level strategy discussions often miss — the workarounds in place, the integration debt that's been accepted, the reporting capabilities people quietly route around. The deliverable's quality depends on this layer being honestly represented.

Third, IT or systems leadership when the scope touches integration architecture, security posture, or multi-system coordination. Even when Strategy & Advisory focuses primarily on HCM platforms, the recommendations almost always have IT implications worth surfacing during the engagement rather than after.

Practical note: RJR's preference is for working sessions that bring these groups together rather than separate interviews. Cross-functional conversation tends to surface gaps and dependencies that individual interviews miss. Most engagements involve three to five working sessions across two to four weeks, with focused interviews supplementing where needed.

Most Strategy & Advisory engagements run four to eight weeks from kickoff to deck delivery, with the specific timeline driven by scope rather than by RJR's process. A focused engagement (single platform, defined decision, executive-level questions) can run three to four weeks. A broader engagement (multi-platform environment, organizational restructuring, M&A integration analysis) typically runs six to eight weeks. Engagements longer than eight weeks usually indicate either expanded scope mid-engagement or insufficient internal access to operational owners during the working sessions.

The structure across that timeline is consistent. The first week or two focuses on current-state assessment: working sessions with operational owners, document review, system access where appropriate, and stakeholder interviews. The middle weeks focus on gap analysis and recommendation development, with periodic check-ins to validate findings rather than waiting until final delivery to surface them. The final week is deck refinement and presentation, including a structured executive readout that walks through findings and recommendations in real time.

The bounded nature is intentional. Strategy & Advisory engagements that drift into ongoing advisory work tend to lose the decision-quality focus that makes the deliverable useful. When clients want continued advisory support after the deck delivers, that's a separate engagement scoped explicitly rather than scope creep on the original.

Success in a Strategy & Advisory engagement looks like the client making better decisions than they would have made without the engagement. That's the primary measure, and it's intentionally outcome-focused rather than deliverable-focused.

Concrete signals that the engagement worked: the executive sponsor can articulate the strategic decisions ahead and why specific options were prioritized; the operational team has clarity on near-term gaps that need addressing regardless of which strategic path is chosen; the IT and systems stakeholders understand integration and architecture implications of the recommended direction; and the deck is being used in active decision conversations rather than sitting in a shared drive.

What success specifically does not look like: agreement on every recommendation. Strategy & Advisory engagements often surface findings that internal stakeholders disagree with, and that disagreement is often productive. The deliverable is meant to inform discussion, not to substitute for it. Clients who push back on specific recommendations, ask hard questions, or take the deck in a different direction than RJR proposed are using the engagement well.

The longer-term signal is that downstream work, whether implementation, optimization, vendor selection, or operational restructuring, runs more cleanly because strategic alignment was achieved upfront. RJR doesn't track this metric formally, but the engagements that produce the strongest follow-on work consistently start with Strategy & Advisory engagements that pushed back hard on initial assumptions.