It was past midnight. My children were asleep.

And I was troubleshooting someone else’s broken automation.

I remember thinking: this is fine. This is what dedication looks like.

I was wrong.

That’s not dedication. That’s a trap. And I had walked into it with my eyes open, convinced it was the price of building something real.

The trap doesn’t announce itself. It disguises itself as ambition.

It tells you the extra hour is worth it. That the DM answered at 11pm is just “being responsive.” That exhaustion is proof you care.

I believed all of it.

I started as a Virtual Assistant in 2009. My clients were coaches, speakers, trainers — brilliant at transforming other people’s lives and completely overwhelmed by the backend of their own businesses.

I was the person behind the curtain. Keeping the machine running while they did the work that actually mattered.

I was good at it. And I was paying attention.

From that seat, I saw everything. The launches held together with duct tape. The onboarding processes that lived entirely in the founder’s head. The six-figure businesses that looked polished from the outside and were quietly falling apart on the inside.

By 2010, I moved into digital marketing project management — working with a company that trained project managers pursuing their certification. That role taught me something that changed how I saw everything: how to think in systems. How to manage outcomes, not tasks. How to build a process that runs without you standing over it.

Then came an agency owned by a business coach in New Zealand. Then ClickFunnels. MailerLite. AppSumo.

I was inside the builds, the launches, the pressure of delivery deadlines and client expectations. Inside the support queues, the product ecosystems, the seven-figure screenshots.

I also saw what was behind the screenshots.

Coaches who couldn’t take a weekend off. Course creators with waitlists and broken backends. Speakers filling stages while their operations were held together with a VA who was doing her best and had no system to follow.

The pattern was always the same: brilliant people, growing fast, breaking faster.

And the advice they kept getting? Do more. Launch again. Hire another VA. Scale harder.

Nobody was saying the obvious thing.

So I will.

Here’s what I didn’t mention until now.

I was doing all of this as a mother.

There was no “before kids” version of my career and an “after kids” version. Motherhood was woven through every support ticket, every product launch, every late-night automation fix. My children were there for all of it — the VA years, the project management work, the agency builds, ClickFunnels, MailerLite, AppSumo.

And that’s exactly what made me see the broken system for what it was.

Motherhood didn’t soften me. It sharpened me.

When your time is no longer infinite — when another human needs you at 6am regardless of how late you worked the night before — you stop tolerating what doesn’t work. You stop attending meetings that should have been a message. You stop doing work that should be systematized.

You build differently. Not because you want to. Because you have to.

My kids didn’t slow my business down. They forced me to build one that actually works — without requiring me to sacrifice everything else that matters.

That realization became the belief I’ve built everything around:

Not just inside businesses. Across every pillar of life — family, career, community.

You cannot build a sustainable business on an unsustainable life. You cannot champion your clients’ growth while your own team is running on fumes. You cannot preach transformation while operating from exhaustion.

The system I left — the one that glorifies burnout and calls it dedication — doesn’t produce better work. It produces burned-out people who eventually stop working altogether.

I know. I was one of them. I bought into the hustle. I ran on adrenaline. I mistook exhaustion for progress.

And I was doing it all while putting kids to bed, making lunches, showing up at recitals — trying to be present in the moments that don’t get a second chance.

So I built Creative Dash.

Not as an agency. Not as a freelancer marketplace. As an operational partner — a team that takes the backend off the plate of people who should never have been carrying it in the first place.

One dedicated project manager. A team of trained specialists. A weekly report. Zero daily management required from the client.

It’s not glamorous. Nobody posts about it. There’s no passive income angle, no laptop lifestyle promise.

It’s the unsexy work that makes the sexy work possible.

If you’re a coach, a trainer, a consultant who’s winning on the outside and drowning on the inside —

You’re not failing.

You’re just building alone.

You don’t have to.

Before I started Creative Dash, I worked at MailerLite.

Not as a consultant. Not as a contractor passing through. I was inside the company, a Customer Support Manager helping run a team that served a globally distributed product used by over a million businesses.

And it quietly rewired how I think about work.

MailerLite had been building a remote-first culture since 2014. Not because a pandemic forced them to. Because their founders believed, deliberately and philosophically, that the office is not where the best work happens.

