How to evaluate us.
A working playbook for sourcing teams evaluating GYNERGY against mature enterprise alternatives. Written by a CTO who has been on both sides of these conversations. Honest about where we are.
The right question, first.
Not "are they ready" — that's a yes/no your security review will answer. The right first question is "is the leverage of being early worth more than the risk of being early?" If the answer is no, do not engage; we are not the right vendor at your stage. If the answer is maybe, the framework below is for you.
What you trade. What you get.
- · SOC 2 Type II report in hand (we are not SOC 2 certified yet; Type I readiness is underway)
- · Mature HRIS integrations live today (Workday is committed for first signed engagement)
- · F500 reference customers we can name on this page (we are pre-first-design-partner-close)
- · Decade-long vendor track record (we are 18 months in)
- · Predictable enterprise pricing benchmarks (early enterprise pricing is still being calibrated)
- · Design-partner pricing held flat for 24 months
- · Direct line to the founder and CTO on architecture decisions
- · Co-roadmap influence on the integrations that matter to your stack
- · An honest counterparty — the disclosures on this site are also our disclosures to your board
- · The kind of attention to your specific organization that does not survive Series B
A four-step framework.
- Step 1
Run the security review on what exists today.
Request our CAIQ v4, SIG Lite, security whitepaper, sub-processor list, and DPA template (all under NDA via security@gynergy.com). Run it through your standard vendor questionnaire. If we fail your minimum, stop here — we are an honest no.
- Step 2
Scope a bounded pilot, not a full deployment.
90–180 leaders, 90 days, one cohort. Pre-define the success metric (retention shift, leadership pipeline candidates surfaced, wellbeing pulse coverage). Bound the data exposure. Time-box the evaluation. Pilot pricing reflects design-partner terms.
- Step 3
Negotiate the exit before the entrance.
We sign data-portability commitments (18-month export, on-request escrow), termination-for-convenience clauses, and clear sub-processor change-notice windows (30 days). The contract we propose has these clauses on by default — your counsel does not have to fight for them.
- Step 4
Decide on outcomes, not on us.
At day 90, you have data: retention shifted or it did not; managers used the dashboards or they did not; wellbeing pulse coverage hit your target or it did not. Decide on what the data says. Expansion or graceful exit — either is a clean outcome and we expect you to choose on the merits.
What we ask of you in return.
- · Name a single decision-maker on your side. We will not manage a committee.
- · Tell us early when we fall short of a bar — silence is the most expensive feedback.
- · Let us co-name the success metric before the pilot starts.
- · Bring your hardest question on the walkthrough. We would rather lose the deal in week one than mid-year.
What this is not.
This page is not a substitute for your standard vendor review. It is the framework we wish vendors we evaluated had given us when we were the buyer. Use it alongside your own process, not instead of it. If you take only one thing from this page: decide on what the pilot data says — not on us. If we are not the right vendor, your data will tell you faster than any slide deck.
Questions, redlines, or a pilot scope to discuss?