Every so often, an ad lands in front of screenwriters with the confidence of a man wearing sunglasses indoors.
This time, the ad was for Quilty, an AI-powered script coverage tool promising “professional script coverage in minutes.” The offer was simple enough: upload a screenplay, get a free preview report, no credit card, no signup, and see what the machine thinks.
That is exactly the kind of thing The Writer’s Room exists to test.
So I uploaded my half-hour comedy pilot, The Final Countdown, and waited to see whether Quilty would behave like a useful first-pass reader, a digital fortune cookie with screenplay formatting, or a very confident assistant who just discovered the word “marketability.”
What Quilty Promises
The landing page makes a clean, tempting pitch: upload your screenplay and get a free coverage preview in a few minutes. The page promises a report with a logline, synopsis, character breakdown, market analysis, and a Quilty Score. It also emphasizes the writer-friendly hooks: no credit card, no signup, no AI training, confidentiality, and delivery in roughly four to five minutes.
That is a strong pitch because it hits several screenwriter pressure points at once. We want feedback. We want it quickly. We do not want to hand over a credit card just to discover the “free” part was doing a lot of interpretive dance. And many writers are understandably nervous about uploading unpublished material into anything AI-related.
Quilty also displayed updated Terms of Service language before continuing. The highlights were reassuring on their face: the writer keeps ownership of the uploaded work, the script is not used to train or fine-tune AI models, Quilty uses a limited license to process the material for analysis, and the analysis is informational only — not financial advice or a guarantee of commercial success.
That last part matters. The front-facing pitch says “professional script coverage.” The terms, more sensibly, say the results are informational tools. Those two ideas are not necessarily in conflict, but writers should notice the difference between marketing language and legal caution. One gets you to upload the script. The other reminds you not to mortgage the porch because a software platform liked your second act.
What I Submitted
For the test, I used my half-hour comedy pilot The Final Countdown.
The premise: the Four Horsepeople of the Apocalypse have been summoned to start the end of days, but they are not exactly operating at divine peak efficiency. Conquest is Victor, a corporate executive who treats world domination like a quarterly growth strategy. War is Rayna, a fighter who is perhaps a little too ready for the world to get violent. Famine is Paula, a food blogger whose relationship with hunger is both professional and apocalyptic. Death is Dylan, an 18-year-old slacker who is more moved by a butterfly documentary than by the end of the world.
Dylan is supposed to bring the apocalypse manual, the Book, to the others. Instead, after a collision on the street, his backpack gets switched with Alex, a petty thief who has been running from the police. Alex takes the wrong bag home and finds the Book inside.
That matters because Alex is not just a random thief. He is caring for Eli, his sick younger brother. When Eli has a breathing crisis and Alex has no medicine, no charger, and no good options, the Book opens on its own and offers him one word: “BREATH.” Alex uses it. Eli recovers. And somewhere else, something that should not have been opened starts waking up.
So this was not a straight drama, a conventional fantasy pilot, or a tidy three-act feature. It was an ensemble comedy pilot with supernatural rules, biblical absurdity, and an emotional subplot running under the jokes.
In other words: a pretty good stress test for AI coverage.
For the test, I used my half-hour comedy pilot The Final Countdown.
The premise: the Four Horsepeople of the Apocalypse have been summoned to start the end of days, but they are not exactly operating at divine peak efficiency. Conquest is Victor, a corporate executive who treats world domination like a quarterly growth strategy. War is Rayna, a fighter who is perhaps a little too ready for the world to get violent. Famine is Paula, a food blogger whose relationship with hunger is both professional and apocalyptic. Death is Dylan, an 18-year-old slacker who is more moved by a butterfly documentary than by the end of the world.
Dylan is supposed to bring the apocalypse manual, the Book, to the others. Instead, after a collision on the street, his backpack gets switched with Alex, a petty thief who has been running from the police. Alex takes the wrong bag home and finds the Book inside.
That matters because Alex is not just a random thief. He is caring for Eli, his sick younger brother. When Eli has a breathing crisis and Alex has no medicine, no charger, and no good options, the Book opens on its own and offers him one word: “BREATH.” Alex uses it. Eli recovers. And somewhere else, something that should not have been opened starts waking up.
So this was not a straight drama, a conventional fantasy pilot, or a tidy three-act feature. It was an ensemble comedy pilot with supernatural rules, biblical absurdity, and an emotional subplot running under the jokes.
In other words: a pretty good stress test for AI coverage.
What Came Back
The preview came back in about three or four minutes, which is close to what Quilty advertised.
The follow-up email was also more measured than I expected. It said: “You uploaded ‘The Final Countdown’ for a free Quilty preview. The first pass is ready. Open the preview to see the logline, genre read, and the comparable films our model picked. It is a first pass, not a verdict.”
That last sentence is doing a lot of responsible work. “It is a first pass, not a verdict” is exactly how this kind of tool should be framed. A fast AI read may be useful. It may even catch real issues. But it should not be treated like a producer just leaned back in a leather chair and announced the fate of your career.
The free preview included a logline, genre read, comparable films, character notes, structural comments, market-style positioning, and several locked sections encouraging an upgrade to the paid report.
That is not automatically sinister. Free previews are designed to sell paid products. That is how free previews work. The fair question is whether the free version gives enough real value to evaluate the tool, or whether it mostly exists to wave a velvet rope in front of a writer’s anxiety.
What Quilty Got Right
To Quilty’s credit, the preview was not nonsense. That is a low bar, but in the world of instant AI analysis, it is still a bar worth clearing.
It understood the broad premise of The Final Countdown. It recognized that the pilot is about a group of modern Horsepeople trying to start the apocalypse after losing the Book, while Alex, the petty thief who accidentally ends up with it, opens it for personal reasons. That is the spine of the pilot, and Quilty did not miss it.
It also seemed to understand the tone better than I expected. The script is built around the absurd collision of biblical prophecy and modern incompetence: trumpets bought from a music store, bowls of wrath purchased at a dollar store, apocalyptic figures arguing like people trapped in a bad group project. Quilty did not treat the material like straight horror or solemn fantasy. It recognized the comedy engine.
Some of the notes were fair, too. The preview flagged the ending as compressed, and I can see that. The final pages move quickly from Alex using the Book to help Eli, his sick younger brother, to the realization that something larger and more dangerous has been opened. For a pilot cliffhanger, that speed may be acceptable. As a craft note, though, “this ending moves fast” is not wrong.
The preview also pointed out that Alex and Eli’s story runs somewhat separately from the Horsepeople plot until the final stretch. Again, that is a fair observation. The two threads connect through the backpack switch and the Book, but emotionally, they are operating in different lanes for much of the pilot. That may be intentional, but intentional does not mean invisible. If a reader feels the seam, it is worth looking at the seam.
Where Quilty Got Shaky
The shakier parts came when Quilty moved from summary into interpretation.
The preview identified Victor, the corporate-executive embodiment of Conquest, as the protagonist. I understand why it did that. Victor opens the script. He pushes the Horsepeople toward action. He is loud, organized, controlling, and wrong in entertaining ways.
But The Final Countdown is not really built as “Victor’s story.” It is an ensemble pilot. Victor is one major engine. Alex, the petty thief who ends up with the Book, is another. Alex’s relationship with Eli, his sick younger brother, gives the pilot its human stakes. That does not automatically make Alex the protagonist either, but it does mean the script is not as cleanly centered on Victor as Quilty suggested.
This is where AI coverage can get slippery. It often wants to identify the main character, the antagonist, the emotional arc, and the market lane as neatly as possible. That can be useful when the script wants to be neat. It can be less useful when the script is built around competing comic engines and a larger ensemble.
Quilty also described Dylan, the young slacker version of Death who loses the Book, as one of the weaker supporting characters. There may be a fair note hiding in there. Dylan’s motivation is less developed than Victor’s need for control or Paula’s food-based worldview. But Dylan’s function is clear. He is the keeper of the apocalypse manual, the reason the plot breaks, and the softest, weirdest contrast to what Death is supposed to be.
In other words, calling Dylan underdeveloped may be partly fair. Treating him as ineffective may be a miss.
That distinction matters. Good coverage should not just ask, “Does this character have a big emotional speech?” It should ask, “What job is this character doing in the script, and is the script using that job well?”
The AI Coverage Problem
The useful part of Quilty’s preview is that it was able to summarize the script and spot some real pressure points quickly.
The dangerous part is that it did this in polished coverage language.
That polish matters. A vague note from a person usually sounds vague. A vague note from software can arrive wearing a blazer. It can feel more authoritative than it deserves because the language is clean, organized, and confident.
This is not a Quilty-only issue. It is an AI coverage issue in general. These tools can be very good at recognizing patterns. They can tell you that an ending feels rushed, a subplot feels separate, or a character appears less developed than the others. Sometimes they will be right.
But screenplays are not just pattern-matching exercises. Tone matters. Format matters. Genre expectations matter. Pilot structure matters. Ensemble comedy especially depends on rhythm, contrast, escalation, and character function. A note can be technically plausible and still miss the actual job a scene or character is doing.
That is where writers need to keep their hands on the wheel.
Use AI coverage as a first pass if it helps. Use it as a mirror. Use it as a quick way to see what an outside reader might notice. But do not confuse speed with depth, polish with judgment, or a score with the actual future of a script.
The Paid Upgrade Question
The free preview also included locked sections pointing toward the paid report. That is expected. Quilty is a business, and the free preview is clearly part of the sales path.
The question is not whether the free preview is trying to sell the full report. Of course it is. The question is whether the free preview gives a writer enough useful information to decide whether the paid report is worth buying.
For me, the answer is: maybe.
The preview did enough right that I am not dismissing the paid version out of hand. It understood the premise. It recognized the tone. It flagged a couple of issues that are at least worth thinking about.
But I would not treat the preview as proof that the full report will offer deep story insight. A preview can show whether the tool is awake. It cannot prove whether the tool can think.
That is especially important because Quilty’s broader pitch uses words like professional coverage, market analysis, and scoring. Those phrases carry weight with writers. They suggest something more substantial than a quick summary. If the paid version is truly detailed, specific, and useful, that is worth knowing. If it is mostly the same kind of confident pattern-reading with more pages attached, that is worth knowing too.
For now, this review is only about the free preview. I may test the full paid analysis later. If I do, I will judge it as its own product, not as a promise hiding behind a locked button.
Questions Writers Should Ask Before Paying
Before paying for the full version of any AI coverage tool, writers should slow down and ask a few practical questions.
What exactly is included in the paid report that is not included in the free preview?
Is the analysis based on the full script, or is it mostly extrapolating from a faster first-pass read?
Are the notes specific to the actual script, or could they apply to almost any screenplay with the names swapped out?
Does the tool understand the format being submitted? A half-hour pilot should not be judged exactly like a feature. A comedy should not be judged exactly like a thriller. An ensemble should not be flattened into a single-protagonist template just because the software wants a clean answer.
What does the company do with uploaded scripts? Who processes them? Are third-party AI providers involved? Are scripts retained, deleted, stored, or used in any way beyond the analysis?
And maybe most important: does the report make you think more clearly about the script, or does it simply give you a score to feel good or bad about?
That last question matters because writers are vulnerable to numbers. A score feels objective. It feels clean. It feels like someone weighed your script on a deli scale and handed you the truth by the pound.
But story judgment is not that simple. A score can be useful as a quick signal. It should not become a substitute for taste, craft, experience, or a reader who understands what the script is actually trying to be.
Verdict
Quilty’s free preview was not junk. That may be the most interesting thing about it.
It understood the basic premise of The Final Countdown. It recognized the comic-apocalyptic tone. It flagged a couple of real craft questions, especially around the compressed ending and the separation between the Horsepeople plot and the Alex/Eli emotional thread.
That is useful.
But the preview also showed the limits of fast AI coverage. It seemed eager to impose a clean protagonist framework on an ensemble pilot. It made some character judgments that were plausible, but not necessarily deep. And like a lot of AI-generated analysis, it sounded very polished even when the underlying point needed a little more humility.
So my verdict on the free preview is this: useful as a first-pass mirror, dangerous as a final authority.
For writers, Quilty may be worth testing if you want a fast outside read and you understand what you are getting. It can help you see whether your premise is landing, whether your tone is legible, and whether a machine trained on story patterns notices pressure points you may want to revisit.
But do not mistake “fast” for “wise.” Do not mistake “organized” for “professional judgment.” And definitely do not let a score, whether high or low, boss you around like it paid rent.
The free preview made me curious enough that I might test the paid report later. That is a point in Quilty’s favor. It did not make me confident enough to say writers should pay for it without hesitation. That is the caution.
For now, Quilty’s free preview lands in the category of: interesting, potentially useful, not a replacement for experienced human feedback, and worth approaching with your writer brain fully plugged in.
Bottom line: I would use Quilty’s free preview the way I would use a quick hallway conversation after a reading. Listen carefully. Take notes. Pay attention when something stings because it might be true. Then go home and decide what actually belongs in the script.
Be First to Comment