Nexford University
Nex-OSv26.27-93888
Every domain of Nexford University — designed around AI-first workflows.
Ask NexusWorQ
Internal

Nexford University, operated AI-first.

Nexford exists to deliver superior learner outcomes at a fraction of the cost of traditional universities. Nex-OS is how we get there at scale — a complete redesign of how the university operates, built from scratch around AI-first workflows.
The moat

The data flywheel no one else can build.

A structural competitive advantage that compounds with every learner, every assessment, and every cohort.

Nexford will have the most granular, live, employer-anchored dataset of which teaching and assessment approaches actually develop which workplace capabilities — at scale, continuously refined by AI and human learning design expertise.

This dataset is the moat. The longer Nex-OS runs, the deeper it becomes.
Employer-anchored by design

Every CLO, every assessment, every curriculum decision traces back to what employers actually observe and hire for. WAM maps 152 capabilities to the ESCO v1.2.1 skills taxonomy. CLO-level curriculum mapping — linking each course learning outcome to specific WAM capabilities — is now live and under active review.

Grading is evidence collection

Every graded submission — reviewed by Nexus, confirmed by a human evaluator in GWorQ — generates a structured evidence record: which capabilities the learner demonstrated, at what Bloom's level, on which assessment. This is the raw material for the learner capability profile, the risk score, and personalised coaching. No one else grades this way.

No one else can build this

Tools like Sofia and CourseLoop generate curriculum from content. They have no employer anchor, no live performance feedback loop, and no standardised skills layer. This dataset — capability evidence per learner, per assessment, linked to employer demand — compounds with every cohort. It cannot be replicated without years of operating history.

Northstar metric
Number of active learners
A lagging indicator that only moves when the full customer lifecycle pipeline is working. It cannot be gamed by optimising one stage. Everything built within Nex-OS is in service of this number.
Product-led growth
The product earns acquisition.

The current sales-led model cannot scale to 10× active learners at acceptable CAC. The target is product-led: learners who achieve their goals refer others; employers who see outcomes recommend Nexford; alumni who advance become the most credible proof point the business has. Every domain is a PLG lever. The primary metric tracking progress is learner referral rate — it must consistently increase.

Goal-anchored model
The goal is not graduation. It is the career outcome the learner enrolled to achieve.

From the first admissions touchpoint, the system captures the learner's current skills baseline and stated career goal. Every subsequent communication, intervention, and academic nudge is anchored to that goal — not course completion for its own sake. A learner completing a module is shown how it moves them closer to where they want to be, not congratulated for an administrative milestone.

The lifecycle

Six lifecycle domains. One unbroken chain.

A breakdown at any stage is visible in the metric chain and traceable to the responsible domain.

1
Marketing & Growth
Product-led growth is the long-term path to 10× active learners. Every enrolled learner who achieves their goal is a marketing asset. The experience drives acquisition.
Lead volume
Referral rate
Brand awareness
2
Enrollment
Owns the lead from first contact through application submission. The quality of pipeline management here directly determines CAC downstream.
Lead → application rate
CAC
Pipeline velocity
3
Admissions
In Build
Evaluates applications against accreditor-defined requirements. An academic function — the integrity of this stage is an accreditation obligation, not just an operational one.
Time-to-decision
Document completeness
Compliance rate
4
Learner Success
In Build
Owns two parallel mandates: persistence (orientation through graduation) and career enablement (skills-to-role mapping, coaching, job search). Career connectedness drives persistence — learners who see a direct line to their goal stay enrolled. Three factors predict persistence above all others: self-confidence (early wins that build belief), community (peer belonging and cohort connection), and career connectedness (visceral belief that this program leads somewhere specific). The single biggest lever on active learner count and lifetime value.
90-day persistence
CRC
Month-1 completion
Career Readiness Progression
In-Program Career Engagement
5
Registrar
In Build
Governs academic standing, dismissals, appeals, records, and credential issuance. The integrity layer — every learner outcome accurately recorded, every departure handled within policy.
SAP compliance rate
Credential turnaround
Appeal resolution time
6
Graduate Outcomes & Alumni
The proof of the mission. Outcomes data feeds back to Marketing — the compounding loop that makes product-led growth work over time.
Graduation rate
Goal achievement
Alumni NPS
Workplace Alignment Model

The employer demand layer.

WAM is what makes every curriculum decision traceable to a real employer signal, not an academic assumption.

What it is

WAM is Nexford's employer-demand intelligence layer. It captures skill signals from job vacancy data, industry reports, professional body standards, and labor market databases — then maps them to observable employer capabilities and the ESCO v1.2.1 skills taxonomy.

Every CLO and MLO in the curriculum is traceable through this chain: capability → ESCO skill → employer demand signal → WAM source. This makes program gaps detectable and redesign priorities evidence-based rather than assumption-driven.

How it differentiates Nexford
Nexford + WAM
Curriculum decisions anchored to live employer demand signals — what skills employers actually hire for, continuously updated.
Sofia / CourseLoop
Generate curriculum from existing content and learning objectives. No employer anchor, no performance feedback loop, no skills taxonomy.
Traditional course design
Subject-matter expert judgment. Updated annually at best. No systematic employer signal or performance validation.
The flywheel

