this is when you DONT need a system

Confession:

I recently process mapped and built a VERY robust sales system for myself - which I had to throw out after a month of not using it once.

I needed more nuance than the rigid system I originally built provided!

I should have known better. Refining and tweaking systems after actually using them is pretty typical with the systems I build for my clients.

The rhythm:

🥁 We process map the ideal system.

🥁 I build.

🥁 Client starts using the systems in real time and find they need something slightly different.

🥁 I tweak and refine.

I design my systems to be flexible in this way.

This came up in one of my regular Voxer talks with Jamie Cox.

Jamie had a similar question to my own:

what is the best way to structure our sales processes?!

🤔 Do we always offer sales calls?

🤔 OR do we always first push folks to our smaller offers that give clarity before upselling to our bigger offer?

🤔 Do we have a robust intake form, or just get straight to discovery on a call?

Jamie and I are both organized and enjoy, prefer, THRIVE on structure. (twins, always.)

So naturally we were doing our best to discover - what is the best process?

What we realized together is that something like sales just has... nuance.

(After Jamie and I discussed this, she offered "you know, you should write an email about when you DON'T need a system.")

But there is still a system!

OR a few different systems that can be interchanged depending on the needs of the lead.

🌱 Some folks come to me with a proven offer that is selling and a feeling of overwhelm.

That means we need to jump into my full Custom System Suite package ASAP so they can actually handle the work that is coming in.

🌱 And other times, what the person needs feels a bit fuzzy to me.

Which means it's a bit fuzzy to them.

Which means we need to start with Process Mapping first and take things from there.

So my sales process is still a system - it's just a roomy and flexible one.

The system still exists. There are still flows and containers.

Knowing when a system should stay loose and flexible or airtight and full of hard boundaries is an art I have been perfecting for years across countless client builds.

Even the parts of your process that feel fully custom to each client can still have a container they live in.

A container that makes your life easier.

For example: my Custom System Suite has strong structure. We have deadlines and due dates. Things happen in a certain order.

And once delivery starts, I might rearrange which tool I train the client on first depending on their style of learning and existing ease with tech.

I might build things in a different order depending on the client's priorities so they can jump into the systems ASAP.

And I might do all that rearranging mid-build, reacting to my client's feedback in real time.

The point is, I have a container all of this lives in. A bigger system that can be rearranged like legos as needed.

If delivering your services feels too nuanced to systematize yet too messy to deliver comfortably, it's time to bring me in to build 💅🏻

I will take the absolute mess in your head and spin it into a magical system that lets your business function with ease - even with the nuances of each client 💞