Challenge

In the energy market, the billing process involves actors with very different responsibilities. The transmission company distributes the invoices, the generator receives them, monitors defaults and issues invoices, and the agent manages the payments. Each step requires a specific type of information, at the right level of detail, for the operation to function smoothly.

When this workflow relies on a third-party system, control is lost to the operator. Functionalities don't evolve at the same pace as the business, limitations become part of daily life, and even the tool's identity slips out of control.

That was the scenario. The operation already existed, but it was based on a solution that didn't keep pace with the business's growth—neither in terms of product nor positioning. There was a need to build something of their own, not only for autonomy but also to transform this process into a commercial offering.

The challenge was not to create a single system to meet the needs of three completely different profiles, without overlapping information and without compromising the user experience. Furthermore, it had to allow each client to use the platform with their own visual identity.

Transformation_

The solution began by structuring the three perspectives as independent experiences within the same system, each designed to reflect precisely the role of the user.

The transmission company began operating with a more administrative approach, centralizing the uploading, organization, and distribution of invoices. The generating company gained control over the entire billing cycle, monitoring everything from receipt to identifying defaults and issuing payment slips within a continuous workflow. Meanwhile, the agent gained a direct and objective experience, focused exclusively on payments, with clear access to outstanding balances and a complete payment history.

The interface was built to maintain consistency with other systems already in use, reducing the learning curve and facilitating adoption from the first access.

Personalization was treated as a native part of the product. Each client can configure their own visual identity — colors, logo, and brand elements — without depending on technical adjustments. The system adapts to the client, not the other way around.

Benefits_

• Independence from third-party systems: Simple Energy gained full control over the product, roadmap, and visual identity of GAC.
• Three profiles served on one platform: Transmitter, generator, and agent each operate with the precise vision that their function demands.
• White label as a commercial differentiator: GAC can be adopted by customers with their own brand, without exposing the Simple Energy identity.
• Consistency with the ecosystem: The layout, aligned with Sim Geração, reduces the learning curve for those already using other company products.

Tools used_

• .NET
• AWS
• Angular

The .NET API centralizes business logic and data exposure. Lambda functions in AWS automate integrations and periodic routines. Angular structures the frontend, organizing different views by profile and enabling the system's customization layer.