By the time I joined, this wasn’t a policy on an HR page. It was the air in the room. Or rather, the air across 40+ countries where the team was scattered, working asynchronously, without anyone looking over anyone’s shoulder.

I’d never experienced anything like it.

Trust wasn’t earned. It was the starting position.

This is the thing that changed me.

Most companies hand out trust the way they hand out promotions: slowly, conditionally, after you’ve proven you deserve it. You earn trust by showing up early, staying late, and responding to messages before you’ve had time to think.

MailerLite flipped that. Trust was the default. From day one, you were given ownership of your work, autonomy over how you did it, and the quiet expectation that you’d deliver. Not because someone was watching, but because you were a professional who wanted to do good work.

When trust is conditional, people learn to look trustworthy. They attend meetings they have nothing to contribute to. They stay visible because visibility is the currency.

When trust is the starting position, all of that falls away.

The only question left is: Is the work good?

That’s not a subtle shift. That’s a completely different company.

The quietest teams think the deepest.

Here’s something counterintuitive about MailerLite: the best communication happened slowly.

Meetings were rare, short, and had a clear reason to exist. Most communication happened in writing, at a time that worked for the person receiving it, not the person sending it.

At first, this felt strange. I was used to workplaces where responsiveness meant immediacy. Where a Slack message expected a reply within minutes. Where the day was a series of interruptions disguised as collaboration.

MailerLite treated uninterrupted time as sacred. Not as a perk. As infrastructure.

Every unnecessary meeting, every ping that demands an immediate response, every tool that creates the expectation of real-time availability: that’s a tax on deep work. And MailerLite refused to pay it.

I carried this into Creative Dash. Our clients don’t hear from us every day. They get one structured update on Friday that tells them everything that matters.

That’s not less communication. That’s respect for their time, expressed as a system.

Connection doesn’t die without an office. It just has to be chosen.

The most common argument against remote work is the hardest to dismiss: without physical proximity, culture evaporates. The hallway conversations. The lunch-table ideas. The human texture of being in the same room.

MailerLite didn’t pretend Slack could replace that. Instead, they did something smarter. They invested in intentional, in-person moments.

Every year, the entire global team met for a workation. A different country each time. Not a corporate retreat with icebreakers and keynote speakers. A real gathering. Shared meals. Long conversations that had nothing to do with deadlines. The chance to remember that the person on the other side of the thread is a human being with a full life.

And every time, the same thing happened: the people you already trusted became more real. Not because the in-person experience changed who they were. Because it confirmed it.

Remote work doesn’t mean isolated work. It means the relationships underneath the work have to be chosen, not left to chance.

Hierarchy is a substitute for trust.

One of the quietest things I noticed at MailerLite was how flat the structure was.

Not flat in a naive, everyone-gets-a-vote way. Flat in the way that mattered: good ideas weren’t held hostage by seniority. The people closest to the work made decisions about the work. And nobody needed three levels of approval to move.

The default instinct in a growing company is to add layers. More managers. More oversight. More structure. Because hierarchy feels like control, and control feels like safety.

But hierarchy is what you build when you don’t trust people. when you do trust them, genuinely and operationally and not just on a values page, you need far less of it.

The one hiring filter that matters most.

This is the lesson I carried most directly into Creative Dash.

MailerLite didn’t just hire for skills. They hired for self-direction: the ability to figure out what needs doing, do it without being told, and raise a problem before it becomes a crisis.

Remote work exposes the gap between people who can manage themselves and people who need to be managed. There is no hiding in a remote team. No looking busy at a desk. No performing for an audience that isn’t watching.

Every specialist on the Creative Dash team is evaluated for this quality. Not just whether they can execute, but whether they can own. Can they take responsibility for an outcome without someone hovering? Can they communicate proactively rather than waiting to be asked?

These aren’t soft skills. They’re the difference between a team that functions without supervision and a team that requires it.

And for a company whose entire promise is that the client shouldn’t have to manage the people managing their business, they’re non-negotiable.

What I built with what I learned.

The Creative Dash model (one dedicated Project Manager, a team of trained specialists, a weekly report, zero daily management required) didn’t come from a business plan.

