Most people manage a funnel.
I manage the whole journey.
Revenue does not live in one stage. It compounds across every touchpoint: how leads enter, how fast they convert, how long they stay, how much they grow. My work starts at the beginning of that journey and does not stop at the sale.
The work,
up close.
Spent 8 months on the ground as Customer Service before being handed the keys to rebuild the entire system. That time mattered: I saw firsthand where leads were going cold, where handoffs were breaking, and where customers were quietly churning before anyone noticed.
When I stepped into the RevOps role, each market was still running its own playbook: different tools, different handoffs, no shared visibility. I designed a unified CRM architecture across three layers. At the acquisition layer, Meta and Instagram auto-replies and auto-messages captured inbound leads the moment they landed. In SleekFlow, I built data and status-based tagging, automated broadcasts, scheduled messages, and Click-to-WhatsApp Ads flows that moved leads through the funnel. And in Airtable, auto-updating records pushed real-time status to the right Slack channels, so the team always had visibility. 60+ workflows in total, cutting manual workload 40% while keeping response SLA under five minutes.
The real work was in the lifecycle redesign. With shared visibility across the full journey, we could finally see where leads were going cold, where onboarding was stalling, and where customers were quietly churning before anyone noticed. We rebuilt the journey from cold lead through long-term retained and closed every gap that was bleeding LTV. That is what drove the numbers below, not the tooling.
Plenty of people want to break into customer service but have nowhere safe to practice before facing real, demanding customers. So I built one. CS Simulator lets anyone rehearse live customer conversations across difficulty levels and two languages, then get scored instantly on empathy, solution quality, communication, and professionalism.
The technical core: I used the Claude API in two distinct modes, first as a roleplaying customer persona that adapts its tone to the chosen difficulty, then as a structured evaluator returning category scores as clean JSON. I routed every call through an n8n webhook so the API key never touches the client, wired up Supabase for auth and session management, and handled access through a simple paid flow. Frontend, backend orchestration, AI prompting, and go-to-market, all owned end-to-end.
Community management sounds soft until you treat it like a lifecycle product. I mapped the player journey, identified high-churn moments where players went quiet and did not come back, and designed engagement campaigns and feedback loops at each critical touchpoint.
The result was compounding: more engaged users stayed longer, generated organic content, and brought in new players. What started as community management became a full retention and growth operation, which is the same logic I now apply to CRM and lifecycle work.
I came up through public policy, humanitarian data systems, gaming communities, and startup CRM, which sounds random until you realize it is all the same thing: understanding how people move through systems, and designing those systems to work better for them.
The thread running through all of it is lifecycle thinking. Whether it is a player journey, a customer journey, or a community journey, I find where people get stuck, where they leave, and what would have kept them. Then I build the system that fixes it.
Based in Indonesia. I speak in outcomes. If your lifecycle ops is held together with spreadsheets and good intentions, let's talk.
Open to Operations, CRM, RevOps, and Lifecycle roles. Based in Indonesia, open to remote.
perseus.mazida@gmail.comTools I use.
Systems I build with them.
Let's build something
that keeps working.
Open to RevOps, CRM, Operations, and Lifecycle roles. Based in Indonesia, open to remote.
Start a conversation