Letters from a ttRPG Dev to a Freelancer, 1. Turnaround Times.
I recently moved toward the contract stage of a small project (1,500-2,500 words) with a new freelancer, and asked them what timeframe they thought would work for them as a deadline (so I could put it in the contract). Quite reasonably (especially given I had told the freelancer I was available for general industry questions), the freelancer wanted to know what kind of turnaround time was reasonable and typical in the industry. Also, how much back-and-forth was their going to be between the freelancer and myself, as that would impact their thinking on a deadline.
So, I wrote a short letter in response. It then occurred to me that this was exactly the kind of drill-down detail prospective and relatively new freelance ttRPG writers often ask about in seminars and such.
So I have copied it here, minus any identifying information and with a dab of editorial clean-up, as a generic “Letter from a ttRPG Dev to a Freelancer.” I might do more of these in the future, or this might just be a 1-off.
After a polite intro, I wrote:
“So, turnaround can vary wildly. At the “experienced freelancer” level, I normally expect someone to be able to produce a finished draft of 10,000 words per month, starting from the time they have a full outline (if needed) and contract. That’s assuming they aren’t doing this full time, and don’t have any other freelance assignments.
However, when I am working with a freelancer, it’s not really any of my business if they are doing it full time or have other contracts. I just offer a contact with a deadline, and see if they agree they can hit that.
There are freelancers I know quite well who can product 20k, 30k, or even 45k words in a month… but I try to never plan to need that. And, even those who can aren’t always free to do so when I have an emergency project. I also work with some people who can only manage 5k in a month, and only if the timing is right. But as long as they produce good work when they do take a contract, I can work around that.
When I personally began ttRPG writing in the mid-1990s, I averaged a mere 1,000 words in a month Luckily, I just did magazine articles at first, often with no set deadline. However, by the time I left Wizards of the Coast in 2001, after more than a year of full-time, in-house game writing, I was producing 40k-50k words per month as a freelancer. Now that I’m in my 50s, I can’t really keep that up anymore. 😛
Most developers/editors/producers assume newer writers need more time, and try to work around that. In this case, I *could* perfectly well give you 90 days to write this. Given it’s short length, I’d expect an experienced freelancer to be able to do it in 1-2 weeks, and a veteran to be able to do it in one day (if the timing is right and they can spare a day when I need it written).
I would expect anywhere up to 30 days for someone with very little experience, but honestly in my dealings it often seems most people who can’t do it in 2 weeks just can’t do it. That’s not being judgmental — some people just have too much going on in their lives to spend much time writing about imaginary magic creatures. And there ARE exceptions. So if you wanted to pad your time with this first project because it made you more comfortable, I’d be okay with that.
As a side note, never be afraid to tell someone offering you a freelance writing project up-front you can’t do it in the timeframe suggested. Also, if you want the job, feel free to tell them when you COULD have it done by. Something like “I love this idea, but my schedule wouldn’t allow me to get it back to you in 6 weeks. However, if you could extend the deadline to 9 weeks, I could accomplish that.” Missing a deadline after you say you can do it is bad, but telling people you can’t meet a deadline when turning down work is never seen as a bad thing. It’s usually taken as a sign you know your limits, and are thus more likely to be reliable.
(And missing a deadline after you agree to a job isn’t the end of the world, especially if there are extenuating circumstances. The most important things are to communicate with your developer early, and let them know if problems are growing. If you have 4 weeks for a project, and 2 weeks in you tell them “This is going slower than expected, can I have an extra week to get it done?” they may be free to give it to you. But if you tell them that the day before it is due, it both gives them much less leeway, and shows you haven;t been working on it throughout, or haven’t been tracking your progress. Even then, exigent circumstances CAN arise. I once had a freelancer tell me the day before their deadline they were going to be weeks late–because their home had been hit by a Category 4 hurricane. And, yeah, I could see how that would make delivery nearly impossible even if they were mostly done.)
(As a second aside, communication is important. Telling someone on the last day that you are giving up on a project and won’t be turning over any work for it at all is BAD, but not telling them that and not replying to their inquiries is still much worse.)
As for how much back-and-forth is needed, it’s a fine line. Especially for something short, if everything goes smoothly, you may do your work and send it to me without ever needing any other advice or input. However, if you aren’t sure if you are doing it right, or aren’t sure if an idea you have had fits what the person paying you wants, or want to change something from the pitch that was already agreed to, or can’t figure out how to write a rule or describe an issue or fix a plot hole, those are all great reasons to reach out to your developer and explain the issue and ask for feedback.
For bigger projects, there are often “milestones” where you are asked 1/2-way through the project’s writing time to show you have done 1/2 the work. And some projects later on where you are asked to work with multiple writers may have some forum or Discord channel set up where writers can brainstorm and bounce ideas off each other.
OTOH, the person paying you to write something normally doesn’t want to spend as much time answering your questions as it would take them to write it themselves.”
So, there’s some of the advice you might get from me, if I was contracting you to write for me.
Support My Patreon
The more support I get, the more time I can spend on writing things like this.
If you enjoy any of my articles, please sign up, for as little as the cost of one cup of coffee a month!