Background & Opportunity
Yorkshire Gas and Power's growth story begins with a deliberate choice not to build everything at once. Known as YGP and operated through E E Solutions Ltd, the business sells commercial gas and electricity to customers across England, Scotland and Wales, mainly through fixed-price contracts. It buys energy in wholesale markets and uses hedging intended to match expected customer consumption. That model requires commercial judgment, but a small entrant does not necessarily need a large proprietary technology estate at the outset. YGP was founded by Rishi Raichura. In its early phase, the company used a white-label supply model. This reduced the cost and complexity of entering the market because YGP could focus on serving customers without first constructing every component of an energy-retail platform. In an interview published on 14 January 2019, the founder recalled operating the business alone for about four years. That recollection is a management account rather than audited financial evidence, but it helps explain why simple tools and direct coordination were initially practical. A lean model can be rational before demand is proven. It limits upfront investment, keeps attention on sales and customer relationships, and avoids creating a complete system environment before the organization has enough activity to use it. Basic Microsoft tools can hold forecasts, record trades, organize correspondence and support invoice review. In a very small team, personal knowledge and direct communication can fill gaps that a larger organization would need to address through formal workflows. The operating context changed as YGP expanded. Fixed-price contracts connect customer promises to uncertain future consumption and changing wholesale costs. The supplier needs a current view of expected customer usage, energy already purchased or traded, forward curves, required notifications and counterparty invoices. Each activity may be manageable alone. The difficulty is keeping the records consistent across time, contracts and counterparties as volume increases. YGP's documented problem was that basic Microsoft tools were no longer effective for managing forecast positions, traded positions, forward curves, notification positions and invoices. This was a control and visibility problem, not merely a complaint about spreadsheets. When information is distributed across general-purpose tools, users must collect and reconcile it before answering a commercial question. Comparing one position with a later position, or testing different curves, becomes slower and more vulnerable to inconsistency. Delayed information can make exposure harder to understand. The issue mattered particularly for fixed-price contracts. A fixed customer price includes commodity cost. If expected consumption is wrong, purchased volume may not match the volume ultimately required. If market prices move, that mismatch can have material financial consequences. YGP's regulatory disclosure describes a back-to-back, volume-based hedge: the company matches hedging to customer contract volume and revisits the position using demand data, customer usage, contract dates and weather forecasts. This policy does not eliminate risk, but it explains why current, comparable information is important. Management therefore had to decide whether the original low-cost approach could be extended through more manual effort or whether trading and market communication had become core infrastructure. Continuing with basic tools would preserve familiarity and avoid an implementation project, but it would also preserve the documented difficulty of following multiple positions and invoices. Manual work can be effective when activity is limited; as the organization grows, it is more exposed to version confusion, hand-offs and key-person dependence. A specialist system would create its own work. Data would need to be prepared and moved, users would need to learn procedures, and existing processes would need testing. YGP would have to manage transition risk while continuing to serve customers and meet market obligations. A platform would not remove forecasting, procurement, hedging judgment or invoice review. Its potential value was to provide a structure designed around energy trading rather than repeatedly adapting office tools to energy-specific tasks. YGP chose Energy One's enTrader and enVoy. The supplier's customer case describes the combination as a way to centralize trading data and improve related operating processes. enTrader addressed trading activities including positions, comparisons, curves, wholesale trading costs and invoice-related work. enVoy addressed market communications, scheduling and notification processes associated with the United Kingdom electricity market. Connecting these functions was important: trades, notifications, invoices and pricing information could be managed in a more coherent system environment rather than as separate administrative topics. The reported operating benefits were specific. YGP could upload and extract trading positions, compare positions from different points in time and against different curves, validate counterparty invoices, report wholesale trading costs and produce price-position information more quickly. These capabilities corresponded to the bottlenecks identified before implementation. They created a more repeatable basis for reviewing the relationship between customer exposure and wholesale activity. However, the public evidence does not provide an independently measured error reduction, time saving or profit uplift. That evidence boundary is important. Energy One published a customer success story supporting the operational problem, the selected solution and the described process improvements. YGP's later disclosure provides financial and supply-scale figures. Neither source establishes what revenue, EBITDA or meter-point growth would have occurred without the system. It would therefore be inaccurate to claim that enTrader and enVoy alone produced the company's later financial performance. The available scale indicators still provide useful context. For the financial year ended 31 March 2025, E E Solutions Ltd reported approximately £73.6m in total revenue and approximately £6.1m in EBITDA. The average electricity supply base was approximately 134,000 meter points, and the gas supply base was approximately 32,000 meter points. Together, these figures represent approximately 166,000 average supply meter points. They show an operating scale at which trading, hedging, settlement and communication controls were not peripheral administrative matters. A larger supply base creates more consumption data and more opportunities for actual usage to diverge from expectations. More contracts can mean more dates, volumes, market positions and invoice relationships to monitor. Centralized information may help management identify exceptions earlier and make reviews more consistent. That is an operating rationale, not proof of a financial causal chain. Revenue depends on customer volumes, prices and contract terms; EBITDA also depends on costs and commercial factors beyond the technology project. The implementation supported, rather than replaced, YGP's hedge process. The company did not abandon fixed-price contracts or volume matching. It continued to use customer contract volumes as a basis for back-to-back, volume-based hedging while updating positions with demand data, consumption, contract dates and weather forecasts. This distinction matters: technology can enable process execution and improve visibility, while management remains responsible for policy, assumptions and judgment. The decision addressed several risks. Incomplete or inconsistent position views could weaken planning. Counterparty invoices required validation against underlying commercial activity. Market notifications needed to be handled reliably. A process that worked for a small founder-led operation might not remain appropriate as the supply base increased. The specialist systems addressed these information, settlement, communication and scale risks without claiming to solve market volatility or customer-demand uncertainty. The decision also introduced implementation risks. Data, roles and interfaces would need careful management. Staff would need to know which source was authoritative, when positions were updated and how exceptions were escalated. Centralized data would not guarantee good decisions if inputs were late or assumptions weak. Access, approvals and market obligations would still require controls. Public evidence does not quantify these implementation details, so they should be treated as considerations rather than reported outcomes. Competitive context reinforces the infrastructure rationale. Large energy groups could possess greater purchasing scale, broader technology resources and larger operational teams. Enterprise customers could negotiate over price and contract terms, while wholesale participation involved credit and collateral considerations. Energy supply also involved regulatory and licensing barriers. YGP's scale was meaningful but smaller than that of the largest players. A specialist platform could provide greater structure, but it could not automatically remove the disadvantages of scale. The case is therefore best understood as infrastructure alignment. The white-label model was useful when the priority was entering the market without a costly system build. As growth increased the number and importance of linked trading processes, that low-cost approach became a constraint. YGP selected systems designed for energy trading and market communications while preserving fixed-price contracts and systematic hedging. The later financial disclosure gives outcome context without supporting a simple causal conclusion. Approximately £73.6m of revenue, £6.1m of EBITDA and approximately 166,000 average supply meter points show a substantial operating business in the year ended 31 March 2025. They do not show how much performance came from software, commercial execution, market conditions, customer growth or other choices. The most defensible conclusion is that the systems supported infrastructure for scale and risk control. The managerial lesson is to identify when a lean process becomes a control liability. There is no universal revenue or customer threshold. The trigger appears when the organization can no longer reliably connect commitments, forecasts, trades, market communications and settlement checks through existing tools. At that point, specialist technology should be assessed as a response to a defined operating exposure, not simply as a fashionable upgrade. YGP improved supporting infrastructure while keeping the commercial model that already worked. Its experience shows that digital systems become strategic when they govern the quality and speed of decisions around material commercial exposure.
Original Problem / Model
YGP's starting point was deliberately lean. Its white-label model reduced the need to build a complete energy-retail system before demand was proven, allowing the company to concentrate on commercial customers and market entry while limiting upfront technology cost. Founder Rishi Raichura's 14 January 2019 interview recalled that he operated the business alone for about four years; this is management recollection, not audited financial evidence. At that stage, a small team could rely on direct communication, personal knowledge and basic Microsoft tools for forecasts, trade records, correspondence and invoice review. Those tools were not inherently irrational for a low-volume operation. The constraint emerged as activity expanded. Positions, forward curves, notifications and invoices became interconnected, and informal coordination made it harder to maintain one consistent view. The original model therefore provided a low-cost route into commercial energy supply, but it left YGP dependent on manual visibility and key-person knowledge as the business grew.
Turning Point
Growth changed the problem from simple record-keeping to linked exposure control. Forecast positions, traded positions, forward curves, notification positions and counterparty invoices had to be followed together rather than in isolated files or workflows. For fixed-price contracts, those records connect customer commitments with wholesale-market exposure: the supplier must compare expected consumption with energy purchased or traded. YGP's disclosed policy used back-to-back, volume-based hedging and revisited positions using demand data, customer usage, contract dates and weather forecasts. If information was late, inconsistent or difficult to compare across time and curves, management could have less visibility into whether the hedge remained aligned with expected volume. The public case does not quantify a specific loss caused by the old tools, but it clearly documents that basic Microsoft tools had become difficult for managing these activities. That operational bottleneck made specialist infrastructure a strategic question.
Core Decision
The choice was between extending general office tools and investing in specialist infrastructure. A larger manual process could preserve familiarity, but it would not remove the documented complexity. A specialist platform introduced transition work, yet it matched the nature of the trading and communication problem more directly.
Execution / Model / Acquisition Changes
YGP adopted Energy One's enTrader and enVoy rather than continuing to extend basic office tools. The systems centralized trading information and supported position uploads and extraction, comparisons across time and curves, counterparty-invoice validation, wholesale trading-cost reporting and faster price-position information. enTrader addressed the trading and position-management side, while enVoy supported United Kingdom electricity-market communications, scheduling and notification processes. These capabilities matched the documented bottleneck: users could work from more coherent trading data and connect related checks instead of repeatedly assembling information from general-purpose files. The implementation did not replace YGP's fixed-price offer or its back-to-back, volume-based hedge policy. It supported that policy by improving visibility around customer exposure, market activity and related invoices. Transition work, user training, data preparation and control design would still be required, and the public sources do not quantify implementation cost or time. The evidence supports process enablement, not a claim that the platform independently removed market or forecasting risk.
Measurable Results
The reported outcome is operational enablement rather than a proven standalone financial uplift. Energy One's customer case supports the ability to centralize and extract trading positions, compare positions across time and curves, validate counterparty invoices, report wholesale trading costs and improve the speed of price-position information. YGP's disclosure for the year ended 31 March 2025 provides scale context: approximately £73.6m in revenue, approximately £6.1m in EBITDA, about 134,000 average electricity supply meter points and about 32,000 average gas supply meter points. Together, the meter-point figures represent approximately 166,000 average supply points. These results show a substantial operating business in which trading, hedging, settlement and communications controls mattered. They do not establish what performance would have been without enTrader and enVoy, nor do they measure a standalone error, time or margin improvement. Revenue and EBITDA also reflect customer volumes, prices, contract terms, market conditions and other costs. The defensible result is that the systems supported scale and risk-control infrastructure, not that they alone caused the reported financial figures.
Lessons
The durable lesson is to upgrade control infrastructure when business exposure outgrows informal tools. YGP's white-label model was appropriate for limiting the cost of market entry, but growth connected forecasts, trades, curves, notifications and invoices into one operational control problem. Specialist technology provided a more structured basis for managing those relationships while allowing YGP to retain its fixed-price commercial model and volume-based, back-to-back hedging discipline. The case also shows what technology cannot do. enTrader and enVoy did not remove the need for demand forecasting, weather assessment, procurement judgment, wholesale-price management, credit controls or settlement review. Nor does the public evidence prove that the systems alone produced YGP's later revenue or EBITDA. Managers should therefore judge similar investments by whether they improve visibility, repeatability and accountability around material exposure, while keeping financial attribution disciplined and distinguishing operating enablement from independently measured business impact.