This concludes my presentation.
Q&A session
Shen: Now we would like to proceed to the Q&A session. If anybody
has a question, please click on the Zoom
raise hand button. Please unmute before asking your question.
Please limit your questions to one initial question and one
follow-up per turn. With that, we’d like to begin the
Q&A session.
First, Munakata-san from Goldman Sachs Securities, please go
ahead.
Munakata: Thank you for the opportunity to ask a question. This is
Munakata from Goldman Sachs. Since
we’re limited to one question, I’d like to ask about HR Tech. As was mentioned in the opening remarks, I
believe a workforce reduction was announced.
I’d like to ask again about the background for that, whether it
was a decision made in light of macroeconomic
conditions, or if it's more about a shift in your internal
approach to resource allocation, including the use of AI.
And assuming the macro environment improves in the future, is it
reasonable for us to assume that we won’t
see a drastic increase in headcount again? I'd appreciate your
thoughts on that. Thank you.
Arai: Yes, thank you. As Deko mentioned back in May, we talked about how
to make operations more efficient
and productive, regardless of the environment. I believe that was
the message at the time.
Since then, he returned as CEO of Indeed, and especially in the
US, HR Technology is mainly US-based, as
I’ve said repeatedly, regardless of how the environment changes,
we’re steadily moving forward with new
initiatives for the future. In other words, we’re working toward
delivering good services and good content that
users appreciate and choose to use, and through that, we’re
pushing forward with monetization. That’s the
phase we’re in.
Within that, it’s a matter of how we use opportunities
effectively. We also talked about this in May. Back then,
we said that around 30% of coding involved in creating new
services had already been automated, and that’s
been progressing.
Of course, when we use external technologies, there are
associated costs, like paying for those services. So
as a company, the question becomes: how do we reduce costs and
maintain efficiency?
And in that context, we’re looking at how many people are
actually necessary for future operations. What’s the
appropriate headcount? Should we be increasing headcount for new
R&D, or decreasing it? How do we utilize
automation? That’s the context in which this decision came about.
So of course, if more headcount is needed to grow revenue, we’ll
add people. But within our current HR
Technology framework, we’re trying to figure out how to efficiently
create new products through automation.
Generally speaking, when revenue grows, you tend to need more
people on the sales side, but in our current
setup, the focus is on how to streamline development.
So this doesn’t necessarily translate directly into revenue
growth. As you know, we’re not expecting strong
revenue growth this year in HR Technology, especially in the US. And as you said, even if
something changes
and revenue suddenly jumps, whether we’d rehire the people we let
go, given the reasons I just explained, I
think that’s unlikely.
Munakata: Understood very well. So even when developing new services,
you’re aiming for more efficiency.
That’s clear.
One follow-up question: I understood that this also means your
monetization efforts are steadily progressing.
Considering the external environment, I actually found HR Tech’s Q1 US revenue on a dollar basis to be fairly
resilient. I assume that your monetization initiatives, meaning
higher unit prices, offset the volume decline.
This transcript is provided for the convenience of investors only
and this is a translated version of the Japanese call.
6