Energy Efficiency Program Management Software: Build Custom or Buy PowerClerk, Uplight and Franklin Energy?
The test is one week. If a mid year regulatory order changing a deemed savings value would take your current tools more than a week to absorb, you have a build case.
On this page
The test is one week. If a mid year regulatory order changing a deemed savings value would take your current tools more than a week to absorb, you have a build case. If it would not, buy, and a single residential rebate programme with a stable measure list should stay on PowerClerk permanently. Above that line a programme spine runs $70,000 to $160,000 over 12 to 18 weeks and a full platform $200,000 to $500,000 across 9 to 15 months, and the strongest case belongs to implementation contractors paid on verified savings, because for them the accuracy of the dataset is revenue rather than paperwork.
When is off the shelf genuinely the right call here?
Buy if you run a single residential rebate programme with a stable measure list and modest volume. The configuration cost is a fraction of a build, the evaluation exports already exist, and you would spend more on the annual measure catalogue update for a bespoke system than the platform fee would have been.
The products worth naming, and who should be buying them:
- Clean Power Research PowerClerk. The workhorse of this category and it deserves the position. It is genuinely configurable and it handles forms, workflow and document collection well. A great many programmes run on it successfully, and if yours is one of them there is nothing here to fix.
- Uplight. Strong on the customer facing side, particularly engagement and marketplace journeys, and a sensible partner for the acquisition end of a residential programme. It is not primarily a back office administration system, so do not ask it to carry inspection, payment and evaluation machinery.
- Franklin Energy. An implementer with its own tooling. If you are a utility contracting with them, you inherit their platform, and that can be a perfectly good outcome. If you are a competing implementer, it is simply not available to you.
There is a second reason not to build that has nothing to do with programme size. If your contract is likely to be re-bid to a different implementer inside two years and the utility holds the tracking obligation, do not build. Ownership of the system should follow ownership of the reporting duty, and building a platform you will hand over or abandon is a poor use of capital.
When does a custom build actually pay off?
Four signals, and the first one carries most of the weight.
You are paid on verified savings. When an independent evaluator adjusts your claimed savings, the difference comes straight out of margin. Your tracking data is not administration, it is the invoice. That single fact changes the arithmetic more than any feature comparison.
You administer several programmes whose measure lists change annually by regulatory order. Residential, commercial, income qualified and new construction each carry their own measure set, eligibility rules and reporting, and teams that spend the first quarter of every programme year reconfiguring have already found the ceiling.
You are an implementer competing against firms with proprietary platforms. Utilities increasingly ask what platform you will administer the programme on, so the tooling is visible in your bid and again in your evaluation outcomes.
You cannot reproduce your own claims. Take twenty claims at random from your last programme year and try to reproduce each savings number from your own records. However many you cannot reproduce is the size of your exposure at the next evaluation, and it is a two hour exercise rather than a study.
How do they compare on the things that matter in this industry?
The measure catalogue as a versioned artefact. Deemed savings values, eligible measure definitions, baselines and incentive amounts change every programme year, usually by order, sometimes mid year. If the catalogue is a table updated in place, every historical claim silently re-points at the new value the moment it is edited. The correct design gives each measure effective dates and a citation to the technical reference manual (TRM) section it came from, and stores the version identifier on every application line. Ask any vendor or developer what happens to applications in flight when an order changes a value mid year.
Custom project provenance. Custom projects carry the large kilowatt hours and the large incentives, and they are almost universally managed as workbooks passed around by email. Nothing needs to replace the engineering calculation. What is missing is the chain: the measurement and verification plan, each data collection event, the reviewer approval with identity and date, the calculation file with a hash so nobody wonders which version it is, and the resulting figure linked back to all of it.
Duplicate detection across programmes. Spotting the same rooftop unit submitted under two premise addresses depends on premise normalisation and equipment identity, not on a check against customer name. Cross programme checks need a shared premise key, which per programme spreadsheets structurally cannot provide.
Commitment against spend. The number that matters operationally is not what has been paid, it is what has been approved, reserved or promised. Programmes tracking spend alone discover in September that commitments already exceed budget, and the abrupt suspension that follows damages the trade ally relationships the programme depends on.
Configuration ceilings and change speed. This is the verifiable criticism of packaged products at scale: substantial configuration changes route through the vendor or a trained administrator. That is fine at quarterly cadence. It is a real constraint when your measure list changes by order with weeks of notice.
What does total cost of ownership look like at your scale?
The programme spine, covering a versioned measure catalogue with TRM citations, application intake from trade allies and customers, eligibility and cap rules, and an evaluation ready export carrying lineage on every claimed saving, runs $70,000 to $160,000 over 12 to 18 weeks. The full platform adding offline capable field inspection, incentive payment with tax reporting, a commitment and budget ledger, custom project measurement and verification, and cross programme duplicate detection runs $200,000 to $500,000 across 9 to 15 months. Each additional programme is $12,000 to $30,000.
Application volume barely moves the price, which surprises most buyers. A programme processing 60,000 applications a year against a stable measure list is cheaper to build for than one processing 4,000 against a catalogue that changes by order every year.
An implementation contractor delivering four programmes for two utilities, paid on verified savings, with roughly 11,000 applications a year, totals about $138,000 for the spine, upper band because of the four programmes and the commitment rules. A single residential programme with a stable measure list lands nearer $76,000. That same implementer added offline field inspection, incentive payment with tax reporting and custom project measurement the following year for $215,000.
The recurring line that defines this category is the annual measure catalogue update at $12,000 to $35,000 per programme year, and it is not optional, because revised deemed values and measure lists have to be in place before the programme year opens. Add support at 15 to 20 percent of build cost, hosting and document retention at $6,000 to $22,000, evaluation support at $8,000 to $25,000 per cycle, and staff training at $4,000 to $10,000. Trade ally support scales with your contractor population rather than your application count.
Compare that against your platform fee honestly, because per application or per programme year pricing hides the same truth: much of what you pay is the annual measure list update, whoever performs it.
What does the hybrid look like, and when is it the honest answer?
There are two hybrids here and both are cheaper than a full platform.
Keep the platform for intake, build the catalogue and the export. If PowerClerk handles your forms, documents and workflow acceptably and your only real exposure is evaluation, do not replace it. Build the versioned measure catalogue and the evaluation ready export beside it, and have the platform record the version identifier on each application line. That targets the exact failure that produces a low realisation rate without disturbing the process your trade allies already know.
Build the spine, borrow the money movement. Once a platform issues payments it inherits payee records, tax reporting thresholds and finance controls, which is a step change in scope. Exporting an approved payment file to your existing accounts payable is cheap. Building payment issuance is not. The same logic applies to inspection scheduling: if field staff already run on a scheduling product, integrate rather than rebuild.
The largest single scope reduction available anywhere in this category is deferring custom project measurement and verification to phase two. Deemed measures are arithmetic. Custom projects need baseline documentation, engineering review, savings methodology and post installation verification, which is a workflow rather than a form.
One rule regardless of route: the programme year, not engineering, sets your delivery date. Go live between programme years, because cutting over mid year means running two catalogue versions, two eligibility rule sets and two reporting formats at once. Start discovery at least five months before the year opens, and build against next year's measure list rather than this year's.
Which should you choose, by operator size and stage?
A single residential rebate programme with a stable measure list. Buy PowerClerk. There is nothing distinctive here to protect and the configuration cost is far below a build. Revisit only if your measure list starts moving mid year.
A utility running two or three programmes where an implementer holds the tracking obligation. Keep the incumbent and spend on the evaluation layer instead. Lineage on claimed savings is roughly 10 percent of a project when built in and several times that when reconstructed during a review.
An implementation contractor paid on verified savings, three to five programmes. Build the spine at $70,000 to $160,000. Launch with your two highest volume prescriptive programmes, leave custom projects on the existing process, and pay incentives through accounts payable in year one.
A multi utility implementer with custom projects, field inspection and payment issuance. The full platform across 9 to 15 months. Budget multi tenancy explicitly, because each client's data must be genuinely separated while your operations team works across all of it, and that is a design decision rather than a permissions setting.
Before you sign anything, run one acceptance test on any candidate: replay last programme year's applications through the proposed engine and confirm the savings match. It is the cheapest confidence you will ever buy, and it costs about 7 percent of the project.
If you would rather scope this before committing budget, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- The NRF discontinued its long-running annual shrink report, stating that a broad study of retail shrink 'is no longer sufficient for capturing the key challenges and needs of the industry' - important context that qualifies how POS/shrink benchmarks should be cited going forward. Source: Retail Dive (2024) →
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
Frequently asked questions
What does it cost to migrate off PowerClerk mid portfolio?
The software migration is manageable. The programme calendar is what makes it expensive, because cutting over mid year means running two measure catalogue versions, two eligibility rule sets and two reporting formats simultaneously, which roughly doubles acceptance effort for no benefit.
Move between programme years and migrate live applications only. Closed programme years should stay retrievable in place for the evaluation cycle rather than being forced into a new data model, and the reference data worth bringing forward is your measure catalogue, trade ally register and premise records.
What if our platform changes its per application or per programme year pricing?
Model it against programme count rather than application count, because that is what actually drives cost on both sides of the comparison. A portfolio adding a fourth and fifth programme sees platform cost rise for the same reason a build does: each one is a new measure list, new eligibility rules and usually a new trade ally population.
The item to isolate in any renewal conversation is the annual measure catalogue update. Whoever performs it, you are paying for it, and it is $12,000 to $35,000 per programme year of work.
How long does a build take, and when should we go live?
Twelve to eighteen weeks for the programme spine, and 9 to 15 months for the full platform. The date is set by the programme year rather than by engineering, so plan to go live in the gap between years.
Start discovery at least five months before the year opens. The coming year's measure catalogue is usually settled well before the year starts, and building against next year's list rather than this year's is the difference between launching ready and launching already out of date.
Is PowerClerk good enough for a utility demand side management portfolio?
For many portfolios it is, and it deserves its position, particularly for forms, workflow and document collection. Most programmes that run on it run well, and switching platforms is far cheaper than building one.
The strain appears in two places a practitioner can verify. The savings engine is not its centre of gravity, so versioned measure catalogues tied to TRM sections tend to be worked around rather than expressed natively. And substantial configuration changes route through the vendor, which matters when a measure list changes by order with weeks of notice.
Can we keep our current platform and build only the catalogue and evaluation export?
Yes, and for utilities whose main exposure is the evaluation cycle this is the right first project. Build the versioned catalogue with effective dates and TRM citations, have the platform record the version identifier on every application line, and generate the evaluation export from your own data.
The prerequisite is that your platform can store and export that version identifier per line. If it cannot, you are reconstructing lineage after the fact, which is the expensive scenario the whole approach exists to avoid.
What does the annual programme year update actually cost?
Between $12,000 and $35,000 per programme year, whether you build or buy. New deemed values, revised measure lists and changed incentive levels have to be in place before the year opens, and mid year orders happen on top of that.
Insist that any quote breaks the measure catalogue and the annual update out as separate lines from the application workflow. They have different lifespans and different owners, and bundling them hides the cost that defines what the platform really costs you across five programme years.
Should an implementation contractor build its own platform?
If you are paid on verified savings, this is the strongest build case in the category, because the accuracy of your tracking data is directly your revenue rather than your administration. It also shows up in bids, since utilities increasingly ask what platform you will administer on.
The case weakens sharply if the utility owns the tracking obligation and the contract is likely to be re-bid inside two years. Ownership of the system should follow ownership of the reporting duty.
What does an independent evaluator actually need from the system?
Lineage on every claimed saving: which measure version applied, which deemed value was used, which TRM citation supports it, which inspection confirmed installation, and what quantity was originally claimed against what was verified.
Low realisation rates are usually a records problem rather than an engineering one. Retired measure codes with no version history, custom project savings whose derivation lives in an emailed workbook, and quantities revised after inspection without retaining the original all become adjustments, because an evaluator can only verify what you can evidence.
What does an internal tool cost for a small business with 20 to 50 employees?
Plan on $5,000 to $15,000 for a focused tool that replaces one painful spreadsheet workflow, such as job scheduling, quoting, or PTO tracking. In Digital Heroes projects at this size, the sweet spot is one core workflow, two or three user roles, and a single integration, usually QuickBooks or Google Workspace. Quotes far below $5,000 usually mean a template with your logo on it rather than software built around your process.
Should we build the whole internal tool at once or start with an MVP?
Start with a version that fully replaces one workflow, ship it in 4 to 6 weeks, and let real usage set the roadmap. Internal tools have a captive audience, so you learn within days which features matter, and across Digital Heroes projects roughly a third of initially requested features never get built once staff work with version one. Phasing also spreads the spend: a $40,000 vision becomes a $15,000 phase one that starts paying for itself while phase two is scoped.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
How do I vet a development agency for an internal tools project?
Ask to see two or three internal tools they have shipped and whether those clients still use them daily, because internal tools fail on adoption, not code quality. Good signs: they ask to see your current spreadsheet or process before quoting, they propose a phased build instead of one big launch, and they spell out who handles training and post-launch changes. Walk away from anyone who gives a fixed price before seeing your actual workflow, since internal tools live or die on process details.
Is a freelancer or an agency better for building an internal tool?
A solid freelancer works for a single-workflow tool under roughly $10,000, if you accept that one person holds all the knowledge. An agency earns its premium once the tool spans departments or integrations, because you get a developer, a designer, and a project manager plus continuity when someone leaves or gets sick. The hidden freelancer cost appears 18 months later when you need changes and the original builder has moved on, a rescue situation Digital Heroes is hired for regularly.
How do we migrate years of spreadsheet or Airtable data into a new internal tool?
Migration is a standard part of the build, not a separate project: the agency writes import scripts that clean, deduplicate, and map your existing rows into the new database. On typical spreadsheet and Airtable histories, Digital Heroes budgets 3 to 10 extra days, most of it spent resolving inconsistencies like the same customer spelled four different ways. The safe sequence is a trial migration first, a review of flagged conflicts with your team, then final cutover over a weekend so nobody loses a working day.
Will a custom internal tool scale as our company grows?
Yes, provided it sits on a standard stack with a real database: PostgreSQL comfortably handles millions of records, and adding users costs hosting pennies rather than per-seat fees. The real scaling risks are organizational, not technical: new departments want features, processes change, and the tool needs a budget line to evolve. Set aside a small quarterly improvement budget instead of treating launch as the finish line, and the tool stays useful for a decade rather than getting rebuilt every two years.
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
Published · Last updated .
