Scaling the Business

Growing Your Technical Writing Business Beyond Just You

Most technical writing businesses start as solo operations. You land clients, deliver projects, and build a reputation on the quality of your work. But there’s a ceiling to how much revenue you can generate when your time is the limiting resource. Scaling means moving from trading hours for dollars to building a business that generates revenue through systems, people, and recurring arrangements.

The path from one person to a functioning team isn’t automatic. You’ll need to recognize when you’ve hit capacity, build repeatable processes, and hire strategically. This section walks through what that progression looks like and where most technical writing businesses get stuck.

Stage 1: Maxing Out Solo

You know you’ve hit solo capacity when you’re consistently turning down work, missing deadlines despite working nights and weekends, or raising rates but still can’t keep up with demand. This is actually a good problem—it means your business is validated. But before hiring, spend 2-4 months optimizing what you’re already doing. Audit your current projects: which ones pay the best per hour? Which ones are the least interesting? Which ones could be systematized? Stop taking low-margin work and focus only on projects that justify your time investment. If you’re doing administrative work (scheduling, invoicing, email management), use tools like Zapier, HubSpot, or a basic CRM to automate it. If you’re writing at 40 billable hours per week, you’re probably spending 10-15 additional hours on things that don’t require your expertise.

Document your current workflow before it becomes someone else’s problem. Write down how you approach a client kickoff, how you structure research, your editing process, your revision protocols, and how you handle feedback. You’ll need these documents the moment you hire someone. Also measure your actual billable hours versus your total working hours. Most solo writers think they’re at 50 billable hours per week but are actually closer to 30-35 once you account for client communication, admin work, and downtime between projects.

Stage 2: Your First Hire

Your first hire should handle work that doesn’t require your client-facing presence. A junior technical writer, a content coordinator, or a project manager are common first hires depending on your bottleneck. If you’re drowning in revision cycles and back-and-forth communication, hire a junior writer who can handle first drafts, research, and initial formatting. If you’re spending time scheduling calls, tracking deliverables, and managing documents, hire a project coordinator. Avoid hiring your clone; hire for your weakest point.

Should you hire an employee or contractor? If you expect consistent 20+ hours per week of work and plan to scale further, hire a part-time employee. You’ll pay $18-28/hour for a junior writer in most markets, plus roughly 15-20% in taxes and benefits. If the work is irregular or project-based, use a 1099 contractor at $25-45/hour. Contractors are cheaper upfront and more flexible, but employees are more reliable for building a team culture later. Start with a contractor if you’re uncertain about the volume or your ability to manage someone.

Delegate research, formatting, first drafts, and client communication follow-up. Keep client discovery, complex technical problem-solving, and final review. Your reputation is tied to quality—you can’t fully delegate that yet. Budget $8,000-12,000 for a part-time junior hire in year one (accounting for onboarding, training, and management time). Many solo technical writing businesses see revenue jump 20-40% in the first year after hiring because they can finally say yes to more projects, but don’t expect that person to be profitable immediately. They’ll cost more in management time than they generate in revenue for the first 3-6 months.

Set clear expectations from day one. Define what “done” looks like for every task. Check in weekly. Assign work in batches, not one item at a time. Give real feedback—not “this is bad,” but “this section is unclear because the audience doesn’t know what an API is yet; add a definition before mentioning it.” A bad first hire experience often comes from unclear direction, not a bad hire.

Building Systems Before Scaling

Before you bring on a second or third person, document these systems:

• Client intake process—what information you need before a project starts, how you structure discovery calls, your intake form or questionnaire
• Project scope and estimation—how you estimate hours, how you structure timelines, what counts as in-scope versus change orders
• Research protocol—where you look for technical information, how you interview subject matter experts, how you validate accuracy
• Writing templates and style guide—your formatting standards, tone guidelines, whether you use specific tools like MadCap Flare or Confluence, any client-specific requirements
• Revision and approval workflow—how many rounds you offer, how you track feedback, how you communicate changes back to clients
• Quality checklist—what you review before submitting (grammar, formatting, accuracy, consistency, screenshots up to date)
• Handoff and delivery—how files are organized, what format you deliver in, how you archive completed work
• Communication standards—response time expectations, which channels you use for what (Slack for quick questions, email for decisions), how often you check in with clients

