ElectrifyMe — an operating system for local electrical services.
ElectrifyMe started as an attempt to protect a local electrical-goods business from a changing market. It evolved into a product that connects electrical troubleshooting, AI-guided help, electrician fulfilment and goods purchasing into one service workflow.
What if the real problem isn't simply finding an electrician — but helping a customer explain the problem, helping the electrician arrive prepared, and making the repair transparent for both sides?
A sales problem became a service problem.
My father owns an electrical-goods shop. Counter sales were under pressure from online purchasing, while many experienced staff were leaving to start their own shops. At the same time, a meaningful part of the business came through goods bundled with electrical service.
Staff was becoming the constraint
Experienced staff increasingly wanted to run their own businesses rather than remain employees, making reliable in-house service harder to sustain.
Service still drove goods demand
The opportunity was not to fight online commerce directly. It was to strengthen the service relationship that can lead to a goods purchase.
Turn employees into an independent network
The initial business model became: electricians work independently, ElectrifyMe brings them customers, and the required electrical goods remain connected to the shop.
I mapped two journeys before deciding what the product should be.
Instead of starting with a marketplace feature list, I looked at how a customer currently resolves an electrical problem and how an electrician currently completes a repair task.
Problem → explain → find help → negotiate → repair
The customer often knows the symptom, not the diagnosis. The first communication with an electrician is therefore vague, and the electrician may need to diagnose the problem again after arriving.
Receive job → diagnose → source tools/parts → repair → collect → record
The electrician primarily relies on personal knowledge and experience. Preparation, scheduling, pricing and keeping a record of work can all become fragmented.
Don't just answer the electrical question. Decide what should happen next.
The AI experience starts when the customer describes the problem by typing or speaking. I designed the flow around severity, safety and task difficulty before recommending an action.
Understand the problem
AI interprets everyday descriptions such as a fan not working, poor refrigerator cooling, AC water leakage, current leakage or a short circuit.
Assess severity & difficulty
The system first evaluates whether the situation may be dangerous and whether the task appears suitable for a user without specialist expertise.
Recommend the safest next step
If appropriate, it explains possible causes and DIY steps. If not, it warns the user and moves the experience toward professional help.
The product becomes the communicator between customer and electrician.
Before the visit
The customer can add photos so the electrician gets more context than a verbal description alone.
Prepare the electrician
The platform can provide the likely issue, required tools, possible replacement goods and a recommended repair procedure/SOP.
Make the repair observable
The electrician captures before and after photos/videos as evidence of the repair, creating another layer of trust and accountability.
The same list of possible goods is shared with the customer for transparency, rather than leaving replacement requirements completely opaque.
The electrician can arrive better prepared instead of starting the visit with only a vague phone-call description.
Transparency has to work for both sides.
Standard repair rate card
I defined the rate-card logic with my father for standard repair problems, using fix charge, time taken and number of tasks as the basis.
Customer sees an estimate
Before booking, the customer can use the standard rate card to estimate the repair cost and understand what the service may involve.
Electrician gets less price friction
The rate card addresses a recurring electrician pain point: negotiating the service amount after the job is complete.
Location sharing, scheduled bookings, a work calendar, booking records and an earnings dashboard are designed to reduce the operational overhead of independent electricians.
Electrical goods remain part of the ecosystem, but the service experience has to be strong enough to earn customer trust and make professional repair feel worth paying for.
Not another marketplace. A service operating system.
The product connects three sides of the workflow rather than treating booking as the whole product.
Describe the issue, understand safety, get help, book, estimate cost, share location and receive a transparent service experience.
Interpret the problem, apply safety guardrails, structure the context and support the next-best action.
Receive richer problem context, prepare tools and parts, follow an SOP, schedule work and document the repair.
Keep electrical goods connected to the service journey so the platform can support both repair and product needs.
The service itself has to become part of the product.
The longer-term operating model standardises how electricians represent the platform: professional behaviour, cleanliness, proper service and customer feedback.
Electrician incentives are intended to be influenced by visit volume and service ratings. The goal is to reward reliable service quality rather than simply maximise the number of bookings.
The strongest reason for an electrician to join is still being refined. The product already offers a larger customer pool, customised jobs, scheduling support, operational visibility and better preparation; the GTM and acquisition strategy are the next part of the work.
One person, end-to-end.
I owned the product work myself rather than working within a dedicated product team.
Problem discovery
Started from a real family business problem, then investigated the customer and electrician journeys to identify the underlying service friction.
Product definition
Defined the product model, AI experience, safety guardrails, booking workflow, communication layer, rate-card logic and operating workflows.
Build & iterate
Turned the concepts into the product, using rapid prototyping and iteration to make the ideas tangible and discover what still needed to change.