Stibee
Tap a star to rate
What Stibee is
Stibee (스티비 in Korean) is an email marketing and newsletter platform whose site, help center and blog are all written in Korean. The help center's welcome page sums up the promise in one line: with Stibee, anyone can make and send good-looking emails easily and quickly (누구나 멋진 이메일을 쉽고 빠르게 만들어 보낼 수 있습니다). It goes on to say that senders can understand how customers respond on the basis of subscriber data, and improve both their email marketing results and their business results along the way.
The offer covers the parts a newsletter or brand mailing needs: an email editor and sending, an address book of subscribers, hosted web pages that publish emails and collect sign-ups, statistics, connections to outside services, an API with webhooks, and a paid newsletter feature for charging subscribers. The help center presents itself as Stibee's official documentation, maintained by the Stibee operations team according to how the service actually behaves, and updated as features and policies change.
What a sender gets
Email. The first section of the help center covers editing, sending and managing emails (이메일 편집, 발송, 관리하기). A campaign is built in the editor and then sent to an address book chosen at the recipients step, which is also where the free and paid audiences described below are split.
Address book. Subscribers live in address books (주소록), and the help center's section on them covers adding, editing and managing subscribers. The address book is the unit a sender picks when sending, so a sender with several audiences keeps each in its own book and chooses the right one per email.
Pages. Stibee hosts pages that publish emails on the web and collect subscribers (웹에 이메일 발행하고 구독자 모으기). In practice that gives a newsletter a public archive of past issues and a sign-up point that does not depend on the sender running a website of their own.
Statistics. The statistics section describes checking email statistics in various views (이메일 통계를 다양한 뷰로 확인하기). Stibee's blog pushes senders to use them: its advice to startups is that it is easy to focus only on the act of sending when a newsletter is new, but effective email marketing over the long run means checking the metrics after each send and improving on them. For readers new to the numbers, the blog points to its own dictionary of email marketing performance metrics (이메일 마케팅 성과 지표 사전).
Integrations, API and webhooks. A help section is devoted to connecting Stibee with other services (외부 서비스 연동), and a separate one covers the API and webhooks, described as connection features for a more extended experience. A development team can therefore feed subscribers into Stibee from its own product or react to events from Stibee in its own systems, rather than moving lists by hand.
Users and workspaces. Accounts are organized into workspaces with their own users, and the help center has a section for setting up and editing user and workspace details. A recent post listed on the Stibee blog covers audit logs: the workspace records who did what and when, and the log can be looked up afterwards (감사 로그를 사용해 워크스페이스에서 누가 언제 어떤 작업을 했는지 기록하고 조회할 수 있습니다). For a team where several people write and send, that gives an owner a way to trace a change or a send to the person behind it.
Paid newsletters
Stibee's paid newsletter feature is for collecting and managing paying subscribers (유료 구독자 모으고 관리하기), and it has its own kind of address book, a paid address book (유료 주소록). The help article on sending a paid newsletter states that it applies to the Standard, Pro and Enterprise plans (스탠다드, 프로, 엔터프라이즈 요금제).
The same article explains how a paid address book works. It can hold subscribers whose subscription type is free (무료 구독) alongside paying ones, and a sender can email the free subscribers to promote the paid newsletter to them. To send to paying readers only, the sender creates a new email and, at the step where the address book is chosen, selects paid subscription (유료 구독); the email then goes only to paid subscribers. Selecting both paid and free sends to everyone in the book regardless of subscription type. A writer can therefore run the free issue that attracts readers and the paid issue that earns money from one list, without keeping two copies of the audience in sync.
Plans
The help center has a section on plans and payment (요금제와 결제), and the paid newsletter article names three plans: Standard, Pro and Enterprise. The site publishes no prices on these pages, and paid newsletters are limited to those three plans rather than open to every account.
How Stibee tells startups to use it
The Stibee blog runs categories for email marketing, customer stories, workbooks, product updates, team stories and a tech log. One post, a guide to three types of email newsletter for startups, shows how the company expects its tool to be used. It opens by noting that many startups hesitate to publish a newsletter because they feel unprepared, and argues that a newsletter does not need to start perfectly, because email marketing is not a channel that produces explosive results in a short time but an asset where trust builds up as testing is repeated and time passes.
The three types it describes are these.
A content newsletter (콘텐츠형 뉴스레터) does not ask directly for a purchase or a sign-up. It delivers useful content to customers and prospects steadily, so that the help they get from the newsletter turns into trust in the service. The post's example is Eventus, an event platform whose Event Letter gathers events and meetups by field and goes out every Monday. Once trust has built, the post argues, readers push back less when the company later sends promotional news.
An update newsletter (업데이트 소식 뉴스레터) tells users what has changed in the product. Sent regularly, it shows customers that the service is improving and taking their feedback into account, helps them notice and use new features, and raises engagement and retention. The example is imweb, which summarizes added features and usability improvements for its customers.
Content multi-use (콘텐츠 멀티 유즈) repurposes existing blog or YouTube content as a newsletter. The simplest version, following the example of Wadiz's monthly newsletter, excerpts only the key points and uses a call to action to send readers to the full piece. That cuts the time spent producing each issue, keeps the sending schedule steady, and sends traffic back to the original content, so the newsletter, the blog and the video channel support each other.
The post closes with three tips. An early startup without a backlog of content should start with update news; one that already has blog content can use multi-use; one that can focus on the newsletter should publish a content newsletter that carries its own view. Senders should track results after every send, and a content calendar planned in advance helps keep publishing consistent.
Other recent posts on the blog are customer stories, among them one on the fruit seller Onbrix, which decided to send its fruit stories to customers' inboxes first instead of waiting for them to come, and an interview with Snow Peak Korea about carrying the brand experience it built offline into its newsletter.
Who it suits
Stibee suits Korean-speaking newsletter writers, startups and brands. It fits a writer who wants to grow a free list and sell a paid tier from the same address book, a startup that wants to send product updates or repurpose its blog without building a website for sign-ups first, and a team that needs several users in one workspace with an audit log of who did what. Developers get an API and webhooks for connecting their own product. The help center and blog are written in Korean, so a sender who does not read Korean will find the documentation hard to use, and a writer who wants paid subscriptions has to be on the Standard, Pro or Enterprise plan.