I knew Built on Zero needed email before I knew exactly what I wanted to email people about. That sounds backwards, but the logic was simple. Social media gives me access to an audience on somebody else’s terms. Search can bring a visitor once and never again. If somebody finds my work useful enough to give me an email address, I have a chance to build a relationship that is not completely dependent on an algorithm deciding whether to show my next post.
The mistake would have been collecting email addresses before creating any plan for what happens next. A list is not valuable because a dashboard says 437. It is valuable when the people behind those addresses remember who you are, open because they expect something worthwhile and eventually trust your recommendations enough to act. That means the email setup is partly technical and partly a promise about how I intend to use their attention.
Systeme.io is handling the technical side for Built on Zero. Its current free plan supports up to 2,000 contacts with unlimited email sends, which is a surprisingly generous starting point compared with many dedicated email tools. More importantly, the email functionality sits beside the funnels and pages I am already building, so the subscriber does not need to be pushed through several disconnected systems.
The first setup job is the sender. If you have your own domain, authenticate it properly rather than treating this as optional technical housekeeping. Systeme.io’s current documentation explains the domain-authentication process and generates the DNS records required for your account. I asked Afrihost for help with mine because I did not want to guess inside the DNS zone. Once authentication is complete, the sending identity and the brand make much more sense together.
Then I think about the subscriber journey. Someone who downloads the $0 Business Stack should not receive a random newsletter three weeks later and wonder who I am. The first email needs to arrive when the context is still fresh. It should deliver what was promised, remind the person why they requested it and set a reasonable expectation about what they will hear from me next.
I do not want the welcome email to become a sales ambush. If the reader asked for a free resource, the first job is to deliver the free resource. There can be a relevant link or recommendation, but I want the email to earn trust before it tries to extract value. This is particularly important for affiliate businesses because readers already know links can make the publisher money. Transparency and usefulness are the only long-term defence against becoming another inbox full of “quick question” subject lines leading to a sales pitch.
After delivery, I want a short orientation sequence. One email can explain the Built on Zero experiment and why I started it. Another can address the first practical obstacle most beginners hit. Another can show a tool I am actually using, with the affiliate relationship disclosed. The purpose is not to automate friendship. It is to make sure every new subscriber receives the best starting material even if they join three months after I wrote it.
Systeme.io lets you organise contacts with tags and automation rules, which becomes useful as the list grows. I do not need a complicated segmentation architecture on day one. I need enough organisation to know how someone entered the list and, later, what they appear interested in. A person who joined through a Systeme.io comparison may have different intent from someone who downloaded a general $0 tools guide. Eventually those differences can shape what I send.
START YOUR EMAIL LIST FREE IN SYSTEME.IO — CLICK HERE
That is my affiliate link. If you later upgrade to an eligible paid Systeme.io plan, I may earn a commission. You can begin with the free plan and, in my view, should do exactly that until your list or needs genuinely exceed it.
The writing itself is where I want Built on Zero to feel different. I am not interested in emails that sound like they were assembled from an internet-marketing swipe file. I want normal paragraphs, useful detail and an actual reason for the message to exist. Some emails will be shorter than blog posts, obviously, but I do not want every sentence isolated on its own line because somebody decided that is how “high-converting copy” must look.
Subject lines deserve the same treatment. I would rather be specific than mysterious. “What happened when I connected my first funnel” tells the reader what the email is about. “You won’t believe this…” asks for attention without earning it. Curiosity can be useful, but manufactured curiosity becomes exhausting when every message treats an ordinary tutorial like a season finale.
Frequency is another decision I am not going to pretend has one universal answer. I want to send often enough that people remember Built on Zero but not so often that the list becomes a dumping ground for content created only because the schedule says Tuesday. At the beginning, one useful regular email plus the onboarding sequence may be enough. As I learn what subscribers respond to, I can adjust.
I will also watch the right metrics without worshipping them. Opens are useful but imperfect because privacy features can distort them. Clicks show stronger intent. Replies are particularly valuable for a young brand because they tell me what real people are thinking. Affiliate clicks and eventual conversions matter commercially. Unsubscribes are information too. I would rather someone leave than remain trapped on a list they no longer want.
Deliverability starts with technical authentication but continues with behaviour. Buying lists is out. Adding people who did not ask to hear from me is out. Sending irrelevant promotions because a commission is attractive is out. A smaller engaged list is more useful than a large list trained to ignore the sender. That is not moral decoration; it is practical email strategy.
The email list also gives the blog a longer life. A new article does not have to wait for Google or Pinterest to discover it. I can send it to people who have already said they want this subject. In turn, their clicks tell me which topics have energy. That can influence future articles, lead magnets and products. The list becomes a feedback system as much as a marketing channel.
If you are setting up email today, do not begin by writing thirty automated messages. Authenticate the domain. Create the first opt-in. Make sure the promised resource arrives. Write a good welcome email. Add two or three follow-ups that genuinely help. Test the sequence yourself. Then get subscribers and listen to what happens.
There is a strange tendency in online business to automate before we have learned what deserves automation. I want to do the opposite. I will write the first messages carefully, see what people respond to and automate the parts that prove useful. Systeme.io gives me the machinery, but the machinery should follow the relationship rather than define it.
My goal is not to “have an email list” by the end of this experiment. It is to have a group of people who understand what Built on Zero does and have enough reason to come back. If that eventually produces affiliate commissions or sales, good. But the commission should be the consequence of being useful repeatedly, not the reason every email exists.
There is one email I think every new list should have that is often forgotten: an invitation to reply. A simple question can turn a broadcast channel into research. What are you trying to build? What is stopping you? Which part of starting from $0 feels most confusing? Even a handful of replies can give me language for future articles that no keyword tool would have phrased quite the same way.
I also want to make unsubscribing easy. That sounds counterproductive when you are desperate to grow a new list, but keeping people who no longer want the emails helps nobody. A clean list protects engagement and trust. I am building Built on Zero for the people who find the experiment useful, not trying to hold every address hostage because the subscriber counter looks better.
I also want a simple preference centre eventually, because not every subscriber will care about every part of Built on Zero. Someone may want the practical tool tutorials and have no interest in weekly challenge updates. Giving people some control over what they receive can preserve a relationship that would otherwise end in an unsubscribe. I do not need sophisticated preference architecture at ten subscribers, but I want to remember that the list contains people, not one homogeneous audience.
Another basic habit is sending test emails before a broadcast. Check the subject line, sender name, links, mobile layout and the actual destination behind every button. Affiliate links deserve particular attention because a broken tracking link can cost money silently. A two-minute test is cheaper than emailing the whole list with a typo in the most important URL.
A quick note before you go: Software pricing, features, free-plan limits and terms can change, sometimes without much notice. Everything in this article was accurate to the best of my knowledge when it was written or last updated, but please check the provider’s official website for the latest pricing, features and terms before making a decision or signing up. Built on Zero does its best to keep our guides current, but we can’t guarantee that every price or feature will remain unchanged after publication.
