ADP, delivered with multi-platform fluency that spans the full ADP product line.

ADP Lyric is ADP's next-generation flagship HCM platform, architected as a modern cloud-native product with a different configuration model, integration architecture, and reporting approach than Workforce Now. Lyric represents a different operational shape rather than an incremental update — different patterns for how organizations configure pay rules, manage data, run reporting, and integrate with surrounding systems.

The differences matter for evaluation. Workforce Now's configuration depth comes from years of accumulated capability layered onto an established platform. Getting it right requires understanding the platform's specific patterns and behaviors. Lyric's configuration model is built around modern API-first patterns and a more uniform data architecture. Reporting on Lyric works differently than on Workforce Now; integration architecture follows different patterns; the underlying data model is structured differently. For organizations evaluating both, the choice isn't about platform capability so much as operational fit.

ADP is positioning Lyric as the strategic future for mid-market and enterprise HCM, with new deals increasingly landing on Lyric. Workforce Now remains broadly deployed and continues receiving capability investment. Both are viable platforms; both serve different fit profiles. RJR delivers Lyric implementations and advises clients on the operational fit decision when both platforms are on the table, and this advisory work is itself a meaningful part of our Lyric practice.

The decision between Lyric and Workforce Now turns on operational fit factors: organization size and growth trajectory, deployment timeline preferences, configuration model preferences, integration architecture posture, and the specific HCM modules required. Neither platform is universally better; each fits different operational contexts.

Lyric tends to fit organizations that prefer modern cloud-native architecture, API-first integration patterns, and configuration models built around uniform data structures rather than module-specific patterns. Organizations expecting significant growth or anticipating frequent restructuring may benefit from Lyric's data architecture flexibility. Companies with strong internal IT and integration teams comfortable working with modern API patterns often see Lyric's architecture as advantage. Organizations launching greenfield HCM deployments without legacy ADP investments are increasingly defaulting to Lyric.

Workforce Now tends to fit organizations comfortable with the platform's accumulated capability depth, those with existing ADP relationships and integrations they want to preserve, and operations teams who value the platform's mature reporting and configuration patterns. Workforce Now's depth across complex payroll scenarios (multi-state, multi-EIN, certified payroll, prevailing wage) reflects years of accumulated capability that Lyric is still building toward. Mid-market organizations with stable structure and operational patterns frequently find Workforce Now's mature delivery a better fit than transitioning to a newer platform.

The fit decision often surfaces during evaluation conversations rather than from spec sheets. RJR helps clients work through the decision by surfacing specific operational requirements and matching them against platform capability rather than treating the choice as platform-versus-platform comparison.

The Lyric vs Workforce Now decision has real operational consequences and benefits from honest evaluation rather than vendor-driven enthusiasm. Most clients leaning Lyric do so for sensible reasons: ADP positioning Lyric as strategic future, modern architecture appeal, integration patterns aligning with their broader IT stack. The fit question is whether those reasons hold up against the specific operational requirements your organization actually has.

RJR's advisory work on the fit decision works through a structured conversation. We surface the operational requirements your organization actually runs (payroll complexity, integration architecture, reporting needs, internal team capability, deployment timeline). We map those against platform capability honestly: where Lyric's modern architecture genuinely benefits the use case, where Workforce Now's accumulated depth produces better outcomes, where the answer is genuinely either-platform with the difference coming down to internal team preference. The work is shaped by what the requirements actually are, not by which platform we'd prefer to implement.

The honest framing on these conversations: organizations sometimes lean Lyric for reasons that don't survive operational scrutiny (ADP marketing momentum without specific architectural benefit to their case), and sometimes lean Lyric for reasons that hold up clearly (modern integration architecture aligning with broader IT direction, greenfield deployment without legacy considerations). The advisory work surfaces which case yours is. If Lyric is genuinely the right fit, we move forward into Lyric implementation work confidently. If the fit conversation surfaces that Workforce Now would actually serve the operational requirements better, that's an honest outcome worth taking seriously rather than working around.

A Lyric implementation typically runs 4-8 months for organizations of a few hundred to a few thousand employees, with timeline driven by configuration scope, integration complexity, and data migration shape. The phase-gate structure mirrors the broader HCM implementation pattern: discovery and design, configuration, data migration, integration construction, parallel payroll testing, and post-go-live hypercare.