Stage 3: Running a Team

When you have 2-3 writers working for you, your job fundamentally changes. You’re no longer the person writing; you’re the person ensuring quality, managing relationships, assigning work, and handling business development. Expect your billable hours to drop to 10-20 per week as your management hours climb. This is normal and necessary. You cannot be both the best writer on the team and the best manager; choose to be the manager.

Quality control becomes your primary tool for maintaining reputation. You should review every deliverable before it goes to the client, at least for the first 50-100 projects your team completes. After that, you can move to spot-checking 25-30% of work. Create a quality checklist and have your team self-review against it before handing work to you. Schedule 1-on-1 meetings every 2 weeks to discuss projects, provide feedback, and listen to concerns. Writers who feel supported stay; writers who feel micromanaged or ignored leave, and turnover is expensive.

Revenue Without More of Your Time

The long-term scaling strategy for technical writing isn’t just “hire more writers.” It’s to build revenue streams that don’t require direct labor on every engagement. The most successful technical writing agencies do this through retainers, service packages, and documentation audits.

A retainer means a client pays a flat fee each month (typically $2,000-8,000) for a set amount of work—maybe 40 hours per month of documentation updates, new feature releases, or content strategy. You plan the work, assign it to team members, and deliver it. The client likes having a predictable budget and guaranteed availability; you like predictable monthly revenue that doesn’t spike and drop. Retainers should make up 40-60% of a mature technical writing business’s revenue. They’re stable, they reduce sales cycles, and they’re easier to staff.

Service packages bundle common deliverables at fixed prices. Instead of hourly billing, you offer “API Documentation Package: $4,000” (includes research, writing, diagrams, and one round of revision). This allows you to route work efficiently to your team, standardize delivery, and scale without raising rates. It also makes selling easier because prospects understand exactly what they’re getting.

Once you have systems and a team, consider adjacent services: documentation audits ($3,000-6,000, 2-3 weeks of work that a junior can lead), technical writing training for in-house teams ($5,000-15,000, typically delivered by you with a team member supporting), or content strategy consulting ($2,000-4,000, usually a one-time engagement). These services are high-margin and don’t scale linearly with labor.

Key Metrics to Track

• Billable hours per week per person—target is 30-35 for employees after onboarding, 25-30 accounting for training and admin
• Revenue per billable hour—should improve as you specialize; target $60-120 depending on expertise and location
• Project turnaround time—if your typical project took 80 hours solo and now takes 120 hours with a junior (because of management overhead), that’s normal, but you should see it improve to 90 hours within 6 months
• Percentage of revenue from retainers—track this separately; shoot for 50%+ as you scale
• Client retention rate—aim for 70%+ of clients coming back for additional work or staying on retainer
• Project profitability—not all projects are equally profitable; track which clients, industries, or project types have the best margins
• Time to hire and onboard—measure how long it takes a new hire to be fully productive; aim to reduce this over time through better documentation

Common Scaling Mistakes

• Hiring too fast. You hire two writers before you’ve hired one. You end up managing inexperienced people instead of improving systems. Start with one, get that right, then add more.
• Delegating too early. You hand off client discovery, scope definition, or technical complexity before your team is ready. Clients feel the quality drop; you end up re-doing work. Keep the hard decisions yourself until your team has at least a year of experience.
• Not documenting before hiring. You expect to train verbally and then get frustrated when work quality varies. Write everything down first, even if it’s rough.
• Underbidding retainers to lock in clients. A $2,000 retainer for 40 hours per month ($50/hour) is unsustainable if you need to manage the work, onboard people, or replace team members. Underpriced retainers trap you in low-margin work.
• Losing touch with clients after hiring. You hand off relationships to a project coordinator or junior writer, and clients miss talking to the actual expert. Stay involved in kickoffs and significant feedback rounds.
• Hiring based on resume instead of trial work. You bring someone on full-time who seemed perfect but can’t execute. Use a small project or paid trial (20-30 hours) before committing to a hire.
• Not addressing performance early. You notice a team member is missing deadlines or producing low-quality work, but you’re too busy to manage it. This gets worse, not better. Address it in your first 1-on-1 after noticing the pattern.