PPerfectstory

Invite-only screenplay workspace

Perfectstory

Know what to rewrite next. Diagnose story problems with evidence, turn them into scene-level tasks, and get back to the page.

P

THE SALT LINE

Starter screenplay · calculated story model

Health33Readiness192C7W · 4N
Scene 4Draft 3

EXT. RIOS RANCH - IRRIGATION DITCH - DUSK

Rows of almond trees, half of them the color of paper.

DELL

Forty acres last spring. Ninety now.

SAM FERRO, 19, drags a hose past them, coughs into a bandana, folds it before anyone can see the color.

Evidence, not vibes

Notes a writer can inspect and act on.

These are real findings from the included starter screenplay. Doctor explains why the warning exists, what triggered it, and where the evidence lives.

Subplot "Sam's lungs" never resolves

set up p.8

Trigger

Subplot Sam's lungs has no resolution scene.

Evidence

Setup scene 4, page 8. The script never answers whether the valley admits Sam was poisoned.

Answer it, or cut the setup so the audience never asks.

Tension plateaus for 6 scenes

p.18-36

Trigger

Six consecutive scenes stay within one tension point.

Evidence

Scenes 7-12 hold tension values of 7, 8, 7, 7, 8, and 6.

Raise one scene, drain another, or cut the middle.

Act 1 runs long by 8%

23pp · 33%

Trigger

Act 1's page share differs from its target by eight percentage points.

Evidence

23 pages across eight scenes: 33% actual versus a 25% target.

Review the two weakest scenes in Act 1.

A closed rewrite loop

From diagnosis to changed pages.

01

Diagnose

Find structural, pacing, continuity, and draft-state problems with the evidence attached.

02

Create the work

Convert a useful warning into a rewrite task tied to the scenes that need attention.

03

Rewrite

Open the relevant scene with one clear objective, then return to Doctor when the draft changes.

Built for serious work in an honest beta.

Your screenplay stays yours

You retain ownership of the drafts and story material you bring into Perfectstory.

Controlled beta access

Workspace access is invite-only, with authenticated routes and project-level ownership checks.

Clear infrastructure

Supabase supports authentication and data infrastructure. Resend handles product email delivery.

Product suggestions are editorial aids, not guarantees of quality or commercial outcome. Keep independent source copies of your work.

FAQ

Before you bring in a draft.

Does Perfectstory write my screenplay for me?

No. Perfectstory identifies story risks, shows the evidence behind them, and turns findings into concrete rewrite work. The writer decides what changes and writes the pages.

How does the Doctor decide what to flag?

Doctor rules inspect the project model and screenplay metrics, including unresolved threads, pacing patterns, act proportions, character continuity, and draft state. Every finding exposes its reason, trigger, evidence, and a suggested next action.

What happens to dismissed feedback?

A writer can dismiss, downgrade, or restore a finding. That feedback is retained so repeated review stays relevant instead of presenting the same unwanted note as new information.

Is the private beta a confidential storage service?

No. The beta uses access controls, but it is not a confidentiality or archival service. Do not upload highly sensitive material, and keep your own source copies.

How do I get access?

Request an invite with a short note about your current writing workflow. Beta requests are reviewed manually, and approved testers receive a Supabase invitation by email.

Bring the draft you are actually wrestling with.

Private beta requests are reviewed manually. Tell us what you write and where your current rewrite process breaks down.

Request invite