The configuration phase carries different operational substance than Workforce Now implementations. Lyric's configuration model is more uniform across modules, which can reduce cross-module configuration complexity but requires understanding the platform's specific patterns rather than transferring assumptions from Workforce Now experience. Integration architecture works through Lyric's API-first patterns; clients moving from less API-driven environments may need to adjust integration approaches. Reporting requires building against Lyric's data model, which is structured differently than Workforce Now's.

The honest framing on Lyric implementation reference depth: Lyric is a newer platform than Workforce Now, with fewer reference deployments behind any partner including RJR. We bring strong implementation methodology, deep ADP relationship and platform access, and architectural understanding of Lyric's patterns. We're transparent that the cumulative operational pattern library on Lyric is smaller than on Workforce Now, which means we lean harder on first-principles configuration discipline and tighter validation cycles during implementation.

This transparency is positioning, not hedge. Prospects evaluating Lyric want a partner honest about where the platform is in its lifecycle. The advantage of working with a partner closely engaged with Lyric's evolution is being part of building the operational pattern library rather than working from one. The phase-gate methodology, parallel testing discipline, and hypercare structure carry forward from RJR's broader implementation track record. RJR has delivered 100+ HCM implementations across UKG and ADP; that methodology depth transfers to Lyric work directly.

Lyric's integration architecture is built around modern API patterns: REST endpoints with consistent authentication and authorization, webhook subscriptions for event-driven integrations, and a more uniform data model exposed through the API surface. Workforce Now's integration architecture evolved over years and includes multiple integration paths (file-based feeds, direct database integrations on enterprise tiers, vendor-specific connectors). The two platforms expose data differently and integrate differently.

For most integration use cases, the architectural difference matters more than feature parity. Lyric integrations look like modern API integrations: defined endpoints, predictable behavior, event-driven update patterns. Workforce Now integrations often blend approaches: native ADP connectors for common cases, iPaaS platforms (Boomi being the partnership-anchored choice) for cross-system orchestration, custom integrations for cases neither covers cleanly. Migrating an existing integration landscape from Workforce Now to Lyric isn't direct port; it's typically architectural redesign aligned to Lyric's API patterns.

RJR's Lyric integration work covers initial integration architecture during deployment, integration of Lyric with surrounding systems clients already run (ERP, finance, scheduling, benefits, learning), and architecture review when integration scope expands. Our Boomi partnership extends to Lyric integration work where iPaaS makes sense; native Lyric API patterns work for many common cases without iPaaS overhead. The right architecture depends on integration count, complexity, and broader IT direction rather than on platform preference. Most operational debt we encounter on Lyric integrations traces to architecture decisions that didn't anticipate how Lyric's API patterns differ from legacy integration approaches teams may have been used to.

The decision to migrate from Workforce Now to Lyric is the client's, working with ADP on the migration path and timing. RJR's role is helping execute the migration cleanly once the decision is made. The work isn't about whether to migrate; that's an operational fit conversation worth having on its own merits with ADP and RJR's advisory engagement. Once the decision is made, the migration becomes implementation work with specific characteristics worth understanding.

A Workforce Now to Lyric migration is closer to a fresh Lyric implementation than to a typical platform upgrade. The configuration models are structured differently, so existing Workforce Now configuration doesn't directly map; it needs rebuilding within Lyric's patterns. Integration architecture typically needs redesign to align with Lyric's API-first patterns. Reporting needs rebuilding against Lyric's data model. Data migration requires careful mapping between the two platforms' data structures, with parallel-running periods where appropriate to validate the migrated state matches operational reality.

Migration timeline depends on Workforce Now scope, integration count, and whether the migration runs as full cutover or phased approach. Typical mid-market Workforce Now to Lyric migrations run 4-8 months from kickoff to cutover, with phased approaches running longer. RJR's role spans configuration rebuild, integration architecture redesign, data migration, parallel testing, and cutover coordination. Migration timing itself sits with ADP and the client; we work within the timing decisions made and apply our broader implementation methodology to the execution work. The honest framing is that a Lyric migration is significant implementation work, not a button-click upgrade. Clients comfortable with that scope tend to migrate cleanly.

