Company
We built a company around a box arriving on the right day.
GiftWorks is the merchandise and fulfillment layer under the employee lifecycle. This page is about why that layer needed to exist.
Think about the object itself. A parcel on a desk on the morning of someone's fifth anniversary. The right size. The name spelled correctly. Something the person would actually keep, not a branded item they leave in a drawer. It came out of a policy finance approved, from a supplier who was held to a date, and it cost what it was supposed to cost.
Almost nothing about that is a software problem. It is a decoration lead time, a minimum order quantity, a size curve, an address file, a customs form, a carrier exception at 4pm on a Thursday. Every one of those is a place the day can quietly go wrong, and each one is owned by a different person with a different spreadsheet.
We started GiftWorks because that object is the whole point of a recognition program and the part nobody built for. Deciding who deserves something is well served by software that already exists. Getting it there, correctly, inside budget, on the date it means something, is operations work, and it is the work we already do at volume.
So we built the company from that end. GiftWorks reads the lifecycle signal your HR systems already hold, applies the budget policy your finance team already set, routes the approval to the person who owns it, coordinates the supplier, and tracks the package to the door. Your HR platform stays the system of record. Your recognition program stays yours. We are accountable for whether it arrives.
What we believe
Four positions that decide how the product gets built.
The physical part is the hard part.
Choosing who deserves recognition is a policy question, and good software already helps with it. Getting a correctly sized, correctly branded, correctly addressed object into someone's hands in a specific week, across states and time zones, at a price finance approved, is an operations question. Catalogs are easy to add. Fulfillment is not. We started at the hard end.
Governance is a feature, not friction.
Procurement and Total Rewards do not want a faster way to spend money without a record. They want spending that stays inside policy and can be explained afterward. Budget rules, tier logic, approval routing, and an append-only log of every action are part of the product, not a compliance layer bolted on at the end.
Recognition should arrive, not just be recorded.
A points balance is not a gift. An entry in a system is not a moment. The measure of a program is whether something real showed up when it was supposed to, and whether the employee could tell it was meant for them. We report on delivery, not on activity.
Automation is only useful with human gates.
Agents are good at watching for events, applying rules, drafting quotes, and chasing carriers. They should not be the last word on who gets what, what it costs, or which vendor wins the order. Every agent we ship has one job, defined inputs, defined authority, and a named human who signs off. If nobody owns the gate, we do not automate the step.
Where we come from
We did not start with a demo. We started with a loading dock.
The team behind GiftWorks operates a custom merchandise back office at industrial scale. Across a year, our operations backbone handles on the order of 65,000 requests and 20,500 confirmed orders, roughly $14.4M in turnover-equivalent volume, across 7 countries.
Those numbers describe capability, not GiftWorks traction. They are not customers of this product, not revenue of this product, and not committed demand. We share them for one reason: they are where the product knowledge comes from. Decoration lead times, minimum order quantities, size curve failures, address hygiene, split shipments, customs paperwork, the difference between a quote and a landed cost. You learn that by running it, not by reading about it.
What that experience gave us is a working view of where employee gifting actually breaks. It rarely breaks at the idea. It breaks at the request queue, the approval, the vendor quote, the artwork proof, and the last mile.
Where we are today, stated plainly. Nine suppliers identified for the network. Roughly 400 products loaded from two of them. Our first three agents are shipped and running: product, mockup, and order. The rest of the platform is on a pilot-first roadmap, and we would rather show you the working parts than describe the finished ones.
How we work
Pilot first, measured, and bounded by design.
We start with a pilot, not a rollout.
Two event types, one population, sixty to ninety days. Usually onboarding kits and work anniversaries. We agree in advance on what success looks like, run it end to end, and show the record. If it does not hold up, you have lost a quarter of one program instead of a year of a platform commitment.
We measure what the employee experienced.
Not opens, not logins. Time from lifecycle event to delivery. Percentage of orders inside budget policy without exception. Approval cycle time. Delivery accuracy against the intended date. Cost per moment, landed. If a number cannot be pulled from the log, we do not claim it.
We keep the agents small and the gates human.
Six bounded agents, each with one job. A lifecycle listener that watches for event types HR has approved. A budget and policy agent that applies rules HR and Finance own. A personalization agent that narrows the options, with the employee or their manager making the final pick. An RFQ and procurement agent that prepares the request for quote, the formal ask that goes to suppliers for pricing, with procurement approving the vendor and the number. A fulfillment agent that coordinates the supplier and tracks the shipment, with operations handling exceptions. An insights agent that reports to leadership. Every action is written to an append-only log.
We ask for the least data that makes the workflow function.
Event type, effective date, name, work location, department or cost center, eligibility flags. Not compensation, not Social Security numbers, not performance detail. Integration is staged deliberately: a secure CSV export first, single sign-on next, then API and webhooks once the workflow is validated. Least privilege access, retention limits, decision logs, and a per-employee pause or suppress control from day one.
Tell us where the program breaks
If you already know which part of your gifting program fails, that is the right place to start a conversation.
Most of the teams we talk to are not looking for a new philosophy of recognition. They have one. They are looking for the kits to arrive before day one, the anniversary list to stop living in a spreadsheet, the approvals to stop sitting in an inbox, and the vendor count to come down.
If that sounds familiar, bring us the specific failure. We will tell you honestly whether it is something GiftWorks handles today, something on the pilot roadmap, or something you should solve another way.
- For HR, People Ops, and Total Rewards teams: request a demo and we will walk the lifecycle end to end with your program structure in front of us.
- For procurement and finance: ask for the platform overview. It covers budget policy, approval routing, audit logging, and the data posture in one document.
- For suppliers who decorate, print, or fulfill merchandise: our network is application gated. Apply through the supplier page.