
School device reuse academy
Combine device-specific training with documented reuse readiness.
- For
- School IT educators
- Solves
- Reusable devices are retired because staff lack practical refurbishment guidance.
- Delivers
- Supervised device reuse learning pack
- Built in
- about 5 weeks of creation time, MVP in 6 days
- Investment
- $12,000 for the MVP, $41,000 for the full product
- Run it
- Inside your business, or as part of your offer to clients
What it does
For school IT educators, turn approved device manuals and inventory snapshots into supervised device reuse learning pack.
- Identify supported device families.
- Draft approved checklists.
- Teach data-wipe verification.
- Record supervised practice.
- Flag unsupported repairs.
- Export reuse plans.
What goes in, what comes out
- Approved device manuals
- Inventory snapshots
AI drafts, people review. Role-based learning platform and course authoring console.
- Supervised device reuse learning pack
How it works
The workflow
- InStart with
Approved device manuals and inventory snapshots
- 1
The buyer creates a project
- 2
Supplies approved device manuals and inventory snapshots
- 3
Confirms scope and access
- OutFinish with
Supervised device reuse learning pack
AI does the heavy lifting, people stay in charge
Retrieve approved steps and highlight model-specific differences. Keep model suggestions separate from verified facts. Link factual outputs to authorized input evidence and show missing information explicitly. Use deterministic checks for counts, dates, identifiers and arithmetic where applicable. A designated reviewer validates consequential outputs and signs off the delivered result.
What your team sees
Key screens: Device pathway, Guided lesson, Completion evidence. Provide a learner home with the next useful lesson, a practice activity and progress evidence. Give authors a source-linked course editor and assessment review queue. Supervisors see completed tasks and explicit sign-offs. Use short modules that work on mobile as well as desktop. Open with device pathway; move into guided lesson for the detailed task; finish in completion evidence for review and handoff. Show the source record, uncertainty and approval status beside each proposed output.
Accounts and administration
Learner enrollment, content versions, assessment review, role pathways, accessibility options, supervisor sign-off, progress records and source update alerts. Include organization-scoped access, named project owners, review queues, usage limits, export history and retention settings. Never reuse private customer material for other accounts without permission.
Integrations and data access
Learning resources, course portals and educator review processes. Learning portals, employee or member directories and completion exports. Validate standards and identity requirements before promising native LMS compatibility. Begin with uploads and exports of approved device manuals and inventory snapshots. Any named system or connector is a candidate requiring current access and compatibility checks; no live connection is included by default.
How we build it
We build with our own AI software development factory, so most implementations take days to a few weeks of creation time, not months. You see working software at every step, and exact timing depends on availability.
- 1
Scoping call
Day 1Thirty minutes on your process, your data and how you want to run it: for your own team, or for your clients. You get a fixed scope and price for the MVP.
- 2
MVP
6 daysOne buyer segment, one recurring use case; first modules: identify supported device families; draft approved checklists. Manual review in the loop. Built by our AI software factory.
- 3
Paid pilot
7 daysAccounts, roles, review states, audit trail and the first integration, hardened for two to three paying pilot customers.
- 4
Full product
3 weeksSelf-serve onboarding, billing, monitoring and the wider integration set.
- 5
Run and improve
MonthlyWe host, monitor and improve it for a fixed monthly fee, or hand it over to your team. How the retainer works.
Why we start with an MVP
An MVP, or minimum viable product, is the smallest version that your users can actually work with. It is not a cheap version of the full solution. It is a test, built to answer the questions that decide whether the rest is worth building.
- Pick the riskiest assumption. Here: will school IT educators use it to solve "reusable devices are retired because staff lack practical refurbishment guidance"?
- Build only what tests it. One team, one use case, a few core modules. People do the rest by hand for now.
- Run a paid pilot. Agree the acceptance criteria, input limits and reviewer responsibilities before starting.
- Measure, then decide. Track verified reusable devices and task completion quality. Then expand, change course or stop, with evidence instead of opinions.
MVP scope for this solution. Costed pilot: Training only; certified electrical repairs excluded. Start with one buyer organization and a bounded set of representative inputs. Implement the first two modules: identify supported device families; draft approved checklists. Support the third task through an assisted review queue: teach data-wipe verification. Handle the remaining required functions manually until validated. Include input upload, source references, user correction, a reviewer approval step and export of supervised device reuse learning pack. Authentication, account isolation, deletion controls and basic operational logging are included. Specialized production certification, live write integrations and broader rollout are not included unless explicitly stated.
After the MVP. After paying customers repeatedly accept supervised device reuse learning pack, automate record supervised practice; flag unsupported repairs; export reuse plans. Add one tested read integration, reusable customer configuration and scheduled repeat delivery. Increase supported formats or teams only when evaluation cases and reviewer capacity cover the new scope. Training only; certified electrical repairs excluded.
What the build depends on. Clear objectives, licensed or approved sources, validated assessments, learner state and source-change tracking. Media and accessibility requirements affect production effort. Obtain representative authorized inputs, an agreed review rubric and a buyer-side owner. Specific scope: Training only; certified electrical repairs excluded.
Investment
A planning range to start the conversation, not a quote. You pay per phase, so you can stop after the MVP.
- Phase 1
MVP
One buyer segment, one recurring use case; first modules: identify supported device families; draft approved checklists. Manual review in the loop.
- Phase 2
Paid pilot
Accounts, roles, review states, audit trail and the first integration, hardened for two to three paying pilot customers.
- Phase 3
Full product
Self-serve onboarding, billing, monitoring and the wider integration set.
Indicative total, MVP to full product$41,000about 5 weeks of creation time · start with the MVP from $12,000
Running costs per month
A rough indication of monthly hosting and AI model costs once it is live, not tested. Real costs depend on usage, file sizes and the models chosen.
| Stage | Hosting and infrastructure | AI usage | Total per month |
|---|---|---|---|
| MVP and paid pilotabout 3 customers | $30–$60 | $50–$110 | $80–$170 |
| Full productabout 50 customers | $110–$210 | $420–$840 | $530–$1,050 |
Run it or resell it
For your own team
School IT educators run it inside the business: approved device manuals and inventory snapshots in, supervised device reuse learning pack out, reviewed by your people.
As part of your offer
Agencies, consultancies and software companies can offer it to their own clients under their brand. We build and maintain it; you sell and deliver it.
Your brand, or this one
Run it under your own brand, or start from this concept style.
- primary
#8c9127 - accent
#7b54c9 - surface
#f0f1e4 - ink
#22201e
- Headings
- Sora
- Text
- Work Sans
- Voice
- Encouraging, patient, precise
Selling it to your own clients: the go-to-market playbook
Pricing to test
Test USD 750-3,000 for one custom learning pathway, then USD 10-40 per active learner monthly with a minimum account fee. Public memberships may use lower fixed subscriptions. Prices are experiments, not benchmarks. For this buyer, package the first sale around train staff on one device family and the defined supervised device reuse learning pack. Record actual review effort before offering a recurring allowance. The commercial pilot fee is distinct from the platform development budget.
Message to test
Combine device-specific training with documented reuse readiness. Demonstrate the result with train staff on one device family for school IT educators. Use a concrete before-and-after example without promising unmeasured savings.
Where to find buyers
School IT networks and education sustainability groups
Lead magnet
Train staff on one device family
The first 30 days
- Week 1: interview five prospective buyers from school IT educators and inspect how they handle reusable devices are retired because staff lack practical refurbishment guidance.
- Week 2: prepare train staff on one device family using authorized or synthetic material.
- Week 3: share the demonstration through school IT networks and education sustainability groups and seek one bounded paid pilot.
- Week 4: measure verified reusable devices and task completion quality, review delivery effort and ask for a repeat purchase. This is a validation schedule, not a promise that the full product can be built in thirty days.
Paid pilot
Agree the acceptance criteria, input limits and reviewer responsibilities before starting. Run train staff on one device family and deliver supervised device reuse learning pack. Compare verified reusable devices and task completion quality with the buyer's current process on comparable cases; include corrections, missed issues and reviewer time. Seek payment and repeat use. Stop or revise the scope if data access, accuracy or unit economics fail.
Success metrics
Verified reusable devices and task completion quality
Retention and expansion
Build repeat use around supervised device reuse learning pack. Save approved configurations and review decisions with permission, revisit unresolved exceptions and show progress on verified reusable devices and task completion quality. Offer a recurring volume allowance after repeat demand; expand to adjacent tasks only when the buyer asks and delivery quality remains acceptable.
Why clients would pick it
A reviewed niche curriculum, realistic practice tasks and evidence of useful learning outcomes in a defined role. For this concept, accumulate permissioned examples and reviewer corrections around combine device-specific training with documented reuse readiness. The durable asset is reliable task-specific execution and trusted customer configuration, not access to a general-purpose AI model.
Alternatives and positioning
Courses, internal trainers, learning management systems and static training documents. Position this concept around combine device-specific training with documented reuse readiness. Compare it against the customer's current process on the same representative task. This is proposed differentiation; no exhaustive competitor study or uniqueness claim has been established.
Main delivery costs
Instructional design, subject review, media production, assessment validation, learner support and content refreshes. Initial validation additionally budgets for test devices and IT educator review. Track model usage, storage, reviewer minutes, exception handling and customer support per accepted deliverable.
Safeguards
Use educator-reviewed content and answer keys. Apply appropriate access and consent for learner records and distinguish completion from demonstrated learning. Training only; certified electrical repairs excluded. Require appropriate access and publication approval. Preserve source material, label AI drafts and make corrections traceable. Measure false positives and missed cases alongside speed.