AX Field Notes

All casesNo. 068

Lifetime Products Closes Store Orders While Managers Sleep

Order closing moved from store managers' early mornings to an overnight flow

Case no.
068
Primary source
Microsoft customer story
Source published
2026-08-26

1. Why this case

Lifetime Products manufactures residential basketball systems, tables, chairs, and outdoor equipment used across the United States and in approximately 100 countries. It also runs nine retail stores. Its Microsoft customer story, published on 2026-08-26, lists several agents, but the change it measures most concretely is narrow: the start-of-day close in those stores.

Store managers and assistant managers used to come in early to close orders in the ERP system, reconcile the previous day’s activity, and prepare inventory for the day ahead. That took two to three hours each day. Using Power Automate patterns, Lifetime moved order closing to an overnight run. The number of retail orders someone touched by hand each day went from 50 to 80 to zero.

The case is useful for three reasons. First, it shows where repetitive work sat in a retail operation: at the start of the day, done by the store’s managers. Second, Lifetime has a named internal practice, “rebalance,” for what follows when an agent delivers measurable value: IT, HR, business leaders, and the affected team decide what happens to the time saved. Sinahi Lopez, Global IT Functional Manager, says 45 employees moved into new roles over two years. Third, the store result came from a workflow automation that the story describes as built with Power Automate. The story, titled around Copilot Studio, does not describe a language model or a Copilot Studio agent in that step.

All figures come from a Microsoft customer story and are vendor-published, not independently audited.


2. Problem

The story’s executive summary says Lifetime “needed to reduce repetitive work across retail, HR, supplier communication, accounting, and customer service.” The retail case is the most detailed.

2.1 The store morning

“Retail store managers and assistant managers across nine stores came in early to close orders, reconcile the previous day’s activity, and prepare inventory for the day ahead.” Lopez describes the routine: “Our store managers and assistant managers would come in and manually close out orders in F&O, reconcile the day from the night before, and make sure inventory was accurate for the day.”

F&O refers to Microsoft Dynamics 365 Finance and Operations apps, the ERP system. The story lists Dynamics 365 Finance and Dynamics 365 Supply Chain Management among the products in use. The same routine is quantified later in the story: store managers and assistant managers “previously spent two to three hours each day” on closing orders, reconciling the prior day, and preparing inventory. The story does not say whether that is per store, per person, or across all stores.

2.2 The same pattern in other functions

The story says similar patterns appeared in other functions:

  • HR and payroll teams answered handbook and policy questions by phone or in person.
  • Customer service representatives “had to search four or five systems for product, customer, inventory, dimensions, and parts information.”
  • Supplier and accounting teams were exploring ways to automate communication, purchase order follow-ups, ship dates, and account reconciliation.

2.3 Adoption as the harder problem

Lopez names adoption, not technology, as the main obstacle: “User adoption of AI is definitely the biggest struggle.” The story adds the context: “In a manufacturing company, where automation has changed work before, Lifetime needed to show that AI was not about labor reduction, but about creating new opportunities.”

Confirmed facts: nine stores; store managers and assistant managers came in early to close orders in F&O, reconcile the previous day, and prepare inventory; two to three hours each day (unit not stated); HR and payroll answered policy questions by phone or in person; customer service searched four or five systems; supplier and accounting teams were exploring automation; adoption named “the biggest struggle.”


3. Solution

3.1 Out-of-the-box agents first, then custom ones

John Bowden, Global CIO, describes the sequence: “Lifetime started our AI journey quite a while ago, more than a couple of years ago. We began with out-of-the-box agents and that’s evolved into more custom agents, particularly with Copilot Studio.”

The out-of-the-box agents named are supplier communication and account reconciliation, used “to support core ERP processes.” Lifetime builds custom agents “when teams need solutions aligned to how their work operates.” Lopez: “Going into Copilot Studio has helped us create custom agents that are a niche in our area.”

