Utility Interconnection Queue Management Software: Custom Build vs PowerClerk and GridUnity
Buy PowerClerk. Under roughly 50 distributed energy resource applications a month in one state, with no cluster studies and no upgrade cost allocation, Clean Power Research will serve you properly and the money is better spent on hosting capacity analysis.
On this page
Buy PowerClerk. Under roughly 50 distributed energy resource applications a month in one state, with no cluster studies and no upgrade cost allocation, Clean Power Research will serve you properly and the money is better spent on hosting capacity analysis. Build once missed regulatory deadlines are producing commission complaints, or once upgrade cost allocation across grouped projects has already caused a dispute you settled by hand.
What PowerClerk and GridUnity genuinely do well
An application arrives as an email attachment. An analyst opens it, checks whether the single line diagram is there, whether the inverter is on your approved equipment list, whether the site plan shows the point of common coupling. Half the time something is missing, so a deficiency notice goes out and the application effectively disappears until the installer replies. That is the process in most utilities, and there are two products worth taking seriously before you consider building anything.
Clean Power Research PowerClerk is genuinely strong at configurable forms, correspondence, document checklists and programme workflow, which is unsurprising given its heritage administering incentive programmes. If your need is a well built intake form, templated deficiency letters and a status an installer can see, it does that and does it without a project. GridUnity aims further up the stack at study and queue management and is a serious tool where queue processing is the whole job.
Both beat a shared inbox, and a shared inbox is what most interconnection teams are actually running. If you take fewer than about 50 distributed energy resource (DER) applications a month, operate under one state rule set, have no group or cluster study process and rarely allocate upgrade costs, configure PowerClerk, connect deposits to your existing finance process and accept that engineering will keep a spreadsheet. We will say that on a first call rather than scope a build.
Where they stop: the clock is written into your tariff
The distinguishing feature of interconnection work is that the calendar is law, and that is the workflow generic products model badly.
Your state rule or tariff says you acknowledge receipt within a set number of business days, tell the applicant whether the application is complete within another, run the initial review screens within another, and issue a study agreement or an approval within another. Miss one and the applicant does not send a polite reminder. They file with the commission, and the commission asks for your processing statistics going back three years.
A ticketing system counts age. Interconnection counts a specific clock per milestone, and that clock tolls the moment you send a deficiency notice and restarts when the applicant responds. It counts business days against a state holiday calendar. It behaves differently for a Fast Track application than for supplemental review than for a full study under the Small Generator Interconnection Procedures. The engineer keeping all of that in a spreadsheet tab is not being lazy. No tool the utility owns can express it.
The screens are the second gap. Fast Track and supplemental review turn on tests such as aggregate generation against line section peak load, and those tests need current circuit loading from your planning model rather than a quarterly export. When the aggregate figure is stale, an application that should have failed the penetration screen passes, and the problem surfaces months later inside a study.
The third gap sits at the far end. The system is built, inspection passes, and the account still needs the net metering rate code set in the customer information system and the meter configured. That handoff usually happens by email to a billing analyst, which is why customers generate for six weeks with no credit and call the commission about that too.
The arithmetic: cost per application against the cost to build
Use your own contract rather than a list price. Products here are priced as an annual platform fee, sometimes banded by application volume, sometimes with per programme configuration charges. Take the annual figure, divide by applications received last year, and you have your cost per application. Then divide by named internal users and you have cost per seat, which in interconnection is a small number of analysts and engineers rather than a department.
Now put the real costs beside it. Analyst hours per application, engineer hours per screen run, the cycle time from receipt to permission to operate, and the count of applications that missed a regulatory deadline last year. That last number is the one your commission will ask about.
The crossover is an application rate. Below about 50 applications a month in one state, buy. Between 50 and 60 a month it depends on whether your engineers are running screens by hand against exported feeder data. Above roughly 60 applications a month, or in any second state, a build starts returning more than it costs, because each additional rule set is a separate clock and screen configuration that a configurable product will express partially and your engineers will finish in a spreadsheet. Volume shape matters as much as volume: residential solar arrives in floods from five installers and each application is nearly identical, while commercial storage arrives in ones and twos and each is a real study. Treating both as one work item is how the small ones get slow and the large ones get missed.
What a custom build actually costs, plus migration and year two
In Digital Heroes delivery experience, a first release covering intake with document validation, the clock engine, executable screens for one state rule set and the study workflow through agreement runs $95,000 to $190,000 and ships in 14 to 20 weeks. A full platform adding the deposit and cost ledger, group or cluster studies with reallocation, an installer submission interface, the permission to operate handoff into the customer information system and commission reporting runs $260,000 to $600,000 phased across 8 to 14 months.
Data migration runs 10 to 25 percent of build cost. Here it is the open queue that costs money rather than the closed one. Completed projects load in bulk because nothing is computed from them. Every application still in flight has to be entered and then verified by a second person against the existing tracking sheet, because one mis-anchored receipt date is a missed statutory deadline rather than a data error.
Year two and after runs 15 to 20 percent of build cost annually. In this category that is rule change: state interconnection rules are revised regularly, equipment standards move, and federal reforms to queue processing reshape how grouped studies work. A system nobody funds after go live is a system that quietly stops matching your tariff.
What pushes cost up: operating in more than one state; cluster study support with reallocation on withdrawal; deep planning model integration rather than a scheduled export; and utility security review and hosting requirements, which for a regulated entity can add a month before a line of production code runs. What keeps it down: start with your highest volume class, usually residential net metered solar under a defined size, and leave commercial storage on the existing process for one more release.
The four situations where building wins
Regulatory fit. Your screens, your study fee schedule, your deposit refund rules and your upgrade agreement template are yours. So is your cost sharing method, which is not the method the next state uses. Layer on equipment conformance to IEEE 1547 and its testing standard IEEE 1547.1, plus certification under UL 1741, and the validation rules at intake become specific to your approved equipment list rather than generic.
Scale economics. Past 60 applications a month, or in a second state, the configured product covers the front of the process while engineers own the middle in spreadsheets and billing owns the end elsewhere. The queue status field then summarises work happening somewhere else, and when the commission asks how many applications missed a deadline and why, a summary is not evidence.
A workflow that is your advantage. Group or cluster handling. Applications get grouped by circuit and window, studied together, and upgrade cost allocated by the method in your tariff. Withdrawals trigger restudy and reallocation, and reallocation arithmetic is where disputes live, so it has to be reproducible on demand years later.
Integration sprawl across three or more systems. Count them: the geographic system for circuit and transformer topology, the planning model such as CYME, Synergi Electric or Milsoft for loading and existing generation, the customer information system for the premise and the net metering rate code, electronic signature, and a payment path for deposits. Once one application crosses three, the coordination lives in an analyst's inbox.
How to decide in a week: run the clock audit
Pull every application you received in one month last year, not a sample chosen by anyone. For each, write five dates: received, acknowledged, deficiency notice sent, applicant response received, decision or study agreement issued. A coordinator can do this in two days from records you already keep.
Then compute two things. How many applications met each regulatory milestone, counted in business days against the state holiday calendar with tolling applied properly. And how much of the total elapsed time sits inside your control versus waiting on the applicant. Utilities are consistently surprised by the second figure, and it decides your first release: if most of the delay is applicant response, build document validation at intake and an installer submission channel first, because rejecting an incomplete application within an hour instead of a week is the single largest cycle time reduction available to you. If most of the delay is internal screening, build the clock engine and executable screens first.
Then pay for a discovery phase rather than accepting a free proposal. At Digital Heroes that produces a signed product requirements document before any code exists: the milestone and tolling model, the screen logic against named data sources, the cost allocation method from your tariff, the permission to operate handoff, acceptance criteria and a fixed price. You keep that document whichever firm builds it.
Who we are wrong for: single state utilities under 50 applications a month, and anyone who wants a hosting capacity analysis product rather than a queue system. We work as India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law, you own the repository from the first commit, and you meet the named engineers before signing. More than fifty specialists, over 2,000 projects, checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- ITIF's 2025 report documents that SMEs operate at roughly 60% of large-firm productivity in advanced economies (citing McKinsey), that CRM platforms deliver a 25-40% improvement in customer retention and a 15-30% boost in sales, and that digital advertising returns about $8 in profit per dollar spent on Google Search and Ads. Source: Information Technology and Innovation Foundation (ITIF) (2025) →
- Analyst estimates place CRM implementation failure rates broadly between roughly 30% and 70% (Johnny Grow cites Forrester at 47%), with low user adoption repeatedly cited as a leading cause of failed CRM projects (this being Johnny Grow's own analysis, not a Forrester attribution). Source: Johnny Grow (industry analysis citing Gartner/Forrester) (2025) →
- The Standish Group 1995 CHAOS Report found only 16.2% of software projects fully succeeded; success varied sharply by size, with large-company projects succeeding about 9% of the time versus far higher rates for small projects - best treated as an industry survey, not an audited dataset. Source: Standish Group (1995) →
- The 2015 CHAOS data (based on the modern definition of success) reports that only about 29% of software projects succeed, 52% are challenged, and 19% fail, with the three most important success skills being executive sponsorship, emotional maturity, and user involvement. Source: The Standish Group (reported via InfoQ Q&A with Jennifer Lynch) (2015) →
Frequently asked questions
How long does a custom interconnection queue system take to build?
Fourteen to twenty weeks for a first release covering intake with document validation, the clock engine with tolling, executable screens for one state rule set and the study workflow through agreement. The most common cause of a slipped date is not engineering. It is access approval to the planning model and the customer information system, which inside a regulated utility is routinely measured in weeks rather than days.
Who owns the queue data and the code if we change developers?
You should own the repository, the cloud accounts and the data, agreed in writing before kickoff. Interconnection records support tariff compliance and can be requested by your commission years later, so they cannot live somewhere you cannot reach without another party's cooperation. At Digital Heroes the client owns the code from the first commit and can hire any other firm to continue the work.
What happens to the clock when we send a deficiency notice?
In most rule sets it tolls, meaning the timer pauses when the notice goes out and restarts when the applicant responds, and the pause itself has to be recorded because that record is your defence when processing time is challenged. Ask any developer to model this on a whiteboard before signing. If they cannot describe the pause and its evidence, they have built ticketing systems.
Can we build the intake layer and keep engineering in spreadsheets?
You can, and it is often the right first release, but be clear about what you are buying. Document validation at intake and an installer submission channel cut the deficiency loop and shorten cycle time noticeably. They do nothing for screen accuracy, because that depends on current circuit loading. Sequence intake first only if your audit shows most delay sits with applicants rather than with your engineers.
Should a small utility buy rather than build interconnection software?
Yes, in most cases. Under about 50 applications a month in one state with no cluster studies and no upgrade cost allocation, configure PowerClerk, wire deposits into your existing finance process, and put the money into hosting capacity analysis instead. That analysis reduces study work at source, which is a better return than software that manages study work more tidily.
What is the difference between queue management and hosting capacity analysis?
Queue management tracks applications through statutory milestones, screens, studies, agreements and permission to operate. Hosting capacity analysis models how much generation each circuit can absorb before upgrades are needed, and publishing it lets developers self select onto suitable circuits. They solve different problems. Good hosting capacity work reduces the volume of difficult applications. Queue software handles the ones that still arrive.
How much does supporting a second state add to the build?
Expect a meaningful increase rather than a configuration afternoon, because each state brings its own milestone definitions, business day and holiday handling, screen thresholds, study fee schedule and response codes. If the first release was designed with the rule set as data rather than as logic, the second state is configuration plus testing. If it was not, it is close to a second build, which is why the data model decision matters early.
Can installers submit applications directly into our system?
They can and they should. The handful of installers submitting most of your residential volume will use a bulk portal or an interface because it saves them as much time as it saves you. Structured submissions remove a large share of the deficiency loop before it starts. Publish your validation rules so their software checks before sending rather than after you reject.
What happens on withdrawal from a group or cluster study?
Remaining projects are restudied and upgrade costs reallocated by the method in your tariff, and that reallocation is where disputes live. The requirement is reproducibility: you must be able to show, years later, the group composition, the study inputs and the allocation arithmetic at each revision. Ask any developer how they handle this. The answer tells you whether they read your tariff or skimmed your request for proposal.
Should the permission to operate handoff be automated?
Yes, and it is often the highest goodwill item in the whole build for the least engineering. Once inspection passes, the account needs the net metering rate code set and the meter configured, and when that travels by email to a billing analyst, customers generate for weeks with no credit. Automating the handoff removes a common source of commission complaints that has nothing to do with engineering capacity.
Is a custom internal tool secure enough for HR records and financial data?
A properly built custom tool is generally safer for sensitive data than the shared spreadsheet it replaces, because you get role-based access, audit logs, encrypted storage, and the ability to cut one person's access instantly. Ask the agency specifically for encryption in transit and at rest, permissions down to the field level, and an audit trail showing who viewed or changed each record. If HIPAA, GDPR, or SOC 2 expectations from enterprise clients apply to you, raise it before the quote, because compliance features add real scope.
Should we build our internal tool in Retool instead of hiring developers?
Retool is the right choice if someone on your team is comfortable with SQL and JavaScript and the audience is a handful of technical users, because a basic CRUD dashboard comes together in days. Hire developers when non-technical staff will use the tool daily, when the logic goes beyond forms sitting on a database, or when per-seat pricing stings, since Retool's Business tier lists at $50 per standard user per month. A pattern Digital Heroes sees often: companies arrive after a year on Retool with a tool nobody can maintain because the one person who built it has left.
Can we start on Airtable or Retool now and move to custom software later?
Yes, and it is often the smartest sequence: run the workflow on Airtable or Retool for 6 to 12 months to learn what you actually need, then go custom once the process stabilizes. The no-code version becomes free requirements documentation, and its data exports cleanly into a custom database. The one risk is waiting too long, because teams stack automations and workarounds until migration becomes a project of its own, so set a concrete trigger in advance, such as hitting Airtable's 50,000-record Team plan cap.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
What should I prepare before contacting an agency about an internal tool?
Bring the spreadsheet or document you run the process on today, a list of everyone who touches the workflow and what each person does, and one sentence describing the outcome you want. You do not need wireframes or a technical spec; a 30-minute screen-share of the current process beats a 20-page requirements document. Decide your rough budget band and name a single internal decision-maker, because projects without one take noticeably longer in Digital Heroes experience.
When does a company outgrow Airtable?
The usual breaking points are record limits, permissions, and automation complexity. Airtable's Team plan caps each base at 50,000 records and Business at 125,000, so operations logging thousands of rows a month hit the ceiling within a year or two. The other trigger Digital Heroes sees constantly is permissions: restricting who can view specific fields or records is clumsy below Airtable's Enterprise tier, which becomes a genuine problem once salaries, pricing, or client contracts live in the base.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other internal tools companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Kabir.
Director of Mobile Engineering · Delhi · 2 posts on the site
Published · Last updated .
