AI Funding Solutions · Client Success · 30-Day Plan

The First 30 Days

A complete, step-by-step plan for a new client's first 30 days. The principle is simple: we don't chase a client to hit numbers, we help them optimize their system, and the leads and applications follow. This document gives the team everything, the day-by-day actions, the exact messages to send, and what to do when things go sideways, so nobody has to guess. By day 30 the client has run 300 leads and submitted 20 applications, because we built a working system with them.

Optimize, not push Every message scripted 10 what-if scenarios Days 0 to 3 automated

Built so the team never has to guess. Every day has an action, every touch has a script, and every common problem has a remediation. Product training for Eaze, MagWitch and EZ Check lives in the merchant Training Guide. This is how we help a client put it to work.

The system01

What day 30 looks like

One definition of success, measurable, the same for every client. These numbers are the result of an optimized system, not a target we chase. Optimize the system and they arrive on their own.

Applications submitted

20 or more

Leads through EZ Check

300 or more

Silent days

Zero

A system that runs. Leads flowing into EZ Check, applications moving through Eaze, data connected and compounding.
First deals funded. They have seen the loop close more than once and they trust it.
A confident operator. They can read their portals, run an application, and know exactly where to get help.
Fully supported. A specific, useful touch every working day.

The system02

We optimize, we don't push

A client runs their business better when someone helps them improve it, not when they are chased for numbers. We are the experts. We act like it: calm, specific, and useful, never pushy and never generic.

Not this

"You're behind, run more leads." Motivational lines. Pace pressure. Counting at the client. Leaving them to work the tools out alone.

This

"Let's make sure your data's connected so leads flow." Running their first application with them. Getting their first deal through. Removing the friction so the system does the work.

Why optimization beats pressure

Fix the input, the output follows. Connected data, a clean funnel and a confident operator produce leads and applications without anyone being chased.
Specific help builds trust. "Let me show you where to see your applications" lands. A motivational line does not.
It is why they came. They paid to optimize and run their business well. Help them do that and the 30-day mark takes care of itself.

The voice. Speak like an expert who has done this hundreds of times: clear, warm, and to the point. No hype, no filler, no pressure. Every message names their business and offers a specific next step or a hand.

The system03

The optimization model

This is how we think about every client. We are not chasing leads, we are tuning a system. Every touch answers one question: what can we help optimize today? Run this loop, in this order, for thirty days.

Lead flow and dataThe fuelIs their funnel feeding EZ Check? If they run Meta, is the Pixel connected and firing, so conversion data flows back and their ad system improves? Connected data compounds, every lead makes the next cheaper to find. This is the highest-leverage thing we optimize.
The application, run cleanThe engineDoes their first Eaze application run successfully, end to end? Do they know where to see applications and how to move them through? A clean application loop is the difference between a client who uses the system and one who stalls.
The portals, read with confidenceThe cockpitCan they read EZ Check and Eaze, see lead status and find what they need? Where to look, how to navigate. A confident operator uses the system far more than a confused one.
The first deals, over the lineThe proofThe single biggest optimization is getting their first deal funded. We run the first one with them so they see the loop close, then doing more of it is easy.
Finance applications, movingThe throughputDo they need help submitting or moving applications through? We help, we never leave them to it. Friction here is lost revenue.
Training and confidenceThe multiplierDo they need a walkthrough of any tool? Confidence drives usage, usage drives results. We close every knowledge gap the moment we see it.

The loop. Optimize each of these and more leads flow, more applications flow, and the client runs their business successfully. That is the end result, and it is exactly why they came to us.

The system04

The personalization fuel

This is what makes a message feel written for them. We capture a handful of fields at the sale and onboarding form, and every automated message merges them in. Capture once, personalize for 30 days.

Variable	What it is	Captured at
{{first_name}}	The owner or main contact's first name	Sale / onboarding form
{{business}}	Their business name	Onboarding form
{{vertical}}	Medical, home services, auto, retail, and so on	Onboarding form
{{goal}}	What they want to optimize or achieve, in their words	Discovery call
{{runs_meta}}	Do they run Meta ads? Drives the Pixel-connection help	Onboarding form
{{lead_source}}	Where their leads come from, so we optimize the right funnel	Onboarding form
{{lead}}	Their named point of contact, the human the messages come from	Assigned at form
{{tz}}	Their time zone, so messages land in their morning	Onboarding form

System note. The onboarding form must capture these. {{runs_meta}} and {{lead_source}} are the two that let us optimize the right thing on day one instead of guessing. Square brackets like [time] or [next step] in the messages are filled in by the sender or the automation.

