Case study · Energy · Subscription & Petit Pro

Residential subscription and Petit Pro, live in production.

At OHM Énergie I build and own electricity and gas subscription journeys — for households and for professionals (Petit Pro). Senior PHP/Symfony engineer and application manager: the code, the integrations, and the release.

Contact me Petit Pro
RoleSenior PHP/Symfony · Application manager
PeriodFeb 2025 — present
StackPHP 7.4 · Symfony 5.4 · MySQL · Docker

Product 01

Residential subscription

Public B2C journey to subscribe to electricity, gas or both, on the web, over the phone and in the back-office.

souscription.ohm-energie.com

Product 02

Petit Pro

Public journey for trades, shops and liberal professions (meter ≤ 36 kVA). Company identity (SIRET), same channels, same delivery bar.

pro-souscription.ohm-energie.com

Channel 01Web
Channel 02Phone
Channel 03Back-office

Business problems

Two products, one delivery bar

Residential and Petit Pro must land on the same outcome: an offer, a signed contract, a payment, an operable file — without hand-duplicating the rules.

Three channels, the same rules

Web, phone and back-office cannot drift. An offer refused online must not go through on the phone.

National grid and ELD

National network operators do not cover every site. A local network (ELD) sits outside the national flow — as with R-GDS (Strasbourg / Bas-Rhin).

Person vs company

Households subscribe as a home. Petit Pro subscribes as a company: SIRET, activity, professional site, small-power eligibility.

Value delivered

The job is not “build a funnel”. It is to keep a regulated domain consistent across two products and three channels, then ship it without breaking production.

  • Subscription features (electricity, gas, dual) on residential and Petit Pro.
  • Alignment of web / phone / back-office, including ELD journeys.
  • Payment, CRM, energy-network and messaging integrations — consumed and hardened in real conditions.
  • Code reviews, incident analysis, production-release preparation.
  • Since August 2026: application leadership of a 3–6 person team, sprints and PO reporting.

My role

Feb 2025 — Aug 2026

Senior PHP/Symfony

  • Subscription features on residential and Petit Pro.
  • REST APIs, payments, CRM and energy-network integrations.
  • Alignment of web and phone channels.
  • Code reviews and incident analysis.

Aug 2026 — present

Application manager

  • Sprint leadership and a 3–6 person team.
  • Production-release preparation.
  • Coordination with the Product Owner.
  • Operational follow-up on critical journeys.

Simplified architecture

  1. ProductsResidential subscription · Petit Pro (trades, shops, liberal professions)
  2. ChannelsWeb · Phone · Back-office
  3. ApplicationPHP 7.4 · Symfony 5.4 · Doctrine · MySQL · Twig · Webpack Encore
  4. IntegrationsPayment · Open Banking · CRM · Network operators · Messaging · REST APIs

Quality and delivery

Automated tests, CI/CD, code reviews, release preparation and incident analysis.

Deliverables and results

Public and verifiable

  • 2 public platforms in production: residential and Petit Pro.
  • 3 channels: web, phone, back-office.
  • 2 energies and 3 journeys: electricity, gas and dual.

Delivered as part of my mission

  • ELD R-GDS journeys for Strasbourg / Bas-Rhin.
  • A 3–6 person team coordinated across sprints and reviews.

Stack

Backend

  • PHP 7.4
  • Symfony 5.4
  • Doctrine ORM
  • MySQL
  • Back-office
  • REST APIs
  • JWT
  • Guzzle

Front

  • Twig
  • Webpack Encore
  • Tailwind CSS
  • Stimulus

Integrations

  • Payment
  • Open Banking
  • CRM
  • Network operators
  • Messaging

Delivery

  • Docker
  • PHPUnit
  • CI/CD
  • Scrum
Contact me Residential subscription

Other case studies

Milkiya Collection Souvenir