See your org's AI exposure as a finance-grade read.
Wagecore for Business is a per-seat SaaS shipping in stages through 2026. The financial projection engine — NPV, IRR, Payback Period per role against an inference-cost decline curve — ships today as the Investment view inside every Pro Wagecard, running against the v1 capability matrix. The full multi-axis v1.5 economics (three-model evaluator panel + eval-disagreement confidence signal per ADR-017) lands in Q3 2026. Org-level dashboards, OAuth connectors, and SSO ship in subsequent releases on the roadmap below.
For orgs from 50 to 50,000 employees. Privacy-first by construction.
What ships when
We want you to know exactly what works today versus what's on the roadmap before you spend procurement time.
Individual Wagecards with the full 9-axis methodology. Investment View per-role (NPV, IRR, Payback, cash-flow table). Anonymous adoption signals. Open methodology, monthly refresh. Org preview — paste 50 roles, see a non-persistent heatmap + org-level financial roll-up right now.
Persistent org accounts. CSV ingest for full JD list. Manual analyst engagement available for design partners. JD-parser ingesting from Greenhouse / Lever / Workday CSV exports.
OAuth connectors: Workday, Greenhouse, JIRA, GitHub, Slack. SSO (Okta, Entra). SCIM provisioning. Per-seat self-serve billing.
Deep calibration via Slack / Notion / Confluence sampling. Custom role taxonomy extensions. Audit logs, IP allowlist, regional data residency. On-prem option.
What's in the dashboard
Connectors (Q3 2026)
OAuth integrations ship in Q3 2026. Until then, design-partner cohort customers can use CSV upload (org chart + JD list) — the same engine runs on either ingest method.
- Workday · BambooHR · Rippling · Personio (HRIS)
- Greenhouse · Lever · Ashby (ATS)
- JIRA · Linear · Asana (tickets)
- Google Calendar · Outlook (meeting taxonomy)
- GitHub · GitLab (engineering)
- Slack · Microsoft Teams · Notion (sampling)
- Zendesk · Intercom (support orgs)
- Salesforce · HubSpot (sales orgs)
First-party connectors at GA: Workday, Greenhouse, JIRA, GitHub, Slack. Others via SCIM or CSV upload at launch; native OAuth shipping by Q3 2026 based on customer demand.
Pricing
Per-seat monthly subscription with employee-count bands. Annual commitment 17% off. Indicative for the pre-launch waitlist; final terms set at scoping call.
The optional design-partner audit add-on ($75k–$250k per quarter) is how the first dozen customers will work with us during pre-launch — a manual analyst pass alongside the dashboard so we both learn what to surface next. It's an add-on, not the product.
If the methodology is open, what does Wagecore actually sell?
A reasonable question, and one we want answered before you sign in. The methodology — formula, axes, confidence bands — is open because honest economics need to be auditable. What's under license is the underlying dataset and its continuous refresh:
- The capability matrix. 50 roles × 33 tasks × 9 axes × monthly refresh against three frontier-model evaluators. Reproducing this internally is roughly $300–500k/year in eval compute plus a dedicated engineer.
- Salary benchmark integrations.BLS isn't granular enough at role × geo × experience. Levels.fyi, Glassdoor, and Payscale paid feeds, plus our first-party contribution dataset, cost $50–150k/year to maintain in-house.
- Cross-industry adoption distribution.Anonymous per-task AI-usage signals collected across thousands of workers in different companies and industries. A single company — even a Fortune 500 — can't reproduce this because their internal sample is, by definition, one company.
- Comparability.When your CFO says “our AI exposure is 65,” the CFO across the table understands the number only because both organizations are referencing the same Wagecore scale. A bespoke internal score isn't readable outside.
The formula is open so you can audit our reasoning. The data is what you're paying for — and what's impractical to rebuild even if you wanted to.
How we handle privacy
A dashboard that names individuals isn't a useful product — it's a liability. Four rules govern every deployment:
- Aggregation floor. No insight is computed from fewer than five individuals. Smaller teams roll up.
- No per-person disclosure.The dashboard's deepest unit of analysis is a role within a team. Never a named person.
- Data minimization + discard.Per-person raw signal is parsed, aggregated, then discarded on a rolling 30-day window. We don't retain individual-level inputs.
- Audit trail. Every output is traceable to the source we ingested and the methodology version applied. Reproducible for your legal and audit functions.
Methodology and privacy policy are open: /methodology · /privacy.
Join the business waitlist
We're onboarding a small cohort of design partners through Q3 2026. Drop your work email and we'll reach out to scope.
Prefer a direct line? Email hello@wagecore.ai with company size and the question you're trying to answer. We respond inside 24 hours.
FAQ
- Is this software, consulting, or both?
- Software. Wagecore for Business is a per-seat SaaS subscription. You connect your tools, see the dashboard, pay monthly. The optional audit engagement add-on for the design-partner cohort is a manual analyst pass on top — useful early on while we learn what to surface, but not the product.
- Do you need our employees to fill out a questionnaire?
- No. The dashboard reads from artifacts your company already produces — JDs, tickets, calendars, optionally activity sampling. Adoption signals are opt-in 15-second submissions employees can run from their personal Wagecard, never required.
- If the methodology is open, why pay?
- The formula is open so you can audit reasoning. The data — capability matrix refreshed monthly against three frontier models, salary benchmark integrations, cross-industry adoption distribution, industry-standard score — is what you're paying for. Reproducing it internally runs $300–500k/year in eval and data licensing alone, and the cross-industry signal isn't reproducible at all from inside one company.
- What if our JDs are out of date?
- Common. We flag stale JDs (typically anything not updated in 18+ months) and use ticket-system + calendar signal to fill gaps. The dashboard shows the basis for each inference.
- Does this work for non-knowledge-work roles?
- Methodology is calibrated for knowledge work first — engineering, product, design, marketing, ops, support, sales, finance. Operations and field roles ship in the Q4 2026 matrix update. We won't surface insights for populations the methodology can't defend yet.
- Can we run this against a competitor's org?
- No. We won't connect to an org without its consent. Data ingestion requires authenticated access to your own systems.