Skip to content
§
§ · build vs buy

Energy Broker Software: Build Custom or Buy PowerKiosk, Energy Broker Pro and Aggregate Energy?

The threshold is roughly 400 live contracts and five suppliers. Below it, buy, because a platform subscription is a rounding error next to any build and somebody else maintains the supplier coverage.

CRM Development workflow illustration for Energy Broker Software Build vs Buy Guide.
The short answer

The threshold is roughly 400 live contracts and five suppliers. Below it, buy, because a platform subscription is a rounding error next to any build and somebody else maintains the supplier coverage. Above it the decision turns on two concrete signals rather than volume: a full time person reconciling commission statements, and more than twelve suppliers. A focused first release runs $60,000 to $130,000 over 12 to 16 weeks and a full platform $150,000 to $400,000 across 6 to 12 months, but the sharpest move for most brokerages in the middle is to keep the platform and build only the commission ledger.

When is off the shelf genuinely the right call here?

Buy if you are under roughly 400 live contracts with fewer than five suppliers, and buy again if your commission structure is straightforward upfront and you do not run a channel. In both cases most of the value of a custom build evaporates, because the reconciliation problem is real but still small enough for one person and a disciplined workbook.

The products worth naming, and who should be buying them:

  • PowerKiosk. The common default for a small to mid sized brokerage that wants supplier coverage maintained by somebody else. That maintenance is the actual product, and it is worth paying for while your supplier list is short and stable.
  • Energy Broker Pro. Comparable coverage with a different fit depending on your markets. Moving between platforms is far cheaper than building one, so exhaust that option before you cost anything custom.
  • Aggregate Energy. Another credible option in the same band. All three exist because most brokerages genuinely do not need a bespoke system.
  • Salesforce or HubSpot. Keep whichever you run for customer records and deal stages. Nothing in this guide suggests replacing your customer relationship management (CRM) platform, and replacing it would be a separate and larger project.
  • DocuSign. Keep it for signature and evidence. Rebuilding signature workflow is a category error.

There is a second buy signal worth being blunt about. If nobody at your brokerage can currently state the gap between commission you were contractually owed last year and commission that actually arrived, you do not yet know whether you have the problem a build solves. Spend two weeks measuring it on one supplier before you spend six figures.

When does a custom build actually pay off?

Five signals, and any two of them tips the arithmetic.

You have a full time person whose job is reconciling commission statements. In most brokerages of any size that role exists whether or not it is titled that way, and it is the clearest single tell.

You are paying more than twelve suppliers. Every supplier is a rate matrix adapter, a statement parser and a submission flow. Platform vendors carry that load for the suppliers on their list. Once you need suppliers that are not on it, you are waiting on somebody else's roadmap.

You have crossed a thousand meters and your renewal capture rate is below what you would defend in a board meeting. A residual that dies because a contract lapsed unnoticed is not a small loss, it is the remaining term of that stream.

Your platform vendor cannot add a supplier you need. The answer being next year is a real constraint, and it is verifiable rather than a matter of opinion.

You run a channel with more than twenty agents and compensation disputes reach you personally. Every dollar needs to trace back to a meter, a service month and the statement line it arrived on, and a workbook cannot do that under questioning.

Most brokers build too late rather than too early. They wait until the workbook breaks, which happens at the exact moment they are scaling fastest and can least afford a sixteen week project.

How do they compare on the things that matter in this industry?

What a rate matrix actually is. It is a multi dimensional lookup keyed on utility, zone, rate class, load profile, usage band, start month, term length and green content, and it expires in hours. A product library in a CRM assumes a price list that changes quarterly. Brokers who force it end up with the matrices back in a workbook anyway, which is a configuration ceiling rather than a missing feature.

Detecting the absence of money. Accounting packages record what arrived. They hold no concept of expected commission, so they cannot flag what did not arrive. Neither can a CRM, because the deal closes and the record goes quiet, while the payment stream runs 36 months and can silently degrade in month 14.

