Field notes
Cohorts that respect how Korean SMEs actually buy software
Calendar-month signup cohorts hide procurement and training patterns common among mid-size firms. Cut the data the way buying cycles actually run.
Many retention charts slice users by the calendar month they signed up. That works for consumer apps with continuous individual signup. It misleads when the customer is a mid-size firm that buys seats in batches, trains staff two weeks later, and only then produces meaningful application behavior.
For clients in Gyeonggi-do and the wider Seoul area, we often redefine cohorts by first successful work action—first approved order, first filed report, first completed booking—rather than account creation. The creation date still matters for sales reporting; it is a weak anchor for behavior inside the product.
Role-based cohorts also matter. An admin configuring permissions and a frontline operator completing daily tasks are not the same customer journey, even when they share a company account. Mixing them into one retention curve flattens the story until neither team trusts the chart.
When you present cohort findings, state the cut and the window in one sentence at the top. Stakeholders argue less about the numbers when they can see which real-world event started the clock.