Review draft. This invitation and its proposed agreement are being revised. Please share questions; do not sign the draft or send a screenplay yet.
For screenwriters · A personal invitation
I’m King, the developer behind ReelMetrics. I’m building this on the side, without outside funding, and getting ready for a private alpha. Now I need a writer willing to help me take the next step.
There’s a lot of work behind the software already. But to test it properly and show people what it produces, I need real writing that its owner has agreed to let me use.
ReelMetrics uses AI. I know that can make a request like this a difficult one to consider. Your screenplay represents your imagination, your time, and work that matters to you. You deserve to understand what happens to it—and to see the result before deciding how far you want to participate.
What the tool actually does
ReelMetrics does not tell you whether your screenplay is good or bad.
It helps producers explore the genres a screenplay draws on, possible audiences, and comparable films that could inform how they position a project. Those are useful questions to work through when bringing a story to market.
The analysis is an interpretation. It can get things wrong. It doesn’t predict a film’s success, and it doesn’t measure the creative worth of your writing. The people making the film still make the decisions.
See your report. Then decide.
First, we would agree in writing to a limited private evaluation. I would then arrange delivery of your screenplay and give you the official ReelMetrics Producer’s Report for your screenplay. You would see that report before choosing either of the ongoing permissions below.
With your approval, selected excerpts could be used as test material in our private code repositories. Real scenes help us check parsing, scene handling, and report generation as the software changes.
You’re more than welcome to review the exact excerpts and intended tests before approving their use. This would include private GitHub storage and automated testing, under the agreement’s limits.
With your permission, I want to put your screenplay’s Producer’s Report in front of every producer I possibly can. Your work could become the example I use to show what ReelMetrics can do.
You would review the actual example before it is shared.
A straightforward exchange
Each contributor would receive an official ReelMetrics Producer’s Report, exploring their screenplay’s genres, possible audiences, and comparable films through a producer’s lens.
ReelMetrics grew out of a manual analysis process used in Hollywood—work that took two people about two weeks to complete. I’m bringing that structured approach into software. AI helps analyze and classify the material, while defined calculations and comparisons shape the results. The purpose is to help producers understand how a screenplay might be positioned—not to judge whether it’s good or bad.
Participation would be voluntary and unpaid. You would keep ownership of your screenplay and remain free to sell, option, or license it elsewhere. For any approved public example, you could choose credit or anonymity.
If you’re curious how your screenplay looks through a Hollywood-style market analysis, this is your chance to see.
If you’re curious, I’d welcome a conversation. Ask about the software, the AI involved, the report, or the terms. Tell me what would make you comfortable—and what wouldn’t.
Know a writer with a finished screenplay they might let us use? Please send them this link. Thanks for helping me get the word out.
— King
The commitment, plainly
Public examples: you could withdraw permission at any time. We would stop showing or distributing them on notice and promptly remove the copies we control. The proposed agreement gives us no more than two business days to finish that removal.
Private test excerpts: either side could cancel. The proposal gives us up to three years after cancellation notice to replace already approved test material and end its active use. We could not add more of your writing or expand its uses during that period.
That is a long replacement window, and I want it to be clear before you consider participating. It starts when notice is received: cancel in year five, and the deadline would be year eight. It does not apply if you only authorize the initial report.
Old copies could remain in restricted repository history and its backups afterward, but could not keep being used for tests, analysis, or public examples. We would not promise to erase every historical copy. That archival exception would not be permission to keep using your writing forever.
These are proposed terms for review. The full draft explains the narrower initial evaluation, cleanup periods, and suspension for rights or confidentiality problems.
Email [email protected]. A little about yourself and the kind of screenplay you have in mind is plenty for a first message. Please don’t attach the screenplay.
We would review the rights and both sign a finalized initial evaluation agreement before arranging delivery. This page has no upload or submission form. The current draft is for discussion, not signature.
Project update ·
I’m preparing for a private alpha and looking for writers interested in contributing a finished screenplay. The participation agreement is still a review draft. I’ll post updates here as the project moves forward.
The draft proposes a 60-day permission to analyze the identified screenplay and deliver your report. Either side could end it earlier. It would not allow repository test fixtures, public use, or model training. After it ends, working copies would be deleted within 30 days and ordinary backups would expire within 90 days, subject to legal holds and material you separately approved for another use. No new analysis would be allowed during cleanup.
If you cancel before a report is completed, or a rights issue requires us to stop, we would stop. A further whole-screenplay report after the evaluation period would need a fresh written permission or extension. There is no monthly quota or lifetime-access commitment.
The analysis uses external AI services, including OpenRouter and the model provider serving the request. Private use does not mean the text stays entirely on our equipment. The proposed agreement requires confidentiality, limited-purpose processing, and verified provider terms and controls prohibiting their own model training before we process your work. Those checks must be completed before intake; the draft itself is not proof they have passed.
A complete feature screenplay whose rights you control, a U.S. Copyright Office or WGA Registry number with a copy of the certificate or confirmation, and a signed chain-of-title declaration. Every co-writer or other required rightsholder would need to consent and sign.
The declaration asks about prior options, sales, assignments, commissions, exclusive submissions, third-party material, and other restrictions or consents. Registration supports provenance; it does not by itself prove all the rights are clear.
This is not an offer of representation, employment, screenplay acquisition, or production. There is no promise of a sale, commercial success, or paid work. The included report is the stated benefit. Any future payment or different arrangement would need a separate written agreement.
Initial evaluation comes first. Schedule A covers rights and chain of title; Schedule B is the optional permission for selected private test excerpts; Schedule C is the optional approval of specific public examples. Public withdrawal and private-test cancellation are separate choices.
Review draft—not for signature and not legal advice. The legal licensee, liability/remedies, governing law, and other final terms still need to be settled. Get independent legal advice before signing a final agreement. This proposal does not change any existing signed agreement.
When you email, we receive your address and the information you choose to send. Our Privacy Policy describes the current service; a licensor-specific notice and these proposed retention terms must be aligned before screenplay intake.