When I explain that I am building Resaco, Resappi and ResaHost, the names can take more remembering than the problems we are trying to solve. Each has a job. As the founder, I need to explain those jobs clearly enough for a customer to understand what we are asking them to consider and what they would be buying.
In Resaco's Finnish business, we help companies grow sales through marketing and websites. The work covers search visibility, advertising and measurement. From the customer's perspective, the aim is to reach the right people and help them move towards becoming customers.
Resaco.co supports our international work. We are building growth in Europe, currently with a particular focus on travel and hospitality. EMEA is the direction of expansion. Daniel Laurean leads the international work. The same question of growing a business comes with new practical demands in a new market.
Resappi grew out of our own need to make information move through the business. Sales, projects, finance and HR need a shared understanding of the work. We are developing the software in daily use and preparing a public launch for November 2026. The waitlist is open as I write this.
ResaHost takes care of website hosting and maintenance. Its job is to make the continuing care of a website understandable for the customer. Updates, backups and monitoring need a place in the service after the website project has been completed.
The connection is visible in an ordinary customer journey. A business needs demand. A visitor needs a working way to make contact. The enquiry needs an owner. Agreed work needs someone to do it and a record of what was promised. Invoicing needs to reflect the agreement with the customer.
We have encountered these transitions in our own work. Building ResaHost's sales process in Resappi is a concrete example. It has required us to resolve lead ownership and the start of delivery after an agreement. Along the way, we have learned how the software needs to support the person doing the job.
For the customer, this should create the freedom to choose the service they need. A company buying marketing does not have to become interested in all our products. They may already have a CRM or maintenance provider that works well. We need to be able to build a working relationship around that. Having a product of our own does not justify replacing a customer's system.
For me, this is also a question of focus. Every service brings its own promises and workload. A shared background may make cooperation easier, but it does not make developing a service free. If a new product takes attention away from client work we have already agreed to deliver, I need to address that.
That is why I want to judge the work through specific situations. With ResaHost, I ask whether maintaining the website is clear for the customer. With Resappi, I ask whether the employee can move forward with the right information. With Resaco, I ask whether our work helps the client's sales and whether we can demonstrate that with the information available.
The combination makes sense for as long as these jobs benefit the customer. The names and shared background matter to us. The customer should not need to study them to get a useful service. They need to find the right person and understand what that person is responsible for.
I have written more about why we founded ResaHost, why we are building Resappi and Resaco's expansion into Europe. What connects them is my wish to build a company whose promises we can keep on an ordinary working day.
