Why I Built BCTO, and Why It Evolved into Aline.team

As a startup CTO, I often get asked for help with development issues.
But one story stayed with me: a founder who had outsourced her project three times and still never received a single line of source code.

I remember thinking,
“There's a simple fix for this. Why isn’t anyone solving it properly?”

That moment sparked the creation of BCTO (bcto.me), a tool designed to make development progress transparent, prevent information asymmetry, and ensure that both internal and outsourced work could be tracked clearly and automatically.

Running BCTO taught me a lot, but it also revealed something bigger.

AI was rapidly transforming the development landscape.
Speed and output were no longer the main bottlenecks.
Collaboration, how people work together, how they understand each other, was becoming the real challenge.

That realization led to Aline.team.
A platform that analyzes how developers actually work, surfaces their strengths, and helps teams collaborate more naturally and effectively.
Because in an era where AI accelerates coding, the most important advantage a team can have is how well its people work together.

BCTO was created to make invisible problems visible.
Aline.team was born to make teams truly work better together.

I’ll keep building tools that bridge the gap between technology and people,
because at the end of the day, the real challenge has always been about people.