Neomot

Problem

Neomot builds elevators and building technology in Caxias do Sul, including the first elevator in Brazil that works with Alexa. The trouble is the category. Sites in this space all look the same: spec sheets, stock photos, a pile of PDFs. Nothing about that says "technology company," and nothing sets the Alexa elevator apart from any other lift.

Approach

So I designed the site like a product, not a catalog. Deep blue, a shot of electric cyan, a confident sans, and one line to hold it together: soluções tecnológicas para edifícios. That puts Neomot where it belongs, a technology company that happens to make elevators. The three lines (Elevadores, Motom, Cubo) speak the same visual language, so the range reads as one platform instead of three products. The Alexa elevator leads as the proof, not a footnote in a feature list. The products are built in OpenGL, giving the visitor a real view of each one: on the elevator page you can change the wallpaper, the flooring, and the ceiling cutout and see the result on the spot, all to bring more immersion and fidelity to the final product. Motion is there to make the building feel alive, not to show off.

Outcome

It was built in Next.js and it's live at neomot.com. Neomot finally reads as what it is, a building-technology company, with the Alexa elevator, the traffic calculator, and the full range under one calm, technical identity.

What I learned

• The category conventions were the real brief. The screens weren't the hard part. Refusing the catalog template the whole sector leans on was.
• A differentiator only counts if the design treats it like one. Putting the Alexa elevator up front, instead of in a feature list, was the call that mattered most.
• Designing for a build partner means designing the system, not just the screens. Handing the build team one coherent language did more than any single comp could.