Your HR system already knows. The gift is still in a spreadsheet.

GiftWorks is the merchandise and gifting layer for the employee lifecycle. It reads the events your HR system already records, applies the budget rules you set once, and gets the right thing to the right person on the right day.

Every moment that matters to an employee is already a row in your HRIS, the system that holds your employee records, such as Workday or ADP. The hire date is there. The five year anniversary is there. The promotion posted last Tuesday is there.

What is not there is the part people actually remember. Someone still keeps the anniversary tracker. Someone still emails Finance for approval, twice, because the first one was missed. Someone still has four vendor contacts, three of whom answer on different days. And somewhere in the middle of all that, the same mug goes out to the person finishing year one and the person finishing year fifteen.

That gap between the system knowing and the organization acting is the work GiftWorks does. Not another place to browse products. The operating layer underneath: detect the event, apply the policy, route the approval to a person, personalize the item, coordinate the supplier, track the delivery, report the spend.

Request a demo Download the platform overview

The moments that matter

Seven moments. The same broken pattern in each one.

Every program below already happens at your company. The question is whether it runs on policy or on someone's memory.

We built GiftWorks around the moments that repeat. Repeating moments are the ones that create administrative load, the ones where inconsistency gets noticed, and the ones where a governed workflow pays for itself. Each one below shows what should happen and what usually happens instead.

Pre-boarding and onboarding kits

What should happen

A kit is on the desk, or at the home address, before day one. It matches the role, the location, and the size the new hire picked when they accepted. The manager gets a note confirming it landed.

What happens today

The offer is signed on the 12th, the start date is the 1st, and nobody starts the kit until the 27th. It arrives in week two. The laptop bag is the wrong one for a field role. Two remote hires in different states get different things for no reason anyone can explain.

How GiftWorks runs it

A new hire record creates a kit task the moment the start date is set. Role and location decide the contents. The employee picks size and a small number of options through a link. Fulfillment is coordinated against the start date, not the order date. HR sees what shipped and when it arrived.

Work anniversaries and service awards

What should happen

Year one feels like year one. Year fifteen feels like year fifteen. Tiers are written down, applied the same way every time, and exceptions go to a named approver.

What happens today

A tenure tracker that lives in one person's downloads folder. A catalog with a hundred items and no rule about who gets which. A director quietly spends triple on a favorite. Nobody can answer what the program cost last year without rebuilding it from invoices.

How GiftWorks runs it

Tenure tiers are a budget and policy problem before they are a catalog problem. The hard questions are what a five year award is worth against a fifteen year award, whether people who joined through an acquisition carry prior service, what happens when a manager wants to go above tier, and who signs that off. GiftWorks holds those as policy. Payroll and HR data supply the tenure, the policy agent applies the tier, exceptions route to a human, and the item is the last decision rather than the first.

Promotions and celebrations

What should happen

A role change becomes a moment within days, with something chosen for that person and a message from a manager who did not have to research vendors to send it.

What happens today

The promotion is announced in a channel. The manager means to do something. Two weeks pass. The moment closes.

How GiftWorks runs it

The role change event opens a short window and a small, pre-approved set of options at the right budget. The manager picks in under a minute and writes the note. Everything else is handled. Consistency across departments comes from the policy, not from which manager happens to be organized.

Recognition fulfillment

What should happen

Points earned in your recognition program turn into a physical thing worth receiving, delivered on a predictable timeline, without the employee ending up with a gift card they will forget to spend.

What happens today

Recognition is healthy and redemption is thin. The catalog behind the points is generic. Fulfillment is slow enough that the recognition and the reward feel unrelated.

How GiftWorks runs it

Your recognition platform stays the system of record for who deserves what. GiftWorks operates how it arrives. Approved point balances from any recognition system become a curated set of physical rewards at the matching value, personalized where it makes sense, sourced and shipped through our supplier network, tracked to the door. We fulfill other platforms' outcomes rather than competing for the recognition relationship.

Wellness and engagement bundles

What should happen

A wellness campaign reaches everyone it is meant to reach, in the right cohort, at a budget Finance already agreed to, with employees choosing what actually suits them.

What happens today

A well-intentioned initiative that turns into a two-week procurement and logistics project for someone whose job is not procurement or logistics. Regional teams get left out. Half the boxes go unopened.

How GiftWorks runs it

Define the cohort, the budget per person, and the window. Employees choose from an eligible set. Distributed teams are handled by address, not by hoping the office manager forwards things. Participation and delivery come back as numbers rather than anecdotes.

Event and offsite kits

What should happen

Kits arrive at the venue before the team does, counted correctly, with the right sizes and the right branding, and the leftover units are accounted for.

What happens today

A last-minute rush order at an expedited rate. Boxes shipped to a hotel that will not hold them. Forty extra larges in a closet for the next two years.

How GiftWorks runs it

Event intent creates a kit plan with quantities pulled from the attendee list, sizes collected in advance, and a delivery date set against the event date. Overage becomes inventory the system knows about instead of a closet nobody inventories.

Branded merchandise procurement, driven by RFQ

What should happen

You describe what you need, quantity, spec, deadline, and destinations, and you get comparable quotes from qualified suppliers with a clean path to a purchase order.

What happens today

An RFQ, meaning the request for quote you send suppliers when you need pricing against a specific quantity and specification, gets typed out four times to four vendors. Quotes come back in different formats with different assumptions about setup fees and freight. Procurement rebuilds them in a spreadsheet to compare. Two weeks disappear.