The system05

Automated vs human

The default is automated. A person steps in where a person genuinely helps: running the first application together, getting the first deal through, and the day-30 review. Days 0 to 3 require no manual work at all.

Runs on automation

Channel creation, the welcome, resource pinning, the health board, the daily nudge, optimization reminders, milestone notes, the check-in prompts. All personalized, scheduled to the client's time zone, sent from their point of contact so they read as a real person.

Stays human

The day-1 kickoff and first application, getting the first deal over the line, any scenario where a client is stuck, the MagWitch transition, and the day-30 review. These are where a real voice changes the result.

Days 0 to 3, the gold standard

Trigger. The onboarding form submit fires the sequence.
Tooling. The Slack channel is created from the form; GHL or a scheduler posts each message on a delay, in {{tz}}, from {{lead}}.
Fallback. If any automated step fails, it alerts the point of contact rather than going silent.

The system06

The supportive channel

The channel is where we help, in the open. It shows the client their system getting healthier and makes it easy to ask for a hand. We mark progress on the things that matter, not vanity counts.

The pinned health board

Data connected Pixel firing, funnel feeding EZ Check, yes or no.
Leads flowing this week, with the trend, not a quota.
Applications moving in the pipeline and submitted.
First deal done or not yet, the milestone that matters most.

Progress markers

Each fires a short, plain note the moment it happens, the markers that mean the system is working.

Pixel connectedData flowingFirst application runFirst deal fundedPipeline fullThe mark: 300 / 20

The daily one-tap

The morning nudge ends with one light action: a single reaction to say "all good" or "need a hand". It keeps the line open, and a client who stops responding is the earliest signal someone is stuck, days before a check-in would catch it. That signal feeds straight into the scenarios in section 10.

The plan07

The day-by-day plan

Monday to Friday, day 0 through 30. Every day we optimize one part of their system and offer specific help. Messages land in the client's morning, in their time zone. The exact wording is in the message library.

Week 1 · get the system live and working

Day	Mode	What we optimize / the help we give	The signal we want
Day 0 (close)	Auto	Set up the channel, welcome from {{lead}}, pin resources, book the kickoff.	In the channel, kickoff booked
Day 1	Auto + Human	Kickoff call: get them live, run their first application together end to end, show where to see it and how to navigate. If {{runs_meta}}, connect or confirm the Pixel.	Live, first application run, data connecting
Day 2	Auto	Optimize the data: confirm the Pixel is firing and lead data flowing; walk them through reading the EZ Check portal.	Data flowing, portal understood
Day 3	Auto	Help get the first deal over the line, with them. Mark it the moment it lands.	First deal funded
Day 4	Human	Check-in: any friction? Training, navigation, a finance application they need a hand with? Clear it.	No blockers left standing
Day 5	Auto + Human if stuck	Optimization check-in 1: review system health, fix the biggest point of friction together.	System healthy, friction removed

Days 0 to 3 are fully automated. The human moments in week 1 are the kickoff, the first deal, and help where a client is stuck.

Weeks 2 to 4 · widen the flow, transition cleanly, let it run

Days	What we optimize / the help we give	The signal
6 to 9	Daily nudge. Widen lead volume with the list-upload play, help with any applications in the pipeline, confirm data still flowing.	More leads in, applications moving
10	Optimization check-in 2: where is the friction, what one change unlocks more flow? Help them make it.	Flow improving week on week
11 to 16	Daily nudge. MagWitch approval typically lands, the human-led transition keeps funding seamless. Keep tuning data and applications.	No funding gap, system flowing
17	Optimization check-in 3: confirm the transition is clean and remove any new friction.	MagWitch live, flow intact
18 to 23	Daily nudge. The system is running. Optimize the long tail: any remaining friction, any last training gap.	Runs with little help
24	Optimization check-in 4: final tune before the review.	Flowing into day 30
25 to 30	Daily nudge, progress markers firing as the system delivers. Day 30: the review call.	An optimized business, a happy client

The plan08

The message library

Every message the team sends, written out. Calm, specific, expert. Posted from {{lead}} so they read as a real person. Copy them, fill the brackets, send. For any day not listed, follow the pattern: name the business, name the thing we're optimizing, offer the next step or a hand.

Week 1

Day 0 · welcome (auto)

