The following describes SlayCorp's proprietary delivery methodology — the operational practices SlayCorp deploys independently to produce the contracted outcomes. Nuclearn.ai does not direct these activities; it receives their outputs. SlayCorp manages prioritization and sequencing of work necessary to produce the contracted deliverables. Baselines will be established within the first 30 days by mutual agreement. Performance against these metrics will be reported at the 90-day review and at engagement close.
| Activity | How SlayCorp Operates | How We Measure Improvement |
|---|---|---|
| Live Implementation Leadership | SlayCorp's delivery methodology requires direct engagement with at least one active nuclear facility implementation within the first 90 days. SlayCorp manages requirements gathering, hardware coordination or cloud provisioning, IT integration, and go-live as part of its standard implementation practice — applying its methodology end-to-end to produce a completed, validated go-live as a contracted outcome. | Days from kickoff to go-live, per deployment model. Baseline pulled from last 6–12 completed implementations at engagement start. Target: 20–30% reduction in average TTV by Month 6. |
| Cross-Functional Delivery Cadence | SlayCorp's implementation methodology includes a structured cross-functional coordination cadence — a weekly sync SlayCorp designs, facilitates, and owns across Engineering, Infrastructure, Security, and Customer Success, including the customer's IT counterparts where applicable. SlayCorp produces the agenda, maintains the action log, and manages the escalation path as part of its delivery practice. | Count of open cross-functional blockers per week. Mean days to resolve. Target: 40% reduction in open items within 60 days of cadence launch. |
| TTV & Scope Tracking | SlayCorp applies a scope confirmation checkpoint at every implementation kickoff as part of its standard delivery methodology. SlayCorp independently maintains a sold scope vs. delivered scope tracker per project and produces variance reporting as a contracted output. | % of implementations closing at full sold scope. Scope variance rate by project. Target: reduce scope slippage by 25% over the engagement term. |
| Customer Onboarding Satisfaction | SlayCorp's delivery methodology includes a post-go-live feedback loop — a structured survey and debrief process SlayCorp designs and administers independently at the close of each implementation. SlayCorp analyzes findings and incorporates them into its own playbook iteration cycle. | CSAT score at go-live. % customers completing onboarding within the target window. If no baseline exists, the first 90-day cohort establishes it. Target: measurable improvement by Month 6. |
| Security & Procurement Cycle Management | SlayCorp's implementation methodology includes facility-specific security and IT procurement cycle mapping — a process SlayCorp applies independently at project initiation to identify review timelines, build compliance milestones into project plans, and proactively engage customer IT security stakeholders. | % of implementations where security or procurement review caused a go-live delay. Target: eliminate security/procurement-caused delays as a top-3 TTV driver within 6 months. |
| Continuous Integration Enrollment | SlayCorp's post-go-live methodology includes a structured customer transition process — a handoff practice SlayCorp develops and deploys independently to move completed implementations into the continuous integration program. SlayCorp produces the enrollment session and confirms data integration milestones with the customer. | % of go-live customers enrolled in the continuous integration program within 30 days of go-live. New expansion opportunities surfaced per cohort. Target: first cohort enrolled within 90 days of framework delivery. |
| Playbook Adoption & Iteration | SlayCorp deploys a playbook orientation as part of its standard implementation methodology onboarding — a structured knowledge transfer SlayCorp designs and delivers independently to Engineering and Customer Success within the first 60 days. Playbook iteration is driven by SlayCorp's own retrospective practice. | % of new implementations started on-playbook. Playbook iteration frequency. Target: 100% of new implementations on-playbook by Month 3. |
SlayCorp will produce and deliver a performance dashboard covering these metrics on a cadence SlayCorp determines appropriate — no less than monthly. The dashboard is a contracted deliverable issued to Nuclearn.ai's designated leadership contacts.