Web Solutions for Malaysian Solar EPCs & Clean Energy
High-converting platforms for solar contractors featuring Solar ATAP calculators and SEDA compliance showcases.
Solar projects require clear engineering evidence and current programme assumptions. We build platforms for Malaysian Solar PV EPCs with verified accreditation displays, commercial roof-assessment enquiries and calculators whose tariff and incentive assumptions are dated and approved before publication.
From NEM to Solar ATAP: what a solar website has to get right
Malaysia's original net metering programme, NEM, is no longer in effect. The current programme, Solar ATAP, works differently: exported energy credit is forfeited monthly rather than carried forward indefinitely, which changes how a system should be sized against a roof and a bill. A marketing page that still describes unlimited rollover isn't giving old information — it's describing a mechanic the current programme doesn't have, and a customer who prices a decision against that description is planning around a number the scheme won't actually pay. We treat programme names and mechanics as content that needs re-checking at every review cycle, not copy written once at launch and left alone until someone notices it's wrong.
A quote is only as good as the bill and the roof
A widget that asks for a postcode and a rough monthly bill figure and returns an instant number is answering a question it doesn't have enough information to answer. What actually determines a workable quote is the customer's TNB bill — consumption pattern, tariff category, whether the account is domestic or commercial — and the physical roof: usable area, orientation, shading, structural condition. We build intake around getting those two inputs to the EPC in a usable form rather than around producing an on-page figure that looks precise but is really a placeholder. Commercial roofs need a different form entirely — load profile and site access constraints up front — because a residential bill-upload field doesn't fit a factory account.
Accreditation is a trust signal, not a badge
SEDA, the Sustainable Energy Development Authority, administers renewable energy programme registration in Malaysia, including the Registered PV Service Provider status a contractor needs to sell under the current schemes; Suruhanjaya Tenaga separately certifies the wiremen who carry out the electrical work. A commercial buyer comparing three EPC quotes checks these before reading a feature list, so an accreditation display needs to be specific enough to check — a registration reference, the certifying body, a renewal date where one exists — rather than a generic seal with nothing behind it. Certification lapses and gets renewed like any other registration, so this is something a website has to keep current, not something it publishes once and forgets.
Two different sales cycles, one site
A facilities manager evaluating a factory roof and a homeowner reacting to a higher bill are not the same buyer, and routing both through one contact form serves neither well. The commercial path needs to collect load and site data, get a site visit scheduled and produce an engineered proposal with equipment specifications — a process that runs over weeks. The residential path needs to be fast: a low-friction way to get someone to call, usually over WhatsApp, with a photo of the latest TNB bill attached. We design those as genuinely separate flows on the same domain, because a form built to satisfy both ends up qualifying neither properly.
What building Trexon Energy's platform taught us
JagaWeb built and maintains the live platform Trexon Energy runs on — the CRM, the WhatsApp lead pipeline, the automated proposal generator, and a savings calculator built to Solar ATAP and RP4 tariff logic rather than the older NEM mechanic. Maintaining that calculator for an active client is why we're conservative about what any solar estimator should claim on a public page: the assumptions behind a savings number can go stale as programmes change, even when nobody has touched the page since it was published. Any estimator we build states its source date and its limitations up front, and gets checked against whatever programme is currently in force rather than left to run unattended and be trusted indefinitely.