2024 · Web app development

RAIN Smart Living

RAIN Smart Living's website, custom CMS and lead desk were built by Niro Digital in 2024 for a Slovenian smart-ventilation manufacturer: catalogue, product pages with an energy-savings calculator, a qualification form, and an admin where every inquiry is worked to closed.

Client: RAIN Smart Living
Industry: Smart ventilation / B2C
Year: 2024
What we did: Web app development

Visit rain.si

The constraint

RAIN makes decentralised heat-recovery ventilation units and sells them to Slovenian homeowners and renovators. A unit is bought on the savings maths, not the spec sheet, and every product has its own kWh, euro, CO2 and payback figures — so the site had to render those from data the client controls. The sales side needed the other end: an inquiry qualified enough to quote against, and somewhere to work it. We built the public site in Slovene — catalogue, product pages with the savings block above the spec accordions, installation, and a form asking about property, walls and insulation with an optional floor-plan upload — and the back office that runs it: a custom CMS for products, media and posts, a lead desk with a Kanban board and lead detail, and first-party analytics. It runs on Next.js, tRPC and Drizzle over Neon Postgres, with better-auth, Cloudflare R2, Resend, and Meta Pixel plus the server-side Conversions API.

95+

Lighthouse on every page, fast for Google and for buyers on phones

*Figures from the project's own accounts and dashboards at the time of writing.

The system

//01Slovene marketing site: home, products, installation, about, inquiry

RAIN product catalogue — availability badges, discounted pricing and feature chips per unit

//02Catalogue with availability badges, sale pricing and feature chips from the CMS

SmartVent 160 product page — description, feature list, price and inquiry CTA

//03Product pages built from CMS records: gallery, features, price, inquiry CTA

Energy-savings section — per-product kWh, euro, CO₂ and payback figures with a worked example

//04Per-product energy-savings block: kWh, euros, CO2, payback, worked example

//05Spec sheets grouped into technical, operation, connectivity and safety accordions

//06Installation page explaining the unit and how it gets fitted

//07Qualification form: property, walls, insulation, optional floor-plan upload

//08Custom admin: products, media library, blog, leads, analytics, billing

//09Lead Kanban: drag an inquiry from new to contacted to closed

//10Lead detail with contact, property and technical panels and a status selector

//11First-party analytics: traffic sources, devices and browsers, no third-party embed

//12The same site on a phone, same hero and calls to action

What changed

//01RAIN edits products, prices, posts and media without a developer
//02Every page of the public site scores 95+ on Lighthouse
//03Every inquiry lands on one board with its property and technical detail attached
//04Lead events reach Meta from browser and server, deduplicated, with hashed contact data

What we'd do differently

The figures here are technical and structural. We can show what the site and the back office do; we cannot publish how many units RAIN sold, because that number is theirs, not ours. What we would do differently: agree the business metric with the client before the first commit, so the case study ends in euros rather than page-speed scores. We would also ship the site bilingual from the start instead of Slovene-only.

All projects