Our work, and how we solve problems.

The Cafe24-based website and consultation, registration, course, attendance, and learning data were spread across multiple tools, creating a bottleneck in both distribution and expansion and employee work. We needed standards to gradually transition to AWS infrastructure, ERP/student management, and a future online lecture platform while maintaining existing data.

As outsourced development, which had been in progress for four months, was suddenly halted, the mobile app, server, and admin page were not completed, and it was difficult to continue the release using only the existing code. The entire structure had to be revisited and rebuilt to accommodate the demo day and full launch schedule.

It was difficult for visitors considering counseling to determine the center's philosophy, counselor qualifications, differences and costs between individual, couple, and corporate programs at once. We needed to build sufficient trust and create a flow that would lead to a reservation while lowering the burden of a sensitive first visit.

Due to repeated developer changes, Flutter and libraries remained in old versions, and support was discontinued, security vulnerabilities, and store distribution rejection warnings occurred. We needed a structure that would allow us to clean up technical debt and update again while maintaining existing services.

Clients had difficulty vetting editors who matched their content among numerous applicants, and editors lacked space to connect expertise and portfolios to ongoing project opportunities. A structure was needed where both sides could trust the matching criteria and inspection process.

It was difficult for ship maintenance personnel to check the supply of necessary engine parts such as piston rings, valves, and seats within a short visit. We had to prove our large-scale inventory and ability to supply directly from manufacturers in Korean and English, as well as connect with overseas quotation inquiries.