What gStride Ships Today (and What's Next): 2026 Coverage Matrix

TL;DR — the short answer

• Today is real. The shipped column maps cell-by-cell to the live feature surface and the related blog references in this post. No vapour.
• 30-day items are committed. Each one is in active development with a target merge date inside 30 days of publication.
• 90-day items are explicit hedges. Where we say "evaluating in 90d" we mean the work is scoped but the ship decision is on the next quarterly review. Where we say "shipping in 90d" it is in active development.
• Anti-features are contractual. The five things we do not build are negative covenants in the master subscription agreement, not just marketing posture.
• The matrix is the contract before the contract. Roadmap-accuracy SLA with a refund clause sits in section 8.

Why publish a coverage matrix at all

Two of the last five founder-led discovery calls I ran stalled in late-stage evaluation because the buyer could not get a clear answer to one question: what does this product ship today, and what is on the roadmap? Both buyers had been burned before — one by a six-month migration that under-delivered, the other by a twelve-month rollout where the headline feature in the original demo was still in beta at the renewal. Both said, in different words, that they would rather see the gap written down than be sold a promise.

Most SaaS hides the roadmap behind some version of "trust us." The honest move is to publish the matrix on the same URL the procurement team can quote in the master subscription agreement, then update it every sprint and let the dateModified field be the audit trail. This page is the gStride version of that, mirroring the architecture we walk every buyer through in the four-layer AI workforce analytics pillar. If you printed a version older than 14 days, the cells you care about may have moved — request the current version via Cal before procurement closes.

The 4-layer coverage matrix

The heart of this post. Four rows — capture, signal, recommendation, action — mapped against three columns: shipped today, 30-day window, 90-day window. Anchored to the architecture described in Pillar #3 on AI workforce analytics.

The shipped column is the surface we walk through on every demo. The capture and signal rows lean on the productivity-monitoring and AI-assistance feature surfaces, the recommendation row on the manager-pulse and overrun affordances, and the action row on the timelines-approvals and payroll-payments flows. The deeper architectural reasoning behind why these four layers are the right shape is in Pillar #3; the deeper signal-list breakdown is in AI productivity scoring for remote employees.

What we do not ship (and will not build)

The interesting half of any honest coverage matrix is the column that does not exist — the things the vendor will not build. Five features are explicit anti-features in the gStride architecture. They are not absent because we have not gotten to them. They are absent because the category we are building does not include them, and bolting them on would damage the product. Framing them as a negative covenant rather than a missing feature is the part most buyers find unusually clarifying.

Compliance and procurement readiness

Most mid-market and enterprise procurement processes gate on the same handful of items: SAML SSO, SCIM provisioning, a DPA with Article 28 terms, an audit trail per access, a documented retention policy, and the relevant industry-specific certifications. The grid below is the current state, mapped against the same three-column shape as the architecture matrix.

The compliance row that matters most for August 2026 is the EU AI Act readiness column. The shipped-today posture covers the requirements for explainability, IC inspection rights, human-in-the-loop recommendation, and documented retention. The 90-day commitment is the full conformity-assessment bundle — the artefact set procurement teams in EU jurisdictions are starting to request as standard. The broader regulatory framing is in is employee monitoring legal in 2026.

Integrations matrix

Integrations are where most coverage matrices quietly evade — the vendor lists every logo they have ever touched and the buyer has to ask which ones are live, which are private beta, and which are aspirational. The grid below is honest about the distinction.

Vertical readiness

A platform that ships well on one vertical and badly on another is a normal mid-stage SaaS reality. The honest move is to publish which verticals the product fits today, which it can fit in 30 days with minor configuration, and which sit in the 90-day evaluation window because the vertical has structural needs we have not yet fully covered.

The verticals where today is real are the four ICP rows — IT services, BPO, agency, and engineering. The vertical guides for those segments — including the BPO India, manufacturing, and law firm guides — go deeper into the fit-and-gap analysis per segment. If your vertical is on the 30-day or 90-day row, the right conversation is on Cal, not in a procurement document yet.

What happens when we miss a roadmap commit

A coverage matrix without an accountability mechanism is marketing. The mechanism gStride attaches has three parts, all sitting in the master subscription agreement alongside the standard SLA. First, the roadmap-accuracy SLA: if a 30-day item slips beyond 45 days from publication, or a 90-day item beyond 120 days, the customer who signed on the strength of that commitment can request a pro-rata refund for the affected quarter on the dependent line items. The clause is a forcing function on us to either ship or de-commit early — not punitive.

Second, the public changelog. Every 30-day cell that ships gets an entry; every cell that is removed in a future matrix version gets a why-note (scope change, deprioritisation, re-scope). The audit trail of what was promised, shipped, and de-committed lives in one place and is queryable by name.

Third, the matrix is referenced in the MSA as the authoritative document for the customer's effective date. Shipped-column cells are warranted capabilities under the standard SLA. 30-day and 90-day cells are roadmap commitments under the refund clause. Anti-features are negative covenants — capabilities we contractually commit not to build during the term, including via acquisition.

A roadmap document the customer can quote in procurement is worth more than a sales-cycle slide deck, even when (especially when) the customer chooses to enforce the refund clause. That is the contract working as designed.

Five-question coverage test for buyers

If you read this far and you are evaluating any productivity intelligence or workforce analytics vendor — including gStride — the five questions below are the ones to put to your current vendor before you renew, and to any new vendor before you sign. They are designed to surface the gap between the demo and the shipped product, which is where most procurement decisions go wrong.

1. Where is your shipped-vs-roadmap matrix and when was it last reviewed? A vendor that cannot send you the URL by end of day is selling demos, not a product. The dateModified field on the page is the single most useful number you will see in the evaluation.
2. What anti-features have you contractually committed not to build? A vendor that has not written down the negative covenants is keeping the option to bolt on surveillance later. That option becomes a liability the moment EU AI Act enforcement starts, and it transfers to your procurement file.
3. What is your SLA on roadmap accuracy? If the answer is "we do our best" or "we have a quarterly review cycle," there is no SLA. A real SLA names the slip window, the refund mechanism, and the document that records both.
4. Which integrations are live versus which are private beta or aspirational? Ask for the same three-column shape as section 6 above. If the answer mixes them in a single logo grid, the vendor is hiding the gap.
5. For my specific vertical, where are you on the today / 30-day / 90-day grid? Vertical fit is the single biggest reason late-stage deals stall and the single biggest source of buyer's remorse 90 days post-signature. A vendor that cannot place themselves on the grid for your vertical is asking you to absorb the discovery cost.

Where this matrix connects to the rest of the gStride buyer surface

This page is one node in a longer chain. Architecture behind the four-layer matrix: Pillar #3 on AI workforce analytics. Enterprise scoring sub-layer for billable timesheet validation: Pillar #5 on enterprise AI timesheet scoring. Anti-surveillance framing for the anti-features section: Pillar #4 on the anti-surveillance productivity stack. ROI math against a 64-employee buyer scenario: ROI calculator. Pricing anchor: pricing page. EU AI Act conformity policy template: gStride playbook.

Frequently asked questions