All documents
Working document / September 2026

Pilot & learning log

A proposed four-week experiment: nine finished stories, a realistic view of the workload, and a decision about what comes next.

Proposed pilot practice. Edit together before use. Worksheet entries stay in this tab; print to preserve completed notes.

06 / The first month

Earn the right to grow.

A proposed four-week pilot: nine finished pieces, three per series. Use it to test the format and your ability to work together.

WhenWorkOwner roleReady when
Week 1
Align
Choose direction, cap time and cash, assign owners, recruit adult guests, rehearse the interview.Producer + editorial leadBriefs, guest expectations, permission process, and shoot plan are ready.
Week 2
Record
Plan recording for all three series, including three short fashion-location visits. Check sound before each conversation.Host + camera/soundEnough usable material for three honest stories per series.
Week 3
Edit
Cut nine episodes, preserve context, verify checkable claims, complete guest review.Editor + editorial leadEach piece passes the publishing checklist.
Week 4
Publish & learn
Release at a manageable cadence; review audience response and actual production time.Publishing lead + teamA written continue, revise, or pause decision, with one clear reason.

What to measure

Track completion and average watch time alongside video length; saves and shares per view where available; comments describing a useful takeaway; guest comfort feedback; and total hours per finished piece.

Record results at consistent intervals, such as 48 hours and seven days. Nine videos provide early learning, not proof of audience demand. Agree your time and cash limits before filming.

How an agency emerges

Use the strongest pilot work as a portfolio. Proposed first paid offer: one discovery session, one interview shoot, three short edits, captions, and one revision round.

Choose price after measuring pilot labor, direct costs, and capacity. Expand into recurring people-led series when the work is repeatable. Keep paid commissions visibly distinct from independent editorial interviews.

Founding-team decisions to document

Who owns the name, accounts, raw footage, and finished work? Who can commit spending? How are expenses reimbursed, labor recognized, and revenue shared? Who has final editorial responsibility? What happens when someone leaves?

Capture your intended answers in the charter before taking paid work. This package covers creative and operational formation; it does not establish a legal entity, clear the Aurora name, or create a legal agreement.

Episode tracker

EpisodeStory focusOwner / record dateReview / permissionPublish / lesson
SFI 01To assignTo assignPendingPending
SFI 02To assignTo assignPendingPending
SFI 03To assignTo assignPendingPending
SYW 01To assignTo assignPendingPending
SYW 02To assignTo assignPendingPending
SYW 03To assignTo assignPendingPending
WIW 01Market / occasion rouletteTo assignPendingPending
WIW 02After-work / one-swap remixTo assignPendingPending
WIW 03Art night / outfit backstoryTo assignPendingPending

Capacity before pricing

Log actual hours for recruiting, preparation, travel, recording, editing, captions, revisions, and publishing. Add direct expenses separately. Compare the total with your agreed weekly availability and pilot cash cap.

Pricing worksheet: estimated labor hours × agreed internal hourly cost + direct expenses + contingency = estimated delivery cost. Set the quoted price above cost at a margin the team deliberately chooses. This is a planning formula, not a market rate.

Retrospective / 45 minutes

  1. Watch the strongest and weakest piece from each series.
  2. Describe what worked using the actual story and edit.
  3. Review participant feedback and any unresolved concerns.
  4. Compare effort, direct costs, and audience usefulness signals.
  5. Decide continue, revise, or pause for each series.
  6. Assign one change and one owner for the next batch.
Suggested continuation gate: the team can deliver consistently inside its agreed capacity, every released piece passes the editorial gate, and the team can point to concrete usefulness feedback. If evidence is thin, run another bounded test rather than declare success.

Working notes