The question of what to delegate and what to keep is one I get asked in almost every new client conversation, and most of the time it’s not phrased that way. It comes through as: "I’ve been thinking about getting help but I’m not sure what I actually need." Or: "I hired a VA for three months and it didn’t really work." Or, most honestly: "I know how to do all of this. I just can’t do all of it anymore."
Author marketing delegation is not a question of capability. Almost every author I work with could, in theory, run their own ARC campaign, write their own captions, build their own email sequences, and manage their own launch calendar. The question is whether doing those things themselves is the best use of the time they have, and whether the quality holds when they’re doing it in the margins of everything else.
The answer is rarely obvious, which is why it’s worth thinking through properly rather than defaulting to "hire for everything" or "do it yourself until you can’t."
What tends to break first
The first sign that the DIY model is failing is usually not quality. It’s lateness. The ARC reader gets a reminder email that goes out four days later than it should because the author was in edits. The newsletter misses its send window because something happened during launch week. The caption bank runs out in week two of a six-week campaign and everything goes dark. None of these failures are dramatic. They’re just the accumulated cost of fitting marketing into the gaps around the actual work of writing.
When I look at a launch that underperformed relative to the book, the culprit is often something in this category. Not a bad strategy, not a weak ARC team, not the wrong platforms. A good plan that was executed in fragments because the author was also trying to finish book three.
The second thing that breaks is judgment under pressure. This is harder to see coming. An author who is calm and thoughtful in a planning conversation can become reactive during launch week: responding to an ARC reader complaint in a way that escalates rather than resolves it, or pulling a social post that wasn’t actually a problem because they’re exhausted and anxious. The decisions that get made at 11pm during a launch week when the author has been on for twelve hours are rarely the decisions they’d make with fresh eyes.
These are not personal failures. They’re capacity problems. And capacity problems are worth treating as practical business questions.
The things worth keeping
There’s a category of work that only the author can do, and it’s worth being specific about what it actually is, because it’s smaller than most authors think.
The author’s voice in their own newsletter, where they’re speaking directly to readers who subscribed because of them specifically. The creative direction decisions: what tone a campaign should have, what images feel right, what the caption should be about even if someone else writes it. The relationships with ARC readers who have been with them across multiple books and who expect to hear from the author personally. The strategic calls: when to move a release date, whether to go wide or stay in KU, how to price a series starter.
These are genuinely not delegatable without losing something real. An author assistant can send a newsletter but cannot write it in a voice that sounds like the author, unless the author has put in the work of documenting that voice so precisely that another person can approximate it. That’s possible, but it’s its own project.
What’s often kept by default, without much thought, is everything else. The BookFunnel setup. The ARC sign-up form and the sequence of emails that go out to readers after they claim a copy. The reminder sequence in week three. The caption bank for the six weeks following release. The tracking sheet for who has posted reviews where. This work is not uncreative, but it’s procedural enough that it can be briefed clearly and executed by someone other than the author without the author losing anything that matters.
The things worth delegating
The best candidates for delegation are tasks that meet three criteria: they can be briefed with enough specificity that someone else can execute them without constant check-ins, they’re genuinely time-consuming, and they don’t require the author’s voice or creative judgment at the point of execution.
ARC campaign logistics are the clearest example. The author needs to make decisions about timing, reader selection criteria, and review targets. Once those decisions are made, the setup and execution, the emails, the reminders, the tracking, the reader communication when someone hasn’t posted, is procedural. It’s also the part that tends to leak most badly when authors are managing it themselves during the sprint of a launch.
Caption writing is more nuanced. The brief has to be specific enough that the output sounds like the author, not like a generic author marketing account. When this fails, and I’ve seen it fail, it’s usually because the brief was too vague. The author said "write captions for my romance release" without specifying tone, what they’re comfortable talking about personally, what they won’t say, or what the campaign is actually trying to do. The captions that come back are technically competent and completely generic, and the author ends up rewriting them anyway, which defeats the point.
The delegation of the execution only works when the author has done the upstream creative work clearly enough to hand it off.
Where it goes wrong
The most common failure mode I see is authors who delegate before they’ve built the brief infrastructure to support it. They hire a VA, hand over a vague sense of what they need, and then spend the first month in a feedback loop of corrections that costs more time than it saves. After a few months of that, the conclusion is "I tried getting help and it didn’t work," when what actually happened is that the author needed to document their voice and their process before the help could be useful.
The second failure mode is authors who try to delegate judgment. Not execution, judgment. They want someone else to decide whether a reader’s review is worth following up on, whether a caption idea is on-brand, whether a promotion is worth running. These are decisions that require knowing the author’s books, their positioning, their reader relationship, and their risk tolerance. They’re not things that can be handed off until the relationship is long enough and documented enough that the person doing the work genuinely understands the context.
This doesn’t mean delegation is impossible or inefficient. It means the prep work is part of the work.
A practical frame
Before deciding what to delegate, it’s useful to run through the last three months of marketing tasks and sort them into two lists. The first: things you did that only you could have done. The second: things you did that could have been briefed clearly to someone else. The ratio is usually more surprising than authors expect. The second list tends to be longer, and a significant portion of the tasks on it are the ones that ate the most time.
That’s where the delegation conversation actually starts. Not with "what do I need help with" in the abstract, but with a specific accounting of where the time is going and which of those tasks have clear enough requirements that someone else could execute them without checking in constantly.
If you’re looking at that second list and thinking about what it would take to hand those tasks off well, get in touch. That’s the kind of problem worth working through with someone who has built those systems before.
At Literary Inspired, I work with indie and traditionally published fiction authors to build marketing that fits the book, not a template, whether that’s ARC campaigns, launch planning, or the systems behind it. That work spans YA, children’s, NA, romance, contemporary, romantasy, fantasy, paranormal, thriller, and beyond. If you want a second set of eyes on your setup, get in touch.
