The First Customer Stories Will Be Written With Our Founding Customers. One Could Be Yours.
We are bringing Benefits Reimagined to its first employers now. We will not publish names, quotes or numbers we do not have. This page says what founding customers get, what we ask in return, and how their stories will appear here.
Most platforms fill this page with logos. We would rather tell you where we are: the product is live and listed on SAP Store, the first employers are going live, and the people who built it are the people on your call. Going first has real advantages, and we have written them down.
What You Can Check Today, What You Cannot Yet
The product, on your plans
A 45-minute walkthrough set up as your program — your plans, carriers and HR system — run by the product team.
Available nowThe SAP Store listing
Benefits Reimagined is an SAP partner product built on SAP BTP and listed on SAP Store. You can read the listing without talking to us.
Available nowSecurity and privacy review pack
The written answers your IT and procurement teams will ask for, including what is in place and what is in progress.
On requestReference calls with live customers
Available once founding customers are live and have agreed to take calls. We will not put you in touch with anyone who has not signed off.
Coming with the founding cohortNamed case studies with numbers
Written after ninety days of measured use, reviewed word by word by the customer, published only with written permission.
Planned · this pageIndependent certifications
The platform runs on certified clouds (SAP BTP and AWS). Independent certification of the platform itself is planned and in progress.
In progressWhat Founding Customers Get
Going first should be worth something. These six things are written into the founding agreement, not promised on a call.
A direct line to the people who built it
The founder and the product lead are on your rollout. Questions go to the person who can change the answer, not to a queue.
Rollout done with you
We set up your plans, rules and carrier connections alongside your team, run a parallel period against your current process, and switch only when the numbers match.
Founding terms, locked
Your founding price and terms hold for the full length of your first agreement, whatever we charge later customers.
A seat on the roadmap
Founding customers meet the product team every month, see what is being built next, and shape it. When you ask for something, you hear back with a date or a reason.
The review pack, up front
Security, privacy and accessibility answers for your IT, legal and procurement teams before you sign anything, with what is in progress marked as such.
Your story, on your terms
If you want one, a written case study after ninety days, with numbers you have checked and every word approved by you. If you do not, nothing is published — ever.
What We Ask in Return
A founding customer is a partner in the first year, not a beta tester. This is the whole list; there is nothing hidden in the agreement.
1From you
- Two named people — one from benefits, one from payroll or IT — who can answer questions and make decisions
- A 30-minute check-in every two weeks during rollout, monthly after go-live
- Plain feedback — what is slow, what is confusing, what you would not renew for
- A parallel period — running your current process alongside ours for one or two pay cycles so both sides can prove the numbers match
- Patience with rough edges — some screens will improve while you use them; we tell you what is changing before it changes
2What we will never ask
- Your logo or a quote before you have seen results — permission is asked after ninety days, and “no” is a complete answer
- Real employee data before a signed agreement — walkthroughs and setup use a made-up population that looks like yours
- Numbers you have not checked — every figure in a story is yours to verify first
- Anything that is not written down — the offer and the ask above are the founding agreement, in the same words
Who Fits the Founding Cohort — and Who Should Wait
We keep the founding cohort small so every customer gets the founders' attention. That means saying no to some good fits for now. Here is how we decide.
✓A good fit now
- U.S. employers with roughly 500 to 50,000 employees , one or several legal entities
- SAP SuccessFactors customers , or employers on Workday, UKG, ADP, Dayforce or Paycom
- A real problem to solve this year — a carrier bill nobody trusts, an HR inbox that never empties, an open enrollment that needs fewer errors
- A benefits leader with time to meet every two weeks and the authority to decide
- Willing to run a parallel period and switch on evidence, not on a date
–Better to wait
- You need full COBRA administration on day one. It is on the roadmap; we will tell you when it is live. Everything else — individual coverage HRAs, multi-entity groups, PEO set-ups — is live, and the Advanced Features page lists it all.
- You need a vendor with published customer references before any conversation. Fair — come back when the first stories are on this page.
- You want to sign this quarter and go live next month. A careful rollout takes twelve to twenty weeks, and we will not shorten it.
If you are not sure which column you are in, the 45-minute walkthrough is the fastest way to find out — and Why Benefits Reimagined? says who we are built for in more detail.
The Stories We Want to Tell First
Three kinds of story we are looking for founding customers to write with us. Each slot stays marked open until a real employer fills it.
A first open enrollment inside SuccessFactors
An SAP SuccessFactors employer runs open enrollment in Benefits Reimagined with one login, IntelliSuggest recommendations and Athena taking the repeat questions. The story would measure errors chased, questions answered without HR, and time to close.
Founding slot openCarrier bills checked for a group of companies
A group with several legal entities matches every carrier invoice to enrollment and payroll before paying it. The story would measure differences found, dollars recovered or avoided, and month-end hours saved.
Founding slot openAn HR team retires the spreadsheet
A small benefits team moves its problem list, cases and documents into one place. The story would measure the size of the morning list, reply times, and what the team did with the hours it got back.
Founding slot openHow a Story Gets Written Here
The same four steps for every customer, so you know exactly what we do with your results and what we will never do.
Go live, with the founders on the call
Rollout ends with a parallel period and a switch on evidence. Nothing is written yet.
Ninety days, measured together
We agree the three or four numbers that matter to you before go-live and track them with you, not for you.
You review every word
The draft goes to you first. You correct, cut or decline. Every number is yours to verify.
Published only with written sign-off
Name, logo, quotes and figures appear only as you approved them — and can be withdrawn at any time.
What every story will show
- Who the employer is, in as much or as little detail as they choose
- The problem they started with, in their words
- What changed, with numbers they checked
- What did not work as hoped — the honest part readers trust
- Who they would recommend it to, and who they would not
What we will never do
- Invent a quote, a name or a company
- Show a logo without written permission
- Publish a number the customer has not verified
- Present an industry statistic as if it were our result
- Leave a story up after a customer asks to take it down
Apply to Be a Founding Customer
The first step is the 45-minute walkthrough on your plans. Say on the form that you are interested in the founding cohort; a person replies within one business day, and we tell you plainly whether it is the right fit now.
Questions Employers Ask Before Going First
Why there are no logos yet, what founding customers get, and how safe it is — answered plainly.
Because we do not have one to show yet. Benefits Reimagined is live, listed on SAP Store and going in with its first employers. We would rather say that plainly than borrow logos or invent quotes. Stories will appear here as founding customers go live and approve them.
A direct line to the founder and product lead, rollout done with you including a parallel period, founding price and terms locked for your first agreement, a monthly seat on the roadmap, the security and privacy review pack up front, and — only if you want it — a case study you approve word by word.
Two named people, a 30-minute check-in every two weeks during rollout and monthly afterwards, plain feedback, a parallel period against your current process, and patience while some screens improve. We never ask for a logo or quote before you have seen results.
A small number at a time, so each gets the attention the offer promises. When the cohort is full we say so on this page and open a waiting list rather than stretch the team.
That is the right question. The platform runs on SAP BTP and AWS, both independently certified clouds; compliance controls and evidence are built in; a parallel period proves the numbers before you switch; and your founding terms hold whatever happens to our pricing later. Independent certification of the platform itself is in progress, and we will show you where it stands.
Twelve to twenty weeks depending on how many plans, carriers and legal entities you have. We do not shorten it, because the parallel period is what makes the switch safe.
Book the 45-minute walkthrough and say on the form that you are interested in the founding cohort. A person replies within one business day. If you are a better fit for a later cohort, we say so and tell you when to come back.
Early, Deliberately — and Honest About It
The first stories on this page will belong to the employers who go first. We would like one of them to be yours.