"Hi {{first_name}}, I'm {{lead}}. I'll be your point of contact through setup and your first 30 days. The plan is straightforward: we get your system live, make sure it's consistently bringing in leads and funded deals, and I'm here whenever you need a hand. Everything you need is pinned at the top of this channel. We're booked in tomorrow at [time] to get you live and run your first application together. Talk then."

Day 1 · before the call (auto)

"Morning {{first_name}}. We're on at [time] today. On the call we'll switch everything on, run your first application end to end, and I'll show you where everything lives so you're comfortable using it yourself. Nothing to prepare, just bring any questions you've got."

Day 1 · after the call (from {{lead}})

"Good to get you set up, {{first_name}}. Quick recap from today: EZ Check is live, we submitted your first application, and both your leads and applications sit in [where]. Your one job before tomorrow is [next step]. I'll check in tomorrow to make sure your data's flowing properly. Anything in the meantime, message me here."

Day 2 · connect the data (auto)

"Hi {{first_name}}. The thing that makes the biggest difference early is making sure your lead data flows back into the system. If you're running Meta, that means connecting your Pixel, so every lead sharpens your targeting and the next one costs less to find. It's a few minutes. Want me to walk you through it now, or book a slot later today?"

Day 3 · the first deal (from {{lead}})

"{{first_name}}, the priority this week is getting your first deal funded. Once one's through, everything after it is repetition. If you've got a client in mind, send them through and I'll stay on with you while we do it start to finish. Who've you got?"

Day 4 · check-in (human)

"Checking in, {{first_name}}. How are you finding everything so far? If anything's unclear, any tool you'd like a proper walkthrough of, or an application you want a hand with, tell me and I'll sort it today."

Day 5 · end of week one (auto, then a call if needed)

"End of your first week, {{first_name}}. Here's where {{business}} is at: [leads], [applications], [first deal]. It's looking [on track / like there are a couple of things to tighten]. The one thing I'd focus on next week is [x]. Happy to jump on a quick call if that's easier, let me know."

Weeks 2 to 4

Daily nudge (auto, the everyday message)

"Morning {{first_name}}. Where {{business}} is at: [leads this week], [applications moving]. Today's focus: [the day's optimization]. If you'd like a hand with it, say the word, otherwise carry on and I'll check in."

Week 2 · widen the funnel (auto)

"{{first_name}}, now the basics are running we can widen the top of the funnel. The quickest win is the list-upload play, it puts your existing contacts through the system in one go. Want me to set it up with you this week?"

Week 3 · the MagWitch transition (human)

"Quick heads-up, {{first_name}}. Your MagWitch approval is coming through, so we'll move you onto it as your main rail. Nothing changes on your end and there's no gap in funding, I'll handle the switch and confirm once it's done, and walk you through anything new."

Week 4 · into the review (auto)

"{{first_name}}, you're in the final stretch of the first 30 days and the system's doing the work now. I'll put together a proper review for early next week so we can look at what's working and where we take it from here. Anything you want me to dig into for it, let me know."

Progress markers (auto, the moment they happen)

Data connected

"Nice, {{first_name}}, your data's connected and flowing. That's the foundation sorted. From here, every lead makes the system a little sharper."

First application in

"First application's in, {{first_name}}. That's the loop working. We'll keep them moving and I'll flag anything that needs you."

First deal funded

"That's your first funded deal, {{first_name}}. The model works for {{business}}, now it's a matter of doing more of the same. Good work."

Day 30

The review (human, {{lead}})

"{{first_name}}, that's your first 30 days. Here's where {{business}} landed: [leads], [applications], [funded deals]. More importantly, your system's running and you know how to use it. Let's get on a call to go through the numbers, tighten the last few things, and map out the next 30. I'll also ask if there's anyone you know who'd benefit from the same setup."

Two rules. Merge fields are never optional, a message that would render blank is held. And no message ever pushes a number, every one offers help. If a draft reads as pressure rather than support, rewrite it.

The plan09

Optimization check-ins

Four scheduled moments to check the system's health and remove friction. The check-in is automatic, the help is human. We never tell a client they are behind. We find what is slowing the system and we fix it with them.

Check-in	What we look at	How we help	Owner
Day 5	Is data connected and flowing? Did the first deal land? Where's the friction?	Jump on, fix the biggest blocker, reset the loop together	{{lead}} + Harvey
Day 10	Is lead volume widening? Are applications moving?	Introduce or tune the list-upload play, help with stuck applications	Harvey
Day 17	Is the MagWitch transition clean? Any new friction?	Hand-hold the transition, remove anything blocking flow	Harvey + David
Day 24	Is the system running on its own? Any last gap?	Final tune, close any training gap before the review	{{lead}} + Harvey

