Ask most edtech companies whether they’re ready for outcomes-based contracting, and they’ll point to their efficacy study. That instinct makes sense — it’s the evidence they already have. But an efficacy study and an OBC-ready number are answering two different questions. A study usually asks whether typical use of your product produced a positive result. A contingent-payment contract asks something narrower and more specific: exactly how much use, for exactly which students, is required to hit exactly the result you’re being paid on.
What Does OBC Ask That a Typical Study Doesn’t?
Most efficacy studies report an average effect: students who used the product gained more, on average, than students who didn’t. That’s genuinely useful evidence, and it’s the backbone of ESSA tier ratings. But an average effect doesn’t tell a district’s compliance office what they actually need for a contingent-payment clause — a threshold. How many minutes a week, or sessions a month, does it take to reliably see the promised gain? Below that threshold, is there still a meaningful effect, or does the whole case collapse?
That’s a dose-response question, not a does-it-work question, and it requires a different kind of analysis — one that compares outcomes across levels of usage rather than just comparing users to non-users.
What Does This Kind of Analysis Actually Look Like?
LXD Research has run this exact design before, outside of any OBC context, because districts and product teams have always wanted to know whether “more use” meant “more results.” A retrospective study of a math platform examined 667 students in a California district — 91% Hispanic, 89% socioeconomically disadvantaged — comparing classrooms with high usage (averaging 19 sessions) to classrooms with low usage and to comparison schools. The high-usage classrooms gained nearly double on the state assessment. That’s a dose-response finding: not just “it worked,” but a specific usage level tied to a specific result, on a specific population, on a specific test.
That’s the number an OBC contract actually needs. Not “does it work,” but “at what dose, for whom, measured how” — because that’s the sentence a contingent-payment clause has to be written around.
That Classtime analysis wasn’t a special OBC engagement — it’s a standard Lookback Study, the same service LXD Research runs to build ESSA Tier II and III evidence from data a company already has. Starting at $15,000, it’s the natural first step toward an OBC-ready number: no new data collection, no district recruitment, just a rigorous look at the usage and outcome data already sitting in your existing implementation.
One Population, One Assessment Isn’t a Readiness Number — It’s a Starting Point
Here’s the nuance that gets skipped in most readiness conversations: a dose-response number that holds for one population, on one assessment, doesn’t automatically hold everywhere else a district might want to apply it. The 19-sessions-to-double-gains finding above was measured on one state test, with a student population that was heavily Hispanic and heavily low-income. Would the same threshold hold for English learners specifically? For a norm-referenced assessment instead of a state test? For a rural district instead of an urban one? Maybe — but “maybe” is not what belongs in a contract a district’s legal team is reviewing.
This is exactly why the question deserves to be answered before a contract gets signed, across more than one population and more than one assessment — not discovered midway through a contingent-payment period, when a missed target becomes a dispute instead of a data point.
Compares outcomes across levels of engagement within an existing implementation — the direct way to isolate a dose-response threshold from data that already exists. Runs as a Lookback Study, starting at $15,000.
Where an OBC contract ties eligibility or intervention to a cutoff score, this design measures the outcome specifically around that cutoff — the same logic the contract’s payment trigger will use. Runs as a Real-Time Efficacy Study, $40,000–$80,000 depending on scope.
This isn’t a theoretical fit. WestEd’s own evaluation of OBC relied on regression discontinuity wherever a district’s eligibility cutoff — a proficiency threshold on a prior assessment — was applied cleanly enough to support it. Where eligibility and actual participation didn’t line up closely, the evaluators couldn’t use RDD at all, and had to fall back on weaker, non-causal comparisons instead. That’s a direct, real-world illustration of the point above: the same threshold logic that defines who’s eligible for an OBC-funded intervention is what makes or breaks the ability to measure its impact rigorously.
The honest version of “readiness”: knowing your dose-response number for the one population you’ve already studied is a head start, not a finish line. Checking it against the populations and assessments a specific district is likely to ask about is the part that actually derisks the contract.
Does an Existing ESSA Tier II or III Study Give You a Head Start?
Yes, genuinely — just not on every part of what OBC requires. If you’ve already run a Tier II or III efficacy study, you’ve done real work that transfers: you’ve defined a specific student population precisely enough to survive outside review, and you’ve picked and defended an independent outcome measure. Those are exactly the “clearly defined population” and “clearly defined outcomes” domains in the Center for Outcomes Based Contracting’s Standards of Excellence framework. A company with no prior efficacy work is starting those conversations from zero; a company with a Tier II or III study is not.
What doesn’t transfer automatically is the payment structure itself. An ESSA study is retrospective and evaluative — it tells you what already happened. An OBC contract is prospective and financial — a specific number gets written into a legal document, and money moves based on whether it’s hit. Structuring that contingent-payment mechanism, and building the mutual-accountability and continuous-improvement checkpoints around it, is contract and governance work, not research design work — and it’s worth being clear-eyed about which side of that line any given task falls on.
| What You Might Already Have | What OBC Adds on Top |
|---|---|
| A validated, independent outcome measure | A specific usage threshold tied to that measure, checked across populations |
| A precisely defined student population | Confirmation the same relationship holds for the subgroups a district will ask about |
| A completed efficacy study | A contingent-payment structure and mutual-accountability terms built around it |
The overclaim to avoid: a single dose-response study, on one population, is not the same thing as OBC readiness — the same way a single-site pre/post study was never enough to clear an ESSA tier bar. The gap between “we have a number” and “we have a number that holds up under scrutiny” is exactly where these contracts get negotiated, or fall apart.
Why Might a Dose-Response Number Take Longer Than a Year to Trust?
There’s a risk in how OBC contracts tend to get structured around a single school year, especially for the intervention-level students these contracts usually serve: students who start furthest behind often need more than one implementation cycle before a real gain clears the noise of ordinary year-to-year test variation. The WestEd evaluation ran into a direct example of this: one district’s tutoring intervention was delayed during contracting and ended up running for about two months instead of the intended twenty-five weeks, producing no detectable effect. That’s not necessarily evidence the program didn’t work — it’s evidence that a truncated dose, measured too early, can look identical to no effect at all.
There’s a second, harder problem sitting underneath the first, and WestEd’s own evaluators were candid about it: it’s difficult to fully separate whether the program worked from whether the extra coaching, monitoring, and district attention that comes with an outcomes based contract made the year go better regardless of the product. Districts under OBC get more structured implementation support than they typically would otherwise — which is part of what OBC is supposed to produce, but it also means a single year’s result reflects the whole system built around the contract, not the product in isolation.
The practical takeaway: a dose-response number that holds after one semester with an easy-to-reach population isn’t the same quality of evidence as one that holds after a full year or more with the below-proficiency students an OBC contract is actually likely to serve. Negotiating for more than one year of runway, and treating early checkpoints as implementation data to act on rather than a verdict on the product, is part of what “ready” should mean going into the contract — not just having the number in hand.
Do You Know the Dose Your Product Needs Across the Populations That Matter?
LXD Research offers a free consultation to help you figure out which path fits: a Lookback Study analyzing usage and outcome data you already have (starting at $15,000), or a Real-Time Efficacy Study built around your eligibility criteria (from $40,000). We’ll help you scope it to the populations and assessments a district is actually likely to ask about.
Schedule a Free Consultation View Our Services