Your systems already know the moment. GiftWorks makes something arrive.
The agentic layer that turns lifecycle events in platforms like Workday and ADP into merchandise that ships on time, inside budget, with the approvals your policy requires.
A hire record has a start date. An anniversary has a date field. A promotion has a cost center attached. The data is already there, already clean, already dated. GiftWorks is the layer that acts on it.
GiftWorks is the agentic merchandise and gifting layer for the employee lifecycle. It listens to the lifecycle signals that already live in HR platforms like Workday and ADP. Hires, anniversaries, promotions, recognition moments, exits. It converts them into governed, budget-compliant, fulfilled employee experiences, with humans approving the rules and agents doing the work.
The problem
The event is recorded. The experience is not.
Your HRIS, the system that holds employee records, already carries every moment worth marking. What happens next is still done by hand.
Onboarding is a hire record with a start date. A five year anniversary is a date that has been sitting in payroll since the day the person joined. A promotion is an approved business process with a budget owner attached. None of that is hard to find.
The next part is where it breaks. Someone exports a list. Someone builds a spreadsheet. Someone chases an approval in chat, then chases the budget owner, then emails three vendors for quotes and waits. Two weeks later a generic box arrives at an old address, or nothing arrives at all and a manager sends a gift card to close the loop.
This is not a recognition problem. Recognition platforms already decided who deserves what, and they decided it correctly. This is an operations problem. Procurement, personalization, budget policy, shipping, and proof of delivery. That distance between the system knowing and the organization acting is what GiftWorks was built to close.
How it works
One loop. Five steps. A named human at every gate.
Six agents run the work. Each has one job, defined inputs, defined authority, and a person who signs off before anything spends money.
Sense
The Lifecycle Listener watches the event types you approve. New hire, work anniversary, promotion, recognition award, exit. HR decides which events are in scope before a single one runs.
Decide
Budget and Policy applies your rules. Tier by tenure, spend by band, eligibility by location and cost center. Tiering is a budget question, not a catalog question, so it lives in policy where Finance can see it and change it. Personalization then narrows the options to what fits both the policy and the person.
Govern
Approvals route to the people who already own them. HR and Finance own policy. RFQ/Procurement sends an RFQ, a request for quote, to suppliers against one specification and brings back comparable bids. Procurement approves the vendor and the quote. The employee or manager makes the final pick. Nothing moves on an agent's say-so alone.
Fulfill
The Fulfillment agent places the order, tracks artwork proofs and production, follows the shipment, and raises exceptions to your ops team before the recipient notices anything is late.
Learn
Insights reports what shipped, what it cost, what arrived late, and what people actually chose. Every action is written to an append-only log, so the answer to "who approved this and when" takes one click, not one week.
Who it serves
Built for the people who own the moment.
Three ways in, depending on where you sit.
Door 1
HR, Total Rewards, and People Ops
You own the program and the budget, and you are the one who hears about it when a kit shows up late. GiftWorks runs onboarding kits, service awards tiered by tenure, promotion gifts, recognition fulfillment, wellness bundles, and event kits on one set of rules you write once. Built for US teams between 100 and 2,000 people with distributed staff and a hiring calendar that does not stop.
See offerings and use casesDoor 2
Platform and ecosystem partners
GiftWorks is built to work with data from platforms like Workday and ADP, and to sit under recognition platforms rather than beside them. Your system stays the system of record. We take the event, apply the policy, run procurement, and fulfill the physical outcome, then report it back. Integration starts with a secure file export and moves to SSO and API access only after a workflow is proven in a pilot.
Read the integration approachSuppliers. We work with a curated network of manufacturers, decorators, and fulfillment partners. Access is by application, and we review on capability, quality, and delivery record.
Apply to our supplier networkThe operations backbone
The operations backbone behind the platform.
GiftWorks is new. The merchandise operation underneath it is not.
The team behind GiftWorks operates a custom merchandise back office at industrial scale. On the order of 65,000 requests and 20,500 confirmed orders a year, roughly $14.4M in turnover-equivalent volume, across 7 countries. We call it our operations backbone. It is operational capability, not GiftWorks traction and not a contracted demand base, and we describe it that way on purpose.
Live today: nine suppliers identified, roughly 400 products loaded from two of them, and the first agents shipped for product, mockup, and order. That is the honest state of the build.
Governance and trust
Agents do the work. People hold the authority.
Governance is not a policy page we link to at the bottom. It is how the platform is built.
Human gates
HR approves which trigger types are live. HR and Finance own the budget policy. Procurement approves the vendor and the quote. The employee or manager makes the final pick. Ops handles escalations. Leadership reviews the outcome. An agent proposes, a person decides.
Data minimization by design
The workflow needs event type, effective date, name, work location, department or cost center, and eligibility flags. It does not need compensation, Social Security numbers, or performance detail, so we do not ask for them and we do not store them. Access is least privilege, retention is capped, and any employee can be paused or suppressed individually.
Audit you can hand to someone
Every decision and every action is written to an append-only log with the rule that fired and the person who approved it. Integration is staged on purpose. Secure file export first, single sign-on next, API and webhooks once a workflow has been validated in production.
Bring us one moment you are still handling by hand.
Onboarding kits, service awards, or a recognition catalog you are tired of apologizing for. We will walk you through what the loop does with it, on your policy and your calendar.
A demo takes 30 minutes. We will ask what your triggers are, who approves spend, and where your program breaks today. If GiftWorks is not the right fit for that program, we will say so in the call.