The earliest signal is the one-tap. A client who stops responding to the daily nudge is stuck before a check-in would catch it. Watch the engagement and reach out with help first, using the scenarios below.

The plan10

What-if scenarios

The real world. These are the situations that actually come up, with what to do and what to say. For each: the signal that tells us it's happening, which channel to use, the play, and the exact words. No guessing.

Choosing the channel

Channel	Use it when
Slack (the channel)	The default for everything day to day. In the open, async, where the help lives.
Text / SMS	Time-sensitive nudges, or when the channel's gone quiet for a day and you want a light, personal tap.
Email	Anything that needs to be documented or has links and steps, or after no response to a text.
Call	When they're stuck, when it's high-stakes, or when there's been no response across channels. A ten-minute call fixes more than twenty messages.

Escalation ladder for a quiet client: Slack, then a text the next day, then a call, then an email. Never more than 24 hours of silence without a reach-out.

1. The client goes quiet (no response for 48 hours)

The signal

No reply in the channel and no daily one-tap for two days.

Channel

Text first, it's personal and hard to miss. If no reply, call the same day.

The play

Assume they're busy, not unhappy. Make it easy to re-engage with one low-effort reply, and take any blocker off their plate. Do not pile on more messages in the channel.

What we say (text)

"Hi {{first_name}}, it's {{lead}} from AI Funding Solutions. Haven't caught you in a couple of days, just making sure you're not stuck on anything. If something's in the way, tell me what it is and I'll handle it. If you're just heads-down, all good, reply whenever."

2. The business has poor communication generally (slow, hard to reach)

The signal

One-word replies, long gaps, missed calls. They engage, just slowly.

Channel

Match how they communicate. If they only reply to texts, work in texts. Keep everything in short, single asks.

The play

Reduce the effort it takes them to move. One clear question or one clear action per message, never a wall of text. Do more of the work for them, fewer decisions on their side. Agree one regular check-in time that suits them.

What we say

"{{first_name}}, I'll keep things short and simple so this is easy around your day. One thing for today: [single action]. Reply with a thumbs up when it's done, or tell me to take it off your hands and I will."

3. Momentum slows before day 7

The signal

Leads or applications that were moving have flattened in the first week.

Channel

Call. Early momentum matters too much to handle in messages.

The play

Find the one bottleneck. It's almost always one of three: data not connected, they're unsure how to run leads, or they haven't had a first deal yet. Fix that one thing on the call, don't talk about volume.

What we say (call open)

"{{first_name}}, wanted to grab ten minutes early rather than let anything drift. Let's look at what's flowing and what isn't, and I'll sort whatever's slowing it down. Walk me through what you've been doing day to day."

4. No first deal by day 5

The signal

Live and running, but nothing funded yet.

Channel

Call, and do the first deal live on it.

The play

Don't coach, do it with them. Get a real client on the application together, walk every step, and get one over the line on the call. The first deal is the unlock, everything is easier after it.

What we say

"{{first_name}}, let's get your first one done together right now so you've seen the whole thing once. Have you got a client in mind we can run? I'll stay on with you the entire way and we'll get it over the line."

5. Their data or Pixel isn't connected

The signal

Leads aren't flowing back, or the health board shows data not connected.

Channel

Slack with a screen-share offer, or a short call. This is hands-on.

The play

Get on a screen-share and connect it with them, don't send instructions and hope. If they run Meta, set up the Pixel; if not, confirm their funnel is feeding EZ Check. This is the highest-leverage fix, so prioritize it.

What we say

"{{first_name}}, let's get your data connected properly, it's the thing that makes everything else easier. Jump on a quick screen-share with me and we'll have it sorted in a few minutes. What suits, now or [time]?"

6. They're not running leads / the funnel isn't feeding EZ Check

The signal

Low or no lead volume through EZ Check.

Channel

Call to diagnose, then Slack to keep it moving.

The play

Find out where their leads currently come from ({{lead_source}}) and connect that to EZ Check. If they have an existing contact list, run the list-upload play to get immediate volume while the funnel ramps.

What we say

"{{first_name}}, let's make sure your leads are actually flowing into the system. Where are most of your enquiries coming from at the moment? If you've got an existing list, we can run it through in one go and get you moving while we connect the rest."

7. They're overwhelmed or confused by the tools

The signal

Questions that suggest they're lost, or they've gone quiet after a confusing session.

Channel

