Build vs. Buy: A UMC's Decision Framework for Utility Billing Platforms

Every utility management company eventually faces a critical question: should we build our own utility billing platform, or should we buy (license) one? The answer isn't obvious, and the stakes are high—this decision shapes your operational capacity, client relationships, and competitive positioning for years to come.

Why This Decision Matters

The platform powering your utility management operation isn't just software. It's the foundation of your client deliverables, your team's daily workflows, and your ability to scale. Getting this decision wrong means either:

• Overinvesting in proprietary development that diverts capital and attention from client acquisition and service delivery
• Underinvesting in platform capability and falling behind competitors who offer more modern, feature-rich experiences

Total cost of ownership and time-to-market are the two dimensions that matter most. A platform that takes 18 months to build and costs $500K+ in engineering burns runway that could fund 2-3 years of growth with a licensed platform.

The Hidden Costs of Building Proprietary Platforms

When UMC leadership evaluates "build," they typically underestimate the full investment required.

Engineering and Development

Building a production-grade utility billing platform requires:

• Core billing engine: Meter data ingestion, rate calculations, invoice generation, payment processing
• Property management integrations: AppFolio, Entrata, MRI, RealPage, Rent Manager, Yardi connectors
• Meter manufacturer integrations: NextCentury, Inovonics, Master Meter, Itron, Neptune, and others
• Resident portal: Self-service billing views, payment options, usage tracking
• Client portal: White-label dashboards, reporting, approval workflows
• Back-office tools: Exception handling, vendor management, compliance tracking

A realistic MVP takes 12-18 months with a team of 3-5 engineers. At fully-loaded costs of $150-200K per engineer annually, you're looking at $450K-$1.5M before launching a single client.

Ongoing Maintenance

Building is just the beginning. Ongoing costs include:

• Infrastructure and hosting: Cloud costs scale with data volume and client count
• Integration maintenance: PMS platforms and meter vendors release updates; your integrations break
• Security and compliance: SOC 2, data privacy, and audit requirements demand continuous investment
• Feature development: Clients expect improvements; competitors ship new capabilities; you can't stand still

Budget 30-50% of initial development costs annually for maintenance and iteration.

Opportunity Cost

Every engineering hour spent on platform development is an hour not spent on:

• Building client-specific customizations that win new business
• Improving service delivery and client satisfaction
• Developing operational playbooks and training materials

For most UMCs, engineering bandwidth is a constraint. Spending it on commodity platform features rather than differentiated capabilities is often the wrong tradeoff.

The Hidden Costs of Legacy "Buy" Options

Licensing an existing platform solves the build problem, but legacy utility billing software comes with its own challenges.

Fixed Pricing Models

Many legacy vendors charge per-unit or per-transaction fees that don't align with UMC economics. Margins compress as portfolios grow, and pricing is often non-negotiable.

Limited Customization

Legacy platforms were built for specific workflows—often the vendor's original use case. Adapting them to your operational model means either:

• Changing your processes to fit the software (disruptive, often resisted by staff)
• Accepting limited customization (leaves money on the table, frustrates clients)

Locked-In Tech Stacks

Platforms built 10-15 years ago run on aging infrastructure. Integration with modern tools (AI, APIs, webhooks) is limited or unavailable. You're essentially licensing yesterday's technology.

Slow Release Cycles

Annual or semi-annual releases mean waiting months for critical fixes or features. The vendor's roadmap may not align with your priorities.

The Third Option: Modern White-Label Platforms

A new category of platform has emerged that addresses the limitations of both building and legacy buy options.

Modern white-label platforms like SOLV Portal offer:

• Full white-label branding: Your clients see your brand at every touchpoint—not the platform vendor's
• Modern architecture: Cloud-native infrastructure, API-first design, continuous deployment
• Configurable workflows: Adapt the platform to your operational model rather than the reverse
• Native integrations: Pre-built connections to major PMS platforms and meter manufacturers
• Community innovation: Optional shared features developed across the network of UMCs using the platform

The economic model typically involves a combination of platform fees and per-unit charges, structured to align vendor and UMC incentives.

A Decision Framework: 5 Questions to Ask

1. What's our core competency?

If your competitive advantage is technology and software development, building might make sense. If your advantage is client relationships, service delivery, and operational expertise, licensing frees resources to double down on those strengths.

2. What's our time-to-market requirement?

Need to launch or migrate clients in 6 months? Building is almost certainly off the table. Need to modernize gradually over 2-3 years? Building becomes more viable.

3. What's our integration landscape?

The more PMS platforms and meter manufacturers you need to support, the more integration work required. Each integration is ongoing maintenance. Platforms with pre-built connectors eliminate this burden.

4. How important is white-labeling?

If your brand is central to client relationships, you need true white-labeling—not just a logo swap. Evaluate how deeply the platform supports brand customization.

5. What's the vendor's roadmap alignment?

Does the platform vendor's development priorities match yours? Are they investing in the features and integrations you'll need in 2-3 years?

Frequently Asked Questions

How long does migrating to a new platform typically take?

Migration timelines depend on portfolio size and complexity. Most UMCs can migrate to SOLV Portal within 45 days from contract signing, including data migration, integration setup, and team training. Larger portfolios with complex customizations may take 60-90 days.

Can we migrate clients gradually or must we move everyone at once?

Gradual migration is typically preferred. Most platforms support running both systems in parallel during transition, allowing you to migrate clients in cohorts and validate the new system before full cutover.

What happens to our historical data during migration?

Quality platforms include comprehensive data migration as part of onboarding. Historical billing data, property configurations, resident records, and vendor relationships are preserved and accessible in the new system.