How to Hire a Community Solar Subscriber Management Software Company
Run one arithmetic test before hiring anyone. For one project and one month, compare what you allocated, what you invoiced and what the utility actually posted. That gap is your business case.
On this page
Run one arithmetic test before hiring anyone. For one project and one month, compare what you allocated, what you invoiced and what the utility actually posted. That gap is your business case. A first release with an allocation ledger, credit adapters and reconciliation runs $60,000 to $130,000 over 12 to 16 weeks, and a full platform reaches $400,000. Under 1,000 subscribers in one state, use Arcadia.
There is a single test you can run on any community solar platform, existing or proposed, before you spend a dollar. Take one project and one month. Write down the value you allocated to subscribers, the value you invoiced them for, and the value the utility genuinely posted as bill credits. Three numbers. They will not agree, and the size of the disagreement, annualized across your portfolio, is the entire business case. Nobody has to argue about it in a meeting.
What makes this category hard to buy is that the difficulty is not in the software, it is in the counterparties. Credit mechanics are set at the program level and executed at the utility level, so one state can hand you two utilities with meaningfully different behavior. Some send a subscriber level file on a predictable calendar. Some post to the customer's bill and summarize to you days later. Some restate prior periods with no correction marker at all, detectable only by comparing the new file against what you already recorded. A developer can read a utility's documentation. Only observation over several months tells you what the utility actually does.
What a community solar development company actually does
The subscriber portal is the part everyone looks at and roughly a fifth of the work.
The core deliverable is the allocation ledger. Not a percentage on a subscriber record, which breaks the moment anyone transacts mid month, but effective dated entries where every change is a dated transaction carrying a reason, so you can reconstruct exactly what a project's subscribed percentage was on the last day of a quarter and who held each share. That single design decision is what makes lender reporting and diligence survivable.
Then the ingestion layer. Each utility gets its own adapter that parses its file and emits canonical credit events with a period, an account, a value and a source reference, with corrections modelled as superseding events rather than overwrites so the audit trail survives. On top of that sits the monthly three way reconciliation of allocated, invoiced and posted per subscriber, with an exceptions queue ranked by dollars rather than by date.
Beyond the ledger: churn handled as a revenue event with a clock and a backfill task carrying its segment constraint, since a low and moderate income share cannot be filled from just anyone on the waitlist. Income verification built as a document workflow with reviewer assignment, recertification expiry and access controls, because these are household financial documents with retention obligations rather than an upload field. And program rules expressed as configuration, because eligibility, disclosure and credit valuation differ across the state programs you operate in.
What it really costs in 2026
These bands reflect Digital Heroes delivery experience in energy and subscription billing systems.
| Project tier | Cost | Timeline |
|---|---|---|
| Reconciliation layer over your existing platform: credit file ingestion, three way compare, exceptions queue | $35,000 to $70,000 | 8 to 12 weeks |
| First release: allocation ledger, production ingestion, credit adapters for current utilities, invoicing, reconciliation | $60,000 to $130,000 | 12 to 16 weeks |
| Full platform: churn and waitlist automation, income verification workflow, disclosure and consent capture, subscriber portal, asset owner reporting | $150,000 to $400,000 | 6 to 12 months |
| Each additional utility credit adapter | $8,000 to $20,000 | 2 to 4 weeks each |
Two costs hide in plain sight. The first is adapter hardening. A vendor will quote an adapter from a file specification, and the specification describes documented behavior. What you need is observed behavior, which requires several months of that utility's real files including at least one correction cycle. Budget a second pass on every adapter roughly a quarter after launch, and treat any firm that says the adapter is finished at first parse as inexperienced rather than fast.
The second is historical allocation reconciliation. If you are migrating off spreadsheets, those spreadsheets do not reconcile to the credits the utilities posted, and someone has to decide what the opening position is per subscriber. That adjudication is human work, it belongs to your operations lead, and it is the most common reason a twelve week project becomes an eighteen week one.
Signals of a strong partner
- They draw a dated ledger on the whiteboard, not a percentage field. This is the fastest competence check available and it takes about ninety seconds.
- They ask which utilities by name. Community solar experience is specific. General subscription billing experience means they will learn your correction behavior on your budget.
- They model a correction as a superseding event. An update statement over a prior credit destroys the record you need when a subscriber disputes an invoice.
- They treat income verification documents as sensitive from sprint one. Listen for access control and retention rather than file upload.
- They ask how many state programs you operate in. Value stack, Illinois, Massachusetts and Minnesota style programs differ enough that rules belong in configuration rather than code.
- They ask about your lender's reporting requirements. Subscribed percentage at period end, credit realization rate and churn by cohort are diligence questions, and a firm that anticipates them is designing for the right consumer.
- Repository and infrastructure accounts are yours from day one. That is the Digital Heroes default and it should be a condition, not a negotiation.
Red flags
- Allocation is a percentage on the subscriber record. It will not survive the first mid month cancellation, let alone a restated credit file.
- No question about churn. A departure is capacity going dark against a financed subscription assumption, and a firm that has not asked about time to backfill is not thinking about your revenue.
- They promise support for any utility. Nobody supports any utility. They support the ones whose files they have parsed and whose corrections they have seen.
- Income documents land in a shared folder. That is an operational drag and a privacy exposure at the same time, and it is a sign the firm has not handled regulated consumer data.
- They will not quote a migration reconciliation. If historical allocations are waved at rather than priced, that cost arrives later as an overrun.
Questions to ask on the first call
- Design the allocation model on a whiteboard right now, including a subscriber who cancels on the fourteenth.
- A utility restates credits for a period we already invoiced. What does your system do, and what does the subscriber see?
- Which utility credit file formats have you actually parsed, by utility name?
- How would you detect a correction from a utility that sends no correction marker?
- A low and moderate income subscriber leaves. How does your backfill logic keep us above the carve out floor?
- Where do income verification documents live, who can see them, and what is the retention rule?
- How do we reconstruct project subscribed percentage as at the last day of last quarter for a lender?
- What is your plan for handling the accounts a utility closed because a subscriber moved without telling us?
- Who owns the repository, the infrastructure accounts and the subscriber data during and after the build?
A simple way to decide
Do not choose from three proposals built on three sets of assumptions about your utilities. Buy a paid discovery phase from your strongest candidate, three to five weeks, priced separately and cancellable. What you own at the end is a written specification: the allocation ledger design, an adapter specification per named utility written against real files you supply, the reconciliation logic, the churn and carve out rules, the income verification workflow with its access model, and a phased plan with a number against each phase. Digital Heroes works requirements first as standard, with more than 2,000 projects behind the process.
Then take that document to two other firms for comparable quotes. Whatever you decide, you will have written down how your own credit reconciliation is supposed to work, which is more than most portfolios have.
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.
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- Salesforce's field-service research (State of Service / field service trends, survey of 5,500+ service professionals) found that 74% of mobile workers report increasing workloads and 47% say appointments don't go as planned due to customer miscommunication, unaccounted-for parts, or insufficient appointment lengths and travel times. (The separate claim that admin tasks consume ~30% of a technician's hours is NOT supported by the report - the seventh-edition data instead states technicians spend about 18% of working hours, ~7 hours/week, on admin, and only ~32% of time interacting with customers.). Source: Salesforce (2024) →
Frequently asked questions
How much does it cost to hire a community solar subscriber management developer?
A first release with an allocation ledger, production ingestion, utility credit adapters, invoicing and monthly reconciliation runs $60,000 to $130,000 over 12 to 16 weeks. Adding churn and waitlist automation, income verification, a subscriber portal and asset owner reporting takes it to $150,000 to $400,000 across six to twelve months. Each additional utility adapter typically adds $8,000 to $20,000 and two to four weeks.
What single question exposes a vendor who has not done this before?
Ask them to design the allocation model on a whiteboard, including a subscriber who cancels mid month. If they draw a percentage field on a subscriber record, they will not survive the first restated credit file. What you want to see is effective dated ledger entries with a reason on each change and the ability to reconstruct a project's subscription state as at any past date.
Should we build or stay on Arcadia, Ampion or PowerMarket?
Stay if you have a few projects in one state under roughly a thousand subscribers, and put your capital into interconnection positions instead. Developers move off these platforms for structural reasons rather than missing features: revenue share economics, sitting behind someone else's relationship with the subscriber, and limited control of the customer experience. The switch usually makes sense once you hold projects across several state programs.
Why are utility credit adapters more expensive than they look?
Because a file specification describes documented behavior and you need observed behavior. Utilities restate prior periods, sometimes without a correction marker, and close accounts for customers who moved without telling you. That only becomes visible across several months of real files including at least one correction cycle. Budget a second hardening pass on every adapter about a quarter after launch rather than treating first parse as done.
Who owns the code and the subscriber data?
You should own the repository, the cloud infrastructure accounts and the subscriber database, with an unrestricted right to hire another firm, written into the contract before kickoff. At Digital Heroes the client owns the code from the first commit. On assets financed against twenty year cash flows, an operating system your lender cannot inspect and you cannot move is a diligence problem waiting to happen.
How long does it take to build a custom CRM from scratch?
A focused first version takes 10 to 14 weeks in Digital Heroes delivery experience: about 2 weeks of discovery and data modeling, 6 to 9 weeks of build, and 2 weeks of migration and testing. Fully replacing a heavily customized Salesforce setup takes 5 to 8 months. Timelines slip most often on data migration, so insist that legacy data mapping starts in week one, not at the end.
How does a custom CRM handle GDPR, HIPAA, or other compliance requirements?
Compliance has to be designed in from the schema up: field-level encryption, role-based access, audit logs, retention rules, and for GDPR a working way to export and delete a person's data on request. Custom can actually be the stronger option because you decide exactly where data lives, including keeping it in-country or on your own servers, which off-the-shelf tools do not always allow on lower tiers. If HIPAA applies, confirm the agency will sign a business associate agreement and has shipped healthcare systems before, because that experience is not implied.
What should I prepare before contacting an agency about a custom CRM?
Three things: a written list of the 5 to 10 jobs the system must do phrased as tasks (like "produce a quote from a site-visit photo"), an export or screenshots of whatever you use today, and a realistic budget range. You do not need a formal specification; a good agency writes that with you during discovery. Arriving with those three cuts weeks off scoping and gets you a firm quote instead of a padded one.
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.
How many developers does it take to build a custom CRM?
A typical build runs with 4 to 5 people at partial or full allocation: a project lead, one or two developers, a designer, and a QA tester, with design and QA tapering after the middle sprints. Teams larger than six rarely make a CRM ship faster and often slow it down, so do not pay for a bench. On your side, plan for one decision-maker spending 2 to 4 hours a week, because slow client feedback delays more projects than slow code does.
At what team size does building a custom CRM get cheaper than paying for Salesforce?
The crossover usually lands between 15 and 25 users. Salesforce Enterprise lists at $165 per user per month, so a 20-person team pays roughly $39,600 a year indefinitely, while a $45,000 custom build plus $8,000 to $12,000 in annual upkeep breaks even in about 18 months. Below 10 users, Salesforce or Zoho is almost always the cheaper path and a good agency will tell you that.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
Is Zoho or Pipedrive good enough for a small sales team, or should we build custom?
For a straightforward pipeline they are genuinely good and cheap: Zoho CRM Standard starts at $14 per user per month billed annually and Pipedrive Essential is priced about the same. They stop being enough when you need custom objects, industry workflows like job scheduling or inventory-linked quoting, or deep hooks into an internal system. If your team exports to spreadsheets every week to do the real work, the tool has already failed and custom is worth pricing.
Should we pay a consultant to customize Salesforce or just build our own CRM?
If your gaps are configuration-sized, hire the consultant; the Salesforce customization quotes our clients bring to Digital Heroes usually run $150 to $250 per hour, and small changes land fast. Switch to building your own once the customization estimate crosses roughly half the cost of a custom system, because you would be spending custom-development money while still renewing per-seat licenses every year. We regularly see teams put $60,000 into Salesforce customization on top of $40,000 a year in licenses, more than a comparable system they would own outright.
What does it cost to maintain a custom CRM after launch?
Budget 15 to 20 percent of the build cost per year, so roughly $6,000 to $10,000 annually on a $40,000 system, covering hosting, security patches, dependency updates, and a pool of small improvements. Hosting itself is the minor part, typically $50 to $300 a month for companies under 100 users. For comparison, a 20-user team on Salesforce Enterprise pays about $9,900 in licenses every quarter at list price, close to a full year of that maintenance budget.
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.
Related guides
More from Rohan.
Director of Web Platform Engineering · Delhi · 2 posts on the site
Published · Last updated .
