About

Built by an SF admin.
For SF admins.

HCMToolkit started as a browser script that found one broken picklist label three days before a go-live. It grew into nine tools because the same problems kept appearing on every project.

The problem

SF administration has a tooling gap.
These are the problems HCMToolkit was built to close.

Manual picklist audits

Finding one option ID means exporting every list and running a VLOOKUP. A question that should take seconds takes an afternoon.

IT tickets for basic queries

You need Postman access, a whitelisted IP, and two approvals just to look at an OData endpoint you already have credentials for.

Unreadable RBP exports

The JSON is technically complete. In practice it needs an hour of reformatting before you can answer a single compliance question.

No built-in diff

Comparing picklists between releases means exporting both states, opening two Excel sheets, and squinting until something stands out.

Locale gaps you find in production

No coverage view exists. You find out a translation is missing when a user in Munich files a ticket after go-live.

Orphaned cascade references

Inactive parent values that still have active children. Silent until they break a dropdown — and then genuinely hard to trace.

Origin

A deadline forced the first version.

Three days before a go-live, a client’s dropdown was broken in German but working in English. The cause: a duplicated locale label somewhere across 800-plus picklists. The path to find it — export everything, VLOOKUP, repeat — would take hours no one had.

A quick browser script queried the OData endpoint directly and surfaced the problem in eleven seconds. The fix took two minutes.

That script became the Picklist Value Search. The next project brought a different problem, which became the Version Diff. Then an RBP audit, then a cascade hierarchy nobody had documented. Each tool came from a real deadline, not a product roadmap.

HCMToolkit is public because every SF admin hits these same walls. There’s no reason to keep rebuilding the same scripts.

Origin
Internal scripts
Written for real projects experience under real deadlines
Refined by
Daily use
Tested on every SuccessFactors engagement since
Tools
9 and growing
Each one solves exactly one problem
Cost
Free. Full stop.
Every tool, every feature, zero dollars. If that changes, you'll hear about it long before you see a paywall.

Architecture

Your token is never
stored by HCMToolkit.

Your bearer token is held in your browser’s session storage — scoped to your tab and cleared the moment you close it.

Because SuccessFactors enforces CORS restrictions on direct browser requests, API calls are relayed through a stateless proxy (/api/sf-proxy). The proxy receives your token, forwards the request to your SF instance, returns the response, and writes nothing. No database, no logs, no session state. Open DevTools → Network and you’ll see every call go out to your tenant URL after passing through the relay.

No user accounts. No data retention. No analytics scripts. Nothing here is collecting information about you or your tenant.

Network · DevTools
Actual request flow
Browser
→ POST /api/sf-proxy
Token + target URL sent here
(stateless relay — no logs,
no storage, no DB writes)
→ Your SF tenant
api.successfactors.com/odata/v2/...
← Response returned
Proxy holds nothing after this
✗ Token written to any database
✗ Request logged server-side
✗ Analytics or tracking

Philosophy

Four things this project
will not compromise on.

01

Respect for your time

Every tool is built to answer one question precisely — without setup, without configuration, and without waiting. If it takes more than a minute to get a result, something is wrong.

02

Respect for your data

Your bearer token and tenant data never leave your browser tab. Zero-trust by design — not because we claim it, but because there is no backend to receive it.

03

No monetization theater

HCMToolkit is free to use today. No account signup. No credit card "just in case." No free tier with the good features locked behind Pro™. If the economics ever require a different model, it won't show up as a surprise modal while you're three clicks into fixing a production issue. You'll know the why, the when, and the what — with enough runway to decide if it still makes sense for you.

04

Built from real frustration

Every tool here started as a script written under deadline pressure. None were planned — they were all "there has to be a better way" moments that turned into something reusable.

Get started

Enough context.
Time to use the tools.

No account. No install. Paste your credentials and you’ll have your first result in under sixty seconds.

Start with Value Search

Or browse all nine tools on the homepage.