Customer story

How Utility Profit ships code across all departments with cloud agents

Utility Profit

Utility Profit automates utility setup for property managers and their tenants. It syncs upcoming move-ins from property management software, sends tenants branded text and email reminders, tracks utility confirmations in real time, and shares revenue from qualifying utility and internet activations with the property manager. More than 1,000 property managers use Utility Profit nationwide, and tenants have given it more than 58,000 five-star reviews.

Replicas is part of how Utility Profit’s whole team builds software. Engineers use agents for features, bug fixes, database migrations, and production issues. Teammates across departments use the same workflow to ship fixes and small features without writing code by hand.

Visit Utility Profit

What Replicas changed for us isn’t just how fast our engineers move — it’s how many people can build at all. Non-technical teammates can now take an idea to working, review-ready code, and shared sessions let us collaborate on it in real time. The whole team levels up on our codebase as we go.

Martin MoscosaDirector of Engineering, Utility Profit

Software development beyond the engineering team

Teammates who do not code day to day use the same workflows as Utility Profit’s engineers. Account managers and support operations managers pick up tickets, describe fixes in plain language, and have agents take the work to a review-ready pull request.

Every change still passes through the team’s normal code-review and QA gates. Writing the ticket and building the fix now happen in one workflow instead of two separate handoffs between teams.

Engineers join the work without taking it over

When a change gets tricky, engineers open the teammate’s shared session and work in the same environment. They steer the agent, review the work in progress, or pair live on the difficult part.

The teammate keeps the context and ownership of the ticket while engineering provides support where it matters. Martin no longer needs to take the issue away and restart the work from scratch.

From a production error to a pull request

In one production fix, an agent traced a recurring error to two provider-portal messages that meant opposite outcomes but the system treated as the same failure. It rewrote the confirmation logic and opened the fix as a pull request.

Support operations and account management no longer stop at writing a ticket and waiting for an engineering handoff. They work through the fix in Replicas and send review-ready code to engineering. Engineers still own review and QA, while account managers and support operations teammates help build the solution.

Back to customers
Continue reading

More companies who rely on Replicas