We interviewed Mr. Takehiro Takahashi, CEO of Interrupt Co., Ltd., about the background behind introducing Repsona and his experience using it.

Please tell us about your work and your role.

Mr. Takahashi:
We handle contract development as well as in-house package development. I originally started out in marketing as a freelancer rather than as an engineer, but recently I’ve been working as a full-stack engineer, developing many AI-powered systems.

Our main focus is on new business and start-up development. We not only handle system development but also provide proposals on service design and business pivots.

Interrupt Co., Ltd. specializes in system development for new businesses and start-ups.

What kind of work do you use Repsona for?

Mr. Takahashi:
We mainly use it for communication with our contract development clients. Since one project can be used for free, we recommend Repsona to each client, which makes onboarding smooth and easy.

What challenges did you face before using Repsona?

Mr. Takahashi:
We often work in agile development, and delays can occur—especially when tasks get overlooked. Sometimes tasks were forgotten simply because they weren’t properly captured. I think it’s important to carefully organize and track later-phase tasks to avoid omissions.

I tried various tools for that purpose, but some were discontinued, and others—especially those specialized for agile—had too many features and felt heavy. I couldn’t find a simple, well-balanced tool.

Repsona is lightweight, simple, and easy to understand.

Why did you choose Repsona?

Mr. Takahashi:
Before Repsona, I used Wrike, but I found it too heavy. As a contract development company, we collaborate with multiple clients, each starting projects at different times. Since Repsona allows one project to be used for free, it’s easy to start right away and quickly create a shared Gantt Chart (Timeline). This significantly shortens the time needed to get a project up and running.

Repsona shortens the time required to start a project.

How has your experience with Repsona been?

Mr. Takahashi:
There are many web tools available, but when a tool has too many features, you have to start by teaching everyone how to use it. Repsona, on the other hand, is very intuitive—like a shift schedule posted on the wall: “just look here.” It requires almost no explanation and is very easy to roll out to a team.

Sometimes I’m brought into projects that are already in trouble—where I’m suddenly told to take over, and even the stakeholders aren’t clear. In those situations, it’s nearly impossible to introduce a complex project management tool. What matters most is how easily you can create a “state that anyone can understand.” Repsona makes that possible.

“It feels like a shift schedule pinned on the wall at a part-time job.”

What do you expect from Repsona in the future?

Mr. Takahashi:
We often adopt agile development. When tasks aren’t completed within a sprint, they get carried over. It would be great if Repsona’s milestone usability could better support that workflow.

I also see milestones as representing larger goals. If they could be enhanced to show progress rates like OKRs, it would be a valuable feature from a manager’s perspective.

If an API becomes available, I’d like to explore integrating it internally. As Repsona evolves and offers more third-party integrations, I believe it will become even more useful for non-engineers as well.

I do have many small feature requests, but above all, I’d like Repsona to remain simple while continuing to refine its quality and usability.