Call with a screen-share. Confusion never gets fixed over text.

The play

Slow down and reset to one tool at a time. Don't re-explain everything, find the one thing they're stuck on and walk it with them. Point them to the exact part of the Training Guide afterwards so they can self-serve next time.

What we say

"{{first_name}}, totally normal, there's a lot here at the start. Let's not run through all of it, just tell me the one thing that's tripping you up and I'll walk you through it now. We'll take it one step at a time."

8. An application stalls or the client is declined

The signal

An application sits without progress, or a decline comes back.

Channel

Slack to the client for status; the broker team works it in the background.

The play

Get the broker team (Harvey) on it to work the wider lender network for the best viable option. Keep the client informed without over-promising, and never present a decline as a dead end, it's one lender, and we work many.

What we say

"{{first_name}}, one of the lenders couldn't make that one work, which is normal, that's exactly why we work a broad network rather than a single lender. The team's already looking at the best options for this one and I'll come back to you as soon as we've got a path."

9. Mid-month drop-off (they go cold around day 10 to 17)

The signal

Engagement that was good in week one fades in the middle weeks.

Channel

Call. Re-establish the relationship and the momentum in person.

The play

The mid-month dip is the most common place a client drifts. Reconnect to their original goal, show them the progress they've already made, and give them one clear, achievable focus for the week ahead. Make sure the MagWitch transition isn't the hidden cause.

What we say

"{{first_name}}, wanted to check in properly. You came to us to [goal], and you've already got [progress so far], which is a solid base. Let's lock in one focus for this week to build on it. What does the next couple of weeks look like on your side?"

10. Doubt, or "is this actually working?"

The signal

A frustrated message, a comparison to expectations, or quiet hesitation.

Channel

Call, same day. Doubt left in writing hardens, a conversation resolves it.

The play

Take it seriously and don't get defensive. Acknowledge it, show the real progress and the data, and be honest about what's next and the timeline. If something genuinely isn't working, own it and fix it. End with one concrete next step so they leave the call with momentum.

What we say

"{{first_name}}, I hear you, and I'd rather talk it through properly than message back and forth. Let's get on a quick call, I'll show you exactly where things stand and what's coming, and if there's something we need to fix, we'll fix it. When works in the next day?"

The principle across all of them. Reach out first, take the blocker off their plate, and use the channel that fits the moment. We are the experts. A calm, specific response to a problem builds more trust than a month of things going smoothly.

Run it11

How we measure it

We measure the health of the system, not just the totals. These signals tell us where to help next, and the totals follow from them.

System health. Data connected, Pixel firing, funnel feeding EZ Check.
Flow. Leads this week and the trend, applications in the pipeline and submitted.
The first deal. Done or not yet, the milestone that matters most.
Engagement. Is the client still responding to the daily nudge, are they asking for help when they need it.
Day 30. 300 leads, 20 applications, and a client who can run the system themselves.
Program. Across all clients: percent with data connected by day 2, percent with a first deal by day 5, where clients get stuck most often, so we improve the plan itself.

One board for the team. Every client's system health and flow in one place, so anyone can see at a glance who's running well and who needs a hand today.

Run it12

The moments that stay human

Automation carries the load. These moments earn a real voice, because a person genuinely changes the outcome.

The day-1 kickoff and first application{{lead}}Get them live, run the first application together, show them the portals. The moment they realize the system is simple.
The first deal over the line{{lead}}Run the first funded deal with them so they see the loop close. Nothing builds belief faster.
Any scenario where they're stuckHarveyWhen the system slows or a client goes quiet, a call, not a message. Find the friction, remove it together.
The MagWitch transitionHarvey + DavidAround week three, keep funding seamless as they move onto their everyday rail.
The day-30 review{{lead}}Show them their system and what it produced, tune the last bits, map the next 30. The ending they remember.

Run it13

Who runs it

Clear owners, so nothing falls between automation and people.

Point of contact

e.g. Shara

The human the messages come from. Runs the kickoff, the first deal, and the day-30 review.

Harvey

Lead Broker

Owns the check-ins, stuck applications, and any client who needs hands-on help.

Chai

Operations Director

Owns the plan, the health board, and that no client ever has a silent day.

The one upstream job. Make sure the onboarding form captures the personalization fields in section 04, including whether they run Meta and where their leads come from. Everything else runs off them. [Confirm the automation tooling, GHL or scheduler, and who builds the sequences.]

Optimize their system. The results follow.

Help, never push. Every day has an action, every touch has a script, and every problem has a remediation.