It came from watching how a Lithuanian startup with no venture capital and no Silicon Valley address built a world-class team across 40+ countries. By trusting people. By protecting their time. By hiring for ownership. By making human connection deliberate instead of accidental.

MailerLite proved something that most companies still resist: work is about what gets done. Not where you were sitting when you did it.

That belief runs through everything I build.

Further reading:

Remote: Office Not Required by Jason Fried and David Heinemeier Hansson — the original case for distributed work, still the clearest articulation of why the office is not where the best work happens.

Leaving the Base Camp by Ilma Tiki — MailerLite’s co-founder’s account of how a Lithuanian startup pioneered remote work and built a global team. Worth reading if you are building an expert-led business.

I didn’t learn how funnels work by building them.

I learned how they work by fixing them. Hundreds of times, for real businesses, at the worst possible moment.

Before I founded Creative Dash, I spent years as a Technical Support Specialist inside ClickFunnels. My job was simple: sit in the support queue and help entrepreneurs figure out why their funnels were broken.

Not in theory. In production. With real traffic running, real money on the line, and a real person on the other side of the ticket watching their launch fall apart in real time.

You learn things in that seat that no course will teach you.

The gap nobody talks about.

Here’s what the marketing world doesn’t say out loud: a funnel can look perfect in the builder and be completely broken for the person trying to buy.

Your page loads fine because your browser cached everything when you built it. Your Zap fires in test mode because test mode doesn’t replicate real purchase conditions. Your checkout works with your card, the one already saved and verified in Stripe, in a way a cold visitor’s card won’t.

You see a working funnel. Your visitor experiences a broken one.

And they don’t email you to tell you. They just leave.

That invisible gap between what the builder sees and what the buyer experiences is where most funnel conversions die. Not on the headline. Not on the price point. On a broken redirect, a misconfigured automation, or a page that looks beautiful on desktop and falls apart on a phone.

Five patterns. Hundreds of tickets. The same story.

After enough time in the queue, the patterns stopped surprising me. The same failures, different businesses, over and over. Here’s what broke most often, and why.

The Zap pointed at the wrong funnel step.

This was the single most common automation failure I saw.

When you set up a Zap to trigger on a purchase, it needs to point at the Order Page, the page where the transaction happens. Not the confirmation page. Not the thank-you page. The Order Page.

The problem? In ClickFunnels, funnel steps often have similar names across multiple funnels. It’s remarkably easy to select the wrong one. The Zap passes the test. And in production, it either fires on the wrong step, fires multiple times, or doesn’t fire at all.

The consequence depends on what the Zap was supposed to do. If it was adding the buyer to an email list, they never get onboarded. If it was granting course access, they pay and can’t log in. If it was duplicating, they get charged twice.

All of these showed up in my queue. Regularly.

The fix is always the same: go back to the trigger setup, reselect the funnel and funnel step deliberately, and run an end-to-end test with a real transaction before you send any traffic.

The payment gateway was still in test mode.

This sounds too obvious to happen at scale. It happened constantly.

A builder sets up Stripe, runs a test transaction, confirms the checkout works, and launches. The payment gateway is still in test mode. Every real transaction either fails silently or processes without actually charging the card.

From the builder’s analytics, opt-ins are rolling in. From the buyer’s experience, nothing works. From the business owner’s bank account, nothing is arriving.

ClickFunnels doesn’t make it visually obvious when a payment integration is in test versus live mode unless you know exactly where to look. Most builders check whether the integration is connected. They don’t check whether it’s in the correct mode.

One real transaction with a live card before launch. That’s all it takes to catch this.

The funnel was never tested on mobile.

More than 60% of online purchases happen on mobile. Most funnels are built on a desktop.

A page that renders perfectly on a 27-inch monitor (readable text, properly sized buttons, a clean checkout form) can be completely unusable on a phone. Buttons too small to tap. Text overflowing its container. A submit button sitting below the fold where nobody scrolls.

The builder checks the funnel on their desktop. Looks great. Sends traffic. The traffic is mostly mobile. The mobile experience is broken. Conversion rates crater and nobody can figure out why, because the funnel looks fine.

This was one of the most consistent patterns in the queue. Not because anything was dramatically wrong. Because the funnel had never been tested in the environment where most of the traffic would actually encounter it.