Renewal timing. The renewal date is not one date. It is a window driven by contract notice terms, the utility switch calendar, supplier blackout rules and where forward pricing sits. A workflow tool can fire a task 90 days out. It cannot compute the window from the executed contract or rank the worklist by dollars at risk.

Channel compensation. Sales compensation tools such as Spiff, CaptivateIQ and QuotaPath are built for quota carrying representatives on closed won revenue. A 36 month residual with clawbacks when a customer drops in month eight is a different shape, and payroll systems will not touch it because these are contractor payouts against variable third party remittance.

Portability of what matters. In this category your supplier matrix adapters, statement parsers and rate normalisation layer are the asset. If you build, own them outright. A developer who wants to license those back to you is selling you a platform with extra steps.

What does total cost of ownership look like at your scale?

A focused first release covering matrix ingestion, a quote engine, contract records with extracted terms and a commission ledger with variance detection runs $60,000 to $130,000 over 12 to 16 weeks. A full platform adding supplier data exchange, agent and sub broker split engines with clawback modelling, renewal window computation and client facing reporting runs $150,000 to $400,000 phased across 6 to 12 months.

The drivers are countable. Each supplier is $3,500 to $6,500 for an adapter, a parser and a submission flow, and that does not taper much, because the eleventh supplier has its own file layout just like the third. Each additional market is $20,000 to $50,000, since each carries its own utility list, rate class taxonomy and switch calendar. Residual and split depth adds $25,000 to $60,000 when your book mixes upfront, residual, guaranteed payment and blended structures. Historical migration is $20,000 to $45,000 and is the most underestimated line here, because meter numbers, utility names and rate classes were entered inconsistently over years. An agent portal is $18,000 to $40,000 and earns its place above roughly twenty agents.

A brokerage with 2,000 meters, six suppliers, one market and mostly upfront commission with some residual totals about $118,000, near the top of the first release band. Running costs are 15 to 20 percent of build a year as a support retainer, plus $10,000 to $25,000 for parser maintenance, $4,000 to $12,000 for hosting and retention, $6,000 to $18,000 for market and utility changes, and $3,500 to $6,500 every time you onboard a supplier.

Against that, total twelve months of your platform subscription, CRM seats, signature service and market data, then add the salary of the person reconciling statements. Then add the line that appears on no invoice. On a book of a couple of thousand meters, silent underpayment from rate misapplication and dropped meters runs $40,000 to $180,000 a year in our delivery experience, and it compounds because the error persists for the life of the contract rather than being a one month event.

What does the hybrid look like, and when is it the honest answer?

For brokerages in the middle, this is the recommendation, and it is materially cheaper than either extreme. Keep your platform for quoting and supplier coverage. Keep Salesforce or HubSpot for customer records and deal stages. Keep DocuSign. Build only the commission ledger: expected payment schedule generated at contract execution meter by meter and month by month, statement parsers for the suppliers carrying most of your volume, and variance and missing meter detection with a dispute record that carries the confirmation, the expected calculation and the statement line already attached.

That slice is roughly the ledger, parser and variance lines from the worked example rather than the whole thing, and it targets the one problem no purchased product solves. Quoting speed wins deals you can see. The ledger recovers money you cannot see, on contracts you already signed, which means the return does not depend on your sales performance improving.

The hybrid stops working in two places. If your platform will not export contract terms in structured form, the ledger has nothing to generate expectations from and you are extracting them from documents anyway. And if you have crossed twelve suppliers, the adapter and parser work is already most of a first release, so the incremental cost of owning matrix ingestion too is smaller than it looks.

One rule regardless of route: run the ledger alongside the workbook for at least two full statement cycles before trusting it. The first cycle will find things in your historical numbers and you want that on a practice run.

Which should you choose, by operator size and stage?

