The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Every Automation Is Working — and the Customer Journey Is Still Broken
A welcome flow is converting. Abandoned cart emails are generating revenue. Post-purchase messages are delivered on time, and reactivation campaigns continue to bring customers back.
The dashboard suggests that the system is working.
The customer may experience something very different.
They might receive a welcome email after already placing an order, a cart reminder for a product they no longer need, and a promotional campaign that ignores their recent purchase.
Each message is technically correct according to the automation that sent it. Together, they create a disconnected customer journey.
This is one of the most common problems I find in established lifecycle programs: individual flows have been optimized, but the relationships between them have not.
A collection of flows is not a lifecycle system
Automation programs usually grow incrementally. A brand adds welcome, abandoned cart, browse abandonment, post-purchase, cross-sell, review request, and win-back flows as new needs appear.
Each flow may have a valid trigger and produce measurable results. But customers do not experience these automations separately. They experience every email, promotion, and reminder as communication from one brand.
The platform sees a subscriber entering several eligible flows.
The subscriber sees a brand sending several messages that appear unaware of one another.
The missing layer is coordination
A coordinated lifecycle system needs rules that determine which customer state takes priority and how communication should change when that state changes.
For example:
What happens to the welcome journey after a purchase?
Should a recent customer receive the standard promotional cadence?
Can someone enter browse abandonment while already in abandoned checkout?
Which messages should be suppressed when several automations become eligible?
These decisions do not belong to one flow. They belong to the architecture connecting all flows.
When performance slows, adding another automation is not always the answer. Sometimes the system needs clearer entry and exit conditions, better suppression rules, and a shared understanding of the customer’s current state.
A healthy lifecycle program should not feel like independent campaigns triggered by database events. It should feel like one brand responding coherently as the customer relationship changes.
This is the perspective I bring to lifecycle marketing audits: identifying the gaps between otherwise functional automations and turning them into a coordinated customer journey.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
My recent client is an Australian printing firm.
They already had clients coming in.
The problem was what happened after the agreement.
When a client agrees to payment terms, every delay matters.
A payment process that sits waiting for someone to follow up can slow down the entire client journey. And when clients experience unnecessary delays, it can affect more than cash flow. It can affect their confidence in the business.
So I built an Agreed Payment System in Make.com designed around the client journey.
The goal wasn’t simply to automate emails.
It was to create a process that keeps agreed payments moving, keeps communication consistent, and reduces the amount of manual follow-up required from the team.
The workflow takes the agreed payment process and routes it through the appropriate steps, conditions, and Gmail communications.
The system helps keep the process moving.
And this is where my background in sales development and client retention comes into the automation work.
I don’t look at automation as:
Trigger → Action → Done.
I look at it as:
Lead → Sale → Client → Experience → Retention → Repeat business.
Because getting a client is only part of the job.
You also need systems that make it easy for that client to keep doing business with you.
Sales development + client retention + workflow automation.
That’s the intersection I build around.
The handoff after a client agrees to terms is where many service businesses leak cash flow. Automating follow-up there is a practical B2B wedge because it ties the workflow directly to revenue.
How do you keep a brand's promise of calm intact once real users start clicking through checkout?
Mudita builds minimalist devices around one idea: technology that harmonizes with your life instead of competing for your attention. The brandbook lays that promise out in detail - tone, restraint, what the brand should never feel like. My job was carrying that same discipline into the product itself.
I worked across the checkout flow, the storefront and category browsing, and the product page above the fold - three surfaces where small frictions had quietly built up against the brand's own case for calm. The brandbook gave the rules. The UI work was making sure those rules survived contact with a real cart and a real user.
For the case study visuals, I used AI for the first time to produce product footage 🤖 - wind moving through a scene, an object drifting in place. Higgsfield was genuinely a good way to learn that workflow fast.
Full case study - actual before/after breakdowns - is up on Behance 🔗, linked below.
Genuinely curious where people land on this: generating production assets with AI is fast, and honestly kind of fun as a workflow - but there's real pushback that it's taking work away from people who used to shoot this stuff. Where do you fall on that?
The checkout flow detail is what stands out to me, that's usually where a brand's calm promise turns into three different button behaviors fighting each other. On your AI question, I think it matters less whether it's fast and more who's checking the output against the brand's...
I recently built this workflow in n8n to automate the first stage of handling customer support requests.
The idea was to take an incoming ticket and let the system handle the repetitive work:
→ Receive the customer request through a webhook
→ Process and structure the incoming data
→ Use an AI Agent to understand the ticket
→ Classify it as Genuine, Spam, or Unclear
→ Route it based on the classification
→ Trigger the appropriate email action
→ Log the interaction in Google Sheets
I also added an Unclear path so that tickets the AI isn’t confident about don’t get blindly processed.
The goal isn’t to remove humans from customer support.
It’s to reduce the repetitive sorting and routing work, so the team can spend more time on the requests that actually need their attention.
Would you automate customer support differently? I’d love to hear how you’d approach it.
The Unclear lane is exactly the right guardrail. I’d add two production checks: redact PII before sending ticket text to the model, and measure false-positive/false-negative rates by category rather than a single accuracy score. Logging resolutions and human overrides back into...