Success in a Lyric engagement at this stage of the platform's maturity is shaped by the lifecycle context. Concrete operational signals are similar to other HCM engagements: payroll cycles run cleanly, configuration changes happen on schedule, integrations stay healthy as upstream systems evolve, reporting produces accurate operational answers, and the platform supports the operational complexity the business actually runs.

The lifecycle-aware piece is what success looks like for both client and platform together. Lyric is still building its mature operational pattern library; clients deploying now are part of that build. Successful engagements include configuration patterns that prove out, integration architecture that holds up under real production conditions, and operational rhythms that can be documented for future Lyric clients to draw from. RJR engagements that produce strong operational outcomes and document them well contribute to Lyric's broader pattern library, which serves both the client (their patterns get refined and validated) and future Lyric clients (more reference material to draw from).

The honest framing on lifecycle context is that prospects evaluating Lyric should expect a partner working through patterns alongside them rather than transferring a fully-mature operational playbook. RJR's role is bringing strong implementation methodology, deep ADP partnership and platform access, and architectural rigor to the configuration work. We're transparent that the cumulative operational reference depth on Lyric is smaller than on Workforce Now, which means we work harder on first-principles configuration discipline rather than leaning on accumulated pattern recognition. That working-discipline is what success looks like in practice at this lifecycle stage.

An ongoing managed-services arrangement on ADP Lyric provides RJR consultants as extension of your internal team for the platform-substantive work that keeps Lyric running well over time. Scope typically includes payroll cycle support, configuration changes as business policies and organizational structure evolve, integration monitoring and remediation, exception handling, and platform expertise on demand for issues internal teams don't have the bandwidth or specialization to address.

The lifecycle-aware framing matters here. Lyric is still building its mature operational pattern library. Managed-services engagements at this stage of the platform's lifecycle work harder on first-principles configuration discipline and tighter monitoring than the accumulated-pattern-recognition mode that older platforms (UKG Pro, ADP Workforce Now) reach. RJR brings strong implementation methodology and deep ADP partnership engagement to managed services on Lyric, transparently working through patterns alongside the client rather than transferring a fully-mature operational playbook.

The engagement structure mirrors the broader managed-services pattern: defined-hours-per-month, dedicated consultant or small team familiar with your environment, quarterly contract cycles with scope review aligned to platform release cycles. Onboarding typically takes 3-4 weeks at this lifecycle point, longer than on more mature platforms because operational pattern documentation runs alongside familiarization. The honest framing is that Managed Services on Lyric at this maturity stage involves working through the patterns we're collectively learning, in a way that produces both reliable operational support for the client and more refined patterns for future Lyric clients. That collaborative posture is what reliable Lyric managed-services delivery looks like in practice today.

ADP Workforce Now is ADP's all-in-one HCM platform serving mid-to-large enterprise organizations from a few hundred employees through 10,000+. It covers core HR, payroll, time and attendance, benefits, talent and learning, and reporting in a single unified product. Workforce Now handles the operational complexity that defines real-world payroll: multi-state, multi-EIN, prevailing wage, certified payroll, multi-union, and the integration architecture connecting payroll to ERP, scheduling, benefits, and downstream finance systems.

The platform's depth comes with operational territory worth understanding. Workforce Now is configuration-rich rather than code-driven. The work of getting it right is in policy interpretation, pay rule construction, and integration mapping rather than custom development. Implementations typically run as defined-scope projects with phase gates. Ongoing operations require platform-substantive expertise that internal teams may not have full bandwidth for.