Lifetime worked with Microsoft and the partner Argano to establish “the initial AI use cases, governance approach, and technical architecture.” Argano then helped turn early opportunities into a roadmap, “identifying where Microsoft Dynamics 365, Power Platform, and Copilot Studio could be applied first and then extended across additional business functions.” Yogesh Kasat, Principal at Argano, summarizes the approach: “Successful AI transformation starts by proving value quickly and scaling what works.”

The story lists the current stack as Copilot Studio, Power Automate, Microsoft 365 Copilot, Microsoft Foundry, Dynamics 365 Finance, and Dynamics 365 Supply Chain Management.

3.2 The overnight store close

The story describes retail operations as the focus of one of the first custom scenarios: “Using Power Automate patterns, Lifetime moved retail order closing to run overnight while employees sleep. The process supports order flow and accounting handoff without store teams manually completing the same steps each morning.”

It built on the process and architecture work done with Argano, “which helped connect the automation opportunity to Lifetime’s broader Dynamics 365 environment.” Lopez: “With AI, we were able to automate that process. So now that happens while they’re sleeping.”

The story does not describe a language model or a Copilot Studio agent inside this step. The mechanism it names is Power Automate.

3.3 HR self-service agent

HR followed with “a self-service agent built from employee and supervisor handbooks.” Employees ask common questions, such as how PTO accrues or what a policy covers, “without calling HR or visiting the HR office.”

3.4 Knowledge agents for customer service and tax

Lifetime “is also building” a customer service agent that brings together product lifecycle data, Dynamics 365 information, inventory data, dimensions, parts, and customer information. The goal is to give representatives answers in one place instead of four or five systems.

A tax knowledge agent is already in use: “Lifetime’s finance teams use this agent for tax inquires, rather than paying costly consulting fees or spending hours searching through caches of files and data.”

3.5 Rebalance: a decision about the time saved

The story says Lifetime’s AI strategy “is anchored in a word it uses internally: rebalance.” The practice is described this way: “When an agent delivers measurable value, IT, HR, business leaders, and the relevant team come together to understand the time saved and decide how employees can be upskilled, moved into new roles, or freed to focus on high-value work.”

Bowden ties this to the company’s mission: “Part of our mission statement is to offer opportunities for our people.” The story adds: “For Lifetime, AI value isn’t complete until the company understands what happens to the people whose work changes.”

Confirmed facts: out-of-the-box agents (supplier communication, account reconciliation) came first; custom agents with Copilot Studio later; Microsoft and Argano set initial use cases, governance, and architecture; retail order closing runs overnight using Power Automate patterns and supports order flow and accounting handoff; HR agent built from employee and supervisor handbooks; customer service agent being built; tax knowledge agent in use by finance; rebalance review with IT, HR, business leaders, and the team after an agent delivers measurable value.


4. Impact

Figures from the Microsoft customer story dated 2026-08-26.

MetricFigureBasis
Retail orders touched by hand per day50–80 → 0Company-level daily count; Lopez calls the orders “completely touchless”
Time store managers and assistant managers spent each day closing orders, reconciling, and preparing inventory2–3 hours, now saved“2-3 hours saved daily”; unit not stated
Employees moved into new roles45 in two yearsCompany-wide rebalancing (Lopez); not tied to the store close alone
HR and payroll inquiriesReducedNo figure

On the store mornings, the story says store leaders “can now use that time each day for higher-value work, including selling more products and serving customers.”

On the workforce, Lopez said: “We’ve been able to rebalance, in the two years, 45 employees into new roles that give them a lot of opportunity for their family and their career.”

On the HR agent, the story says it “reduced routine HR and payroll inquiries and helped make AI feel practical and approachable.”

4.1 What comes next

Bowden describes four pillars: business systems, “specifically around Dynamics 365 and how we implement out-of-the-box agents”; upskilling employees “to make sure that they have the proper training to work with agents and to deal with new parts of their job”; “personal productivity agents,” which he calls “where we’re headed now”; and “Copilot Cowork to automate and execute tasks while keeping humans in the loop.”

