Who this is for
Businesses with a list, or a way to build one, and no sequences running on it: a store with customers who bought once, a consultancy with leads that went quiet, a course provider with sign-ups who never started, a B2B company that sends a newsletter and nothing else. Campaign planning and the newsletter itself are a different service, email marketing; this page is the automated flows underneath it.
Flows I build
| Flow | Trigger | Typical shape | Best for |
|---|---|---|---|
| Welcome | New subscriber or lead | 3 to 5 emails over 10 days: what you do, proof, the one thing to do next | Everyone |
| Lead nurture | Lead created, no reply in X days | Answers to the objections sales hears most, one per email, ending in a booking link | Services, B2B, education |
| Abandoned cart and browse | Cart or product view without purchase | Reminder at 1 hour, help at 24 hours, incentive (if any) at 72 hours | eCommerce |
| Post-purchase | Order placed or delivered | Confirmation, how to use, review request, cross-sell after the right interval | eCommerce, courses |
| Onboarding | Sign-up or first login | Step-by-step activation with branching on what the user has and has not done | SaaS, memberships |
| Win-back | No purchase or login in N days | Two or three emails, then removal from marketing to protect deliverability | Repeat-purchase businesses |
| Review and referral | Delivery plus interval | One ask, one reminder, routed by rating | Local services, clinics, stores |
What the service includes
- Deliverability setup: SPF, DKIM and DMARC on your domain, a sending subdomain where appropriate, list hygiene and warm-up for new senders.
- Platform setup or migration in ActiveCampaign, Mailchimp, Klaviyo or HubSpot, chosen by your stack; Klaviyo has its own platform page.
- Data model: tags, lists, custom fields and events the flows will branch on, fed from the website, store or CRM; the CRM side is CRM setup and integration.
- Flow logic with entry and exit rules, so a lead who books stops receiving “book a call” emails.
- Copy for every email, in the plain, specific voice that gets replies, in English or Nepali.
- Templates that render on Gmail mobile, which is where most Nepal readers open them.
- Testing of every branch with real test contacts.
- Reporting on the numbers that matter per flow: replies, bookings, revenue, unsubscribes, not just opens.
- Documentation and a monthly review of what to add or cut.
How an email automation project runs
- Audit (week one): list source and consent, current sends, domain authentication, platform fit.
- Flow map (week one): the two or three flows that matter first, with triggers, timing and exits on one page.
- Setup and copy (weeks two to three): platform, data connections, authentication, emails written and approved.
- Test and launch (week four): every branch tested; flows switched on for new entrants first.
- Review (monthly): results by flow; one improvement a month.
What to decide before automating email
- Consent. Only people who opted in receive marketing flows. Transactional messages (order updates) are separate and do not need marketing consent. A bought or scraped list is not something I will send to.
- The one action each flow exists to cause: reply, book, buy, activate. Emails without a single next step get deleted.
- Frequency ceiling across flows, so a contact in three flows does not get three emails a day.
- Who replies when someone answers an automated email, and how fast.
- Which system owns the contact: the email tool or the CRM. One of them, not both.
What breaks, and how I prevent it
- Emails landing in spam because the domain was never authenticated; SPF, DKIM and DMARC are done before any flow is switched on.
- A lead who has already booked still getting “book now” emails; exit conditions on every flow.
- Cart emails firing for completed orders; the purchase event is the exit trigger and is tested.
- Flows sending to bounced or unsubscribed addresses after a list import; suppression lists carried over on migration.
- Open rates that mean nothing since mail privacy features; reporting is on clicks, replies and revenue.
Pricing pointer
Setup is quoted on request: two or three core flows with deliverability setup sit at the low to middle of the range; a full eCommerce flow set with Klaviyo, WooCommerce events and CRM sync sits higher. Maintenance and a monthly improvement cycle are quoted on request; the email platform subscription is paid by you. For stores, the order-side events are built under WooCommerce and eCommerce automation; for leads, the intake is lead generation automation.
Next step
Tell me the size of your list, where it came from and what you sell, and I will reply with the two flows to build first and a fixed price. The rest of the automation services are on the automation hub.
