Alyn
Professional communication platform for Indonesian teams
PM
Revisi logo: ukuran diperbesar
Designer · Jumat · dari chat PM
Alyn is harsa's own product: one shared Space per project where the chat, the task list, and the documents live together. Office teams run client work on it from their phones, and guests follow progress through a link without signing up. We run our studio on it every day.
The context went missing
Ninety percent of Indonesian professionals lose work context every day. A client revision lands in a group chat and dies there. The same revision arrives again by email. A third version surfaces in a meeting. Three months later nobody can say who approved what. The number behind it: about 29 hours a month on WhatsApp, per person, for work.
Tech teams have Jira and Linear. Everyone else, the ops leads and HR managers and account managers holding companies together, runs on WhatsApp and Excel. SMEs lose sight of long programs to spreadsheets. No bridge connects the two worlds, so decisions keep dying in the gap between them.
Alyn puts the structure back without taking the chat away. One Space holds the conversation, the tasks, and the docs for one piece of work, because in real work those are not three things. Chat becomes task. Tasks attach to docs. The monthly leadership report writes itself. All of it on a phone, over 4G, in Bahasa Indonesia.
- harsa (in-house)
- 2026
- Product, design, engineering
- SaaS B2B · chat, tasks, docs in one Space
- Per organization · Rp100K for 10 members
- In development · dogfooded at harsa
One Space, one screen
The Space view is designed around the PM's loop: open, scroll chat for context, glance task updates, reply or assign, back to chat, twenty to thirty times a day. Chat and task preview share one viewport, with task cards sitting inline in the feed. Compact by default (title, status badge, avatar), expanding on tap.
Navigation stays familiar on purpose. Bottom tabs (Home, Chat, Tasks, Profile), swipe gestures, 48px touch targets. Two tabs at first, five once the Space passes five tasks. Desktop gets the three panel treatment (Space list, chat, task detail), but nothing exists on desktop that the phone cannot do.
- Chat-first inline feed
- Home · Chat · Tasks · Profile
- Compact, expand on tap
- 2 tabs, then 5 past 5 tasks
Client A — Rebranding
PM
09.12
Revisi logo: ukuran diperbesar
Designer
09.20
Riset kompetitor
Client A — Rebranding
PM
09.12
Salin
Buat Tugas
Balas
Revisi logo: ukuran diperbesar
Tugas dibuat Batalkan (5 dtk)
A message should not need a meeting
The superhero feature ships on two paths. Path A mirrors the WhatsApp attach button: tap plus, pick Tugas from the bottom sheet, confirm a modal with two fields (title prefilled from context, assignee, optional deadline). Five taps, under ten seconds. Path B is the power move: long-press any bubble, tap Buat Tugas, done in two. A third path, forwarding WhatsApp to an Alyn bot, waits for a later phase as the adoption opener.
Three rules keep it honest. The modal never asks more than two required fields. The created card appears inline in the chat immediately, linked to its source message, with the assignee notified in under a second. And nothing auto-files silently: the title preview asks for confirmation first, because a wrong guess costs more trust than a tap saves.
- + menu, 5 taps, under 10s
- Long-press, 2 taps, under 5s
- 2 required fields + confirm
- 60% of tasks from chat, month 2
The client sees progress, not excuses
The client never installs anything. An invite link opens the Space in the browser within three seconds: milestones with progress, tasks with threads, a comment box that works like the Google Docs one they already know. Display name only, no signup, token single use with a 14 day default and a 90 day ceiling.
Trust runs both directions. Guests read everything but change nothing, with an Internal badge marking the team's own chatter. Comments are rate limited (five per minute per link, twenty per hour per IP), revocation is one tap and keeps prior comments attributed, and overdue work gets flagged to the PM before the client ever sees it. Approval takes three clicks and zero email threads.
- Link, under 3s, no signup
- Read everything, comment only
- 14 days default, 90 max
- Rate limits + one-tap revoke
Campaign Lebaran 2027
Diundang sebagai tamu · tanpa daftar
3 dari 5 milestone selesai
Komentar sebagai tamu · tampil langsung
Laporan Pimpinan
Client A — Rebranding · November 2026
18/22
Tugas selesai
3
Molor
2/4
Milestone
Molor perlu perhatian
Copywriting · 5 hari
Approval owner · 2 hari
Laporan Pimpinan in one tap
The owner used to spend three to five hours a month assembling reports from chat scrolls and spreadsheets, only to hear the data was last month's. The Laporan button generates a fixed-rule table instead: tasks completed, tasks overdue with names attached, milestone status. Counts, never narrative. No scoring, no stories the data cannot support.
Empty and thin data get explicit states rather than confident fiction. Generation shows a skeleton for two to three seconds, the PDF downloads and previews, and the phone's share sheet forwards it straight to WhatsApp. The first time the owner tried it, the client replied in ten minutes: clear and professional.
- Counts + overdue list only
- Deterministic, no narrative
- PDF download + WA forward
- Explicit state, never fiction
Bottlenecks before complaints
The org dashboard opens on red flags, no scroll required: overdue tasks, stalled Spaces, members to review. The owner's thirty second morning replaced a three hour monthly excavation. Cross-Space filters slice by client, and any task opens its thread in one tap so the follow up lands where the work lives.
Operations stay cheap. Deactivating a member and reassigning eight tasks takes two minutes with a full record. Trial timers, pending invites older than seven days, and response tracking sit on the same screen. The console assumes one busy owner, not a data team.
Biro Kreatif
5 Space aktif · 18 anggota · minggu ini
4 hal perlu perhatian
47
Selesai
12
Molor
30 dtk
Cek pagi
1 anggota nonaktif · 8 tugas pindah ke PM · 2 menit
Laporan terkirim · klien balas 10 menit
- Red flags, no scroll needed
- Cross-Space, per client
- 8 tasks, 2 minutes, audited
- Tracked, 2h internal target
Grows when you do
One data model serves two people and a thousand. A tasklist Space and a program Space are the same objects; only the view changes, so nothing ever migrates and nobody re-learns the tool. New capability arrives as an offer, never an obligation: past fifteen tasks, a week of life, and three members, Alyn suggests the Project upgrade and accepts no as a complete answer.
Walk the three shapes. Same Space, same tasks, wider lens.
Tasklist
The default. Flat tasks with three states (todo, in progress, done) for two people who just need shared memory. Zero methodology, available from the second the Space exists.
Four weeks in the product
The project manager
Skeptical of yet another tool, talked into a one month trial. A template spins up the rebranding project in under two minutes with milestones prebuilt. Week two, the client revises over WhatsApp out of habit. The PM forwards it into the Space and it lands as a task on the designer's list. Month end, one tap builds the report: 18 of 22 done, 3 overdue.
The designer
Starts lost across eight groups and a forgotten Trello password. Inside three shared Spaces the fog lifts: one list sorted by deadline, logo due today. The designer works, uploads, marks done, and the PMs find out without a single status chat. A deadline needs a day; a comment and a mention get approval. No meeting. Week tally: 12 of 15.
The client
Two hours on read, one line back: still in process. Then an invite link, no signup, and suddenly five milestones with three complete. The client comments green options onto the mockup thread, approves in three clicks, watches the overdue flag system work before ever needing it.
The owner
Thirty seconds where three hours used to go: five Spaces, eighteen members, this week's completions and overdues. A client stalls past seven days; the owner sees it before the client complains. Report tap, PDF over WhatsApp, reply in ten minutes. When a teammate resigns, eight tasks move to the PM in two minutes flat, with a full record of what moved.
Decisions, on the record
One data model, not three modules
Slack, Notion, and Lark stitch chat to tasks in the interface layer because their schemas grew up separate. Alyn starts with one Space entity holding messages, tasks, and docs with direct links between them. A task remembers its source message; a doc points at a task. Competitors cannot follow without a full rewrite. That is the hard-to-copy part. Validated against 50K messages plus 500 tasks per Space without query degradation.
More power when you ask for it
Every tool makes the user pick a methodology on day one: kanban, scrum, waterfall. Alyn ships a tasklist with the full feature set from the first second and offers Project, then Program, only when the Space earns it. If under 20% convert by month three, the trigger threshold gets re-examined, not the user.
Priced per organization
Rp100K a month covers ten members with every feature and unlimited Spaces, then Rp300K for thirty and Rp750K for a hundred. No per-seat meter running while the team grows. The willingness assumption goes to ten beta agencies for validation. Expired trials lock invites and new Spaces only; editing and viewing continue, and downgrades preview their losses with zero data loss.
Indonesian first, not translated
The UI is authored in Bahasa Indonesia with formal and informal registers, not localized after the fact: Ramadan and THR templates, 17 Agustus workflows, DD/MM/YYYY dates, Rupiah formatting, WIB throughout, and every error message in Indonesian with no HTTP codes. Global tools exclude non-tech teams by language; Alyn starts where they live.
Phone first, honest about signal
Three quarters of Indonesian traffic is mobile, so the app loads in under three seconds on 4G, even on cheap Android phones. Updates push instantly over one connection; fancier realtime tech waits until volume earns it. Disconnects get a quiet banner within half a second, drafts survive on the device, and the checkmarks speak WhatsApp: grey pending, green sent.
Money flows on day one, by hand if needed
Waiting on a payment gateway would stall all revenue learning, so the launch floor is manual transfer plus activation by our admin team within one working day, with receipts carrying an explicit tax note until the payment provider hardens the path in a later phase. Five paying orgs in three months is the target the floor exists to hit.
Reports tell counts, never stories
The leadership report is a fixed-rule table: completed, overdue, milestones. No scoring, no generated narrative, explicit empty states. An AI summary would need data density the product does not have yet, so it waits for a later phase. And a guardrail metric watches the feature: if report opens climb while task adoption stays flat, report optimization stops.
Non-goals, written down
Jira sync, company login (SSO), running on their own servers, a native app, WhatsApp mirroring, and AI summaries are all explicitly out of the launch scope, each with its reason and its phase. The launch floor names eight capabilities that must all ship, with a pre-agreed cut list in firing order (reports shrink to spreadsheet export first) if the four month clock slips. That written list of noes is what lets the yeses ship on time.
In development, used by us first
Alyn runs harsa's own work before it runs anyone else's. When a screen annoys us on a Tuesday, it gets fixed before any customer ever feels it. The three month bar is concrete: five paying orgs with over half of them strangers. Trials must convert above two percent, and fewer than ten percent may leave.
Later phases fill the scoped gaps: kanban boards, drag-select to task, inline approvals, program tracking UI. The enterprise bets wait further out: Jira sync, company login, AI summaries. Each phase has its measurable outcomes written before it, the same discipline that kept the launch list short and shippable.
Alyn is the best argument for how we work. We are our own first client. Have a product that needs this kind of care? Start a conversation.