Skip to content
Book a walkthroughhello@utilitize.africa

Managing agents and portfolios

Utility management software for managing agents and property portfolios

All your schemes in one place. Spot leaks, losses and silent meters across every site. Onboard a complex from spreadsheets, and let the month-end run itself while you approve the exceptions.

A 30‑minute video call with the founder. Bring two schemes' meter lists.

Real Utilitize screen · fictional data
Four alerts with their severity: a probable bypass at C‑04, unaccounted bulk water, a possible running cistern at C‑05 and a probable leak at C‑02 (fictional data)
Ready for pilots

We set up the rules with you.

What your team gets

  1. See everything

    Every scheme's meters, tenants and access in one place.

  2. Catch problems early

    Leaks, losses and silent meters across sites.

  3. Control what matters

    Valves and relays, with one switch that stops every automation.

  4. Bill and collect

    A month-end that runs itself; you approve the exceptions.

What the labels mean

Ready for pilots
Built and tested. Ready for our first pilot sites.
Built · goes live with …
Built and tested on a sandbox or simulator. Goes live once the partner, hardware or service it names is in place.
In preparation
Designed, not built yet. No date until we commit to one.

Built and tested. We're choosing our first pilot sites.See what's built

Bill and collect

Can month-end run itself?

The software runs the steps: validate, draft, issue, remind and reconcile. You decide the exceptions. Issuing waits while a warning or critical exception is open.

Real Utilitize screen · fictional data
Operations autopilot control tower: 4 open exceptions, 1 work order open and overdue, 9 cycles needing you and 0 statements pending, with the first five cycles that need a decision listed below (fictional data)
  1. Exceptions come first. Validation raises exceptions such as missing readings or no tariff. Four are open and need a person.
  2. Overdue work, flagged. Work orders carry deadlines. One is open, and it's already overdue.
  3. Issuing waits for a decision. Issuing waits while a warning or critical exception is open. The other cycles wait for review and approval.
  4. The steps run themselves. Onboarding, the monthly billing cycle and work orders run as steps. The control tower shows what needs a person.
  • A month-end that runs itself

    Missing readings, a missing tariff or a pending move-out become exceptions with a suggested fix.

  • Reminders that stay polite

    At 7, 21 and 35 days, then they stop. The wording is tested never to mention disconnection.

  • Work orders

    Faults and call-outs become work orders with a due time set by priority. Overdue ones are flagged.

Catch problems early

Which sites need you today?

Every scheme's alerts arrive in one inbox, each linked to its meter and its evidence. When the meters behind one gateway go quiet together, Utilitize says it's probably the gateway, not a power cut.

  • Alert rules and an alerts inbox

    Probable bypass, unaccounted water, running cisterns and night-flow leaks, marked by severity, with acknowledge and resolve.

  • Power cuts told apart from silent meters and load-shedding

    A gateway fault, an outage or load-shedding, each with how sure we are. A silent meter isn't called a power cut.

  • Night-flow leaks, running cisterns and bursts

    Water flowing all night is flagged after three nights; a burst within hours.

  • Probable bypass or tamper signals, with the evidence

    Where a scheme has a check meter: the unit whose meter dropped when the loss began, with the evidence.

See everything

How does a new complex come on board?

From six spreadsheets: sites, units, meters, tariffs, occupants and billing accounts. A dry run checks every row, the apply is all or nothing, and a batch can be undone. Installers see each meter's first reading before they leave site.

Real Utilitize screen · fictional data
Installer workspace, Commission with confidence: the Register a meter form with serial number, label, manufacturer, model, driver, data source, utility, phases and payment mode (fictional data)
  1. First reading before leaving. Register, install and bind meters, then check the first reading arrives before you leave site.
  2. Where readings come from. Pick the data source: our own head-end, a provider connection, manual readings or a simulator.
  3. Meter details up front. Utility, phases and payment mode are set when the meter is registered; installation and a tariff can follow.
  • Onboarding from six spreadsheets, with a dry run and a real undo

    Importing the same rows twice creates nothing twice, so a fix and a re-run are safe.

  • Installers register meters on the web

    Register, install and bind a meter, then see its first reading arrive before leaving site.

  • Phone commissioning with a signed certificate

    Scan the label, watch the first reading arrive, and sign a certificate on the installer's phone.

See everything

Can we move tenants and access cleanly?

End a lease from a set date, keep the history and invite the next tenant. Staff access has end dates, and every change lands in an audit log that shows tampering.

Real Utilitize screen · fictional data
Unit M‑03's tenancy: Lindiwe Zulu's lease with an end date of 2026/10/03 being set, the note that history is kept, and the Add a tenant form below (fictional data)
  1. Move-out on a set date. End a lease from a chosen date. Once confirmed, the resident loses access from that day.
  2. History is kept. Ending a tenancy doesn't delete it. Every unit keeps its full tenancy history.
  3. Move-in with an invite. Adding a tenant creates the occupancy and an invite link to pass on; the tenant sets their own password.
  • Add and end tenancies, with history kept

    Ending a tenancy doesn't delete it. The new tenant sets their own password from an invite.

  • Access you can hand out and take back

    Roles by scheme, unit or customer, with end dates. "View as" shows a banner, and both names go in the log.

