The solar EPC jobs a growing operations team needs

When you move from ten projects a month to fifty, you cannot hire five times as many people. Your sales team will not quadruple, and neither will your delivery team. What quadruples is coordination, the work of moving information between desks. You are not hiring for headcount; you are filling the specific solar EPC jobs that keep a project moving, in the order your bottlenecks demand, not a duplicate of the team you already have.

The sales head does not chase paperwork. The telecaller does not decide payment status. The director does not negotiate with the DISCOM. Each person has one screen that shows only their work for the day. Nothing arrives by email that does not also arrive in their task list. A project cannot move to the next stage if its checklist has open items. When a task grows late, it climbs the org chart automatically every night. That structure, clear roles, visible work, automatic escalation, is how a small operations team scales as project volume grows without losing control of any single project.

The five solar EPC jobs your growing team needs

A rooftop solar project passes through 15 working stages from document verification to completion, plus Complete and Cancelled as end states. Not every project hits every stage: a non-loan project skips the loan path, for one. But each stage is a sequence of tasks with dependencies. The paperwork must be correct before delivery can happen, delivery must finish before the closing quality check, and that check must close before invoicing starts.

The documentation ops role verifies the customer papers that the sales team photographs and uploads from site, such as Aadhaar, PAN, the electricity bill, bank documents and the site drawing. Each file gets marked correct or incorrect, and an incorrect one goes straight back to whoever uploaded it. This desk also owns the subsidy redemption task once invoicing opens, because that window closes and nobody in the office notices until it is too late.

The delivery ops role owns material from supplier coordination through site installation. They arrange site access, schedule the driver, and confirm the material arrived undamaged. They know which sites have access issues and which customers need advance notice.

The QC ops role runs the pre-installation site survey, then the closing quality check once the crew is done. That check covers the WiFi and monitoring-portal setup and confirms the portal is showing live data before the project can move to invoicing. Nothing moves to invoicing while that checklist sits open.

The telecaller rings customers on the calling list, qualifies them, and books the site visit on a named salesperson's calendar. The calling list ranks new ad leads ahead of cold numbers, so nobody works stale numbers first. An optional AI telecaller can run the same queue between 9am and 9pm and hand off with notes once a visit is booked. Either way, the outcome flows back to the system so the salesperson knows what was said.

The operations head sees which people are carrying too much, which projects are stuck and why, and which stages are running late, because every overdue task climbs to their screen automatically instead of waiting for someone to raise it in a meeting. That is five people plus a director and general manager. It is roughly the shape that let one Delhi-NCR EPC run a large book of active projects at once, not a promise that headcount alone gets any team to fifty projects a month.

Why automatic task scheduling changes what you hire for

You do not hire the sixth person because you have six times the work. You hire them because a new stage or a new process has opened up, a new DISCOM, a new loan path, documentation that now requires legal review.

When one Delhi-NCR rooftop EPC we work with saw won orders climb steadily month over month, it made one ops hire in that stretch: a third documentation ops person, once the existing two were underwater. No general manager, no sales manager, no project coordinator to chase status in meetings. Tasks were already being written and escalated automatically, so the general manager could see who was underwater without sitting in a meeting. The new hire went straight to the documentation backlog, and the operations headcount (documentation, delivery, QC and the operations head) grew by one on that date, holding there since through a like-for-like QC handover the following quarter. Its task on-time rate climbed noticeably across those months, though the climb was uneven, not a straight line.

The automation does three things that change hiring math. First, a task arrives with its deadline already on it: the loan-sanction check-in is due four days after the stage opens, not because banks sanction that fast, but because that is when the desk should first look, and keep looking while the task sits open; the typical wait for one Delhi-NCR EPC runs long enough that this early check-in matters far more than a token reminder would. If the bank is still deciding weeks later, the task is still open, and the operations head can see it. Second, late tasks climb the org chart automatically; the documentation ops person who is underwater does not have to complain, because the old late tasks are already sitting on the operations head's own screen. Third, handoff points are visible. When documentation ops marks a file verified, delivery ops sees it immediately and can schedule the site visit. No WhatsApp message, no email, no "let me check if that went through." The system is the state.

This means you hire fewer middle managers. You do not hire someone to sit in meetings and ask "where are we on this?" because the system already answered the question. You hire people to do the actual work, verify papers, schedule trucks, run the quality check. And you hire them in order of what is stuck, not in a balanced headcount plan.

The right time to hire each role

These are rules of thumb from running one team's climb from 20 to 45 projects a month, not fixed thresholds every EPC hits at the same number.

Documentation ops is usually the first hire after founder-led work. If your documentation person is working late every night and weekends are disappearing, hire a second one straight away. The bottleneck is visible, and every day the papers sit is a day that loan or delivery is waiting. Delivery ops tends to follow around 30 to 40 projects a month, the point at which the founder can no longer drive to every site personally. This person frees the sales team from logistics calls and frees the general manager from managing drivers.

QC ops tends to come in around 50 projects a month, once a founder can no longer run the site survey and the closing quality check personally on every project. A dedicated telecaller joins around the same range, when ad volume or purchased-list volume exceeds what the sales team can work through while also closing deals. In my experience, an operations coordinator or project manager is rarely worth it before 150 projects a month; below that, an operations head with a metrics screen can usually see who is carrying too much without another layer of management.

How the system teaches new people faster

Onboarding a new documentation ops person this way took about three days in my experience, not the two or three weeks it used to. On the first day, they walk through the checklist, how to verify a file, and what a DISCOM actually accepts versus what it claims to accept. On the second, they work a batch of documents already staged and due, and ask questions about specific files rather than about process, because the checklist is the process. By the third day, they work from their own queue. If they notice a pattern, an Aadhaar that is always expired but a PAN that is current, say, they ask once, it gets resolved, and they apply the rule to the next ten cases. The checklist is the training material, not a manual sitting in a drawer.

The director and general manager still matter

Automation does not eliminate senior roles; it sharpens them. Say a documentation task goes overdue by five days while that ops person is on leave. The system surfaces it immediately, and the general manager decides whether to verify the papers themselves or extend the customer's timeline. Say a delivery site has an access issue. The system flags it, and the general manager decides whether to reschedule or bring in a contractor. What changes is that they see the real problem straight away, not after a status meeting, because the system has already surfaced what is stuck, who is stuck, and for how long. Meetings shrink because nobody needs one to find out what happened.

How much this costs

What this costs in payroll varies by city, role and experience, and is not something the data behind this piece can put a firm number on. What it buys is fewer projects stalling silently between desks, fewer customers ringing to chase their own file, and an operations head who spends time on the tasks that would otherwise run late (on-time rates climbed steadily across those months, at one Delhi-NCR EPC we work with), not on asking each person individually where things stand.

That is also, not coincidentally, what operations software built for solar EPCs is for. Solar Spine writes the checklist for each stage automatically and escalates an overdue task one rung a night until someone closes it, so every role, including the operations head, gets a screen that shows only what needs their attention today. It will not hire the right people, and it will not make a bank sanction a loan faster. It only makes sure nobody on the team can miss that the bank is the one taking thirty days. See what this looked like for one Delhi-NCR EPC's operations team, or read how the same team scaled from 20 to 50 projects a month.

Sources: operations data from a live Solar Spine workspace; author ran this team scaling from 20 to 45 projects monthly at a Delhi-NCR EPC.