Oral-history consent edition manager

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.

1. Pick the riskiest assumption. Here: will community oral-history publishers use it to solve "interview permissions differ across public and restricted editions"?
2. Build only what tests it. One team, one use case, a few core modules. People do the rest by hand for now.
3. Run a paid pilot. Agree the acceptance criteria, input limits and reviewer responsibilities before starting.
4. Measure, then decide. Track permission mismatches and narrator review completion. Then expand, change course or stop, with evidence instead of opinions.

MVP scope for this solution. Costed pilot: Permission tracking; no publication without rights confirmation. Start with one buyer organization and a bounded set of representative inputs. Implement the first two modules: link consent versions; mark restricted passages. Support the third task through an assisted review queue: track narrator corrections. Handle the remaining required functions manually until validated. Include input upload, source references, user correction, a reviewer approval step and export of narrator-approved edition permissions record. 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 narrator-approved edition permissions record, automate compare edition contents; flag unapproved uses; export edition manifests. 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. Permission tracking; no publication without rights confirmation.

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: Permission tracking; no publication without rights confirmation.

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 two editions from consented excerpts and the defined narrator-approved edition permissions record. Record actual review effort before offering a recurring allowance. The commercial pilot fee is distinct from the platform development budget.

Message to test

Respect narrator-specific permissions across publication versions. Demonstrate the result with prepare two editions from consented excerpts for community oral-history publishers. Use a concrete before-and-after example without promising unmeasured savings.

Where to find buyers

Community archives and oral-history organizations

Lead magnet

Prepare two editions from consented excerpts

The first 30 days

1. Week 1: interview five prospective buyers from community oral-history publishers and inspect how they handle interview permissions differ across public and restricted editions.
2. Week 2: prepare prepare two editions from consented excerpts using authorized or synthetic material.
3. Week 3: share the demonstration through community archives and oral-history organizations and seek one bounded paid pilot.
4. Week 4: measure permission mismatches and narrator review completion, 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 two editions from consented excerpts and deliver narrator-approved edition permissions record. Compare permission mismatches and narrator review completion 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

Permission mismatches and narrator review completion

Retention and expansion

Build repeat use around narrator-approved edition permissions record. Save approved configurations and review decisions with permission, revisit unresolved exceptions and show progress on permission mismatches and narrator review completion. 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 respect narrator-specific permissions across publication versions. 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 respect narrator-specific permissions across publication versions. 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 narrator facilitation and archive review. Track model usage, storage, reviewer minutes, exception handling and customer support per accepted deliverable.