A self-reinforcing loop. Every cycle makes it stronger.

Employer demand flows in at the top. Learner performance data flows back out at the bottom. The gap between them is where Nexford improves — continuously, at scale.

01
Employer Demand
Live skill signals from job markets, industry reports, and labor data (WAM)
02
Capabilities
Observable can-do statements extracted from demand signals
03
ESCO Skills
Capabilities mapped to 14,257 standardised skill concepts
04
Curriculum Design
CLOs and MLOs aligned to the capability → skill chain
08
Gap Signals
Under-performing capabilities surface as redesign priorities
07
Capability Scores
CLO performance mapped back to employer capabilities
06
Learner Performance
Submission data, rubric scores, CLO demonstrations at module level
05
Assessments
AI-led build anchored to the demand → curriculum chain
Every graded submission feeds three outputs: a risk score to Learner Success, capability evidence to the learner profile, and a redesign signal to Curriculum — the loop compounds continuously
The intelligence layer

Every graded submission produces three outputs.

Grading is not the end of the assessment — it is the evidence collection event. Each submission, reviewed by Nexus and confirmed by a human evaluator in GWorQ, generates structured data that feeds three domains simultaneously.

01Learner Risk Score
→ Learner Success

Submission quality signals — pillar scores, attempt velocity, time between submissions — aggregate into a per-learner per-course risk score. Learner Success uses this for proactive outreach prioritisation: who needs a check-in before they disengage.

02Capability Evidence
→ Faculty & AI Coach

The written response is semantically matched against WAM capabilities — identifying which employer-recognised skills the learner demonstrated, at what Bloom's level. This builds the learner's capability profile across every assessment, every course, over their full programme.

03Learner Capability Profile
→ Coaching · Career · AI Coach

Aggregated across assessments and courses, the profile surfaces a learner's areas of strength, development, and gap relative to their stated career goal. Faculty use it for coaching. Career coaches use it for skills-to-role mapping. The AI Coach uses it for personalised learning recommendations.

Learning Design
Live

AI-led assessment build and delivery platform. assessments live on Canvas with AI grading and grade passback. Part of the Academic Domains layer — curriculum quality, learning design, and accreditation — which runs in parallel with the lifecycle chain rather than as a stage within it.

Enabling domains

Infrastructure the lifecycle runs on.

No lifecycle domain operates without these. They are not pipeline stages — they are the substrate.

7Product

Learner experience design across platform and curriculum. Courses treated as products with retention and referral metrics. Drives PLG mechanics across the lifecycle.

8Data & Intelligence

Central data layer powering every domain. Personalization engine, AI decision feeds, at-risk signal aggregation, and labor market intelligence. Every domain depends on this.

9Technology & Platform

HubSpot, Canvas, API infrastructure, LMS evolution, internal tooling. Owns the connective tissue between systems — no manual hand-offs.

10Financial Operations

Revenue, billing, financial aid, CAC/LTV/CRC measurement, and payback period tracking per segment. Financial dismissal is a shared signal with Learner Success.

Design constraints

These are not guidelines.

Every workflow, tool, and domain is built against them.

We are not automating what we currently do.

We are redesigning what we do, then automating it. AI-assisted means bolting AI onto existing workflows. AI-first means starting from what AI makes possible and building the workflow around it. The output difference is not incremental.

The measure of success is metric movement, not efficiency.

Operating more efficiently without moving the core metrics delivers no value. Every system, every workflow, every AI action built within Nex-OS is evaluated against one question: did the metric move?

AI acts first. Always.

AI initiates the work. It takes the first action, makes the first assessment, produces the first output. Humans do not initiate workflows AI could initiate. If a human starts something a system could start, that is a design failure.

Human judgment stays in the loop.

Every decision Nexus makes that exceeds its authority goes to WorQ — the Human Judgment Queue — before it takes effect. AI speed, human accountability. Neither is compromised.

Systems trigger humans. Humans do not manage systems.

Human involvement is triggered by the system — not by a team member deciding to check something. When a human is needed, the system surfaces exactly what they need to act: the context, the AI's recommendation, the supporting data, and the decision options. Human attention is a scarce resource. The system manages it.

Rules get codified. Binary decisions get automated.

If a human is making a decision based on a fixed rule, that decision belongs to the machine. If-then logic is never a human task. Learners are empowered to self-serve in real time rather than waiting for a human to execute a rules-based approval. Human memory is a point of failure. Codified rules are not.

Build status

Where we are.

Live
Learning Design
— assessments live with AI grading and Canvas grade passback. GWorQ (faculty/evaluator grading layer) live. WAM CLO-level curriculum mapping active. Capability evidence layer wiring in progress.
In Build
Process Intelligence
Admissions, Learner Success, and Registrar intake forms active — mapping current operations before automating.
Designing
Lifecycle Automation
Enrollment pipeline, at-risk detection, SAP automation, intervention workflows.
Vision
Full Nex-OS
All lifecycle and enabling domains operating AI-first across the university.
Questions about any domain?

Nexus has the full brief in context. Ask it anything — domain scope, metrics, how the pieces connect, or where to focus your work.

Ask Nexus →