Loopmail Template: Email Automation Landing and Console

Loopmail Template: Email Automation Landing and Console

Loopmail is one of the five landing templates in Zugo: a finished marketing page for an email automation product, with a sign in screen and a campaign console behind it. Cloning it into a project of your own is free and runs no model, so credits only start when you edit something.

Here is what the template really contains, which parts are working interface and which are staged data, and how far a few sentences of chat can move it.

What does the Loopmail template include?

The public page is a complete SaaS landing. It opens with a hero built around an automation flow rather than a screenshot, then runs through features, an email template gallery, a three step explanation of how the product works, pricing with a monthly and annual toggle, a customer story, an FAQ, and a closing call to action.

Behind the header sit two more screens. A sign in page with a Google option and an email form, and a campaign console with a sidebar for campaigns, automations, audiences, templates and reports, plus stat cards for open rate, click rate and revenue, and a filterable campaign table.

The email template gallery deserves a note. It is a horizontally scrolling row of cards named for the moment each one serves: a welcome message, a newsletter, a product launch, a promotion, a win back. That naming pattern is doing real persuasive work, because it shows a buyer their own calendar rather than a set of design options.

The FAQ answers the four questions a small brand actually asks about email tooling: importing an existing list, whether technical setup is required, what counts toward a contact limit, and whether a running flow can be paused safely. Those four categories transfer to nearly any subscription product, so keep the shape even after you replace every word.

Why is the flow canvas the center of the page?

Because the hardest thing to explain about automation software is what automation looks like. The hero shows a small vertical flow: a signup trigger, a two day wait, a welcome send, then a branch that goes one way if the message was opened and another way if it was not.

That single element replaces a paragraph of explanation. A visitor understands the product model in about two seconds, and more importantly understands that they could build one themselves. Feature lists never achieve that, because a list describes capabilities while a diagram demonstrates a workflow.

The lesson generalizes past email. If your product has a process at its heart, whether that is approvals, onboarding, routing or scheduling, put a diagram of the process in the hero and let the copy support it. When you edit this template for a different product, this is the block to preserve and adapt rather than replace.

What is working interface and what is staged data?

Being clear about this saves an awkward discovery later.

The open rates, revenue shares and customer counts printed on the page are placeholder content for a fictional company. Replace them before you publish anything. Numbers you did not measure are the fastest way to lose a reader who checks, and they are the first thing a careful buyer checks.

How do you rebrand it in a few edits?

You describe the change in chat and the page rebuilds. Five edits carry most of the distance from Loopmail to your product:

1. Name and promise: "rename the product to Cadence, change the promise to onboarding flows for SaaS teams, rewrite the hero copy".
2. The flow itself: "change the hero flow to trial signup, activation check, nudge, then a branch on whether the user invited a teammate".
3. Features: "replace the four feature blocks with in app messages, segments, scheduling and reporting".
4. The gallery: "rename the template cards to trial start, feature announcement, renewal reminder and reactivation".
5. Proof and pricing: "swap the customer quote for a metric block and cut the pricing to two tiers".

Change one thing at a time and look between each. Every rebuild is opened in a sandbox before you receive it, so a build that does not render is never delivered, which makes trying an idea cheap rather than risky.

What does reshaping Loopmail cost?

Cloning calls no model at all, so the copy into your own project costs nothing.

The Free plan gives 5 credits, which covers the clone plus one edit: enough to see your own product name in the hero. Pro is $25 a month for 200 credits, Business is $99 a month for 800. On Pro that is roughly 66 edits or 33 rebuilds in a month.

A believable rebrand usually takes between four and eight edits, and the last two are always tightening rather than adding. Budget for them. The version you publish is never the first pass, and pretending otherwise just means publishing something you will quietly rewrite next week.

Who should start from Loopmail rather than a blank prompt?

Anyone selling a self serve tool to small teams. The structure fits email, scheduling, CRM, analytics, support inboxes, anything where the buyer signs up without talking to a salesperson and wants to see the workflow before they trust it.

It also fits an agency or a freelancer productizing a service. If you run email programs for clients, this page sells a retainer just as well as it sells software, once the pricing block becomes packages instead of plans.

It fits badly where the buying process is a conversation. Enterprise pages are built around a demo request, a security page and a case study library, and Loopmail is built around a signup button. Reshaping it that far means working against the layout rather than with it. If the console is the part you actually want, how to build a SaaS dashboard with AI approaches it from the app side.

What are the honest limits here?

Three, and they are worth knowing before you start rather than after.

The console is a picture of a product. Making it real means a database, authentication and the logic behind segments and scheduling. Zugo can build a lot of that through Supabase, but it is many edits of work, not one prompt, and on a genuinely complex product it does not replace a development team.

Sending email is a service, not a page. Zugo connects to Resend for transactional mail, and that covers the messages your own product needs to send. Running marketing campaigns at volume, with warm up, authentication and deliverability monitoring, is what dedicated email platforms exist for, and building one is a different project entirely.

And specific business logic gets built by iteration. Branching rules, contact scoring, quiet hours per timezone: each is a conversation of edits rather than a sentence. That is normal, and it is still faster than the alternative, but it is not the one prompt story.

Which integrations matter for this page?

Supabase gives you accounts, a database and file storage, which is what turns the sign in screen into a real door. Stripe handles subscription billing, which any pricing table with a monthly and annual toggle eventually implies. Resend sends the transactional email your product owes its users, from confirmations to password resets.

Google Analytics answers the question the pricing block raises: which tier do people actually click. GitHub export hands you the source as a real repository, and Vercel deploys to your own account, so the project is portable rather than trapped. A custom domain connects on paid plans.

If email capture is the only piece you need right now, rather than a whole product page, how to build a newsletter signup with AI covers the small version of this properly.

How do you publish and test it?

Publishing puts the project on an address like your-project.zugo.run in one action, and the build is verified in a sandbox first, so a page that fails to render is not published silently. A simple build takes about a minute; a multi page platform takes a few minutes.

Publish before the copy feels finished, then watch behavior instead of asking for opinions. Send it to twenty people who match your buyer and look at which section they reach before leaving. The sentence that stops people is rarely the one you spent longest writing.

Where should you start?

Open the template gallery, filter to landing pages, and compare Loopmail against Ledgerly, QuoteKit, Pulseboard and Frame. They differ in structure rather than color, and choosing the closest structure saves more edits than any styling pass will. The full map of what each one covers is in the Zugo templates guide.

Make your first edit the product name and the hero flow, in that order. Once the diagram describes your process correctly, the rest of the page has something true to support, and the copy edits become obvious instead of speculative.

You can clone Loopmail and start reshaping it at zugo.dev. The starting credits are enough to see your own product in the hero and decide whether this shape fits, with no card required.