
Lesson material provenance notebook
Track the origin of adapted teaching content.
- For
- Teacher resource teams
- Solves
- Adapted lessons lose original attribution.
- Delivers
- Lesson provenance register
- Built in
- about 5 weeks of creation time, MVP in 5 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 teacher resource teams, turn licensed materials and teacher edits into lesson provenance register.
- Link source passages.
- Record adaptations.
- Flag missing attribution.
- Link proposed outputs to original source records.
- Capture reviewer corrections and approval.
- Export a versioned lesson provenance register.
What goes in, what comes out
- Licensed materials
- Teacher edits
AI drafts, people review. Searchable structured library and data stewardship console.
- Lesson provenance register
How it works
The workflow
- InStart with
Licensed materials and teacher edits
- 1
The buyer creates a project
- 2
Supplies licensed materials and teacher edits
- 3
Confirms scope and access
- OutFinish with
Lesson provenance register
AI does the heavy lifting, people stay in charge
AI assists these bounded tasks: link source passages; record adaptations; flag missing attribution. Use only licensed materials and teacher edits and preserve uncertainty in lesson provenance register. 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: Brief and sources, Lesson material provenance notebook, Review and delivery. Use a searchable table or visual gallery with filters for the domain’s important attributes. Open each item into a detail drawer containing source records, ownership and history. Put proposed merges and field changes in a separate review queue. Provide a preview before any bulk export. Open with brief and sources; move into lesson material provenance notebook for the detailed task; finish in review and delivery for review and handoff. Show the source record, uncertainty and approval status beside each proposed output.
Accounts and administration
Record ownership, access permissions, change proposals, original-value retention, version history, review dates, bulk import/export and duplicate resolution. 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. Source systems, catalog exports and cloud file storage. Start with reversible CSV or file imports and validate identifiers before any direct writes. Begin with uploads and exports of licensed materials and teacher edits. 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
5 daysOne buyer segment, one recurring use case; first modules: link source passages; record adaptations. Manual review in the loop. Built by our AI software factory.
- 3
Paid pilot
6 daysAccounts, roles, review states, audit trail and the first integration, hardened for two to three paying pilot customers.
- 4
Full product
2 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 teacher resource teams use it to solve "adapted lessons lose original attribution"?
- 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 unattributed material items; reviewer correction minutes; buyer acceptance and repeat purchase. Then expand, change course or stop, with evidence instead of opinions.
MVP scope for this solution. Costed pilot: One organization, one defined input format and one representative pilot batch using licensed materials and teacher edits. Professional judgment, physical inspections, live external actions and production certification remain outside this prototype. Start with one buyer organization and a bounded set of representative inputs. Implement the first two modules: link source passages; record adaptations. Support the third task through an assisted review queue: flag missing attribution. Handle the remaining required functions manually until validated. Include input upload, source references, user correction, a reviewer approval step and export of lesson provenance register. 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 lesson provenance register, automate link proposed outputs to original source records; capture reviewer corrections and approval; export a versioned lesson provenance register. 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. One organization, one defined input format and one representative pilot batch using licensed materials and teacher edits. Professional judgment, physical inspections, live external actions and production certification remain outside this prototype.
What the build depends on. Stable identifiers, an agreed data schema, reversible imports, mapping review and source ownership. Data quality work can exceed model development effort. Obtain representative authorized inputs, an agreed review rubric and a buyer-side owner. Specific scope: One organization, one defined input format and one representative pilot batch using licensed materials and teacher edits. Professional judgment, physical inspections, live external actions and production certification remain outside this prototype.
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: link source passages; record adaptations. 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–$100 | $80–$160 |
| Full productabout 50 customers | $110–$210 | $350–$700 | $460–$910 |
Run it or resell it
For your own team
Teacher resource teams run it inside the business: licensed materials and teacher edits in, lesson provenance register 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
#918127 - accent
#545ec9 - surface
#f1efe4 - 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 500-2,500 for one collection cleanup and launch, followed by USD 100-500 monthly for maintenance within agreed record limits. Larger migrations and complex rights management are separately scoped. Prices are hypotheses. For this buyer, package the first sale around prepare a sample lesson provenance register from a small authorized set of licensed materials and teacher edits and the defined lesson provenance register. Record actual review effort before offering a recurring allowance. The commercial pilot fee is distinct from the platform development budget.
Message to test
Track the origin of adapted teaching content. Demonstrate the result with prepare a sample lesson provenance register from a small authorized set of licensed materials and teacher edits for teacher resource teams. Use a concrete before-and-after example without promising unmeasured savings.
Where to find buyers
Educator associations and specialist training providers
Lead magnet
Prepare a sample lesson provenance register from a small authorized set of licensed materials and teacher edits
The first 30 days
- Week 1: interview five prospective buyers from teacher resource teams and inspect how they handle adapted lessons lose original attribution.
- Week 2: prepare prepare a sample lesson provenance register from a small authorized set of licensed materials and teacher edits using authorized or synthetic material.
- Week 3: share the demonstration through educator associations and specialist training providers and seek one bounded paid pilot.
- Week 4: measure unattributed material items; reviewer correction minutes; buyer acceptance and repeat purchase, 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 prepare a sample lesson provenance register from a small authorized set of licensed materials and teacher edits and deliver lesson provenance register. Compare unattributed material items; reviewer correction minutes; buyer acceptance and repeat purchase 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
Unattributed material items; reviewer correction minutes; buyer acceptance and repeat purchase
Retention and expansion
Build repeat use around lesson provenance register. Save approved configurations and review decisions with permission, revisit unresolved exceptions and show progress on unattributed material items; reviewer correction minutes; buyer acceptance and repeat purchase. 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 useful niche taxonomy, customer-approved mappings and accumulated correction history that improve retrieval and reduce repeated cleanup. For this concept, accumulate permissioned examples and reviewer corrections around track the origin of adapted teaching content. The durable asset is reliable task-specific execution and trusted customer configuration, not access to a general-purpose AI model.
Alternatives and positioning
Spreadsheets, shared folders, existing asset or information management systems and manual data cleanup. Position this concept around track the origin of adapted teaching content. 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
Import cleanup, extraction, storage, indexing, steward review, duplicate investigation and recurring source updates. Initial validation additionally budgets for representative sample preparation, interviews with teacher resource teams, and buyer-side review of lesson provenance register. 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. One organization, one defined input format and one representative pilot batch using licensed materials and teacher edits. Professional judgment, physical inspections, live external actions and production certification remain outside this prototype. Require appropriate access and publication approval. Preserve source material, label AI drafts and make corrections traceable. Measure false positives and missed cases alongside speed.