How GiftWorks runs it

One request becomes a structured quote pack. Suppliers respond against the same specification, so the comparison is real. Procurement approves the vendor and the quote, the same way it approves any other purchase. The order then flows into the same fulfillment and reporting path as every other GiftWorks program, so branded merchandise stops being a separate process with separate records.

Request a demo Talk to our team

How a program runs

Set the rules once. Approve the exceptions. Watch it arrive.

A buyer's view of the workflow, from the day you turn a program on to the report you take into your quarterly review.

1

Set rules and budgets. You decide which events count, what each one is worth, which populations are eligible, and who approves what. This is a working session, not a configuration project. The rules are written in your language: tenure tiers, cost centers, regions, spend caps, exception paths.
2

Send the data, in the form you can send it today. Most programs start with a secure CSV or scheduled export from your HR system. Single sign-on comes next. API and webhook connections come after the workflow is proven, not before. We ask for event type, effective date, name, work location, department or cost center, and eligibility flags. We do not ask for compensation, Social Security numbers, or performance detail.
3

Approve the exceptions, not the routine. Programs running to policy run without you. Anything outside policy stops and waits for a named human: HR approves trigger types, HR and Finance own budget policy, Procurement approves the vendor and the quote. These are human gates by design. Agents do the work between them, and every action is logged so an auditor can follow it.
4

Employees choose. For most programs the final pick belongs to the person receiving it, inside the eligible set you approved. Choice is what makes the difference between an item and a gift. It also removes the sizing and preference guesswork that generates returns.
5

Delivery is tracked, and exceptions are worked. Orders are coordinated with suppliers, and shipments are tracked to the destination. When something goes wrong, and occasionally something will, our operations team handles it. You find out from a status update, not from the employee.
6

Spend and outcomes are reported. Budget used against budget approved, by program and cost center. On-time delivery. Employee take-up. Exceptions granted and by whom. The reporting is built so you can defend the program in a budget conversation.

On the roadmap

One more thing belongs here, and it is on the roadmap rather than shipped. Non-cash awards are generally treated as taxable fringe benefits, which creates imputed income, the value of a non-cash award that has to be added to an employee's taxable wages and reported through payroll. Today that work lands on payroll by hand. We intend to emit it as a clean per-employee taxable-value feed, and we will call it available when it is.

Request a demo Download the platform overview

Who this is for

Built for the company that has the volume but not the headcount.

US mid-market, 100 to 2,000 employees, with lifecycle moments happening every week and nobody whose full time job is running them.

GiftWorks fits best when four things are true.

You are mid-market and growing. Between 100 and 2,000 employees is where the volume becomes real. Below that, a spreadsheet still works. Above that, you have a team dedicated to it. In between, the work is genuinely painful and genuinely under-resourced.

Your people are distributed. Multiple sites, remote employees across many states, field or shift teams who never pass through a head office. Anything that depends on an office manager walking a box to a desk has already failed for half your workforce.

Your lifecycle volume recurs. Steady hiring, a real tenure curve with people crossing milestones every month, recognition activity, offsites and events on the calendar. Recurring volume is what makes a governed program worth having.

You have no HR operations capacity to spare. Your People team is running benefits, compliance, hiring, and half a dozen systems. Gifting programs get done well when someone has time, and skipped when they do not. That inconsistency is what employees notice.

Typical buyers: HR and People Ops leaders who own the employee experience, Total Rewards teams who own the policy, and Procurement teams who own the vendors and the spend. Healthcare, professional services, manufacturing, and field services organizations tend to feel this earliest, because retention matters and the workforce is spread out.

If you have a dedicated internal team already running this well, you do not need us. If you are the person who owns it on top of your actual job, keep reading.

Request a demo Talk to our team

Start with a pilot

Two programs. Sixty to ninety days. A CSV file to begin.

We would rather show you the workflow on your real data than describe it in a deck.

The first engagement is deliberately narrow. Onboarding kits and work anniversaries, for one population or one department. Those two are concrete, they repeat, and they are easy to tie to data you can already export.

What we set up

Your event rules, your budget tiers, the approval path, and a curated set of options at each tier, including an employee-choice option and branded packaging if you want it.

What you send

A secure CSV export or scheduled file from your HR system. No integration project, no IT ticket queue, no API work to start. The path to single sign-on and API connections is documented so your technical team can see where it goes, and we take those steps after the workflow is proven.

What you approve

The trigger types, the budget policy, the option set, the exception handling, and the first orders. Nothing goes out that you have not agreed to.

What you get every week

A short metrics review: orders created and completed, on-time delivery, employee take-up, budget used against budget approved, exceptions and who approved them, and an estimate of administrative hours removed from your team. At the end we hand you the same numbers in a form you can take to Finance.

What it costs you to find out

One working session to set the rules, one file, and a named person on your side to approve exceptions. That is the commitment.

Pilot scope and timeline are agreed in writing before anything is ordered.

Request a demo Talk to our team

The event data already exists. The experience is the part that goes missing.

Show us one program you are running by hand, and we will show you what it looks like governed.

Bring your hardest one. The anniversary tracker with the color coding. The onboarding kit that arrives in week two. The RFQ you have retyped for four suppliers this quarter. A demo takes thirty minutes and uses your scenario, not a sample account.

We will be direct about what runs today, what is on the roadmap, and what we would not recommend starting with. If a pilot makes sense, we will scope it on the call.

Request a demo Talk to our team