<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Yopie Suryadi on Medium]]></title>
        <description><![CDATA[Stories by Yopie Suryadi on Medium]]></description>
        <link>https://medium.com/@yopiesuryadi?source=rss-ce532905a140------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9lQ3Ico72l6BCzcFXs6tPw.jpeg</url>
            <title>Stories by Yopie Suryadi on Medium</title>
            <link>https://medium.com/@yopiesuryadi?source=rss-ce532905a140------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:03:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yopiesuryadi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I Built mailbot the Same Way You Would]]></title>
            <link>https://medium.com/@yopiesuryadi/i-built-mailbot-the-same-way-you-would-59aa2b29a63c?source=rss-ce532905a140------2</link>
            <guid isPermaLink="false">https://medium.com/p/59aa2b29a63c</guid>
            <dc:creator><![CDATA[Yopie Suryadi]]></dc:creator>
            <pubDate>Sat, 28 Mar 2026 07:11:43 GMT</pubDate>
            <atom:updated>2026-03-28T07:11:43.929Z</atom:updated>
            <content:encoded><![CDATA[<p><em>No special access. No internal favors. Just a </em><a href="http://mailtarget.co/pricing"><em>Mailtarget</em></a><em> plan and an idea.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tv8HyLMKXWj5_R6bQqv_ng.png" /><figcaption>Building in public</figcaption></figure><p>I’m the founder of <a href="http://mailtarget.co/">Mailtarget</a>. We’ve been running email infrastructure for nine years. Companies send millions of emails through our platform every day. And when I decided to build mailbot, I opened a browser, went to mailtarget.co, and signed up for a plan. Like a stranger. No Slack message to the engineering team. No special IP allocation, no priority queue, no backdoor. Just the public API, the documentation site, and a cup of coffee at midnight.</p><h4><strong>Why would a founder do that?</strong></h4><p>Because I needed to know something that no internal demo, no QA report, and no customer success metric could tell me. I needed to know what it actually feels like to build on <a href="http://mailtarget.co/">Mailtarget</a> when nobody knows who you are. Every platform looks great from the inside. The dashboards work. The endpoints respond. The team is one Slack message away when something breaks. But that’s not your experience. Your experience is the documentation page at 2am when everyone’s asleep. The error message that doesn’t explain what went wrong. The onboarding flow that assumes you already know things you don’t.</p><p><em>I wanted that experience. The real one.</em></p><h4><strong>The first night</strong></h4><p>I started on a Saturday. No one from the team knew what I was doing. I created an account, set up a sending domain, configured SPF, DKIM, DMARC through the standard flow, and sent my first test email. It arrived. In the inbox, not spam. Good start.</p><p>Then I started building <a href="http://getmail.bot/"><strong>mailbot’s core: a programmable inbox system where developers and AI agents can send and receive email through a simple API</strong></a><strong>.</strong> The first thing I hit was the configuration for inbound email. The <a href="http://getmail.bot/docs">docs</a> explained the concept, but I had to figure out parts of the implementation myself. There was a moment where I stared at a 400 error for twenty minutes before realizing I had the payload format wrong. No one to ask. No internal team to ping. Just me and the error message.</p><p>I noted it down. That part of the docs has since been improved.</p><h4><strong>What actually worked</strong></h4><p>The core infrastructure held up. That was the most important finding. Transactional emails went out and arrived. Not “arrived eventually.” Arrived fast. SPF passed. DKIM passed. DMARC aligned. The reputation was real. I built <a href="http://getmail.bot/">mailbot’s</a> entire email layer on top of <a href="http://mailtarget.co/">Mailtarget</a>. Every email that <a href="http://getmail.bot/">mailbot</a> sends for its users goes through the same infrastructure that powers millions of emails for other companies. The same servers. The same IPs. The same deliverability standards. And it just worked. No special configuration. No enterprise contract. No phone call to the sales team.</p><p>This isn’t a proof of concept. <a href="http://getmail.bot/"><strong>mailbot</strong></a><strong> is live</strong>, serving real users, handling real email. On the same plan you can sign up for today.</p><h4><strong>What didn’t work (at first)</strong></h4><p>I’d be lying if I said it was all smooth. There were error messages that told me something failed without telling me why. There was a moment where I misconfigured a domain and spent an hour debugging what turned out to be a DNS propagation issue that the dashboard could have warned me about.</p><p>There were times I thought, “If I just messaged the team, this would take five minutes instead of an hour.” But I didn’t. Because the whole point was to feel what you feel.</p><p>Every friction point I found, I documented. Some were fixed within days. Others are still on the roadmap. But I know about them now. Not from a bug report. From frustration. <em>That’s a different kind of knowing.</em></p><h4><strong>The product I want Mailtarget to be</strong></h4><p>Here’s the thing about building your own product as a customer: it changes how you think about everything. Every missing tooltip becomes personal. Every confusing error message is something you remember struggling with. Every undocumented edge case is an hour of your own life you’ll never get back.</p><p>I want Mailtarget to be the kind of platform where the founder doesn’t need special treatment. Where the API is complete enough, the docs are clear enough, and the infrastructure is reliable enough that someone can go from zero to production without knowing anyone at the company. mailbot is my proof that we’re getting there.</p><p>Not because it’s perfect. But because I built it the same way you would. And it worked.</p><h4><strong>If</strong> <strong>you’re</strong> <strong>thinking</strong> <strong>about</strong> <strong>building</strong></h4><p><strong>You don’t need permission.</strong> You don’t need a partnership or an enterprise contract or a special relationship with the team. If you’re building something that needs email, a notification pipeline, a transactional system, a SaaS that sends receipts or onboarding sequences, an agent that communicates through email, you already have everything you need.</p><p>I signed up. I built. It worked. That’s the standard I’m holding us to.</p><p><a href="https://getmail.bot/">https://getmail.bot</a> | <a href="https://mailtarget.co/">https://mailtarget.co</a> | <a href="https://github.com/yopiesuryadi/mailbot-programmable-inbox">https://github.com/yopiesuryadi/mailbot-programmable-inbox</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59aa2b29a63c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Spent 3 Weeks Playing With AI Tools. Then I Decided to Give Agents an Email Address.]]></title>
            <link>https://medium.com/@yopiesuryadi/i-spent-3-weeks-playing-with-ai-tools-then-i-decided-to-give-agents-an-email-address-16d2c24d5b9b?source=rss-ce532905a140------2</link>
            <guid isPermaLink="false">https://medium.com/p/16d2c24d5b9b</guid>
            <dc:creator><![CDATA[Yopie Suryadi]]></dc:creator>
            <pubDate>Sat, 21 Mar 2026 16:24:08 GMT</pubDate>
            <atom:updated>2026-03-21T16:24:08.291Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f861t2EwI9NZqRwHhHfWsw.jpeg" /><figcaption><strong><em>“The result never betrays the process.”</em></strong></figcaption></figure><p>I spent the last 3 weeks playing with AI tools and building a few nice to have things.</p><p>At first, I was chasing the same question everyone else was chasing:</p><p>Can AI actually improve productivity, or are we just surrounding ourselves with impressive demos and nice to have tools?</p><p>My conclusion is simple.</p><p>AI can <strong>absolutely</strong> improve productivity.</p><p>But not in the clean, glamorous way social media makes it look.</p><p>That part bothered me.</p><p>Every day I saw more posts, more videos, more threads showing what AI could do. Build this. Automate that. Create something in minutes. Amazing outputs everywhere.</p><p>What almost nobody talked about was the cost behind the result.</p><p>Not only the token cost.</p><p>The cost of trial and error.<br>The cost of failed orchestration.<br>The cost of hallucinations.<br>The cost of screenshots, re-runs, broken flows, wrong deletes, wrong reverts, and hours of trying to figure out why something worked once and then stopped working the next time.</p><p>A lot of AI content today glorifies the outcome.<br>Very little of it educates people about the heavy side of actually building with these tools.</p><p>That was where things started to change for me.</p><p>I am the founder of Mailtarget. I know Mailtarget has earned trust from the industry and from its customers. But I also knew this was not the right time to push AI experimentation directly into the Mailtarget operating environment, with multiple teams and moving parts involved.</p><p>So I took a different path.</p><p>I subscribed to Mailtarget as if I were just another user.<br>No special help.<br>No founder privilege.<br>No shortcut because I happen to be the CEO.</p><p>I wanted to see if something real could be built from the outside, using the same infrastructure a customer would use.</p><p>And it worked.</p><p>That became <a href="http://getmail.bot/">mailbot</a>.</p><p>Website: <a href="https://getmail.bot/">https://getmail.bot</a><br>Repo: <a href="https://github.com/yopiesuryadi/mailbot-programmable-inbox">https://github.com/yopiesuryadi/mailbot-programmable-inbox</a></p><p>The deeper reason behind it was this:</p><p>As a non-technical founder, I felt I had to build something for technical people.</p><p>That is uncomfortable to admit, because the obvious gap is right there.<br>I do not have deep technical ability.</p><p>If I stayed inside the safe zone of non-technical thinking, I would probably keep producing ideas that felt interesting but solved nothing important. I have been there. I have done that.</p><p>So I forced myself into a harder problem.</p><p>I chose to work on something that could actually solve a problem for technical people.</p><p>That decision took me into a level of mess I was not prepared for.</p><p>There were screenshots everywhere.<br>Agent orchestration kept going wrong.<br>Things got deleted by mistake.<br>Things got reverted to earlier versions because I did not fully understand what I was touching.<br>Some workflows looked promising, then broke in ways I could not explain.</p><p>More than once, I felt like giving up.</p><p>Then I realized something important about myself.</p><p>I do not have technical strength.<br>What I do have is resilience.</p><p>I fall.<br>I make mistakes.<br>I keep going.</p><p>If I were the kind of person who stopped at that point, Mailtarget would never have made it to year ten.</p><p>At one point I looked at an image that reminded me what I needed to do next. It gave me enough clarity to make one decision:</p><p><strong><em>“finish first, improve later.”</em></strong></p><p>That decision mattered.</p><p>Because somewhere inside all that chaos, the real problem started to become clearer.</p><p>No matter how sophisticated AI becomes, building with it still feels a lot like solving a puzzle.</p><p>And when you solve a puzzle, the first thing you need is not the first piece.<br>It is not the edge.<br>It is not the top corner.</p><p><strong>You need the full picture.</strong></p><p>That is what founders are supposed to protect.<br>The picture.<br>The vision.</p><p>Today, <a href="http://chatgpt.com/">ChatGPT</a>, <a href="http://claude.com/">Claude</a>, <a href="http://perplexity.ai/">Perplexity</a>, and many other AI tools can validate an idea much faster than they could before. That changes a lot.</p><p>But even now, vision still matters.That insight led me to another conclusion.</p><p>Most AI tools still live inside chat.</p><p>And chat is fine.<br>I am not against chatbots.<br>They have a place.</p><p>But chat has limits.</p><p>Email has different strengths.<br>It is private.<br>It works across devices.<br>It works across contexts.<br>It does not require someone to be inside a dashboard or sitting in a live chat window.</p><p>With email, you send a message and the agent can respond in context.</p><p>That is why I do not see email and chat as competing with each other.<br>I see them as complementary.</p><p>And that is why the idea behind mailbot became so compelling to me.</p><p>Give your agent an inbox.</p><p>Not just a prompt box.<br>Not just a chat thread.<br>An inbox.</p><p>Because when an AI agent can operate through email, a different set of use cases opens up.</p><h3>Where I Think This Becomes Useful</h3><h4>1. Customer support and ticketing</h4><p>This is still the most obvious use case to me.</p><p>A lot of people have become pessimistic about email support. They assume email means slow response, no continuity, and no real conversation.</p><p>I think that changes in the AI era.</p><p>Email can become conversational again.<br>It can stay recorded inside a system.<br>It can preserve the thread.<br>It can make support easier to trace, easier to review, and easier to improve.</p><p>That is a big shift.</p><h4>2. Operational workflows</h4><p>A lot of important work still starts through email.</p><p>Requests.<br>Approvals.<br>Confirmations.<br>Invoices.<br>Documents.<br>Escalations.</p><p>These workflows do not disappear just because chat tools exist.</p><p>They become more useful when an agent can participate in them without breaking the context.</p><h4>3. Traceability and accountability</h4><p>Agents are everywhere now, whether people admit it or not.</p><p>If that is true, then companies will need channels that make tracing easier, not harder.</p><p>Threaded email helps with that.<br>It is recorded.<br>It is reviewable.<br>It is easier to inspect when something goes wrong.</p><p>That matters.</p><h3>What mailbot Actually Is</h3><p><a href="http://getmail.bot/">mailbot</a> is a way to give your agent an email identity on top of Mailtarget’s infrastructure.</p><p>Instead of treating email as a side channel, it treats email as part of the agent workflow itself.</p><p>That means your agent can work with:</p><p>- inboxes<br>- messages<br>- threads<br>- events<br>- replay</p><p>The technical framing matters, but that is not the most important part of the story for me.</p><p>The most important part is what the process taught me.</p><p>Patience matters.<br>Process matters.<br>Even with AI, nothing meaningful is truly instant.</p><p>And I still believe this:</p><p><strong><em>“The result never betrays the process.”</em></strong></p><p>mailbot is still early. It’s still beta.</p><p>But it did not come out of theory.<br>It came out of frustration, persistence, wrong turns, and a refusal to stop just because I was outside my comfort zone.</p><p>That is why it matters to me.</p><p>Yopie Suryadi</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16d2c24d5b9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m Not a Developer. Last Week I Built an Autonomous Email System Anyway.]]></title>
            <link>https://medium.com/@yopiesuryadi/im-not-a-developer-last-week-i-built-an-autonomous-email-system-anyway-4b7754638aea?source=rss-ce532905a140------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b7754638aea</guid>
            <dc:creator><![CDATA[Yopie Suryadi]]></dc:creator>
            <pubDate>Mon, 23 Feb 2026 06:11:59 GMT</pubDate>
            <atom:updated>2026-02-23T06:48:31.905Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>And all I used was a vision, an AI agent, and Mailtarget’s API.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tb6JemyTP5ECmU21EBXF4w.jpeg" /></figure><p>I have a confession to make.</p><p>I am the CEO of an email infrastructure company. I have been in the email industry for years. I talk about APIs, webhooks, SMTP relays, and deliverability at conferences.</p><p>And I cannot write a single line of code.</p><p>Not one.</p><p>I am what the tech world politely calls “non-technical.” What that actually means is: I have spent my entire career relying on developers to build the things I imagine. I have great ideas. Someone else always had to execute them.</p><p>Until last week.</p><h3>The Week That Changed Everything</h3><p>It started as curiosity. I had been hearing about <a href="http://openclaw.ai/">OpenClaw</a> for a while. An AI agent framework that runs locally on your machine. You give it tools, skills, context, and a task. It figures out the rest.</p><p>I decided to try something ambitious. I wanted to see if I could integrate <a href="https://mailtarget.co/email-api">Mailtarget’s transactional email API</a> into OpenClaw. By myself. No developer. No technical support. No one looking over my shoulder.</p><p>I gave myself a week.</p><p>What followed was one of the most surprising weeks of my career.</p><h3>Day One: Setting the Context</h3><p>I started by giving the OpenClaw agent context about Mailtarget. What the API does. What the endpoints look like. What I wanted to accomplish.</p><p>I told it: I want to send a real email campaign to a real recipient list using Mailtarget’s API. I want you to write the email, design the HTML, and send it.</p><p>The agent started asking questions. Clarifying. Mapping out the flow.</p><p>No error messages. No “you need to install this library first.” Just a conversation.</p><p>I realized immediately that this was different from anything I had tried before.</p><h3>Day Three: The Agent Writes Its First Email</h3><p>By day three, something remarkable happened.</p><p>The agent wrote the email HTML from scratch. Not a template. Not a pre-built design. A fully structured HTML email with headers, body copy, call-to-action buttons, and responsive layout.</p><p>I had given it Mailtarget’s Transmission API structure. It understood the payload format. It built the request body. It called the API.</p><p>The email landed in my inbox within seconds.</p><p>I stared at it for a long time.</p><p>It looked good. Better than good, actually. The copy was clear. The layout was clean. The call to action was obvious.</p><p>A non-technical CEO had just sent a professionally designed email campaign without touching a single line of code. The agent wrote everything. I just directed.</p><h3>Day Five: The Report Arrived Before I Asked</h3><p>This is the part that genuinely surprised me.</p><p>I had set up Mailtarget’s webhook integration. When a recipient opens an email, Mailtarget fires an event to a webhook endpoint. When they click a link. When the email bounces.</p><p>The OpenClaw agent was listening.</p><p>Within minutes of the campaign going out, the agent started receiving webhook events. It compiled them into a report. Opens. Clicks. Deliveries. Bounces. All organized. All real time.</p><p>I had not asked for a report. The agent just built one because it knew that was the logical next step.</p><p>That is when everything became clear to me.</p><h3>The Three Players</h3><p>Here is what I realized after that week.</p><p>There are three players in this new model of email marketing.</p><p><strong>Mailtarget handles the infrastructure.</strong></p><p><strong>The delivery engine. The reliability. The authentication layer (SPF, DKIM, DMARC). The dedicated IP. The suppression lists. The webhook system that fires events in real time. The 99.9% uptime SLA. That is our job. We are obsessed with it. We have been building it for years so that you never have to think about it.</strong></p><p><strong>OpenClaw handles everything else.</strong></p><p>The writing. The design. The sending logic. The reporting. The optimization. Everything that used to require a developer, a copywriter, a designer, and a marketing ops person. The agent handles it. All of it. In one session.</p><p><strong>You just need three things.</strong></p><p>A vision. A strategy. And the willingness to step outside your comfort zone.</p><p>That is the entire model. Three players. Three roles. No code required.</p><h3>What This Actually Means</h3><p>Let me be specific about what the OpenClaw agent can do when connected to Mailtarget’s API.</p><p>It can write email copy in any voice or style you define. It can design HTML emails that render correctly across email clients. It can manage recipient lists and send to segments. It can handle substitution data so every email feels personal. It can enable open tracking and click tracking with a single flag. It can receive webhook events in real time and process them automatically. It can generate reports, surface anomalies, and suggest what to do next.</p><p>And it can do all of this without you writing a single line of code.</p><p>The only thing you need to bring is the strategy. Who are you sending to. What do you want them to feel. What action do you want them to take. What does success look like.</p><p>The rest is handled.</p><h3>Why This Is a Breakthrough</h3><p>We have been talking about AI and email marketing for years. AI will personalize your subject lines. AI will predict the best send time. AI will optimize your content.</p><p>These are incremental improvements. They make existing workflows slightly better.</p><p>What happened last week was categorically different.</p><p>The AI did not optimize a workflow. It replaced the workflow. The entire pipeline. From content creation to delivery to reporting. End to end. Autonomously.</p><p>And it was connected to real infrastructure. Not a toy demo. Not a sandbox experiment. Mailtarget’s production API. Real emails. Real recipients. Real delivery data.</p><p>That distinction matters enormously.</p><p>A lot of AI email tools are built on top of shared infrastructure with limited visibility. You send. You wait. You check a dashboard. You guess.</p><p>This is different. The agent sends through Mailtarget’s infrastructure. Mailtarget fires webhook events back to the agent in real time. The agent knows exactly what happened to every email. It has full visibility. Full control. Full accountability.</p><p>That is what enterprise-grade email infrastructure makes possible. And now, that infrastructure is accessible to anyone who can type a clear instruction to an AI agent.</p><h3>The Comfort Zone Problem</h3><p>I want to say something to other non-technical founders and executives who are reading this.</p><p>We have a habit of deferring technical work to technical people. This is reasonable. It has worked for decades. It is why we hire engineers and developers and technical co-founders.</p><p>But something has shifted.</p><p>The barrier to executing technical work has dropped dramatically. Not because the underlying infrastructure got simpler. Mailtarget’s API is still an API. Webhooks still require endpoints. Authentication still requires proper configuration.</p><p>But the AI agent handles all of that. It understands the technical layer. You just need to understand what you want.</p><p>The only thing standing between you and an autonomous email system is your comfort zone.</p><p>Last week I stepped outside mine. The results were extraordinary.</p><p>I am not suggesting you abandon your engineering team. I am suggesting that the definition of what a non-technical person can execute has permanently expanded. And the executives and founders who recognize this first will have a significant advantage.</p><h3>What to Try</h3><p>If you are an OpenClaw user, connect the <a href="https://mailtarget.co/email-api">Mailtarget API</a>. Give the agent your API key. Tell it what you want to send and who you want to send it to. Watch what happens.</p><p>If you are not yet using <a href="http://openclaw.ai/">OpenClaw</a>, this is a good reason to start.</p><p>And if you want to understand the infrastructure layer, the API documentation is at developer.mailtarget.co. The Transmission API accepts HTML content, manages recipients, enables open and click tracking, and fires webhook events for every delivery action.</p><p>The full stack is available. The agent handles the complexity. You bring the vision.</p><h3>A Final Thought</h3><p>We built <a href="http://mailtarget.co/">Mailtarget</a> to be the most reliable email delivery infrastructure in Southeast Asia. Precision engineering. Enterprise-grade. Built for teams that need to know their emails arrive.</p><p>We built it for developers. For engineering teams. For technical operations.</p><p>Last week I discovered that we also built it for the non-technical CEO who just needed the right AI agent to unlock it.</p><p>That was not part of the original plan.</p><p>But it might be the most exciting thing we have ever built.</p><p>If you are an OpenClaw user, the skill is already built. Go to ClawHub and install it:</p><p><a href="https://clawhub.ai/masasdani/mailtarget-email">clawhub install masasdani/mailtarget-email</a></p><p>That’s it. One command. The skill is ready. Give it your Mailtarget API key, tell the agent what you want to send and who to send it to, and watch what happens.</p><p>If you are not yet using OpenClaw, this is a good reason to start. The Mailtarget skill is live at <a href="https://clawhub.ai/masasdani/mailtarget-email">clawhub.ai/masasdani/mailtarget-email.</a></p><p><em>Yopie Suryadi is the founder and CEO of </em><a href="http://mailtarget.co/"><em>Mailtarget</em></a><em>, an enterprise email infrastructure platform. mailtarget.co</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b7754638aea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nine Years of Grit, Grace, and Growth.]]></title>
            <link>https://medium.com/@yopiesuryadi/nine-years-of-grit-grace-and-growth-1c0c14a59e66?source=rss-ce532905a140------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c0c14a59e66</guid>
            <dc:creator><![CDATA[Yopie Suryadi]]></dc:creator>
            <pubDate>Sat, 25 Oct 2025 02:57:08 GMT</pubDate>
            <atom:updated>2025-11-02T07:07:49.515Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bny5qU0irF5epFLkBdNphg.jpeg" /><figcaption>The email company.</figcaption></figure><p>Nine years.</p><p>We’ve been through hell and back. It all started with a dream and a lot of mistakes. A lot. This is the only job me and Masas have ever had. We don’t have a backup plan. Our families live off Mailtarget. So do our teammates.</p><p>This isn’t just work, it’s life.</p><p>Over the years, people came and went. Joy and pain, hope and heartbreak, they all took turns.</p><p>Moments when we built our own infrastructure because we were tired of relying on others, and it worked.</p><p>Moments when we were trusted with accounts bigger than what we thought we could handle.</p><p>Moments when we had to face contract cuts, delays, and churns, and still chose to move forward.</p><p>Moments when cash was thin, and we still decided not to take the shortcuts.</p><p>Moments when we said no to investments that could have saved us in the short term, because we wanted to protect what we built in the long run.</p><p>Moments when we learned that integrity is expensive, but it’s the only thing that compounds over time.</p><p>Moments when we hit global standards, proving that a local company can be world-class.</p><p>Moments when we rebuilt, rebranded, and restarted again and again.</p><p>Moments when we realized we don’t have to be the biggest, we just have to be the most reliable.</p><p>Moments when we expanded our vision, from product to platform, from local to regional, from users to partners.</p><p>When we learned that breakthrough doesn’t always mean growth in numbers, sometimes it means staying steady when everyone else gives up.</p><p>Fail fast. Execute fast. That’s what we’ve done since day one. And one of my greatest joys is seeing how my team keeps growing. Not just in skill, but in character, confidence, and ownership. Watching them become better versions of themselves is the quiet reward that keeps me going.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*top0osIa6xjjVJ_3GPbGbg.jpeg" /><figcaption>Cheers for 9 years</figcaption></figure><p>I give my utmost respect to Masas. He stayed when everybody else left. I’ve seen him grow, not just as a CTO, but as a partner, a leader, and a man. Twelve years side by side through seasons that could break most teams, but somehow, we’re still here.</p><p>And to Johan &amp; Astrid, they believed in us when nobody else did. Their faith became our foundation.</p><p>At the end of the day, nine years is not a short time. But we’re just getting started.</p><p>The first phase is done, now it’s time for a new season. I’ve learned that it’s not me or Masas who are great.</p><p><strong><em>It’s God.</em></strong></p><p>If He has brought us this far, He will also provide what’s next.</p><p>We’ll leave it to Him.</p><p><strong>Happy 9th anniversary, Mailtarget.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c0c14a59e66" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Go Back to That Pool: My Healing Story]]></title>
            <link>https://medium.com/@yopiesuryadi/dont-go-back-to-that-pool-my-healing-story-1f81a2e1ba38?source=rss-ce532905a140------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f81a2e1ba38</guid>
            <dc:creator><![CDATA[Yopie Suryadi]]></dc:creator>
            <pubDate>Thu, 11 Sep 2025 01:25:55 GMT</pubDate>
            <atom:updated>2025-09-11T01:25:55.580Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YEcaN-G1axljFl0Xf66_Ug.png" /><figcaption>Made with AI</figcaption></figure><p>For years, my right ear lived in silence. Hearing loss and constant tinnitus — that endless ringing — became my daily companion. I went to multiple doctors, and the conclusion was always the same: <em>this cannot be healed</em>.</p><p>One of my biggest regrets happened on <strong>Sunday, May 18</strong>. My wife Lia asked me to stay overnight at my dad’s house. I refused, because the next morning I had an ENT appointment. The next day, <strong>May 19</strong>, my father passed away. A week later, I went to the doctor — and heard the verdict that my hearing loss was permanent. It felt like a double blow.</p><h3>July 5: The Wedding and the Miracle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wwh24cNPm95AtfklXZ-1wQ.jpeg" /><figcaption>The miraculous wedding</figcaption></figure><p>Fast forward to <strong>July 5</strong>, at the wedding of my best friend David &amp; Caitlin. At that wedding, something extraordinary happened.</p><p>My ear was prayed for and anointed with olive oil that Daniel had brought all the way from Sicily. Ankia and everyone sitting at <strong>Table №5</strong> (funny enough, 5 also means <em>grace</em>) agreed in prayer for my healing.</p><p>As the oil touched my ear, <strong>everything muted</strong>. And then — suddenly — it opened. Exactly the same sensation I felt the very first time I wore a hearing aid years ago. Suddenly, the world was in <strong>stereo</strong> again.</p><p>That night, I made a decision: <strong>no more hearing aid</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pSF9UhQEZNmu2FDcQzG7eQ.jpeg" /><figcaption>Daniel prayed for my ear.</figcaption></figure><h3>August 5: From Silent Witness to Bold Testimony</h3><p>A month later, on <strong>August 5</strong>, I was in Hamisi, Kenya, on a mission trip. The sound system there blasted at <em>minimum 108db</em> — loud, very loud. Liz looked at me and casually asked: <em>“Your ear is okay, right?”</em></p><p>That small question stirred something in me. I was asked to share, but I didn’t know what to say. At the last moment, I chose to share <strong>my healing testimony</strong>.</p><p>I spoke in Bahasa Indonesia. Liz translated into English. And then another translation went into Swahili. Three languages, one message: <strong>God heals.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7o2HDPQkHz5b1X4DqHDqcg.png" /><figcaption>I went as a <strong>documentarian</strong>. God asked me to be a <strong>witness</strong>. Different job description. Same King.</figcaption></figure><h3>September 5: The Struggle</h3><p>Then came another twist. On <strong>September 5</strong>, exactly one month later, my right ear slowly began to lose sound again. Day by day, hearing became muffled.</p><p>It was painful — not just physically, but spiritually. I had already shared my testimony publicly. I had thanked God every day. I had declared that I was healed. So why was this happening again?</p><p>That week, I remembered the sermon Ankia preached in Hamisi. She spoke about the paralyzed man at the Pool of Bethesda. For 38 years, he had waited for the water to stir. But when Jesus healed him, the key was this: <strong>don’t go back to that pool.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohijhliVVEi6u5Ev6IxBDw.jpeg" /><figcaption>Don’t go back to that pool!</figcaption></figure><h3>The Doctor’s Visit</h3><p>I booked another ENT appointment. The day before the visit, I told Lia: <em>“I see something being pulled from my ear, and then it opens again.”</em></p><p>The next day at the doctor, that vision became reality. She said, <em>“There’s a blockage.”</em> And with one careful pull, I felt it — something was removed, and my hearing came rushing back. Stereo, full, alive.</p><p>I could only smile and whisper, <em>“Thank You, Jesus.”</em></p><h3>Don’t Go Back to That Pool</h3><p>This whole journey taught me:</p><ul><li>Healing is real, but so is the test.</li><li>Faith is declaring life even when the evidence looks the opposite.</li><li>Gratitude and perseverance are stronger than fear.</li></ul><p>So today, I remind myself — and maybe you too:</p><blockquote><strong>Don’t go back to that pool.</strong></blockquote><p>Declare life. Speak hope. Believe.</p><p>Our God is bigger than any of our problems.</p><p><em>If you’re struggling with something you think is permanent, I pray this story gives you courage. Healing might not come the way you expect, but it will always come through the One who knows you best.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f81a2e1ba38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Salt & Light Mission Trip: Dying to Self, Finding Fire]]></title>
            <link>https://medium.com/@yopiesuryadi/salt-light-mission-trip-dying-to-self-finding-fire-560f36ed9233?source=rss-ce532905a140------2</link>
            <guid isPermaLink="false">https://medium.com/p/560f36ed9233</guid>
            <dc:creator><![CDATA[Yopie Suryadi]]></dc:creator>
            <pubDate>Thu, 21 Aug 2025 04:27:32 GMT</pubDate>
            <atom:updated>2025-08-28T00:56:28.247Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qO1LjmxFUdhuWD-kwAVg3A.jpeg" /><figcaption>Salt &amp; Light 2025</figcaption></figure><p>I didn’t go to Kenya to be comfortable. I went to obey. And sometimes obedience looks like squeezing into a van with 16 people and a few cockroaches, eating food your palate doesn’t know yet, and whispering to yourself on a sleepless flight: <em>flesh must die</em>. This was the <strong>Salt &amp; Light Mission Trip</strong> with Tamim Ministries. And this is my journal from Hamisi, Kenya — written as much for my future self as for anyone else.</p><h3>Day 1 — Jakarta → Singapore → Mumbai → Nairobi: “Why am I doing this?”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sJiuBfcY6mSps6xgWFFfaw.jpeg" /><figcaption>Me, Andre, Liz, and Elsi while transit in Singapore</figcaption></figure><p>We left Jakarta early — me, Andre, and Liz — still half-asleep, lugging backpacks and faith. A short hop to Singapore, five hours of transit, then we met the rest of the team and boarded the long flight to Nairobi with a three-hour stop in Mumbai.</p><p>Somewhere in that cramped economy seat, with the AC either too cold or not cold enough, I started to regret coming. <em>Why </em>did I sign up for this? But I knew the answer before I asked it: on mission, <strong>the flesh must die</strong>. My comfort, my routine, my preference — <em>semua harus mati</em>. That was the first lesson, and I hadn’t even arrived.</p><h3>Day 2 — Nairobi at Dawn, Hamisi by Dusk</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYRxu9FAM7HbS-0J911h2A.jpeg" /><figcaption>Welcome to Nairobi</figcaption></figure><p>We landed at 5:30 a.m. Nairobi was in its winter mood — around 12°C. Cool. Clean. A surprise to my Jakarta lungs.</p><p>Then the road trip: nearly ten hours from Nairobi to Hamisi. Sixteen people squeezed into a small vehicle. Laughter, worship, quick naps, and yes — <em>kecoak di mana-mana</em>. It wasn’t pretty, but it was real. Comfort officially exited the chat.</p><p>By 6:30 p.m. we reached <strong>Mago Guest House</strong>. Sheila, the owner, met us with a warmth that cut through the fatigue. Dinner was our first full African meal. New spices, different textures. My Jakarta taste buds needed humility. That night, I reminded myself: <em>we don’t come here for convenience; we come here to be changed</em>.</p><h3>Day 3 — Communion, a Dream, and Fresh Fire</h3><p>We began with communion as a team — Scripture, worship, prayer. I’ve had sleep issues for a long time, and I was honestly worried about nights here. Strangely, I slept deeply and even woke before my alarm. In the night I had a vivid dream: I was pulling worms out of my ankle. Not exactly a postcard — but the morning devotion was about <strong>“pure heart and clean hands.”</strong> <em>Okay, Tuhan, I hear You.</em></p><p>We visited the local government office to pray for leaders. Ankia decreed that <strong>Hamisi Hospital would be empty</strong> because God would heal many. A bold word. I wrote it down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z9XWOtbzHSOeQBWPI1mdWw.jpeg" /><figcaption>Pray for the authorities</figcaption></figure><p>Then <strong>Fresh Fire Conference</strong> Day 1 kicked off. The church welcomed us like family. The presence of God felt near — not loud, not forced, just present. We closed the night with my favorite rhythm: <strong>“highs &amp; lows.”</strong> Honest sharing. Safe space. Team becoming family.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5q3z7pZpu6YutiPTEuOZ4g.jpeg" /><figcaption>Hamisi Worship Centre, Kenya</figcaption></figure><h3>Day 4 — I Came to Document, God Asked Me to Speak</h3><p>Another morning of worship, Word, and communion. Day 2 of the conference flowed.</p><p>Then came a surprise: they asked me to share. I wasn’t ready. I came to be <strong>the documentarian</strong>, not the speaker. But God had other plans. I shared the testimony of my <strong>healed ear</strong> — in Bahasa Indonesia. Liz translated to English. Someone else translated to Swahili. Three languages, one story, one Spirit. <em>Beautiful.</em> I put the camera down for a moment and let the story do the work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5E6n7w21zAV7RqfWXMnLfg.png" /><figcaption>Another plot twist by God :)</figcaption></figure><p>After my sharing, the meeting continued with a <strong>healing session</strong>. And what I saw was unforgettable: so many people touched by God, so many miracles happening before my eyes. People healed, tears streaming, faith rising. For a moment I forgot I was holding a camera, because I was simply in awe of what God was doing in that room.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oA0PX6zHIa6RXXsI5mxRlA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1KUyEGkbzQjdLEF4Ktnz3w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kxc8WjNfjQUQluOOtNXZHQ.jpeg" /></figure><p>We closed with “highs &amp; lows” again. My low was fear. My high was obedience.</p><h3>Day 5 — “Shem, Not Shame”</h3><p>This day was for <strong>pastors and leaders</strong> from across Hamisi and nearby towns. Ankia spoke about how God doesn’t call us by our <em>title</em> but by our <strong>“shem”</strong> — our name, our character, our integrity. <em>Shem, not shame.</em> (I even have a t-shirt that says that. Irony: I didn’t wear it.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohijhliVVEi6u5Ev6IxBDw.jpeg" /><figcaption>Ankia’s giving bold message</figcaption></figure><p>The afternoon turned playful — <strong>sports</strong> with local youth (some of our team played football), ministry to <strong>widows</strong>, and <strong>bracelet-making</strong> with kids. I stood behind my lens witnessing the real sermon: people loving people. Tamim Ministries showed up with their whole hearts. I pressed record and whispered, <em>Thank You, Jesus.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CsiYGmI45n0Cas-xXbbs8A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8KtxmYY0vtC9cFBG6sjdKg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9jV4_QNB6REM7lDMxhcdFw.jpeg" /></figure><p>By evening, <strong>Fresh Fire</strong> wrapped after three days. Seeds were planted. Some already sprouting.</p><h3>Day 6 — Baptisms, an Empty Hospital, a Small School with a Big Dream</h3><p>We planned to baptize around <strong>15 people</strong> — adults, teens, kids. No instruments. No big production. Just voices, water, and <strong>longing</strong>. That’s the word I felt in the air: <strong>longing</strong>. One boy, <strong>Farouq</strong>, said, “<strong>I don’t want to miss heaven.</strong>” I swallowed tears behind the camera.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xb5OXgfI8F9LCvyt0Oo58Q.jpeg" /><figcaption>“I don’t want to missed heaven”</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4CjunnUk8BvrHn__82iFDA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VA_RBqKRuf-eipYDq-5Zdg.jpeg" /></figure><p>Then we went to <strong>Hamisi Hospital</strong>. And just like that Day 3 decree — <strong>it was empty</strong>. No patients. Staff were smiling. <em>First time ever</em>, they said. I don’t care how you label it — coincidence or miracle — but I know what I witnessed: <strong>answered prayer</strong>.</p><p>We visited <strong>Winners Township Academy</strong>, a simple school run by Hamisi Worship Center. Few facilities, a big mission: educate the next generation. Later, we went to another church packed with children — many seeing Asians for the first time. Curious, fearless, joyful. We ate lunch there. I realized I was starting to get used to the food.</p><p>That night’s “highs &amp; lows”? Honestly — <strong>no lows</strong>. Just highs. I broke down in tears. Gratitude does that.</p><h3>Day 7 — Sent Like the Apostles</h3><p>Sunday. Of our 15 who came to Hamisi, <strong>13 were sent to preach</strong> across multiple churches. Some even did <strong>two services</strong>. Many had never preached before. Didn’t matter — <strong>the Spirit supplied what was lacking</strong>. That’s the thing about obedience; ability follows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j4hM3f7tmjnwJJwqH_DoSQ.jpeg" /><figcaption>With the Apostles</figcaption></figure><p>We closed the day with a farewell dinner at Pastor Zaddock’s home. I met <strong>Tania</strong>, a quiet two-year-old who climbed onto my lap and just sat there. Calm. Safe. We didn’t speak the same language, but compassion did the translation. I’m going to miss her.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KzQLI9jDtNqFvKzqRLSNuA.jpeg" /><figcaption>Tania</figcaption></figure><h3>Day 8 — Kisumu, Nairobi, and Electric Fences</h3><p>We said goodbye to our Hamisi family and flew from <strong>Kisumu</strong> back to <strong>Nairobi</strong> (nobody wanted another 10-hour marathon by road). Nairobi is a modern city — with malls, traffic, and yes, <strong>gates and electric fences</strong> everywhere. We stayed mostly at the hotel, had lunch out, and let our backs and hearts rest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CD44YDSx_VX2KqBA8ae0HQ.jpeg" /><figcaption>Farewell Hamisi</figcaption></figure><h3>Day 9 — Safari, City Skyline, and Family</h3><p>At 6 a.m. we headed to <strong>Nairobi National Park</strong> — wildlife with a city skyline. Lions, elephants, rhinos, ostriches. We saw a lot. Some of the team fed giraffes; I didn’t — <em>FYI</em>. But I soaked in the moment: friendship forged through prayer, sweat, and shared discomfort. Strangers turned <strong>family</strong>. That’s the real miracle.</p><h3>Day 10 — Home</h3><p>Flights home split us: some to Singapore, some to KL, us to Jakarta. This time the journey felt lighter. Maybe the plane was the same, but the heart wasn’t.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f0Hmc0gpx7j5ypgx1NKnaA.jpeg" /><figcaption>Flying back home</figcaption></figure><h3>What Kenya Left in Me</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YC1m4UnfU7xsjb7tSaMz6A.jpeg" /></figure><p>I never planned to set foot in Africa — <strong>God planned it first</strong>. In Hamisi, I witnessed things my camera can’t fully capture: <strong>longing for God</strong> in simple worship, <strong>prophetic words</strong> landing as reality, <strong>children’s laughter</strong> echoing through cracked walls, leaders receiving <strong>fresh revelation</strong>, and a hospital with <strong>no patients</strong>.</p><p>For me, this trip taught three things:</p><ol><li><strong>Obedience over comfort.</strong> You can’t hold both with the same hand.</li><li><strong>Integrity over title.</strong> <em>Shem, not shame.</em> Be who God calls you — consistently.</li><li><strong>Die to self, find real life.</strong> <em>Flesh must die</em> wasn’t a slogan; it was the doorway.</li></ol><p>I went as a <strong>documentarian</strong>. God asked me to be a <strong>witness</strong>. Different job description. Same King.</p><p>I’m back in Jakarta, grateful and smaller in the best way. More ready to serve, to obey, to let go of control. This was a <strong>life-changing</strong> trip for me. I can’t wait to go again — wherever He sends.</p><p><strong>Asante sana, Hamisi. Baraka tele.</strong></p><p>Karibu — You’re welcome in my heart too.</p><p><em>If you read this far — thank you. If you’re considering a mission trip: go. Not because it’s easy, but because you’ll meet God in the places your comfort can’t take you.</em></p><p>This journal rewritten by AI from my daily journal.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=560f36ed9233" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Ode to My Father]]></title>
            <link>https://medium.com/@yopiesuryadi/an-ode-to-my-father-c54e544916e9?source=rss-ce532905a140------2</link>
            <guid isPermaLink="false">https://medium.com/p/c54e544916e9</guid>
            <dc:creator><![CDATA[Yopie Suryadi]]></dc:creator>
            <pubDate>Tue, 03 Jun 2025 03:31:45 GMT</pubDate>
            <atom:updated>2025-06-03T03:33:48.238Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wfIIqYJUA2ZQaSgqLRhaZA.jpeg" /><figcaption>Rest well, Papa</figcaption></figure><p>He was a quiet man. Didn’t say much, but did more than most. He wasn’t made of grand speeches or loud praises, but of consistency, of routines, of being there.</p><p>At thirteen, he left Semarang for Jakarta — alone. By seventeen, he had brought his siblings with him. No complaints. Just duty. Just motion.</p><p>That’s how he lived — not chasing glory, but doing what needed to be done.</p><p>He raised us without drama.</p><p>Worked with his hands, his mind, his stubbornness. He didn’t always get it right. But he never stopped trying.</p><p>It all started after his 72nd birthday.</p><p>His health began to fade — in and out of the hospital, until July brought a name to it:</p><p><strong><em>Colorectal cancer.</em></strong></p><p>Not the kind that spreads fast, but the kind that slowly takes away movement, one function at a time.</p><p>We brought him to Penang. Just getting him on the plane felt like a battle. Radiotherapy followed, and the doctor, calm but certain, told us what no one wants to hear:</p><p><strong><em>Three months.</em></strong></p><p>That’s when the real journey began, and then a brief moment of “okay.” He could walk again. He even smiled again.</p><p><strong><em>But one day, he fell.</em></strong></p><p>March 20.</p><p>The first time I rode an ambulance — not as a bystander, but as a son.</p><p><strong><em>I prayed it would be the last.</em></strong></p><p>He stayed a month in the hospital.</p><p>And then we did everything it took to bring him home.</p><p><strong><em>Exactly one month later, he left us.</em></strong></p><p>Peacefully. Quietly.</p><p>While everyone else was asleep.</p><p>I thought we were ready. We had the timeline. We knew it would happen. But nothing truly prepares you. Grief is not a calendar. It comes in waves. Some days, it drowns you. Other days, it lets you breathe. I’ve learned that time doesn’t heal everything. It just teaches you how to carry it better.</p><p>Our last real conversation stays with me. I told him how much I loved our Sundays — doing crossword puzzles together. How his return from Medan with syrup markisa or the day he brought home a Nintendo was everything to us. That was our last talk.</p><p>He was just a man. He made mistakes. Many. Some we talked about, some we didn’t.But we choose to remember his kindness. His quiet sacrifice. His fierce loyalty. How he stayed soft in a hard world. How he gave, even when it cost him. That’s what we carry now. Not the suffering. Not the fading.</p><p><strong><em>But the love.</em></strong></p><p><strong>I miss him.</strong></p><p>But I’m thankful.</p><p>That I got to walk beside him in his final stretch. That I had the chance to know him not just as a father — but as a man.</p><p>He’s home now.</p><p>No more pain.</p><p>Just rest.</p><p>And here we are — still walking.</p><p>Carrying him with us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c54e544916e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[More Than Email. This Is Why We Build.]]></title>
            <link>https://medium.com/@yopiesuryadi/more-than-email-this-is-why-we-build-55eff17e2ee2?source=rss-ce532905a140------2</link>
            <guid isPermaLink="false">https://medium.com/p/55eff17e2ee2</guid>
            <dc:creator><![CDATA[Yopie Suryadi]]></dc:creator>
            <pubDate>Wed, 14 May 2025 04:32:42 GMT</pubDate>
            <atom:updated>2025-05-14T04:33:27.068Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Mailtarget isn’t just an email company — it’s a belief system. We believe in building meaningful communication tools grounded in purpose, integrity, and excellence. Our manifesto lays out why we exist, how we work, and what we value. We’re here to create impact, not just deliver email. No shortcuts, no noise — just real solutions that move businesses forward.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oVPAyCG2FBcf9xgjMwzyjQ.png" /><figcaption>Made by AI</figcaption></figure><p><strong><em>The Mailtarget Manifesto</em></strong></p><p>At <a href="http://mtarget.co/">Mailtarget</a>, we don’t just build email infrastructure, or the best SMTP Relay email</p><p>We build with conviction.</p><p>We believe the way businesses communicate matters — not just for conversions, but for connection.</p><p>Not just for delivery, but for impact.</p><p>This isn’t just about email.</p><p>It’s about <strong>how</strong> we show up in the world.</p><p>So we put our beliefs into words.</p><p>Here’s the manifesto that guides everything we do.</p><h3>Our Vision</h3><p><strong>To become a world-class email company that empowers businesses.</strong></p><p>It’s not just a line.</p><p>It’s a daily decision to build with global standards, and local understanding.</p><p>To be trusted by the biggest names, while still caring like a small team next door.</p><h3>Our Purpose (Why)</h3><p>We believe meaningful communication fuels business growth.</p><p>We exist to <strong>empower</strong>, to <strong>connect</strong>, and to turn every email into an opportunity — not just a notification.</p><p>Business communication should never be boring.</p><p>It should move people.</p><p>And we’re here to make that happen.</p><h3>Our Approach (How)</h3><p>Innovation. Integrity. Excellence.</p><p>We don’t just throw tools at our clients.</p><p>We listen. We learn.</p><p>We design with precision — especially for industries like finance and retail where trust is everything.</p><p>And most of all, we remember there’s always a human on the other side of every send.</p><h3>Our Actions (What)</h3><p>We build tools that aren’t just functional.</p><p>They’re <strong>transformative</strong>.</p><p>We stick to our principles — even when it’s harder.</p><p>That means no shortcuts. No gray areas.</p><p>And we measure success by impact:</p><p>What did we help our clients unlock?</p><p>How did their customers feel?</p><p>What legacy did we leave behind?</p><h3>Our Core Values</h3><h3>Excellence</h3><p>We don’t settle.</p><p>We refine. We question. We evolve.</p><p>Every detail matters.</p><h3>Integrity</h3><p>We walk our talk.</p><p>We honor our word.</p><p>We earn trust — and we keep it.</p><h3>Impact</h3><p>We want to be known for more than uptime and delivery rate.</p><p>We want to be known for moving the industry forward — and bringing others with us.</p><h3>In the End…</h3><p><a href="http://mailtarget.co/">Mailtarget</a> isn’t just a product.</p><p>It’s a belief system.</p><p>A belief that business should be human.</p><p>That communication should mean something.</p><p>And that purpose and product can coexist without compromise.</p><p>We’re not here to be loud.</p><p>We’re here to be <strong>useful</strong>, <strong>honest</strong>, and <strong>world-class</strong>.</p><p>And if you believe in those things too — welcome.</p><p>Let’s build something that lasts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55eff17e2ee2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Sky Doesn’t Brag, and Neither Should You]]></title>
            <link>https://medium.com/@yopiesuryadi/the-sky-doesnt-brag-and-neither-should-you-9bc4f4824984?source=rss-ce532905a140------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bc4f4824984</guid>
            <dc:creator><![CDATA[Yopie Suryadi]]></dc:creator>
            <pubDate>Thu, 08 May 2025 05:24:07 GMT</pubDate>
            <atom:updated>2025-05-08T05:27:26.279Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f9L23EnwwznmTCPKRoSlyg.jpeg" /></figure><p>In my office, there’s a poster that quietly reminds me what kind of founder I want to be.</p><p>It says:</p><p><strong>“Langit tak perlu menjelaskan bahwa dirinya tinggi.”</strong></p><p><em>“The sky doesn’t need to explain that it is high.”</em></p><p>That line hit me hard the first time I read it.</p><p>Because in a world obsessed with loud wins, personal branding, and shouting for attention,</p><p>I’ve always believed in the quiet kind of strength.</p><p>The kind that doesn’t brag.</p><p>The kind that doesn’t chase claps.</p><p>The kind that just… delivers.</p><h3>Build with Integrity. Let It Speak.</h3><p>At <a href="http://mtarget.co/">Mailtarget</a>, we’ve chosen to take the long way.</p><p>Not the loud way.</p><p>We focus on product. On reliability. On listening more than talking.</p><p>We don’t spend time writing threads about how good we are.</p><p>We spend time making sure our infrastructure <em>actually is</em>.</p><p>Excellence. Integrity. Impact.</p><p>That’s our compass — not virality.</p><p>And sometimes, when you do the right thing long enough,</p><p><strong>someone notices.</strong></p><h3>One Day, ChatGPT Said Our Name</h3><p>A few weeks ago, one of our customers shared something with us.</p><p>They were testing ChatGPT, asking it for the best SMTP relay email provider.</p><p><a href="http://mailtarget.co/">Mailtarget</a> came up as the <strong>top recommendation</strong>.</p><p>Not because we paid for it.</p><p>Not because we hacked the algorithm.</p><p>But because we’ve been doing the work — consistently, quietly, and well.</p><p>That moment didn’t need to be shouted.</p><p>It didn’t need a press release.</p><p>But to me, it meant everything.</p><h3>Believe in What You Build</h3><p>If you don’t believe in your product, why should anyone else?</p><p>You don’t need to fake it.</p><p>You don’t need to flex.</p><p>You just need to build something useful, honest, and strong enough that when people need it — it’s already there.</p><p>Because the sky doesn’t shout to prove it’s high.</p><p>It just is.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bc4f4824984" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Spare Parts to Startups: How I Found My Way into Tech]]></title>
            <link>https://medium.com/@yopiesuryadi/from-spare-parts-to-startups-how-i-found-my-way-into-tech-cade7a6fefe3?source=rss-ce532905a140------2</link>
            <guid isPermaLink="false">https://medium.com/p/cade7a6fefe3</guid>
            <dc:creator><![CDATA[Yopie Suryadi]]></dc:creator>
            <pubDate>Fri, 02 May 2025 18:10:59 GMT</pubDate>
            <atom:updated>2025-05-02T18:11:27.541Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>I started my career selling automotive spare parts across Indonesia — no passion, just transactions. But when BlackBerry entered the scene, I fell in love with tech and never looked back. I helped build a gadget portal, a social media analytics startup, and eventually co-founded Mailtarget. Along the way, I made every mistake you can imagine — chased vanity, burned through funding, treated side projects like real companies. I’ve failed, exited, rebuilt, and now lead a growing email infrastructure company. This is my journey: messy, redemptive, and held together by grace. God is good.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xNAtibG57h-wEUqipqhITA.png" /><figcaption>Made by AI</figcaption></figure><p>Before we started a company called <a href="http://mailtarget.co/">Mailtarget</a>,</p><p>Before I understood infrastructure, APIs, or SaaS…</p><p>I was selling <strong>automotive spare parts</strong>.</p><p>I traveled from city to city, crossing islands in Indonesia just to close a deal.</p><p>I knew how to sell.</p><p>I knew how to profit.</p><p>But I didn’t care about the product.</p><p>There was <strong>no connection</strong> — just transactions.</p><h3>Then Came BlackBerry.</h3><p>When BlackBerry started booming in Indonesia, I joined a mailing list.</p><p>That was my first real dive into <strong>digital life</strong> — and I fell in love instantly.</p><p>I didn’t come from tech.</p><p>I studied <strong>journalism</strong>, not engineering.</p><p>But something in this world clicked with me.</p><p>Some friends invited me to build a gadget news portal.</p><p>Just five of us.</p><p>Traffic started growing. Ad revenue came in easily.</p><p>It felt fun. Fast. Full of potential.</p><p>And then it died.</p><p>We treated it like a side project.</p><p>We gave it side-project energy.</p><p><strong>And that’s what it stayed.</strong></p><p>That was my first real lesson:</p><blockquote>If you build something on the side, don’t expect it to stand in the center.</blockquote><h3>The Second Try: Big Vision, Big Exit</h3><p>Later, I met <strong>Masas</strong> and some great people.</p><p>We started a <strong>social media analytics startup</strong>.</p><p>This time I was all in.</p><p>I felt like Steve Jobs.</p><p>I wanted to change the world.</p><p>I was chasing <strong>valuation</strong> instead of value.</p><p>Eventually, our shares were bought out.</p><p>You could call it an <em>exit</em>.</p><p>But in truth, it was also an <em>exit from who I was trying to become.</em></p><p>And I learned:</p><blockquote>Don’t build what’s “nice to have.” Build what people <strong>need</strong>.</blockquote><h3>The Third Startup: Lessons in Humility</h3><p>Me, Masas, and a few passive shareholders started again.</p><p>This time we got investment.</p><p>We met <strong>Johan and Astrid</strong> — people I’ll never forget.</p><p>At the time, they felt like lifesavers.</p><p>But I made a mistake:</p><p>Instead of chasing revenue, I chased <em>the feeling</em> of being a Silicon Valley startup.</p><p>We renovated our office.</p><p>Tried to look “cool.”</p><p>Bought into the image instead of the mission.</p><p>The money dried up.</p><p>Disputes followed.</p><p>The company shut down.</p><p>And it all collapsed again.</p><h3>Then Came the Night MailTarget Was Born</h3><p>Just three of us left:</p><p>Me, Masas, and Johan/Astrid.</p><p>In the middle of the night, we agreed to start fresh.</p><p>We registered a new company:</p><p><strong>PT Target Sukses Sinergi.</strong></p><p>And in October 2016, <a href="http://mailtarget/"><strong>MailTarget</strong></a> was born.</p><p>This time, I wasn’t trying to look successful.</p><p>I was just trying to <strong>build something real</strong>.</p><p>We still make mistakes.</p><p>But now we treat them as <strong>learning</strong>, not <strong>losing</strong>.</p><p>We don’t have fancy offices.</p><p>No free lunches.</p><p>No ping-pong tables.</p><p>Just good internet, a focused team, and one shared belief:</p><blockquote>We’re building something that’s not “nice to have.” We’re building something that’s needed.</blockquote><h3>What I Know Now</h3><p>I’ve failed more than I’ve succeeded.</p><p>I’ve made bad calls.</p><p>I’ve been humbled.</p><p>But I’ve also been <strong>saved</strong>.</p><p>I believe it was <strong>Jesus</strong> who pulled me back when everything fell apart.</p><p>When I was running out of hope,</p><p>He gave me one more chance.</p><p>I took it.</p><p>And I’m still walking.</p><p>Mailtarget is growing now.</p><p>Not because we’re lucky —</p><p>But because we’ve learned.</p><p>Because we’ve fallen and chosen to rise again.</p><p>And because <strong>God is good</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cade7a6fefe3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>