<?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 Mihai Jiplea on Medium]]></title>
        <description><![CDATA[Stories by Mihai Jiplea on Medium]]></description>
        <link>https://medium.com/@mihaijiplea?source=rss-9b683cf8ceed------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YryMMNpZ_raLCbhxP5Juvw.jpeg</url>
            <title>Stories by Mihai Jiplea on Medium</title>
            <link>https://medium.com/@mihaijiplea?source=rss-9b683cf8ceed------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:52:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mihaijiplea/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[Why I built AguMail after my own store’s email marketing failed]]></title>
            <link>https://medium.com/@mihaijiplea/why-i-built-agumail-after-my-own-stores-email-marketing-failed-490c851a97eb?source=rss-9b683cf8ceed------2</link>
            <guid isPermaLink="false">https://medium.com/p/490c851a97eb</guid>
            <category><![CDATA[wasp]]></category>
            <category><![CDATA[email-marketing]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Mihai Jiplea]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 00:40:01 GMT</pubDate>
            <atom:updated>2026-11-03T00:40:01.997Z</atom:updated>
            <content:encoded><![CDATA[<p><em>My WooCommerce store needed email that just worked. When nothing on the market fit, I started building my own tool.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wa5tmfP3q4fN4U0wBO5mhw.png" /></figure><h3>The store that taught me email matters</h3><p>I’ve been a software engineer for over ten years, with time at Google, Amazon, and Splunk. For some time, I’ve owned an online store called <a href="https://pixelandcanvas.net/">Pixel &amp; Canvas</a> that sells personalized portraits and gifts (well, co-owned since my wife ran it, I just built it on the weekends). It runs on WooCommerce, and like most store owners, I knew email marketing mattered. If you’re not in someone’s inbox, they forget you exist, and repeat purchases dry up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fd8AMy4qWkB6R3gfKIQPCg.png" /></figure><p>So I set up Mailchimp. The abandoned-cart flow underperformed and threw errors I couldn’t fix. My own template looked ugly. Agencies were too expensive. I looked at Klaviyo, Mailchimp, Omnisend. They’re mature and powerful, but ease of use gets lost. Onboarding is hard, and you often need extra integrations. The budget options like EmailOctopus or MailerLite are cheap, but I still had to figure out what to send. Every tool left me doing the work. I left my job in 2026 and decided to build a tool that does the work for me, full time.</p><h3>What AguMail is</h3><p><a href="https://agumail.com/">AguMail</a> is email marketing for small and medium businesses that runs by itself after setup. It’s for independent online stores, SaaS and list-based businesses like studios, cafés, service firms, and creators. Setup is designed to take under an hour. AguMail reads your site to pull your logo, colors, and fonts, then builds on-brand templates. Flows are pre-built per business type: a store gets a welcome series, abandoned cart, and post-purchase emails. You approve each email, then switch it on. Pricing starts free up to 2,500 contacts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CbzFvbsaBuCeqJGs1Y6rtg.png" /><figcaption>Paste a website, get templates in its logo, colors and fonts</figcaption></figure><h3>Starting from OpenSaaS</h3><p>I first started blank, but soon enough I switched the codebase to <a href="https://opensaas.sh/">OpenSaaS</a>, the free open-source SaaS starter built on <a href="https://wasp.sh/">Wasp</a>. That move gave me signup and login with email verification, Stripe subscriptions for AguMail’s own billing, an admin dashboard, a blog, and an end-to-end test setup, all from day one. I extended the admin dashboard, added Google sign-in, and redesigned the landing pages. Starting from a working foundation meant I could focus on the email product itself.</p><h3>Wasp: one config, full stack</h3><p>Wasp is a full-stack framework for React, Node.js, and Prisma. You declare your app in one config file: pages, auth, server functions, background jobs. Wasp wires the client and server together. Signup, login, email verification, and Google sign-in all come from Wasp. Background jobs are scheduled and backed by the app’s Postgres database, no extra queue service needed. For example, abandoned-cart detection runs frequently, and a weekly summary email goes to the owner. I’ve followed Wasp’s release cadence closely and adopted version 0.26 the day it was published.</p><h3>Temporal: surviving the waiting</h3><p>Email marketing involves a lot of waiting. There are days between emails in a flow, campaigns planned for later, A/B tests where the winner is chosen hours after sending. It also means interacting with external services that can be slow or fail: Amazon SES, AI providers, Stripe. A deploy must never drop a contact halfway through a flow. <a href="https://temporal.io/">Temporal</a> is open-source durable execution. Workflows are plain TypeScript, and progress is persisted, so multi-day waits and retries survive restarts and deploys. In AguMail, the Wasp app is the sole database writer and holds the business rules. A separate Temporal worker handles all the waiting and all outside calls, then reports results back to the Wasp app. Campaign sends, per-contact flow runs, contact imports, and sending-domain checks all run on Temporal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_MNNuuZnn4JKZAen2eWxow.png" /></figure><h3>Where AguMail runs</h3><p>AguMail runs on AWS, with the whole stack defined in the AWS CDK. EC2 instances run the Wasp app and the Temporal workers, both as Docker images. A single RDS Postgres database serves both the app and Temporal. Amazon SES handles sending, and bounces or complaints flow back into the app automatically. Images and templates sit in S3 behind CloudFront. Deploys come from GitHub, and new servers have to pass health checks before old ones are retired. The React frontend and blog run on Cloudflare Workers, not AWS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xTXtLT1VM0KjxruFj3gPZA.png" /></figure><h3>Back to the store</h3><p>Pixel &amp; Canvas is now running on AguMail. So far the results are good and encouraging. A Seattle photographer is also piloting AguMail, another local business that moved off Mailchimp. The store that taught me email matters now runs on the tool I built because of it. You can find it at <a href="https://agumail.com/">agumail.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=490c851a97eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>