Puja Patel · The Systems Map

get the free systems map

every system a service business runs on, in the order a stranger becomes a client, with the questions that get each one out of your head.

please fill in every field.

that doesn't look like a mobile number. outside the US? start with + and your country code.

By adding your number, you agree to get texts and calls from Puja Patel and her team. Msg & data rates may apply. Reply STOP anytime. Privacy

Puja Patel · The Systems Map

how it all connects

every system in your business connects. they chain into one process: the path a stranger takes to becoming a paying client. answer the questions across the map and you're not taking notes. you're extracting your own system.

start with the stage that costs you the most. answer its questions out loud, the messy version. that's how a system gets out of your head.

↔ scroll the map sideways to follow the whole flow.

Where are your leads currently coming from?
→
Where do they go?
→
Do you get notified when that happens?
→
How long before you reach out / reply?
→
Are you getting the info you need through the intake?
→
Triage each lead into the correct offer
Define your ICP for each offer
Industry / niche
Actual problem
Timeline
Etc.
↑ your ICP — defined here, deepened in day 3, applied in day 4
→
What questions get them to rant about their problem?
Define your ICP on a deeper level
Their buyer type
Symptoms of their problems
→
Research what you already have (LinkedIn, website, etc.)
→
Where do your call notes live?
→
What questions do you NEED answered on your proposal?
The problem (in their words)
The outcome (desired result)
The scope (actual work)
The terms (price / timeline)
→
Do you have a structure for your proposals?
→
How long from end of discovery call to proposal sent?
→
Do you present the proposal, or just send it?
→
What next step do you set? (a decision date, not "let me know")
→
What objections do you hear over & over?
Your objection bank
Price
Timing
"Let me think about it"
"Check with my partner"
→
What happens the second they say yes? (contract + deposit ready)
→
Who's gone quiet — and how many with no next step?
→
What's your rule for when a follow-up fires? (days quiet · # of touches)
→
Where does each lead's status live?
→
What do you say each time?
Your message bank
Quiet warm lead
Proposal — no reply
Past-client reactivation
→
Which past clients haven't heard from you in 90+ days?
→
The second they say yes — what locks it in? (contract + deposit)
→
What do you need from them to start?
Your kickoff intake
Access & logins
Assets & brand
Answers only they have
Points of contact
→
What do they hear right after? (welcome + what's next + timeline)
→
Is the kickoff call booked in the same motion?
→
Where does the project live on day one?
→
When a client's ready to start — what gets set up on your end?
Your setup checklist
Workspace / project home
Tools & access
The tracker
First tasks staged
↑ project home created day 7 → fully set up here (day 8)
→
What do you hand them to step in — and how do they find their way + reach you?
→
What do you both lock in before the work starts? (how you'll talk · what you each need)
→
Who needs to be on the same page before you start?
Which brief?
Internal — align your team on the work
External — align the client on deliverables
Often both — one brief, pointed each way
↑ onboarded (day 8) → the work defined here → scheduled (day 10)
→
What's the one goal — in THEIR words?
→
What's in scope — and what's explicitly OUT?
→
Who owns what — and who makes the call?
→
How will you stay synced? (checkpoints · how you share progress)
→
What are your milestone deadlines? (from your kickoff brief)
→
What are the tactical tasks — with verbs — to hit each milestone?
Sort every task
Can run at the same time
Has to go in order (one can't start till another's done)
↑ milestones from the kickoff brief (day 9) → each task gets a seat + a done (day 11)
→
Which of those tasks need client input?
→
By when does each piece land — with buffer to beat the client's deadline?
→
Is each piece small enough to finish in one sitting?
→
Who owns it — name the SEAT, not just the person
Who owns it
You — the calls only you can make
Someone you pay — team, contractor, VA, agency
The client — with a date, same as anyone
AI — the lines nothing about you needs to do
↑ solo? you hold every seat on your side — the client's is still theirs
→
When's it due — and how does that person find out it's theirs?
→
What does done look like — and where do you both see status?
The output
You see what's stuck without asking anyone
↑ scheduled (day 10) → owned & tracked here → reported weekly (day 12) →
→
What does your client need to know every week?
Only four things
What got finished
What's next
What's sitting with THEM
Did anything move the date
↑ owned & tracked (day 11) → read out to the client here
→
When does it go out — and does it still go out on a slow week?
→
Where do the facts come from — and what's the one thing you need back?
The output
A client who never has to check in
A written record of every week it sat on their side
↑ pull from the tracker, not your memory → it goes out on the boring weeks too
→
What does this meeting need to PRODUCE? (a decision — not a check-in)
Every agenda line is a…
Decision to make
Question to answer
Not a topic — topics wander
↑ if it's just a readout, that was the day-12 update
→
What do you walk in already knowing?
Pull from where the work lives
What's moved since last time
What's sitting on THEIR side
Last meeting's action items — done?
→
Does the agenda go out BEFORE — so they show up ready to decide?
The output
One call, decisions made, everyone clear
No "let me get back to you" second meeting
↑ reported weekly (day 12) → the live meeting prepped here → notes → actions (day 14) →
→
What actually got DECIDED? (capture decisions, not the discussion)
Pull the 5%, not the transcript
The decisions made
The owned next steps
The open questions left
↑ a notetaker gives you a receipt — this makes the record
→
Which actions are real — who owns each, by when?
Every action gets…
An owner — a seat, not a name
A date
A home: your tracker (day 11)
→
Where does it land — and who hears it?
The output
Actions in the tracker, nothing on the floor
A recap to the room within the hour
↑ prepped (day 13) → the meeting → notes → actions → the work (day 15) →
→
What do you start from — a blank page, or a structure you reuse?
Start from your standard skeleton
Your sections, in your order
Your voice + depth
Same for every deliverable of this type
↑ the blank page is a missing template, not missing ideas
→
How much is assembling what's decided vs. your expertise?
Name the 80 / 20 line
~80% assembly: goal in their words, scope, meeting calls
~20% expertise: the judgment only you make
Pour in the assembly — spend your brain on the 20%
→
What makes a first draft done — and where does it go next?
A wrong-but-whole v1
Complete enough to react to, not perfect
The judgment calls flagged for you
→ the quality check (day 16)
↑ notes → actions (day 14) → the first draft of the work → checked (day 16) →
→
What has to be true of everything you send?
The universal bar
Right name, links open
Dates match what you promised
No leftovers from a past version
↑ written once — stops depending on whether you looked
→
What checks matter for the one thing you deliver most?
One list per thing you make
A report, an ad, a contract each carry their own
Past 2? it's an unwritten checklist in your head
→
Different eyes, every time?
Held against the brief, not just typos
"Is it correct" catches the cheap misses
"Does it do the job" catches the expensive ones
→ feedback & revisions (day 17)
↑ drafted (day 15) → checked vs the brief (day 9) → out to the client →
→
When feedback comes back, where does it land?
One list, tied to the deliverable
Call, email, doc, text — one place
Revise from the list, not memory
↑ scattered notes get dropped → the round reopens
→
Fix, or new request?
Sort before you touch the work
Fix: in the brief — just do it
New: a change, its own conversation
Rounds bounded in the contract (day 7)
↑ the sort = revision vs unpaid scope creep
→
Concrete change, or vague feeling?
Translate, then send back note by note
"Make it pop" → one question first
Send back: each note → what changed
→ approval & sign-off (day 18)
↑ checked (day 16) → sorted & revised → the yes (day 18) →
→
Before it goes out, does it clear a sign-off?
A required yes, from the right person
Ships on a yes — not on "someone finished it"
Each type of work → who's allowed to approve it (day 9)
↑ no gate, or the wrong approver → it reopens later
→
When it's approved, where does the yes live?
Written down: what · who · when · version
Not a "go ahead" nobody can find later
"Did we approve this?" → one-second lookup
↑ a verbal yes → "i never approved that" wins
→
Once approved, is it locked?
Locked — next phase starts, invoice goes
Anything new after = new work (day 7 / 17)
→ progress dashboard (day 19)
↑ sorted & revised (day 17) → the documented yes → locked (day 19) →
→
Where does every project's status live?
One view, every project
Pulled from the tracker (day 11), not your memory
Status · next step · who it's waiting on
↑ if you have to ask around, there's no dashboard
→
What does each project need to show?
Only what moves a decision
On track · at risk · blocked
Next milestone + date (day 10)
What's sitting with the client
↑ the same facts as the weekly update (day 12)
→
Who looks at it, and when?
A rhythm, not a rescue
You: a 10-minute scan, same time every week
→ final handoff & delivery (day 20)
↑ locked (day 18) → visible here → delivered (day 20) →
→
What does the client receive at the end?
The complete package, named
Every deliverable, final version (day 18)
Access, logins, files: transferred, not shared
↑ done = they have everything without asking
→
How does it reach them?
One delivery moment
A handoff call or a walkthrough video
One place for everything, not six emails
↑ a messy handoff erases a great project
→
What do they need to keep it running?
The how-to that stays behind
How to use it · who to call
→ close-out & retro (day 21)
↑ tracked (day 19) → handed off → closed out (day 21) →
→
What officially closes the project?
A clear end
Final invoice paid
Written: what was delivered vs the brief (day 9)
↑ no close → the project quietly never ends
→
What went well, and what broke?
A 15-minute retro
What to repeat
What to fix in the system, not the person
↑ every mistake becomes a rule, once
→
Where do the lessons go?
Into the systems, not a doc nobody opens
Update the checklist (day 16) or the template (day 22)
→ deliverable to template (day 22)
↑ delivered (day 20) → closed & learned → reused (day 22) →
→
Which finished deliverable will you make again?
Pick the one you rebuild most
Proposal · report · onboarding doc · SOP
↑ the blank page is a missing template (day 15)
→
What stays the same every time?
Strip it to the skeleton
Sections, order, standard language
Mark the parts that change per client
↑ ~80% assembly · ~20% your judgment (day 15)
→
Where does the template live, and who uses it?
One home, findable in seconds
Named so anyone can find it
→ support request intake (day 23)
↑ closed out (day 21) → templated → the next client starts faster →
→
When a client has a question, where does it go?
One front door
Not your personal text thread
Email, form, or a shared channel: pick one
↑ five doors → things fall through
→
Who answers, and how fast?
A seat and a promise
Owner: a seat, not a name (day 11)
A response time they can count on
↑ fast and predictable beats instant and random
→
Is it a quick answer or new work?
Sort it like feedback (day 17)
Question → answer it
New request → its own scope
→ FAQ / knowledge base (day 24)
↑ templated (day 22) → asked → answered once (day 24) →
→
What do clients ask you over and over?
Your top 10 questions
Pull them from support (day 23) and your calls
↑ answered 50 times = written down zero times
→
Where do the answers live?
One page clients can find
In onboarding (day 8) and your welcome
Written once, linked forever
↑ the answer you send most should be a link
→
Who keeps it current?
Update it when the answer changes
Asked twice → it goes in
→ feedback & check-ins (day 25)
↑ asked (day 23) → answered once → asked less →
→
When do you ask how it's going?
Before they have to tell you
Mid-project, not just at the end
After each milestone (day 10)
↑ silence isn't satisfaction
→
What do you ask?
Two questions, every time
How's it going, 1 to 10?
What would make it better?
↑ a number you can track + words you can use
→
What happens with the answer?
Act on it, out loud
Low score → a call this week
High score → testimonial ask (day 26)
↑ answered once (day 24) → checked in → captured (day 26) →
→
When do you ask for a testimonial?
At the high point
Right after a win or a 9-10 check-in (day 25)
↑ ask while it's fresh, not at the end
→
What do you ask them?
The before, the after, the how
Where were you before?
What changed?
What would you tell someone like you?
↑ their words sell better than yours
→
Where does it go?
One library, ready to use
Website, sales calls, proposals (day 4)
→ renewal & upsell (day 27)
↑ checked in (day 25) → captured → used to sell →
→
When does the next engagement come up?
Before the current one ends
At close-out (day 21) at the latest
Built from what they told you (day 25)
↑ the best time to sell is while it's working
→
What's the natural next step for them?
The next problem, not more of the same
Retainer · phase 2 · a bigger scope
↑ offer what they need next, not what you need to sell
→
How do you offer it?
A real proposal and a decision date (day 5)
Same structure as any proposal (day 4)
→ referral request (day 28)
↑ captured (day 26) → renewed → referred (day 28) →
→
Who do you ask?
Happy clients, at the right moment
9-10 check-ins (day 25)
Right after a testimonial (day 26)
↑ your happiest clients know people like them
→
What exactly do you ask?
Make it easy to say yes
"Who else do you know who…" + your ICP (day 2)
A short intro message they can forward
↑ a vague ask gets a vague "sure!"
→
What happens when they refer?
Close the loop
Thank them, every time
The referral → lead intake (day 1)
↑ renewed (day 27) → referred → back to the start (day 1) →
→
When a client leaves, what's the checklist?
End it cleanly
Final deliverables + access handed back (day 20)
Final invoice settled
↑ a messy exit undoes a good project
→
What do they hear from you?
A warm, written goodbye
What you did together
How to reach you later
↑ how it ends is what they remember
→
What keeps the door open?
Stay in touch on purpose
A check-in date on your calendar (day 6)
→ one brain (day 30)
↑ every past client is a future referral (day 28)
→
Where does all of this live?
One place, not 29 tools
Your second brain: the files Claude reads
Clients · offers · systems · rules
↑ one source of truth per fact
→
Who runs each system besides you?
Every system has an owner
You: the calls only you can make
Your team or contractors
AI: the assembly
↑ the work stops routing through you
→
What runs without you now?
That's the whole point
Start with your top 3
Add one system a week
↑ lead intake (day 1) → … → offboarding (day 29) → one brain

by system 30 it's your whole client-getting-and-delivering operation on one page: your second brain, laid out.

want your top 3 out of your head this week?

The Systems Setup File, $27. you talk, Claude writes. in one sitting you set up your second brain, score your systems, and get the 3 that cost you the most written down, so they stop running through you.

get the Systems Setup File →

Puja Patel · puja-patel.com