RJR has delivered Workforce Now across the operational spectrum. Our work covers fresh implementations, tenant stabilization (when prior partner work didn't land cleanly), complex payroll engineering, integration architecture, and ongoing managed services. We've scaled delivery from small-headcount tenants through enterprise deployments running 10,000+ employees in complex payroll and integration landscapes.

An ADP Workforce Now implementation typically runs 4-8 months for organizations of a few hundred to a few thousand employees, with timeline driven primarily by payroll complexity, location count, and integration scope rather than by employee count alone. The work runs as a phase-gate project: discovery and design, configuration, data migration, integration construction, parallel payroll testing, and post-go-live hypercare. Each phase has explicit exit criteria. We don't compress phases past where the data and testing actually support it.

The configuration phase carries most of the operational substance. Workforce Now's policy and pay-rule engine is deep enough to handle multi-state, multi-EIN, multi-union, prevailing wage, and certified payroll scenarios cleanly when the configuration is right. Getting that configuration right is what separates implementations that run smoothly post-go-live from ones that accumulate operational debt.

Parallel payroll testing is the load-bearing verification step. Two clean parallel pay cycles is the floor. Three is more common when payroll complexity warrants additional verification before cutover. After go-live, RJR runs hypercare as a bounded engagement: typically two complete pay periods with measurable exit criteria. Hypercare addresses production issues that surface only when real payroll volume hits the system. From there, clients transition to internal operation, ongoing managed services, or a quarterly optimization cadence depending on internal team capacity and platform complexity. RJR has delivered 100+ HCM implementations across UKG and ADP. The methodology specifics carry across both vendor environments.

Complex payroll on Workforce Now means multi-state, multi-EIN, multi-union, prevailing wage, certified payroll, or some combination — scenarios where standard configuration patterns don't adequately reflect the business policy. Workforce Now handles all of these natively when configuration is built around the actual operational reality, but the work of building that configuration correctly is where most of the complexity lives.

Multi-state and multi-EIN scenarios require careful tax setup, locality-specific deductions, and reporting alignment across jurisdictions. Multi-union environments add layered pay rules, dues calculations, and fund contributions that vary by local agreement. Prevailing wage and certified payroll engagements layer compliance reporting on top: Davis-Bacon, state-level prevailing wage rules, fringe benefit reporting, and certified payroll forms (WH-347 federally; state variants where applicable). Our delivery typically combines payroll specialists who understand the policy domain with platform consultants who execute the configuration.

The honest read on complex payroll is that the platform isn't usually the constraint. The constraint is whether the implementation team understands both the policy and the platform deeply enough to build configuration that survives operational reality. RJR's complex-payroll work spans construction, public sector, healthcare, and multi-entity environments where standard payroll wisdom doesn't directly apply. Most of the operational debt we encounter on inherited tenants traces back to configuration decisions made without that policy depth.

Workforce Now ships with a comprehensive standard report library covering HR, payroll, benefits, and time-and-attendance domains: typically several hundred pre-built reports out of the box. The custom report builder lets administrators construct reports against the platform's data model, with parameter-driven filtering and standard aggregations. For clients needing analytics beyond what reports provide, ADP offers a separate analytics tier and API access for extracting data to external BI tools.

The honest read on reporting is that the platform's capability is genuinely deep, but operational teams rarely access that depth without help. The custom report builder requires understanding of Workforce Now's underlying data model, which varies in non-obvious ways across modules (payroll history, time records, benefits enrollment, talent records). API extraction works well but requires knowing what the API exposes, what it doesn't, and what data shape downstream BI tools expect. Most clients we work with have either built brittle custom reports that break on configuration changes or settled for standard reports that don't quite answer the operational questions they need answered.

RJR helps clients get reporting that actually serves operations. Our work spans custom report development against Workforce Now's data model, BI integration when external warehouse extraction makes sense, and reporting strategy reviews when the question is what to report on rather than how to report on it. The reporting work often surfaces underlying configuration issues: reports that can't be built typically reveal that the data isn't being captured or structured correctly upstream.

Yes, and tenant stabilization is a recurring engagement type for us on Workforce Now. The work usually starts with structured assessment (typically 2-3 weeks) that documents the actual state of configuration, integrations, data quality, and operational readiness. The assessment separates what's salvageable through targeted intervention from what requires more substantive rework.

Most inherited tenants we engage with show similar patterns: configuration gaps masked by manual workarounds, integrations that didn't fully ship or have drifted out of alignment with current systems, and reporting that no longer answers the business questions it's supposed to. The remediation path depends on what the assessment surfaces. Targeted intervention closes specific configuration gaps and stabilizes flow. Scope reset (when the underlying configuration choices don't match how the business actually operates) requires acknowledging what won't work and rebuilding affected components while preserving the rest.

The honest read on stabilization is that the work is rarely glamorous. It's disciplined remediation rather than dramatic intervention, and the outcome is a tenant that operates reliably with operational debt cleared rather than papered over for the next vendor to discover. RJR's stabilization work spans Workforce Now tenants where the original implementation didn't land cleanly and tenants where configuration drifted as the business changed faster than the implementation accounted for. Our ADP partnership depth and stabilization track record give us continuity when inherited tenants need substantive remediation.

Integration scope on Workforce Now typically spans payroll feeds to processors, ERP and finance integrations (NetSuite, SAP, Oracle, Sage, etc.), time and attendance from systems beyond ADP's eTime, benefits administrators, retirement providers, and a long tail of organization-specific applications. Most enterprise Workforce Now environments run 10-20 active integrations across these categories. The architectural decisions about which system is authoritative for which data are the most consequential design choices in the integration landscape.

RJR delivers integration work using native ADP connectors where they exist and serve the use case, iPaaS platforms (Boomi specifically, where our partnership depth lives) when integration scope spans multiple systems with shared logic or when centralized monitoring matters, and custom integrations only when the use case justifies the maintenance commitment. The right choice depends on integration count, complexity, and how the integration fits into the broader architecture rather than on platform preference. Our 5 partnerships (UKG, ADP, Boomi, Paylocity, NCR + Deel) give us delivery depth across the integration tooling landscape Workforce Now most often connects to.

We've built integration architectures for ADP Workforce Now clients running across the operational spectrum, including a global digital identity and payments client running 15+ integrations under managed care. The integration work that holds up over time isn't the most technically clever. It's the architecture that anticipates upstream system changes, surfaces exceptions cleanly, and assigns clear ownership so changes get coordinated when downstream systems shift. Most integration debt we encounter on inherited tenants traces to architecture decisions that didn't anticipate how the integration would need to evolve.

An ongoing managed-services arrangement on Workforce Now provides RJR consultants as extension of your internal team for the platform-substantive work that keeps the system running well over time. Scope typically includes payroll cycle support, configuration changes as business policies and organizational structure evolve, integration monitoring and remediation when upstream systems shift, exception handling for edge cases, and platform expertise on demand for issues internal teams don't have the bandwidth or specialization to address.

The arrangement runs as a defined-hours-per-month engagement with a dedicated consultant or small team familiar with your environment. Onboarding typically takes 2-4 weeks, during which RJR consultants familiarize themselves with configuration, integration architecture, operational patterns, and team coordination expectations. Once steady-state, communication rhythm includes weekly check-ins, monthly engagement reviews, quarterly contract cycles, and ad-hoc availability for issues that need fast response. Scope flexes 50% up or down at quarterly boundaries based on prior-quarter actuals and upcoming-quarter anticipated work.

The work is designed for clients whose Workforce Now usage is mature enough to have moved past implementation but who don't want the operational risk or hiring cost of building the full platform-substantive capability internally. Some clients run managed services as their long-term operational model; others use it as a bridge during internal team development or M&A integration periods. The honest framing is that managed services done well becomes invisible operationally (you stop thinking about the platform because the work just keeps happening), which is what reliable operational support should produce.

Success in an ADP Workforce Now engagement looks like the platform operating reliably as infrastructure rather than as ongoing operational risk. The signals are concrete: payroll cycles run cleanly without exception accumulation, configuration changes happen on schedule when policies shift, integrations stay healthy as upstream systems evolve, reporting produces accurate operational answers, and your internal team's capacity is freed for higher-value work rather than consumed by platform-substantive issues they're not equipped to solve.

The harder-to-quantify signal is what the platform makes possible elsewhere. Internal HR, finance, and operations leaders can focus on strategic work rather than firefighting platform issues. Business decisions can be made faster because the data underlying them is trusted rather than reconciled-around. Operational debt clears rather than compounds. The shift typically takes 3-6 months of consistent engagement to surface, regardless of whether the engagement shape is implementation, stabilization, optimization, or managed services.

RJR runs Workforce Now engagements with measurable success criteria appropriate to the engagement shape: phase-gate exit criteria on implementations, prioritized backlog completion on optimization, service-level metrics on managed services. The honest read on success is that Workforce Now done well becomes infrastructure — present and trusted, not consuming operational attention because it keeps working. That's what mature platform delivery should produce, and that's the outcome we work toward across every engagement shape.