A solar and battery brand in Spain, built around a six step calculator that turns a decision worth around 10,000 euros into a guided conversation.

Industry: Residential solar and battery storage

Services: Website Design, Webflow Development, Custom Calculator, Analytics Setup

Luxda sells complete home energy systems in Spain. Solar panels, a hybrid inverter and a high capacity battery, packaged as three systems at three fixed price points rather than quoted per installation.

Dario arrived with a positioning line and held it for the whole project: Luxda does not sell solar panels, it sells a power plant for the home, sized for everything the household runs, including an electric vehicle and a heat pump. The reference points were Tesla Energy and Apple, not the local installer down the road.

The site had one job. Turn homeowners with high electricity bills into qualified leads, through a quote request, a call, or a WhatsApp conversation.

A purchase of around 10,000 euros with no obvious entry point. A homeowner cannot tell which system size fits their roof and their consumption, and a price list does not answer that question. Without a way to self qualify, the only route into the business was a cold contact form.

Category expectations working against the brand. Solar sites in this market tend to be dense, discount led and technical. Luxda needed to read as a considered product, which meant resisting the pull toward packing every claim onto the page.

Content that kept moving. The brief opened at eight sections and grew as Dario sharpened the proposition. Pricing, financing terms, FAQ copy, product imagery and section order were all revised after the build had started.

Generate qualified leads rather than sell online

Let a homeowner reach the right package without speaking to anyone first

Present three systems with clear pricing and monthly financing

Read as an energy brand, not an installer

Ship in Spanish first, with the structure ready for more languages

Feed Google Ads campaigns with trackable conversions

Design before build. Dario asked directly whether the design was AI generated. It was drawn in Figma first and reviewed as a design before any Webflow work began, which gave us a cheap place to argue about structure while changes were still free.

The calculator as the front door. Rather than bolting a savings widget onto a page, the calculator became the main conversion path. Six steps covering consumption, property type, installable area, interest in storage, objective and contact details, ending on a recommended system. It answers the question the copy could not: which of these three is mine.

Cutting rather than adding. Two sections were doing the same job, a compact pricing overview and a detailed breakdown with specifications and separate calls to action. Keeping both would have made the page argue with itself, so the detailed version moved to the contact page and each page kept one purpose.

Pushing back on density. Several reference layouts arrived built as social media banners, heavy with text. Those work in a feed and fail on a landing page, where every extra claim delays the decision. We kept the substance and rebuilt it as simpler sections.

Holding a scope line. When requests moved from refining sections to replacing built ones, Bilal proposed taking the two highest value changes into the current phase and treating the rest as a separate one. The launch date survived.

Localization decided on evidence. We compared Webflow native localization, which gives clean per locale URLs and better search performance at a higher plan cost, against a translation widget that is cheaper and weaker. Dario chose to validate Spanish in Spain first, so the site shipped with Spanish as the primary locale and a structure ready for more.

A dark, high contrast hero carrying one product claim and the entry price, so the cost is visible before a visitor has to ask.

The three systems are presented as a comparable set. Same card structure, same order of specifications, price and monthly financing shown together so the number feels reachable, with the financing caveat in plain sight rather than buried.

Section rhythm alternates full width statement bands with content sections to give the page a pulse, and the navigation resolves to a solid background on scroll so it never sits illegibly over the hero image.

Built in Webflow with Spanish as the primary locale.

The calculator is custom JavaScript layered over a Webflow form. State carries across all six steps, a recommendation rule maps the consumption and property answers onto one of the three systems, and submission fires from the final call to action so every answer reaches the notification email, not just the contact fields. That last detail was a real fix: the form was originally wired to a secondary button on the results screen, which meant the collected answers were being lost.

Also implemented: a persistent WhatsApp action with a pre filled Spanish message, submissions stored in Webflow with email notification, Google Analytics 4 and Tag Manager, anchor IDs so Google Ads sitelinks can deep link into sections, and duplicated landing pages for campaign targeting. The project was migrated between Webflow sites to attach the correct plan, and the domain was connected from Namecheap.

The site is live at luxda.com and is the destination for Luxda's Google Ads campaigns.

The calculator captures leads end to end. Submissions arrive by email and are stored in Webflow, confirmed in live testing with Dario after launch.

Dario rated the work five stars and has continued to bring new requests to the studio.

No traffic or conversion figures are published here. The campaigns started close to launch and Luxda has not shared performance data yet. Those numbers will be added when they exist rather than estimated.

When a product needs explaining, a guided tool converts better than a longer page. The calculator carries the qualification that copy alone cannot.

Reference material is not always a template. A banner and a landing page have different jobs, and translating the intent matters more than copying the composition.

On a fixed scope build with an engaged client, the useful move is not refusing changes. It is separating the ones that change the outcome from the ones that only change the page.

Dario Founder · Luxda