Test on at least two different phones. Not in the ClickFunnels mobile preview. On an actual device, with an actual browser, going through the actual purchase flow.

Third-party integrations fighting each other.

Most funnels connect to an email platform, a CRM, a webinar tool, and one or more automation layers. Each connection is a potential conflict point.

What I saw repeatedly: a funnel that worked perfectly with one integration broke the moment a second was added. Not because either was configured incorrectly on its own, but because the two were conflicting in ways neither tool’s documentation mentioned.

The most common version: two tools trying to update the same contact record simultaneously. Duplicate entries. Incorrect tags. Automations that appeared to fire in the logs but produced nothing on the other end.

You can’t test integrations in isolation and assume they’ll play nice together. The full chain has to be tested end-to-end.

The SSL certificate wasn’t properly secured.

This one is quiet and expensive.

A domain that shows “Not Secure” in a visitor’s browser is a conversion killer. And most visitors won’t tell you about it. They’ll just close the tab.

In ClickFunnels, SSL status has to be manually verified after domain setup. The platform doesn’t always make this obvious. The verification step is easy to skip, especially when the domain appears connected and the page loads without errors.

What the builder sees: a page that loads. What the visitor’s browser shows: a security warning before the page even renders.

Manual SSL verification after every new domain connection. Not assumed. Verified.

The thread running through all five.

None of these failures are visible in the funnel builder.

Every one of them appears only when a real visitor, on their device, with their browser, using their payment method, tries to go through the funnel in production.

This is the fundamental problem: most people test funnels from the builder’s perspective. They check whether the page loads. They don’t check whether it converts. They confirm the Zap is connected. They don’t confirm it fires correctly in a live purchase scenario. They see the checkout form. They don’t complete a real transaction and verify the funds.

The most important test you’ll ever run on a funnel is the end-to-end buyer test. Going through your own funnel, on a mobile device you didn’t build it on, with a real payment method, as a brand new visitor who has never seen your brand before.

Most funnel builders have never done this. Every failure I just described would be caught immediately if they had.

The checklist I built from the queue.

After years of seeing the same patterns repeat, I developed a pre-launch protocol that Creative Dash now applies to every funnel we deliver. It’s the reason our clients don’t discover their funnel is broken on launch day.

• Confirm payment gateway is in live mode and verify a real charge appears in the processor dashboard.
• Test the complete funnel end-to-end on at least two different mobile devices.
• Verify every Zap trigger is pointed at the correct funnel step.
• Complete a real transaction and confirm all automation outputs in every connected system.
• Check SSL status manually in domain settings after every new domain connection.
• Test all forms for submission errors.
• Disable conflicting integrations one at a time and test after each re-enabling.
• Verify all redirect sequences land on the correct pages in the correct order.
• Check every link in every post-purchase email.
• Test cross-browser compatibility, at minimum Chrome and Safari on both desktop and mobile.

This checklist won’t make your funnel convert better. What it does is ensure that the funnel you built is actually the funnel your visitors experience.

That’s the prerequisite for everything else.

Why this matters if you build funnels for clients.

A broken funnel on your own business costs you revenue. A broken funnel delivered to a client costs you the client.

The agencies I’ve worked with who have the most consistent client satisfaction are the ones who built quality assurance into their delivery process as a non-negotiable step. Not something that happens when there’s time. A structured gate that every deliverable passes through before it reaches the client.

A client who receives a funnel that works on launch day, every time, is a client who stays. A client who discovers a broken automation after launch, regardless of how good the strategy and copy were, is a client who quietly starts looking for someone else.

The technical standard of your delivery is your brand.

Treat it accordingly.

The bottom line.

Funnels break because they aren’t tested properly before they go live.

Not because the copy is wrong. Not because the offer is weak. Because someone built the funnel, looked at it in the builder, and assumed it would work the same way for a cold visitor on a mobile device with a real credit card.

It usually doesn’t.

I spent years watching this happen from inside the support queue. Then I built the protocols to prevent it.

If your agency delivers funnels and you want a fulfillment partner whose standards come from inside the error logs,
not from a course, that conversation starts with a 30-minute call. No pitch. Just a clear look at whether this is the right fit.