Who is behind Nemus: the team that walks the forest

This is not a stock photo. It is part of the Nemus team, in one of the forests we work with.

And that image (people from the sector, on the ground where the sector works) sums up who we are better than anything else.

From the sector, not for the sector

Nemus was not born in an office in the urban world or in a tech incubator. It was born at the Cesefor Foundation, an organization that has spent decades working with forest owners, timber harvesting contractors, sawmills, haulers and public administrations across the whole country.

The difference between building a tool for the sector and building it from the sector shows. It shows in the vocabulary, in the processes that are understood without anyone having to explain them, and in the real difficulties of timber harvesting that lie behind every product decision.

Nemus is not generic software with a forestry layer added on top. It is a tool designed for the trade, from inside the trade.

One team, many profiles

Behind Nemus there are more people than you usually see from the outside:

• Software developers who build the platform and its mobile apps.
• Integration engineers who connect Nemus with the management systems companies already use, so that information flows without duplication.
• Implementation team that supports each client company from day one: forest visit, setup with real data, team training and support during the first months.
• Marketing and communications team that brings the sector information about digitalization, regulation and good practices.

Each profile has a different role, but they all share one principle: don’t build in the abstract. Listen before proposing. Validate before launching.

How we work: needs come from the field

At Nemus, features are not invented in an office meeting. They are detected in the field.

The implementation and support team regularly visits processing industries, sawmills and forests. It listens to what each type of company needs, what still costs them time, what doesn’t fit their real operations. Those needs are passed on to the development team, which studies them, prioritizes them and turns them into concrete features. Before they are launched, they are validated with real companies in the sector.

It is a continuous loop: field → product team → development → validation → field. And it works because the people who talk to companies know the sector, and the people who develop work close to the people who talk to companies.

Support, not a manual

When a company signs up with Nemus, it doesn’t get an email with a username, a password and a PDF with instructions. It gets an assigned companion, a visit to the field and support available at any point in the process: by phone, through the chat on nemus.app or through the information request form. Before the implementation, during the implementation and after the implementation.

We already wrote about exactly what that first month looks like (what happens from the “yes” until the platform is running with your company’s real data) in an earlier article: After the “yes”: what the first month with Nemus is like.

We take care of the rest

Digitalizing the forestry and timber sector is not a lab project. It is a project of the street, the skid trail, the sawmill and the weighbridge. And behind a tool that aims to support that process there have to be people who know that terrain.

At Nemus, those people are us.

Cut, transport, deliver. Nemus takes care of the rest.

Want to meet the team in person? Write to us and we’ll schedule a 20-minute conversation, no slides, to understand your case and tell you how we work 👉 here