Under 400 live contracts, fewer than five suppliers, upfront commission, no channel. Buy PowerKiosk, Energy Broker Pro or Aggregate Energy. Take the constraint and spend the money on selling. Revisit when a second signal appears.

Four hundred to a thousand contracts, five to eight suppliers, one part time reconciler. Hybrid. Keep the platform and build the ledger with variance detection only. This is the highest return spend available in the category and it disturbs nothing your desk already uses.

One to two and a half thousand meters, six to twelve suppliers, one market. The focused first release at $60,000 to $130,000. Scope to the four to six suppliers carrying most of your volume, migrate live contracts only, and add the remainder post launch at one to two weeks each.

Above two and a half thousand meters, twelve or more suppliers, multiple markets, twenty or more agents. The full platform across 6 to 12 months. Sequence the commission ledger first, matrix ingestion second, then renewal computation and the agent portal.

Whatever you choose, ask any developer to model the commission ledger on a whiteboard before you sign: meter, service month, expected against actual, upfront and residual, clawback, agent split. If they reach for a single table with an amount column, they have never done this, and it takes an hour to find out.

When you are ready to turn this into a specification, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You can take that specification to any other firm on your shortlist.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. Acquiring a new customer is five to 25 times more expensive than retaining an existing one, and research by Frederick Reichheld of Bain & Company found that increasing customer retention rates by 5% increases profits by 25% to 95% - underscoring the ROI of support that keeps customers. Source: Harvard Business Review / Bain & Company (2014) →
  2. Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
  3. Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
  4. Across ten outpatient clinics the mean no-show rate was 18.8%, and the marginal cost of no-shows reached $14.58 million per year for those clinics, at roughly $196 per missed appointment (2008 figures). Source: BMC Health Services Research / PubMed Central (Kheirkhah et al.) (2015) →
FAQ

Frequently asked questions

What does it cost to move off PowerKiosk or a similar platform?

The subscription is the easy part to cancel. The real switching cost is your supplier coverage, because the platform maintains matrix formats and statement layouts that you would then own. Budget $3,500 to $6,500 per supplier to bring that in house, which is why starting with the four to six carrying most of your volume matters.

Contract history is the other half. Migrate live contracts first so the system is usable, then backfill history in a second pass for dispute and trend purposes. Trying to do both at once is where the four to six week migration becomes three months.

What happens if our platform vendor changes pricing or tiers?

Model it against contract growth rather than today's invoice, because platform pricing in this category commonly scales with the book, which means the cost rises exactly as your commission does. That is not unreasonable pricing, but it changes the five year arithmetic in a way a single renewal quote hides.

The more common trigger is not price at all. It is being told that a supplier you need is on next year's roadmap, which is a verifiable constraint rather than a negotiation, and it is what usually starts the build conversation.

How long before we can stop using the Excel rate matrix workbook?

Twelve to sixteen weeks for a first release scoped to four to six suppliers. Matrix ingestion and the quote engine are normally delivered first because they produce value daily, and your analysts can validate output against the workbook in parallel for a few weeks before you retire it.

Do not retire it on launch day. Run both until the analysts stop finding differences, which usually takes two to three weeks of live quoting rather than a test cycle.

Is PowerKiosk enough at 800 live contracts?

Often yes, and the honest answer depends on your supplier list rather than your contract count. If the suppliers you write with are covered, the maintenance the platform performs on matrix formats and statement layouts is genuine value you would otherwise fund yourself at $10,000 to $25,000 a year.

Where it stops is commission reconciliation depth. No platform in this band generates an expected payment schedule meter by meter out to end of term and matches statements against it, and that is the gap the hybrid build fills without replacing anything.

Can we keep HubSpot and build only the commission ledger?

Yes, and for most brokerages in the middle of this market that is the right first project. HubSpot or Salesforce keeps holding customer records and deal stages, your platform keeps quoting, and the build owns the expected payment schedule, the statement parsers and the variance and missing meter detection.

