2023 · Website development

Zendotik

Zendotik is a B2B site that Niro Digital built in 2023 for a Japanese chair-massage provider, selling workplace health promotion to Slovenian employers.

Client: Zendotik
Industry: Workplace wellbeing / B2B services
Year: 2023
What we did: Website development

Visit zendotik.si

The constraint

Zendotik sells chair massage to employers, not to the people who receive it, so the site had to convince an HR or office manager rather than an end user. The category usually markets itself like a spa flyer, and the client had nothing that made a business case a manager could take to a budget holder. We built a benefit-led home page, a service explainer for buyers who have never bought chair massage, a four-step process page that removes the room-and-downtime objection, and a public pricing page. The enquiry form qualifies before the first call: company, headcount, stated interest and a GDPR consent box. It runs on a feature-sliced Next.js app with server actions, Nodemailer over the client's own SMTP host, UTM attribution middleware and a full privacy, cookies and terms set.

The system

//01Home page pitching employee health and productivity to the employer

Zendotik benefits section — health, mood and workplace relationships

//02Benefits section arguing health, mood and workplace relationships

Zendotik testimonial from an HR manager, with the benefits grid below

//03An HR-manager testimonial placed above the benefits grid

Zendotik process section — four steps from free demo to massages on site

//04Four-step process: demo, scheduling, room prep, sessions on site

//05A service explainer for buyers new to chair massage

//06A public pricing page, so the rate is on the site instead of quoted on request

//07Enquiry form capturing company, headcount, interest and GDPR consent

//08Privacy, cookies and terms pages for a GDPR-facing B2B site

//09The same benefit-led pitch on a phone

What changed

//01Rates are published on a public page instead of quoted on request
//02Every enquiry arrives with company, headcount and stated interest attached
//03Each submission sends both an admin notification and a client confirmation
//04UTM middleware attributes each enquiry to the campaign that produced it

What we'd do differently

The site is a lead-generation front end, not a booking system: there is no calendar, no database and no record of what happens after the email lands. What we would do differently: the middleware captures UTM attribution on every enquiry, but with no database there is nowhere to keep it, so the campaign that produced a lead is only ever visible inside one email. We would write each enquiry to a record first, then attribute it.

All projects