Lifetime also wants to use AI to “improve accuracy, reduce chargebacks, and ensure data is entered correctly.” For customer service, the goals are shorter call handling time, fewer repeat calls, and faster answers from a single place. These are goals, not results.


5. Insight

The work that moved sat at the start of the day. The store close was done by store managers and assistant managers, who came in early to do it. Moving it overnight returned that time to the store day. The story names the use of that time: selling more products and serving customers.

The measured win was a workflow, not a conversation. The 50-to-zero result comes from a step the story attributes to “Power Automate patterns.” Closing orders and handing them off to accounting is a fixed sequence on records already in the ERP system. Lopez calls it AI, and the story places it among Lifetime’s custom scenarios, but it does not describe a model making judgments in it. The program’s clearest number came from automating a well-defined ERP routine, not from a chat agent.

Rebalance turns time saved into a decision with owners. The rule starts after measurement: “When an agent delivers measurable value.” IT, HR, business leaders, and the team then decide among three outcomes: upskill, move into a new role, or free time for higher-value work. With HR in that review, the company reports a workforce number (45 employees in two years), not only a time-saved number. The precondition is that each automation has a measured before and after.

Adoption came through low-risk agents. In a manufacturer where automation had changed jobs before, Lopez called adoption “the biggest struggle.” The HR handbook agent, which answers PTO and policy questions, is the one the story credits with making AI “feel practical and approachable.” The agent credited with that answers questions; it does not take over anyone’s task.

Limits. This is a vendor story with three figures. The unit behind “two to three hours” is not stated. The 45 moves are company-wide over two years and are not broken down by automation. The HR, tax, and customer service agents have no figures, and the customer service agent is still being built. The story does not say how orders that cannot close cleanly are handled, or whether the overnight run also covers inventory preparation.

One-line takeaway: Lifetime’s clearest result came from moving a fixed ERP routine out of store managers’ mornings into an overnight flow, and its rebalance practice is what turned that saved time into a decision about people.


6. Implementation hypotheses (not in the source)

6.1 Scheduled close against Dynamics 365 with a morning exception list

Basis: “Using Power Automate patterns, Lifetime moved retail order closing to run overnight while employees sleep. The process supports order flow and accounting handoff.” Orders are described as “completely touchless.”

The likely shape is a scheduled Power Automate cloud flow that runs after the stores close. It would read the day’s open retail orders from Dynamics 365 Finance and Operations, check each against the conditions a manager used to confirm by hand, such as payment captured and goods fulfilled or picked up, and then close the order. The phrase “accounting handoff” suggests the run ends by leaving closed orders in a state finance can post or reconcile, so accounting no longer waits for a store manager to finish the morning close. An order that fails a check would probably not be forced closed. It would more likely be written to a short exception list for a store manager or accounting to review, which means “touchless” describes the normal day rather than a guarantee for every order. A run log or failure alert would also be needed so that a missed overnight run is noticed before the store opens, not when accounting finds a gap.

6.2 Handbook-grounded HR agent with a route back to HR

Basis: The HR agent was “built from employee and supervisor handbooks” and answers questions “such as how PTO accrues or what a policy covers, without calling HR or visiting the HR office.”

The agent was probably built in Copilot Studio with the two handbooks as its knowledge source, answering from the policy text rather than from payroll records. The example question, how PTO accrues, is a policy question, not a request for one employee’s balance, which suggests the agent explains rules and does not read individual HR data. Having separate employee and supervisor handbooks implies the answers depend on who is asking, so supervisor content was likely limited to supervisors through sign-in. Questions the handbooks do not cover, or personal cases, would most likely be passed to HR or payroll, keeping the team as the second line instead of the first.


7. Sources

  1. Microsoft — Lifetime Products rebalances work with Microsoft Copilot Studio
    https://www.microsoft.com/en/customers/story/27087-lifetime-products-microsoft-copilot-studio
    2026-08-26 (accessed 2026-11-17)