See everything

Running a metering business, or many roofs?

Bureaus and metering operators can run all their meters on Utilitize, each client walled off from the next. Owners of many solar roofs see every site's import, export and export alerts in one place.

  • Run all your meters on Utilitize

    Bureaus and operators run their clients' meters here, each client walled off from the next, tested in the software and in the database.

  • Moving a scheme to another customer account

    When a scheme moves to a new customer account, its meters and history move with it. We do it for you today.

  • Every site's solar on one overview

    Every site's import, export and export-drop alerts on one portfolio overview.

  • Battery and inverter data

    Solar, grid and battery figures from one inverter make's cloud, with each owner's own access. Other inverters are in preparation.

Control what matters

Can we act across sites, safely?

Valves and relays show the state the meter confirmed, not the one that was asked for. Real hardware starts switched off. One switch stops every automation at once.

Real Utilitize screen · fictional data
Controls console: an automation kill switch above a devices table, where each supply, geyser and water valve shows its confirmed state, how it's controlled and its switch buttons (fictional data)
  1. One switch stops automation. Stops every automated action and prepaid disconnection at once. Turning it back on needs a fresh confirmation.
  2. Confirmed, not assumed. The state column shows what the device reports back, not what was asked for. A‑02 Supply reads Connected.
  3. Real hardware starts disabled. A‑01 is real hardware. It stays disabled until a manager enables it, with a fresh confirmation.
  4. Switch with a reason. Disconnect a supply, switch a geyser or close a water valve, each with a reason. These devices are simulated.
  • Valve and relay control, confirmed by the meter

    Every command carries a reason and counts as done only when the meter confirms it.

  • Burst shut-off

    Where a smart valve is fitted, a burst closes the water and everyone at home is told. One tap reopens it.

  • Holiday mode

    Households set it themselves: the water closes, the geyser switches off, and everything is restored before they're back.

A fictional example

Example (fictional): a managing agent's Monday

On Utilitize's fictional demo data. Where a figure appears on a screen on this page, it's quoted from that capture.

  1. 07:30

    Four exceptions first

    The control tower lists four open exceptions, such as missing readings or no tariff, each with a suggested fix.

  2. 08:15

    A quiet gateway, not a power cut

    Several meters at one block went quiet together. Utilitize flags a probable communication fault at their gateway, so one work order goes out instead of one per meter.

  3. 10:00

    One overdue work order

    A contractor's job is past its due time, and the control tower flags it as overdue.

  4. 14:00

    A new complex from six spreadsheets

    The dry run reports on every row before anything is created. Then the batch applies all or nothing, and it can be undone.

  5. 16:30

    Decisions, not data entry

    Six billing cycles wait for a decision, most of them for review and approval. Issuing waits until their exceptions are cleared.

No real agency, scheme or person. The software runs the steps; people make the decisions.

On site

What you need on site

What a portfolio needs, scheme by scheme. We look at each site's meters with you first.

  • A meter list per scheme

    Models, serial numbers and how they're read today. The six spreadsheet templates take it from there.

  • Smart meters that report every half‑hour

    Keypad meters can't give half‑hourly data.

  • A way for readings to reach us

    Meters on a provider's network, or a gateway per distribution board.

  • A check meter per bulk supplyPer scheme

    Only where you want loss and bypass signals.

  • Valves and relaysOptional

    Only where you want shut-off, schedules or holiday mode.

Bring the meters you have

We'll tell you honestly what we can read.

Meters we read · Send us a photo of one meter

Keypad prepaid meters

We're working on options for keypad sites. Tell us about your meters.

Join the keypad list

Questions

Honest answers

Our clients must never see each other's data. How is that enforced?

Each client's data is walled off from the next, tested in the software and in the database. Managing agents, bureaus and installers each run their own organisation and see only their own schemes.

Does Utilitize run the month-end for us?

The software runs the steps and your team approves the exceptions, so the decisions stay with you. Prefer us to own and look after the meters? Ask about our managed option.

Can we bring a whole complex across at once?

Yes, from six spreadsheet templates: sites, units, meters, tariff assignments, occupants and billing accounts. A dry run checks every row first, the apply is all or nothing, and a batch can be undone.

Some of our schemes have keypad prepaid meters. What then?

We're working on options for keypad sites. Tell us about your meters and join the keypad list.

Keypad meters can't give half‑hourly data, so the loss and leak signals need smart meters.

What happens when a staff member leaves?

Revoke their access in one step; it's recorded, never deleted. Grants can carry an end date, and money or access changes need a fresh identity check.

Is 30 minutes enough for a portfolio?

It's enough to see onboarding, the control tower and the alerts on real screens. If your portfolio needs longer, we'll book a follow-up.

See it live. Book a 30-minute portfolio walkthrough.

Bring two schemes' meter lists.