We build apps shaped around each community's own schedule and way of running things. Setups that prove themselves will become reusable templates over time.
Testing the prototype · 8 users · Not yet for sale
Why we design this way
When the people running a community change, the know-how shouldn't disappear.
Schedules, notices, tasks and participation records scatter across chats and documents, so each new leadership team ends up rebuilding from scratch. We're trying to address this in three ways.
01
Bring it together
We design so schedules, notices, tasks and participation records live in one place instead of scattering.
02
Fit the community's way
Clubs, study groups and project teams each run differently, and we build around that difference.
03
Hand it on to the next team
We aim to structure accumulated schedules, roles and participation records so the next leadership team can understand and continue them.
Custom-built, then shaped into templates
We start by mapping out how your community runs.
When you request a custom build, we first map out how your community actually operates. We then build and test it with you, and plan to turn setups that repeat across communities into templates.
STEP 01
Map the operating flow
We walk through how schedules, notices, roles and participation records work today and decide what screens are needed.
STEP 02
Build for your community
We build to that flow, then refine it as you use it in real operation.
STEP 03
Grow what's proven
We plan to identify setups that repeat across communities and prepare them as reusable templates.
Clubs
Schedule · notices · attendance
Bring session schedules and notices into one place, and keep attendance simple.
Study groups
Goals · roles · progress
Manage study goals, each member's role, and weekly progress together.
Project teams
Owner · deadline · progress
Track task owners, deadlines and progress alongside the team's shared schedule.
We don't have a packaged template for sale yet. If you contact us about a build, we'll work out the right setup for your community together.
Our first validation
GRIT: our first experiment in bringing scattered operations together
GRIT is our first operations app prototype for exploring this direction. Eight people currently use its scheduling, attendance and team-project features as we test the operating flow. Below is the real orientation timetable screen.
Partial real screen ·
01
Title and date
The event name, date and duration appear together.
02
Activity order
Introductions, curriculum briefing and other items are listed in sequence.
Select a feature to change the screen and description together. You can also use the arrow keys.
Schedule & timetable
Schedules and session order
Select a date or event on the monthly calendar to see its details. The session timeline shows activity order and duration in time blocks.
Team projects
Team projects and tasks
Select a project to manage tasks, assignees, deadlines, progress and the team's shared schedule in one screen.
Attendance & notices
Attendance and community notices
Record attendance, lateness and absence separately for regular sessions and additional events, and send advance notice for upcoming ones.
Admin workspace
Administrator workspace
Schedule management, attendance review and advance notices are all handled from one administrator workspace.
All screens · 9 captures
Public captures exclude entered profile values and detail areas containing personal information. We plan to experiment with Claude API summaries and activity reviews; these are not integrated into the app yet. The app interface itself is in Korean.
From one community to the next
One community's experience, the starting point for the next.
We plan to grow by starting with custom builds, identifying what repeats across communities, and refining that into templates.
PHASE 01
Validate the operating flow with a prototype
Keep testing GRIT with its 8 current users, refining the schedule, attendance, project and notice flows.
Current stagePHASE 02
Validate repeat needs through custom builds
Build custom apps for more clubs, study groups and project teams to see what repeats, and use Claude Code to refine build documentation and early template drafts.
Planned developmentPHASE 03
Launch validated setups as template products
We plan to sell reusable templates so communities can choose an operating app and get started. Additional needs can lead to custom builds, supported by guides and learning materials that help teams adapt and run their apps.
Path to launch
About KCW Startup
Helping student groups get the apps they need, and grow from there.
Early-stage project in Seoul · Founder: Kim Chaewon
Every university club, study group and community runs differently. KCW Startup builds custom apps around how each community actually operates, and plans to grow validated setups into templates.
Kim Chaewon started this project in Seoul in July 2026. We're currently validating the operating flow through the GRIT prototype, and preparing custom builds and templates for other communities.