How a request becomes a scene

A thing people don't quite believe: the requests get read. All of them. By me. There is no assistant.

What people also don't know is what happens next, which is why most requests arrive in a shape I can't do anything with. So here's the pipeline, honestly, from the message to the scene.

Stage one: is it a request or a fantasy?

These feel the same to write and they are completely different to receive.

A fantasy is a description of a feeling. "I want to see you with someone who's really into it." That's not nothing — it's actually useful — but there's no scene in it yet.

A request is a description of a thing that could be filmed. A setup, a dynamic, a specific moment. "The bit where she's still deciding" is a request. It's small, it's concrete, and I know what the camera does.

Most of what arrives is the first kind, and my job at this stage is to translate. The good news for anyone writing to me: you do not need to be a director. You need to tell me what you actually want to feel, and let me work out where to stand.

Stage two: can it be made, with who

This is where most ideas die, and almost never for the reason people assume.

They don't die because they're too filthy. They die because they'd require a person who hasn't consented to be in them.

I shoot with a specific group of collaborators, each of whom has a lane, limits, and a say. A request that involves a dynamic somebody isn't into is not a request, it's a suggestion that I go pressure a colleague. It gets a no, and it gets one instantly, and honestly it doesn't feel like a hard decision.

So the real gate is: does this map onto something one of my collaborators actually wants to do? When it does — and it does more often than you'd think — the idea has a real chance. When it doesn't, no amount of enthusiasm from the requester moves it.

The second gate is whether it's legal and clean: it needs paperwork, it needs everyone tested and current, it needs to be a thing I can put my name and my custodian statement on. Anything that can't survive that is not a scene, it's a liability with a plot.

Stage three: the money conversation, if it's a custom

If it's a custom — something made for one person rather than the catalogue — this is where it becomes a transaction, and where I'm deliberately unromantic.

A deposit holds it. Not because I think you're going to vanish, but because some people do — enough that deposits are standard practice in this business — and a custom is a real day of real work with a real collaborator who gets paid whether or not you're still excited about it next week. The deposit is the point at which an idea becomes a commitment, and both of us find out something true.

Scope gets written down. What's in, what's out, how long, when it lands. Pricing isn't a mystery and I'd rather have that conversation in one clear message than discover a mismatch after it's shot.

And if I can't do it, you get told, quickly, and you get your money back. A slow no is worse than a fast one.

Stage four: it becomes a shoot day

At which point it stops being a request and becomes exactly what I described in the anatomy of a shoot day: agreements, testing, a location, a conversation, and a long day that produces a short scene.

The person who requested it won't see any of that. They'll see the finished thing, weeks later, and odds are they won't recognise it as theirs, because what they described was a feeling and what they'll get is a scene, and those look different even when the second is a faithful rendering of the first.

What actually gets made

The requests that turn into scenes have almost nothing in common with what people assume works.

Specific beats over extreme acts. The most-requested things are rarely the most-shot things, because "more extreme" is easy to type and hard to build a scene around. A precise small moment is worth ten escalations.

Dynamics over positions. Who wants what, who's deciding, who's watching. That's what the work I do is actually about, and it's what people are usually reaching for even when they write it as a list of acts.

Things one of my collaborators is genuinely into. This is the whole ballgame. The scenes that land are the ones where somebody actually wanted to be there, and you can't fake that, and it means the best requests are the ones that give a performer something she wants to do rather than something she'd tolerate.

So: send it

The pipeline is real and it isn't a void. Requests get read, the buildable ones get in line, and what makes one buildable is usually not what the sender thought was its strongest feature.

Tell me what you want to feel. I'll work out where the camera goes.

Customs and the direct line run through my platforms.

— Sly