Analyse whether Daskerel is ready for learners, labs, teams, and employers.

Current evidence

• Account, dashboard, study planner, skill assessment, tracks, labs, feedback, and support routes exist.
• Language and button-fit fixes have improved the front-door learning flow.

Ready signals

• Learners can find a path, start a plan, launch a lab, and report friction without staff intervention.
• Repeated learner issues are visible to management through the feedback queue.

Improve next

• Run mobile and desktop learner journey checks before each launch cycle.
• Use feedback trends to remove repeated friction from onboarding, labs, translations, and checkout.

Current evidence

• AWS, Azure, and Google Cloud lab pool routing exists in code and planning documents.
• Africa, Americas, Europe, and global routing concepts are represented in the multi-cloud lab plans.

Ready signals

• Real learner lab sessions are distributed across approved accounts, subscriptions, projects, and regions.
• Dashboards show active sessions, failed provisioning, cleanup, quota pressure, and regional demand.

Improve next

• Run concurrency simulations and real smoke tests against production lab pools before public launch.
• Add monitoring evidence for active sessions, cleanup success, cost, and regional saturation.

Current evidence

• HMRC VAT registration is approved from 13 July 2026; the live Stripe account has an active GB registration and default invoice VAT ID, while checkout remains gated for MTD evidence and owner VAT-readiness approval.
• Live production deployment remains paused while tax and billing readiness are resolved.

Ready signals

• Stripe Tax has an active registration, production secrets are configured, and checkout smoke tests pass.
• Refund, Direct Debit, billing portal, invoice, and entitlement flows are verified end to end.

Improve next

• Replace the generic Stripe fallback tax code with owner-approved, evidenced product classifications, then complete MTD, invoice, refund, reconciliation, and owner VAT-readiness approval before accepting live payments.
• Re-run checkout, webhook, billing portal, and entitlement smoke checks after configuration changes.

Current evidence

• Owner, privacy, terms, refunds, security, IP, partnership, Teams, employer-use, and vendor-independence policies are visible.
• Employment, contractor, confidentiality, data-protection, and IP assignment draft PDFs exist for review.

Ready signals

• Learners, teams, employers, partners, and staff can see responsibilities before payment or collaboration.
• High-risk contracts and public claims are routed through owner/legal review before signature or publication.

Improve next

• Ask a solicitor to review employer, partner, employment, contractor, data-protection, and IP templates.
• Add a separate employer partnership agreement PDF when the commercial offer is ready.

Current evidence

• Provider roadmaps, certification coverage, source-review queues, and learning-material comparison reports exist.
• AWS, Azure, Google Cloud, and wider provider paths are represented across tracks and reports.

Ready signals

• Every track has a review owner, source date, gap list, and next update action.
• Mock exams and lab tasks remain aligned to current vendor objectives and practical job outcomes.

Improve next

• Keep official-source review cadence visible in the content quality dashboard.
• Prioritise high-demand tracks and stale certification objectives for review before marketing pushes.

Current evidence

• Post-lab feedback, course ratings, NPS-style scoring, bug/friction reports, and translation reports exist.
• Management can review feedback records, repeated issue patterns, priority, owner, and SLA context.

Ready signals

• Repeated problems are grouped and assigned to the right service owner.
• Improvement actions are visible in management review, not lost in support inboxes.

Improve next

• Review feedback weekly during launch preparation and daily during the first live cohort.
• Track top recurring friction themes and close them with release notes or runbook updates.

Current evidence

• Teams quote, billing-owner visibility, named learner seats, invitations, team materials, and manager reporting are represented.
• Partnership and employer-use clauses explain party responsibilities, evidence limits, lab controls, data, IP, branding, and public claims.

Ready signals

• A team can request a quote, receive approved checkout, invite learners, and understand evidence/reporting boundaries.
• Employer claims and proof packs stay separate from exam guarantees, hiring guarantees, and vendor endorsements.

Improve next

• Create the separate employer partnership agreement PDF before active partner sales.
• Run a pilot cohort with clear onboarding, reporting, support, billing, and evidence-review ownership.

Current evidence

• Google Workspace SSO/MFA, delegated management roles, access review, audit logs, service dashboards, and runbooks exist.
• Owner-only record reset controls and urgent notification routes are represented in management tooling.

Ready signals

• Each service role can see its assigned work, handoffs, response risk, and escalation path.
• Owner review catches broad access, stale users, password fallback risk, and sensitive operations.

Improve next

• Keep quarterly owner acknowledgement active and test break-glass access before enforcing SSO-only production mode.
• Add trend charts once enough production audit, feedback, case, and incident history exists.