The one prerequisite is that your existing systems can export contract terms in structured form. If they cannot, you will be extracting terms from documents anyway, which moves the project closer to a full first release.

Will a custom system integrate with supplier portals?

Partially, and any developer promising full integration across your supplier list has not tried it. Assume roughly half your suppliers will never expose a usable interface, so the build should ingest matrices from a dedicated inbox and file drops, parse statements from documents and data files, and generate clean submission packets for portals that require manual entry.

Design for a human submitting in four minutes rather than forty. That is a realistic target and it is worth more than an integration promise that arrives in month nine.

What does migrating years of contract and commission history cost?

Between $20,000 and $45,000, typically four to six weeks, and it is the single most underestimated line in this category. The difficulty is not volume. It is that meter numbers, utility names and rate classes were entered inconsistently over the years and need normalisation plus a human review pass on the exceptions.

Migrate live contracts first, which makes the system usable, then backfill historical commission in a second pass once the ledger has proven itself against current statements.

Who owns the parsers and the rate normalisation layer?

You should, and it belongs in the contract before the first invoice rather than at handover. In this category the supplier adapters, statement parsers and rate normalisation layer are the competitive asset, not the user interface.

Ask specifically what happens when a supplier changes a statement layout with no notice. The right answer involves per supplier adapters, a validation pass and an operational alert when parse confidence drops, not a promise that layouts are stable. They are not.

Should I hire a freelancer or an agency to build my CRM?

A strong freelancer works for a single-pipeline tool under roughly $15,000, but a CRM your company runs on needs design, backend, and QA skills plus someone available when the original builder moves on. The most expensive projects Digital Heroes inherits are freelancer builds abandoned at 80 percent, where finishing cost more than starting with a team would have. If you do go freelance, require the code to live in your own repository from week one.

Should I hire a freelancer or an agency for my software project?

A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.

How does moving our data from Salesforce or spreadsheets into a custom CRM work?

The agency exports your records, writes mapping scripts that translate old fields into the new schema, runs test migrations into a staging system for you to verify, and only then performs the final cutover. Salesforce exports cleanly through its API including notes and attachments; spreadsheets are messier and need a deduplication pass, where we commonly see 10 to 20 percent duplicate contacts. Expect migration to be 10 to 15 percent of total project effort, and be suspicious of any quote that treats it as an afterthought.

Can we start with a small MVP version of the CRM and add features later?

Yes, starting small is how most successful projects run: launch with contacts, one pipeline, activity logging, and your two most-used integrations, then extend in monthly or quarterly cycles. At Digital Heroes an MVP scope like that typically ships in 10 to 12 weeks for $15,000 to $30,000. The projects that fail usually tried to clone every Salesforce feature on day one instead of the six workflows the team actually uses.

How do I calculate whether custom software will pay for itself?

Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.

What tech stack should a custom CRM be built with?

Boring and mainstream wins: React or Next.js on the front end, Node.js, Python, or Laravel on the back end, PostgreSQL as the database, hosted on AWS or a managed platform. Any of those combinations will run a CRM for a decade; what actually matters is that the stack is common enough for other developers in your market to take over. Treat an exotic stack choice as a red flag, because it usually serves the agency's convenience rather than your continuity.

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.

Will a custom CRM scale as we grow from 10 to 200 users?

Yes, if the data model and hosting are planned for it in discovery, and scaling economics are one of custom's quiet advantages: adding 190 users to a system you own means a hosting upgrade of a few hundred dollars a month, not 190 new licenses. The same growth on Salesforce Enterprise adds about $376,000 a year at list price. Tell the agency your three-year headcount plan up front, because the decisions that make 200 users painless are made before the first line of code.

How many SaaS seats do we need before building custom becomes cheaper?

The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.

Why do agencies charge for a discovery phase instead of quoting for free?

Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.

Who can build a custom CRM software system?

Digital Heroes builds custom CRM software 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 CRM software 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.

Keep reading

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply