05_Senior_Consultant_Review

SENIOR CONSULTANT REVIEW: InstantNonprofit Discovery Call

Critical Assessment of Solanasis’s First Client Engagement

Reviewer: Independent Senior Consulting Partner (25+ years IT/fractional CxO advisory) Client: InstantNonprofit (Christian LeFer, CEO) Date of Review: March 16, 2026 Engagement Status: Pre-proposal, discovery call completed Risk Level: MODERATE-TO-HIGH without structural corrections

---

EXECUTIVE SUMMARY

Dmitri has positioned Solanasis’s first engagement perfectly on paper, but the discovery call reveals dangerous patterns that will kill this engagement if not corrected immediately. The good news: these are all fixable if he acts now. The bad news: they’re the exact mistakes I’ve watched destroy a hundred first-time consultancies.

RECOMMENDATION: GO — but with strict conditions. No exceptions.

This engagement can work, but it requires:

1. Hard boundaries on scope (NOW, before the proposal)
2. Payment structure that protects Solanasis (50% upfront, no exceptions)
3. A written SOW with explicit change order triggers
4. Weekly check-ins with both Christian and Jackie
5. Maximum 8-week commitment for Phase 1 (not open-ended)

Skip these and you’ll be doing $15Kofworkfor$5K in fees, wondering where your nights and weekends went.

---

1. FIRST ENGAGEMENT PITFALLS ANALYSIS

I’ve seen first-time consultancies fail on these ten mistakes. Dmitri is at risk on almost all of them.

1.1 — UNDERPRICING (RISK: HIGH)

The mistake: Charging below market rate to “prove value” and get the foot in the door.

Evidence from the call:

• Christian explicitly said: “I have contractors who work for $10-$20/hr” — this is the anchor point Dmitri is comparing against
• The pricing doc shows internal models ranging from $5K-$15K for Phase 1, but Dmitri’s instinct will be to “be competitive” with Christian’s existing spend
• Dmitri has positioned this as a “partnership play” where upside comes later, which signals to Christian that the initial fee is negotiable

The Reality: Christian is NOT comparing Dmitri to market rates. He’s comparing him to Catherine at $20/hr.Dmitriwillcuthisfeeto$7-8K to seem “affordable,” do 120 hours of work, and net $60/hour.Acontractorearning$20/hr will have made $2,400.Dmitrijustmade$7,200 total while committing 3x the time. That’s not smart — that’s self-harm.

What should happen:

• Lead with Model 2 pricing: $12K-$15K for the 2-3 week intensive (non-negotiable)
• If Christian flinches, bridge to Model 3 (success fee) or Model 4 (deferred + retainer lock-in)
• Do NOT discount below $8K for Phase 1, no matter what Christian says about his budget
• Get this in writing before the proposal conversation even starts

Pro Tip: The worst clients are the ones you discounted for. They’ll forever view you as a $60/hrvendor,nota$175/hr strategist. And when you try to charge full rate for Iconic Impact work later, the friction will be toxic.

---

1.2 — SCOPE CREEP (RISK: CRITICAL)

The mistake: The client asks for “a little help with X,” and by week 3 you’re rebuilding their entire operations.

Evidence from the call:

• Christian’s stated need: “basic initial engagement” to fix website/funnel issues
• What Dmitri wrote in the proposal planning doc: systems audit, security baseline, ClickUp optimization, automation buildout, data enrichment, upsell strategy design, new assistant infrastructure, agent system design
• The summary notes: “115-160 hours estimated for the first month”
• The pricing doc shows Phase 1 at “$5K-$8K” but that’s for a narrow scope; Phase 2 is “$8K-$15K” for the bigger stuff

This is the classic scope creep setup. Christian will agree to $7-8K for “systems audit + security baseline,” then in week 2 ask: “Can you also set up the assistant infrastructure?” Week 3: “Since you’re in ClickUp, can you optimize it for the CRM workflow?” Week 4: “While we’re doing this, can we start enriching the 5,000-client database?”

And Dmitri will say yes to all of it because:

• It’s a friend
• The work is interesting
• He wants to prove value
• The next phase depends on it being done first

Result: Dmitri delivers 140 hours of work at $8K,whichis$57/hour. He’s now resentful, Christian thinks he’s slow and expensive (“We could have done it cheaper with a contractor”), and the relationship turns sour.

What should happen: This is NON-NEGOTIABLE. The proposal must include:

1. Explicit Phase 1 Scope (and ONLY Phase 1):

   • Systems audit (10 hours max)
   • Security baseline (8 hours max)
   • ClickUp assessment (5 hours max)
   • Top 3 automation quick wins (15 hours max)
   • Assistant onboarding infrastructure (10 hours max)
   • Deliverables: audit report, security findings, ClickUp recommendations, 3 playbooks, onboarding checklist
   • TOTAL: ~48 hours, $8K-$10K project fee

2. Explicit What’s NOT Included:

   • Data enrichment project (Phase 2)
   • Upsell system design (Phase 2)
   • Website staging/testing (Phase 2)
   • Agent system architecture (Phase 3)
   • Iconic Impact advisory (separate engagement)

3. Change Order Trigger: Any request outside this scope requires a written change order, signed by both parties, with additional fees.

4. Timeline Cap: Phase 1 is 3-4 weeks max. If it’s running longer, the scope was larger than agreed.

Pro Tip: The way to handle scope creep with a friend is the same as with anyone else: friendly but firm. “Christian, that’s a great question — and it’s definitely important. But that’s actually Phase 2 work. Let’s finish Phase 1 first, then we’ll scope Phase 2 and price it separately. Otherwise we’ll never get Phase 1 delivered on time.” This builds CREDIBILITY, not resentment. Clients respect you more when you protect your own commitments.

---

1.3 — FRIEND-CLIENT BOUNDARY ISSUES (RISK: CRITICAL)

The mistake: Treating a friend like a friend instead of a client. No hard conversations, no payment pressure, no accountability.

Evidence from the call:

• Christian is “brother” language with Dmitri
• The call itself was chaotic — materials sent last-minute, Jackie wasn’t prepared, Christian didn’t send what was asked for beforehand
• Christian said: “I apologize. The reason I didn’t send you the materials earlier and only sent them a few minutes ago is because Jackie and I were on a screen share earlier and we both agreed that we would move the call tomorrow”
• This is a busy founder making excuses, and Dmitri was accommodating: “No problem, let’s just dive in”
• Dmitri’s internal documents talk about this as a “partnership” play, which softens the business dynamics

The real risk: When the first invoice goes out, will Dmitri ask for payment on time? Will he push back if Christian says “Can we pay half now and half in 60 days?” Will he implement a change order process if Christian asks for things outside scope?

Friends don’t do change orders with friends. Friends absorb the cost. Friends wait to get paid. Friends don’t make hard decisions.

What happened at the call that showed weak boundaries:

1. Dmitri accepted a half-prepared discovery call instead of rescheduling
2. He didn’t push back on the missing materials
3. He kept calling it “Christian” and “brother” language that matched Christian’s energy (fine for relationship, but shouldn’t affect business terms)
4. He didn’t ask directly about budget or payment terms during the call
5. He’s planning to offer “creative pricing models” as a gift, not as professional options

What should happen: NOW, before the proposal is sent:

1. Send a brief email that says (professionally, warmly):

   “Christian — great energy on the call today. Before I send the proposal, I want to make sure we’re aligned on how we’ll work together. For Solanasis’s first engagement, I’m putting strong structure in place around scope, timeline, and payment. Not because of you — because I’ve learned that clarity protects both of us. I’ll be recommending 50% upfront, 50% at delivery, and a tight SOW with change orders for anything outside scope. This is how I want to run all my engagements, starting with you. Cool with that approach?”

2. Implement these boundaries immediately:

   • Payment: 50% upon signing SOW, 50% upon delivery. No exceptions, no “friends” clauses.
   • Scope: Documented SOW with change order process (reference your template).
   • Meetings: Weekly 30-min check-in with both Christian and Jackie (not optional).
   • Deliverables: Specific outputs with due dates, not “ongoing advisory.”
   • Escalation: If Christian wants something outside scope, Dmitri says “Let’s document that as Phase 2” and moves on.

3. The magic words when boundaries are tested:

   “Christian, I love this idea. And it’s exactly why we need Phase 2. If I try to squeeze it into Phase 1, both of us lose — you get slower delivery and I miss my timeline. Let’s crush Phase 1 first, then we’ll scope Phase 2 and decide if you want to move forward. That keeps everything clean.”

Pro Tip: The best way to preserve a friendship is to be MORE professional, not less. Vague boundaries and blurry handshakes kill friendships. Crystal-clear contracts protect them. Christian will RESPECT Dmitri more if he says “Here’s how I work” than if he says “Whatever you need, brother — we’ll figure it out.”

---

1.4 — NOT GETTING PAID UPFRONT (RISK: HIGH)

The mistake: Starting work without securing the first payment, betting on goodwill.

Evidence from the call:

• Christian mentioned he’s “fundraising” and bootstrapped a “mature lifestyle business”
• He has contractors at $10-$20/hr, suggesting cash flow is tight
• He recently “took an $8Klossonafailedoperatorengagement"—actually$8,000 out of a $40,000 original commitment he bailed on — meaning he’s both cautious about spending AND has a history of abandoning paid engagements. This is a payment risk indicator.
• Dmitri’s pricing doc says: “Could stretch to $10K-$15K/month if he’s convinced it’s directly tied to revenue” — this is Dmitri trying to figure out how much Christian CAN afford, not what the work is worth
• The engagement agreement template shows “50% upfront” but there’s zero discussion in the discovery call about payment terms

The trap: Dmitri will send the proposal, Christian will say “Love it, let’s get started,” and will delay the first invoice for 2-3 weeks citing “payroll timing” or “waiting for investor funding.” By then, Dmitri has already started work, and he’s psychologically committed to finishing. He’s also spending 15-20 hours per week, which eats his ability to do other work.

What happens: Dmitri delivers Phase 1 in 6 weeks (instead of 3) because he’s working part-time, Christian loves the work, says “This is amazing, let’s do Phase 2,” but still hasn’t paid for Phase 1. Dmitri now owes $16K+ of free time.

What should happen:

1. In the proposal email, be explicit:

   “Payment structure: 50% ($5,000)dueuponsigningthisSOW.50$5,000) due upon delivery of Phase 1 deliverables. No work begins until the first payment clears.”

2. Accept payment immediately after signing:

   • Don’t wait for an invoice
   • Use Stripe, ACH, or wire
   • Don’t start the clock until you see the money in your account

3. If Christian pushes back (“Can we do 30/70?” or “Can you invoice after you start?“):

   • Respond professionally but firmly: “For a firm like mine, I always collect 50% upfront. It’s standard across the industry and it keeps both of us protected. Happy to invoice immediately after you sign, and I can start work once the payment clears.”
   • If he can’t do 50/50, offer Model 4 (deferred + retainer lock-in) instead: “If 50% upfront is tight, here’s an alternative: $3,000nowtokickoffPhase1,andwelockina6-monthretainerat$3,500/month to cover the rest. Spreads the cost but locks in the commitment.”
   • Do NOT start work on a handshake.

4. If payment is still delayed after he says yes:

   • Follow up within 2 business days: “Hey Christian, just confirming you got the SOW. What’s the best way to get the first payment over?”
   • If it’s delayed 5+ business days: “Christian, I want to make sure this is still the right fit. I can’t start Phase 1 work until the first payment comes through. Let me know if there’s a barrier on your end and we can figure it out together.”
   • Do not be passive-aggressive. Be direct.

Pro Tip: Getting paid upfront protects the relationship. If Christian can’t front 50%, he doesn’t believe in the value. And if he doesn’t believe in the value, the engagement will be miserable. Better to find out now.

---

1.5 — TRYING TO SOLVE EVERYTHING AT ONCE (RISK: HIGH)

The mistake: Wanting to prove you’re amazing by tackling all the client’s pain points in one engagement.

Evidence from the call:

• The summary lists 12 different problem areas (flat revenue, funnel fixes, upsell potential, missing CTO, fundraising goals, data enrichment, etc.)
• Dmitri’s internal docs show 115-160 hours of work just for Phase 1, spread across 10 different categories
• The pricing models show escalating phases (Phase 1, Phase 2, Phase 3, Iconic Impact) — this is good, but the temptation will be to “get ahead” and design everything in Phase 1
• Dmitri keeps using language like “full tech stack audit,” “complete security baseline,” “all automations” — each of these is its own project

The trap: Dmitri will spend his first month in a frenzy trying to audit everything, fix everything, build everything. Christian will be happy with the activity but confused about priorities. Jackie will see Dmitri working 60 hours/week and think “This consultant is expensive and stretched.” By week 4, Dmitri is burned out, and the deliverables are half-baked.

What should happen:

FOCUS. RUTHLESSLY.

Phase 1 should have ONE primary goal: Get Christian’s personal operations in order so the new assistant can succeed.

That’s it. Not “fix everything.” Not “architect the entire tech stack.” Just: “Christian is disorganized, he’s bringing in an assistant, and we need systems in place for that assistant to be effective.”

Scoped narrowly, this is:

• Email triage and follow-up automation (Christian’s biggest pain point)
• ClickUp setup for Christian’s personal workflow (not the whole company)
• Security baseline on the systems Christian and the assistant will use
• Onboarding infrastructure so the assistant has SOPs and access

That’s 4 things, 40-50 hours, done in 3-4 weeks.

EVERYTHING ELSE becomes Phase 2, Phase 3, or Iconic Impact.

Pro Tip: New consultants always want to do too much. Experienced consultants know that delivering one thing perfectly creates more trust and more revenue than delivering ten things poorly. Christian will hire you for Phase 2 because you nailed Phase 1 — he won’t hire you for Phase 2 because you overwhelmed him in Phase 1.

---

1.6 — OVERSELLING CAPABILITIES (RISK: MODERATE)

The mistake: Positioning yourself as more experienced/bigger than you are.

Evidence from the call:

• Dmitri is 1 person (Solanasis is brand new)
• He positioned this as a “fractional CIO” engagement, which implies ongoing operational ownership
• The pricing docs show commitments for “20-40 hrs/month” retainer, “attending team meetings,” “owning the tech roadmap” — this is language that suggests Dmitri is deeply embedded

The reality: Dmitri is one person juggling other clients. He can’t be at weekly team meetings AND do other work. He can’t “own the tech roadmap” for two companies. After Phase 1, he’ll either have to disappoint Christian on the retainer, or burn out trying to over-deliver.

What should happen:

• Be honest about your stage in the proposal: “This is Solanasis’s first formal client engagement. You’ll have my full attention on Phase 1, which is why I’m blocking 2-3 weeks. For Phase 2 and beyond, I’ll be leveraging contractors for execution while I focus on strategy and oversight.”
• This is BETTER, not worse. Christian wants a CIO who thinks, not a contractor who executes. Dmitri should lead with that.
• On the retainer side, be specific: “3-5 hours/week, async and scheduled meetings, not continuous presence.” Not “I’ll own the roadmap” but “I’ll advise on tech decisions and oversee execution.”

Pro Tip: Clients trust you MORE when you’re honest about constraints. “I’m 1 person and I’m careful about what I commit to” beats “I can do anything” every time.

---

1.7 — NOT HAVING CLEAR DELIVERABLES (RISK: HIGH)

The mistake: Vague promises like “we’ll improve your operations” instead of specific outputs.

Evidence from the call:

• The prep documents talk about “strategic advisory,” “operational improvements,” “KPI reporting” — these are nebulous
• The action items list says “Provide strategic advice on operational improvements” but doesn’t define what that means
• Dmitri’s framing is all inputs (“systems audit,” “security review”) not outputs (“here’s the audit report,” “here’s the risk register”)

The trap: In week 3, Christian will ask “So what do we have to show for this?” and Dmitri will realize he hasn’t produced anything concrete yet. Christian will feel like he’s paying for consulting talks, not consulting work. The relationship will sour.

What should happen: The proposal should list SPECIFIC deliverables:

Phase 1 Deliverables (due Week 3-4):

1. Systems Audit Report — 1-page overview of Christian’s tech stack, what’s working, what’s not
2. Security Findings Document — MFA status, password management, backup testing results, risk register
3. ClickUp Configuration Recommendations — Specific setup changes + 5-page playbook
4. 3 Automation Playbooks — Email triage setup, follow-up automation, weekly briefing agent (step-by-step)
5. Assistant Onboarding Checklist — Systems access, training videos, SOP templates

These are THINGS. Christian can show them to Jackie. They can be implemented. They have value that can be felt immediately.

Pro Tip: Always end a discovery call with explicit deliverables listed in the proposal. If the client asks “What will you deliver?” and you have to think about it, the scope isn’t tight enough.

---

1.8 — POOR DISCOVERY EXECUTION (RISK: MODERATE)

The mistake: Asking generic questions and not digging into the decision-maker’s real concerns.

Evidence from the call:

• The call started chaotic (materials not sent, Jackie not prepped, time crunch)
• Dmitri didn’t push back or reschedule — he accepted the suboptimal conditions
• The discovery call was 93 minutes but the notes don’t show deep questioning of Jackie’s perspective
• Dmitri asked ABOUT Jackie’s role but not her concerns, her priorities, or her constraints
• No explicit question about budget or payment terms

What happened: Dmitri gathered information but didn’t negotiate alignment. He’s now going to propose something that may not match what Jackie actually needs.

What should happen:

• Reschedule bad calls. If materials aren’t sent, if the client isn’t prepped, if a key stakeholder isn’t available — reschedule. A good discovery call is worth more than a rushed one.
• Ask about decision-making power. “Christian, you’re driving this engagement. Jackie, what’s your veto power? If you think something won’t work, will we pivot?” Get this on record.
• Ask the question people are afraid to ask. “So Christian, you’ve got $30Kcashandyo{u}^{\prime }refundraising.Wha{t}^{\prime }stherealisticbudgetforthisengagement?Arewetalking$3K, $5K,$10K? Let’s be honest about it so I can scope accordingly.”
• Dig into the second-order effects. “If we do this engagement and it’s successful, what does success look like 90 days from now? What’s the earliest you’d feel it’s worked?” This prevents misaligned expectations.

Pro Tip: A good discovery call ends with both parties knowing exactly what success looks like and what it costs. If you’re not 100% sure the client can afford what you’re about to propose, you haven’t discovered enough.

---

1.9 — NO ESCALATION PLAN FOR PROBLEMS (RISK: MODERATE)

The mistake: Assuming the engagement will go smoothly, with no plan for what happens if it doesn’t.

Evidence from the call:

• The action items say “Upon successful initial engagement, prepare proposals for extended services” — this assumes success
• There’s no discussion of what happens if Phase 1 reveals major problems (e.g., a security breach, a data migration nightmare, a compliance gap)
• There’s no walk-away clause if the scope spirals

What should happen: The proposal should include:

Success Criteria (for Phase 1):

• All deliverables completed and approved by Christian and Jackie
• Christian confirms the onboarding infrastructure is usable by the new assistant
• No critical security issues discovered requiring incident response

If Issues Arise:

• Security breach discovered: We’ll notify you and pause assessment. You’ll engage incident response (separate engagement).
• Scope larger than estimated: We’ll discuss a change order by Day 3 of Phase 1.
• Timeline slips (on our end): We’ll propose a compressed Phase 1 or partial delivery.
• Timeline slips (on your end): Engagement pauses, you pay for work completed, we resume when you’re ready.

This protects BOTH parties.

---

1.10 — MISALIGNED EXPECTATIONS ON “PARTNERSHIP” (RISK: CRITICAL)

The mistake: Using partnership language to lower price, then failing to deliver partnership-level commitment.

Evidence from the call:

• Dmitri’s prep docs say: “Lead with operational optimization, weave in security” and “exploring partnership WITH them”
• The pricing models show “success fee” and “equity” options positioned as the “real partnership” models
• Christian has probably heard this and is thinking: “If this guy is so confident, why is he charging me $8K upfront?”
• Jackie heard: “We’re a partner, not a vendor” and is probably thinking: “Then why are there change orders and scope limits?”

The trap: Dmitri is signaling that he wants a partnership, which makes Christian expect partnership pricing (i.e., a deal). Christian will counter: “But if you’re a real partner, shouldn’t you take some risk?” Dmitri will feel guilted into success fees or equity, which he’s not ready for.

What should happen: Be CLEAR about the relationship structure:

“Christian, I want to be clear about how we’ll work together. Phase 1 is service-for-fee: you pay, I deliver. This is how I build trust and prove I can execute. If Phase 1 goes well, Phase 2 is also service-for-fee, but now we’re deeper into the business. Down the road — if we’re talking about Iconic Impact and I’m part of that platform from the ground up — THEN we have a real partnership conversation with equity or revenue share. But I don’t lead with equity. I earn it. Cool?”

This does THREE things:

1. Sets clear expectations
2. Removes guilt-based pricing
3. Positions equity as a REAL upgrade, not a consolation prize

Pro Tip: The best partnerships start with one flawlessly executed service engagement. Period. Everything else is premature.

---

SUMMARY: FIRST ENGAGEMENT PITFALLS

Pitfall	Risk	Dmitri’s Status	Action Required
Underpricing	HIGH	At risk	Commit to $8K-$10K minimum for Phase 1; no discounting below that
Scope creep	CRITICAL	At risk	Document Phase 1 scope tightly; implement change order process now
Friend-client boundaries	CRITICAL	At risk	Send boundary-setting email before proposal; implement weekly check-ins
Payment upfront	HIGH	At risk	Get 50% ($5K) before you touch a single file; have alternative payment models ready
Everything at once	HIGH	At risk	Narrow Phase 1 to Christian’s personal systems + assistant onboarding only
Overselling capabilities	MODERATE	At risk	Be honest about your 1-person stage; position as strength, not weakness
No clear deliverables	HIGH	At risk	List specific outputs (reports, playbooks, checklists) in proposal
Discovery execution	MODERATE	At risk	Always reschedule if conditions are suboptimal
No escalation plan	MODERATE	At risk	Add “If X happens, here’s how we handle it” section to SOW
Partnership misalignment	CRITICAL	At risk	Define “service-for-fee now, partnership opportunity later” clearly before proposal

---

2. THE FRIEND-CLIENT DYNAMIC

This is the single biggest risk in the engagement. Get this wrong and you lose both the client AND the friend.

2.1 — Why Friends Make Bad First Clients

There’s a reason every consultant book says “Don’t take your friends as your first clients.” Here’s why:

1. You have no leverage in hard conversations. If you’re not friends, you can say “Sorry, that’s outside scope, that’s a change order.” With a friend, you feel obligated to say “No problem, I got this.”

2. Misaligned expectations hide until it’s too late. With a stranger, you write it down. With a friend, you assume you’re aligned because you know each other.

3. Payment pressure is awkward. With a stranger, you invoice and they pay or they don’t. With a friend, the first time payment is late, you feel guilty asking about it. By month 2, you’re doing free work.

4. Success and failure hit differently. If you under-deliver to a stranger, you lose the client. If you under-deliver to a friend, you lose the client AND the friend.

2.2 — Warning Signs Already Present in This Call

Signal 1: Disorganized startup Christian didn’t send materials on time. He and Jackie weren’t aligned on whether the call was even happening. He was late to his own discovery call.

What this means: Christian is chaos-mode. Founders in chaos-mode don’t make good clients because they don’t execute on your recommendations. They’re too busy fighting fires. Dmitri will deliver a beautiful systems audit, and Christian will say “Yeah, this is great, I’ll implement it next month” — and next month never comes. Dmitri will feel unappreciated.

Signal 2: Jackie’s body language The summary doesn’t explicitly note Jackie’s reactions, but the fact that she asked for “references/examples” is telling. She’s the operator. She knows the difference between a consultant who can actually execute and one who just talks big. She’s skeptical. This is GOOD — she’s the voice of reason. But it also means Dmitri needs to prove himself to HER, not just Christian.

Signal 3: The “friend language” Dmitri used “brother” language. Christian responded in kind. This is warm, but it’s also a warning sign: if the relationship is already “brother” level, Dmitri is going to have trouble switching to “business partner” mode when needed.

Signal 4: The budget dance Christian said he’s “profitable but not highly” and has $30Kincash.H{e}^{\prime }sclearlyspendingcarefully.Hewascautiousaboutthe$8K loss on a failed operator engagement that was originally a $40K commitment. This signals: Christian is friendly but financially conservative. He’ll expect value, and he won’t overpay out of friendship.

Signal 4B: CRITICAL FINANCIAL RED FLAG — Bankruptcy History Christian disclosed a severe bankruptcy history that fundamentally changes the payment risk profile. He revealed: “We went through chapter 11 and 20 and I personally went through a chapter 7 and 22.” This indicates:

• Company underwent Chapter 11 reorganization (around 2020)
• Christian personally underwent Chapter 7 liquidation (around 2022)
• This is a HIGH payment risk indicator. Bankruptcy history precludes access to SBA loans and indicates severe financial distress
• Combined with “$30Kincash"and"only$8K available from a failed $40K engagement,” this paints a picture of persistent tight cash flow
• Christian’s personal creditworthiness is compromised, which affects his ability to access traditional financing or personal guarantees
• As a senior consultant, you need to flag this: If Phase 1 payment terms slip, you have limited recourse. Get 50% upfront. This is not negotiable.

Also, on revenue: Christian claimed “What we have built is like a $10millioncompany,butw{e}^{\prime }renotdoingtwo"(meaning$2M). This is aspirational framing. Actual revenue is significantly UNDER $2M. Adjust any revenue-based pricing models accordingly.

Signal 5: No explicit conversation about payment During a 93-minute call, if payment terms weren’t discussed, Dmitri isn’t treating this like a real engagement. With a friend, you avoid that conversation. With a real client, it’s in the first 30 minutes.

2.3 — How to Set Boundaries Without Damaging the Friendship

This is doable. Here’s the playbook:

Step 1: Reframe boundaries as mutual protection (not burden)

Send an email BEFORE the proposal:

“Christian — loved the call yesterday. Before I send the proposal, wanted to make sure we’re on the same page about how to work together. I’ve done this a few times now, and I’ve learned that the cleanest engagements are the ones where we have crystal-clear scope, timeline, and payment terms. Not because of you specifically — because that clarity actually PROTECTS the friendship. When things go sideways, it’s usually because expectations were blurry, not because someone dropped the ball.

So here’s what I’m proposing: We’ll define Phase 1 scope tight (4-5 specific deliverables, not open-ended), we’ll set a 4-week timeline, and we’ll do 50% upfront / 50% on delivery. And we’ll do weekly 30-min check-ins (me, you, Jackie) so there’s no surprises.

This is how I want to work with all my clients, and I’m starting with you because I want to set the tone right. Cool with that?”

This email does several things:

• It normalizes boundaries (not a Christian thing, a Dmitri-thing)
• It positions them as FOR the friendship, not against it
• It gives Christian a chance to object before there’s a proposal to argue about

Step 2: Implement boundaries gently but firmly

When Christian pushes back (and he will), use the “Yes, and” technique:

Christian: “But won’t the scope be bigger once we get started?”

Dmitri: “Totally, that’s actually why we’re phasing it. Phase 1 is foundations — we lock that down tight. Then in week 3, we’ll look at what’s working and what else came up, and we’ll scope Phase 2 separately. If we try to do everything at once, we both lose.”

This is not “no.” It’s “yes, and here’s how we handle it professionally.”

Step 3: Weekly check-ins with BOTH founders

Insist on this, and stick to it. 30 minutes every Thursday, all three of you.

Why? Because:

• It keeps expectations aligned in real-time
• It prevents scope creep (Christian asks for something, Dmitri says “Let’s add that to Phase 2” right there)
• It gives Jackie a voice (she’ll call out unrealistic requests that Christian won’t)
• It’s a forcing function for Christian to actually THINK about what he needs, instead of just asking

Step 4: Document everything in writing

After each check-in, send a 1-minute recap:

“Weekly sync summary (3/20):

• Scope: Still on track for Phase 1 (audit + security + automations)
• Timeline: On pace for delivery by 4/6
• Blockers: Waiting for ClickUp access (Christian to send by tomorrow)
• Next phase prep: We’ll discuss Phase 2 scope next week

Next sync: Thursday 3/27, same time.”

This is magic. It creates a paper trail. Christian can’t later say “I thought you were doing X” when the email clearly said “X is Phase 2.”

Step 5: Use the “partnership escalation” as a reward for execution

Here’s the deeper play: Don’t position equity/revenue share as a negotiation tactic. Position it as an UPGRADE after Phase 1 is crushed.

Week 4, when Phase 1 is done and Christian is thrilled:

“Christian, this went really well. You got your systems in place, the assistant is productive, and we’ve got a clear roadmap forward. I want to talk about how we scale this. Phase 2 is still service-for-fee. But if we get to Iconic Impact, and you want me as a true tech co-founder building that platform with you — not just a consultant — then we have a different conversation. We’d structure equity or revenue share. But I want to earn that seat first. You with me?”

This works because:

• He’s seen you deliver
• He trusts you now (not at the beginning)
• He WANTS to keep working with you
• The equity conversation feels like a promotion, not a negotiation

2.3B — Understanding Christian: His Strengths and His Red Flags

What you need to know about Christian as a founder:

Christian is a natural salesman and visionary. He himself acknowledged: “My expertise in fact, is selling vaporware and then building it.” This is BOTH his superpower and his vulnerability:

Superpower: He can sell a vision that doesn’t exist yet. He can convince investors, partners, and employees to buy into a future state. He built a “mature lifestyle business” from zero. This is real talent.

Red Flag: If you’re not careful, you’ll be on the receiving end of this skill. He can convince you that your Phase 1 scope is “just a little bigger” or that payment delays are “temporary.” He can overpromise what he’ll implement and under-deliver on execution. He does this naturally and probably doesn’t see it as manipulation — it’s just how he operates.

How to navigate this:

• Admire the skill without being seduced by it
• When Christian says “This is going to be amazing,” respond with “Yes, and here’s how we scope it in phases to make sure it actually happens”
• Document everything in writing AFTER the verbal conversation
• Watch what he actually commits to doing (vs. what he says sounds good)
• Don’t let his enthusiasm become your timeline

This is where Jackie’s skepticism is your partner. She’ll slow down the “vaporware” instinct. Let her.

2.4 — The Jackie Factor

Jackie is the key to this entire engagement. Here’s why:

Who she is: Operator, skeptical, knows the business better than Christian, will call BS if something’s not working.

What she thinks: “Is this consultant going to actually help us, or is he just going to bill hours while we struggle?”

What she needs from Dmitri: Proof that he can prioritize ruthlessly. That he won’t overwhelm the team. That he understands operations (not just tech).

What Dmitri should do:

In the proposal, address Jackie directly:

“Jackie — I know you’re the one executing on these systems. I’m going to deliver things that YOU can use, not things that are theoretically cool. You’ll have playbooks, not theories. And I’m going to keep Phase 1 scoped tight so it’s not a 3-month project. You tell me if something isn’t working, and we pivot.”

Then, in every weekly check-in:

• Ask Jackie first: “How are you feeling about the work this week? What’s working, what’s not?”
• She gets to veto scope creep: “Christian, Jackie’s right, that should be Phase 2.”
• She gets to flag if Dmitri is overcomplicating things: “Dmitri, this is too complex for the team.”

Why this matters: Jackie will be the difference between this engagement succeeding and failing. She’s the one who’ll use the systems. If she’s aligned, Christian will follow. If she’s skeptical, Christian will lose faith.

---

3. SCOPE REALITY CHECK

Let me map what Christian ACTUALLY asked for vs. what Dmitri is planning to deliver.

3.1 — The Gap

What Christian explicitly asked for:

1. Funnel/website fixes (urgent)
2. Automated error detection and testing
3. Security review
4. Operational improvements/best practices
5. KPI reporting

What Dmitri is planning to deliver (from the prep docs):

1. Systems audit (15-20 hours)
2. Security baseline (10-15 hours)
3. ClickUp optimization (10-15 hours)
4. Personal automation for Christian (15-20 hours)
5. Assistant onboarding infrastructure (10-15 hours)
6. Data enrichment project kickoff (15-20 hours)
7. Agent system design (15-20 hours)
8. Website staging + testing (8-12 hours)
9. Client intake questionnaire (8-12 hours)
10. Strategic advisory (8-12 hours)
11. TOTAL: 115-160 hours

This is the classic mismatch. Christian asked for A, B, C. Dmitri is planning to deliver A, B, C, D, E, F, G, H, I, J.

3.2 — Where the misalignment came from

Looking at the call summary, Christian mentioned all ten of these needs at various points. And they’re ALL legitimate. The problem is Dmitri is treating them as a single Phase 1 engagement instead of a 3-6 month roadmap.

Reality: With 115-160 hours of work, you can’t deliver this for $8K.Youneed3-4monthsminimum.AndifDmitricharges$8K and works 140 hours, he’s at $57/hour. That’s not consulting. That’s contracting at contractor rates.

3.3 — The ORB-Washing Risk

Here’s what I’m seeing: Dmitri has a beautiful ORB (Operational Resilience Baseline) framework that costs $5K-$7.5K for a 10-day engagement. It’s a proven product. Clean scope. Deliverables. Done.

But InstantNonprofit doesn’t need an ORB. They need operational optimization. So Dmitri is trying to stretch the ORB to fit, adding a bunch of extra stuff (automations, data enrichment, agent systems) to make it feel like a holistic engagement.

This is ORB-washing. It’s what happens when you try to force-fit a product into a situation where it doesn’t belong.

The real problem: InstantNonprofit needs a fractional CIO engagement (monthly retainer), not a single 10-day assessment. They need someone who’s going to be there for 6-12 months, gradually optimizing systems, building infrastructure, and training the team.

3.4 — What the engagement should actually be

Phase 1 (3-4 weeks, $8K-$10K):

• Systems audit of Christian’s personal stack (email, ClickUp, calendar, passwords)
• Security baseline (MFA, password manager, backup testing)
• Top 3 automation quick wins (email triage, follow-up, daily briefing)
• Assistant onboarding infrastructure (systems access, SOPs, training plan)

Deliverables:

• 1-page audit report
• Security findings document
• 3 playbooks (step-by-step automation setups)
• Assistant onboarding checklist

Phase 2 (4-6 weeks, $8K-$15K):

• Website staging environment + automated testing
• Client questionnaire/intake process design
• ClickUp restructuring for operations (not just Christian’s workflow)
• Data enrichment strategy for the 5,000-client database
• Upsell system design

Phase 3 (Ongoing, $3K-$5K/month retainer):

• Fractional CIO/CTO role
• Monthly systems oversight and optimization
• Agent system design and buildout
• Iconic Impact platform advisory

Total Year 1: $20K-$50K depending on how many phases they buy in the first year

This is honest, it’s scoped correctly, and it allows Dmitri to deliver at a good rate without burning out.

3.5 — How to pitch this correctly

In the proposal, be explicit:

“Christian, I got a clear picture of everything you need. And there’s a lot — probably 6-8 months of work to fully optimize your operations. So I’m recommending we break this into phases.

Phase 1 (next 3-4 weeks) focuses on YOUR personal systems and getting your new assistant set up. This is the foundation everything else sits on.

Phase 2 (following month) is about your team’s operations — ClickUp, processes, customer data.

Phase 3 (ongoing) is where I become your fractional CIO and we keep optimizing as the business grows.

This approach means: you get value fast (assistant is productive in 3 weeks), you see what works before committing to more, and I can actually deliver at a high level instead of trying to boil the ocean in 30 days.”

This repositions the phases not as “Dmitri cutting scope to seem affordable” but as “smart project management.”

---

4. FINANCIAL RISK ASSESSMENT

Can Christian actually pay? And what happens if he doesn’t?

4.1 — Red Flags From the Call

Signal 1: “Recent loss” on operator engagement The summary notes: “The company is cautious about spending due to past disappointments but is actively hiring an EA with project management skills to improve task follow-through. Current recruitment efforts for operational support have been challenging, with a recent $8,000 loss on a failed operator engagement.”

Translation: Christian hired someone for operations, it didn’t work, he lost $8K. He’s gun-shy about hiring, but he’s STILL hiring (he just brought in an EA). This means:

• He’s willing to spend on the right people
• But he’s been burned before
• He’s evaluating whether Dmitri is the “right person”

Signal 2: Contractor-heavy team at low rates “He has contractors at $10-$20/hr (Egypt, Catherine)” — this is a classic sign of a bootstrapped founder. He’s squeezing every dollar.

But here’s the twist: he JUST hired a “full stack marketer/PPC/CRO person” at market rates. So he’s not ALWAYS cheap. He spends when he believes in ROI.

Signal 3: Fundraising in progress He’s actively fundraising ($1-2M raise) but nothing is closed. This is precarious — it means:

• He might have great income projections
• But he doesn’t have the cash yet
• He’s betting on a fundraise to come through
• If the fundraise delays, his budget tightens

**Signal 4: The $30Kcashstatement\ast \ast Thecontextsays:"Theclienthasabout$30K cash and can spare maybe $7-8K.”

This is REAL money, not theoretical money. He has it. He can spend it. $7-8K is ~25% of his runway. He’s not going to waste it on a consultant who doesn’t deliver.

4.2 — Probability He’ll Pay

Upfront (50% of fee): HIGH (80%+) Christian is a professional. He will send the first payment. Worst case, it’s 2 weeks late, but it will come.

Final payment (50% of fee): HIGH (75%+) Once he sees the work is real, he’ll pay.

Retainer (if Phase 2 happens): MEDIUM (50%) This is where it gets risky. A retainer is an ongoing commitment. If the business tightens or the fundraise delays, the retainer is the first thing that gets cut.

4.3 — Payment Structure Recommendations

Given the above, here’s what Dmitri should do:

For Phase 1:

• 50% upfront ($5K),50$5K)
• Payment due on signing, work starts 24 hours after payment clears
• Net 15 (15 days) for final payment from delivery
• Late fees: 1.5%/month if overdue

For Phase 2 (if it happens):

• 50% upfront, 50% on delivery (same as Phase 1)
• Budget decision: Christian commits to Phase 2 budget at the end of Phase 1, before Dmitri starts work

For Phase 3 Retainer:

• Monthly in advance (due by the 1st of the month)
• No work in a month until payment is received
• 3-month minimum commitment (then month-to-month)
• Either party can end with 30 days’ notice

4.4 — What Happens If He Doesn’t Pay

Scenario 1: First payment is late (2+ weeks)

• Send a friendly reminder after 1 week: “Hey Christian, just checking — do you need any clarification on the SOW to move forward with payment? Want to make sure there’s no blockers.”
• If another week passes: “Christian, I can’t start Phase 1 work until the payment comes through. Let me know what’s happening on your end and we’ll figure it out.”
• If it’s 3 weeks late: Call him. Not angry, but direct. “Christian, something’s come up? I want to help, but I also have to manage my own cash flow. What’s the holdup?”

Scenario 2: Final payment is late (2+ weeks after delivery)

• First reminder: professional but firm. “Christian, I delivered Phase 1 on time. Can you confirm you got everything? The final payment is due by [date].”
• After 2 weeks: “Christian, the final invoice is now overdue. I need to get this resolved this week so I can move on. What’s the barrier?”
• After 4 weeks: “I’ve tried to be flexible, but I need payment by Friday. If it doesn’t come through, I’ll have to pause Phase 2 planning until this is settled. Let’s figure this out.”
• After 6 weeks: You have a problem. You may need to stop all work and consider small claims court or just eat the loss.

Scenario 3: He wants to stretch the retainer (e.g., “Can we do $2Kinsteadof$3K?“)

• After Phase 1 delivery: “Christian, I’m glad Phase 1 went well. For Phase 3, I’m recommending a $3,500/monthretainer.Iftha{t}^{\prime }stight,wehaveafewoptions:(1)gowith$3K/month but cap hours at 15/week, (2) do a 3-month commitment at $3,500thendropto$3K/month after, or (3) wait 30 days and revisit when you’ve got more cash. Which makes sense for you?”

This is professional and shows flexibility without devaluing the work.

4.5 — The Real Risk

The actual risk isn’t that Christian can’t pay. It’s that Dmitri will do free work while waiting for payment.

Christian will say: “Dmitri, we’re going to move forward. I’m going to send the first payment tomorrow. In the meantime, can you go ahead and start the audit? I want to get rolling.”

And Dmitri will say: “Sure, brother, let’s go.”

And Christian will not send the payment tomorrow. Or the next week. But Dmitri is now 30 hours in, and he feels too committed to ask Christian to pay before continuing.

DON’T DO THIS. Money first, work second. Every time. No exceptions, even for friends.

---

5. THE JACKIE FACTOR

Jackie is the COO/CMO hybrid. She’s the operator. She’s the person who has to implement what Dmitri recommends. What does her body language tell us?

5.1 — What We Know From the Summary

• She asked for “references/examples” — this is the operator’s version of due diligence
• She’s the one focusing on “strategy and operational materials for high-ticket offers” — she’s thinking bigger picture, not just “fix what’s broken”
• She’s worried about “differentiating marketing versus operational responsibilities” — she knows she’s wearing two hats and it’s unsustainable
• She wanted more time to prep for the discovery call — she’s conscientious

5.2 — What These Signals Mean

“References/examples” = skepticism Jackie doesn’t know Dmitri. She wants proof that he’s delivered before. She’s protecting Christian from another bad hire.

This is GOOD. This means Jackie will keep Dmitri honest. She won’t let him over-promise. She’ll call him out if the playbooks are too complex or the scope is unrealistic.

But it also means: Dmitri needs to mention a reference-ability moment in the proposal. “Christian, Jackie — once Phase 1 is done, I’ll put together a case study we can share. You’ll have before/after metrics and everything.”

Focusing on “strategy and operational materials” = she sees the bigger opportunity Jackie isn’t just asking for a band-aid fix. She’s thinking about systems that scale. This is good — it means she’ll support Dmitri if he pushes for quality Phase 1 work.

“Differentiating marketing vs. operations” = she’s drowning Jackie is one person doing two jobs. She’s the bottleneck. Whatever Dmitri does in Phase 1 needs to free up SOME of her time, or the engagement is a failure in her eyes.

This is crucial. The proposal should explicitly mention: “One goal of Phase 1 is to set up systems that take at least 5-10 hours/week off Jackie’s plate so she can focus on strategy instead of execution.”

Wanted more prep time = she takes this seriously A lot of people would have just shown up unprepared. Jackie wanted to be ready. This signals professionalism. Dmitri should respect that by delivering professional work in return.

5.3 — The Christian-Jackie Dynamic Tension

From the notes: “There is a clear need to build out the high-ticket offer with AI-enabled systems and evergreen solutions but this is a longer-term project that requires strategic planning and operational support. Jackie emphasized that building the backend AI infrastructure and smart customer experience layers should not consume the founders’ time.”

Translation:

• Christian wants to build everything (AI agents, fancy systems, etc.)
• Jackie wants to build it in a way that doesn’t require her to execute everything
• They’re aligned but with different priorities

Critical signals about Jackie’s actual stance:

Jackie’s body language during the call revealed hesitation that didn’t make it fully into the notes. She said explicitly: “This conversation to me is a little premature based off the fact that we don’t have the funding for that yet.” She’s signaling that she feels the engagement is being pushed without proper financial foundation. This is a major red flag that Jackie is skeptical, not just cautious. She needs proof the money is real before committing to implementation.

By the end of the call, Jackie essentially withdrew from decision-making: “Christian, you own this project. You just, you let me know whatever you want to do.” This is operator-speak for “I’ve raised my concerns, but if you’re moving forward, it’s on you to make it work.” She’s protecting herself by not being seen as endorsing a decision she has reservations about.

What this means for Dmitri:

• Jackie is NOT a cheerleader for this engagement. She’s skeptical about timing and funding.
• Christian is pushing forward despite Jackie’s concerns.
• If things go wrong, Jackie has already distanced herself (“not my decision”).
• Dmitri MUST get Jackie’s explicit buy-in during check-ins or she’ll become a silent saboteur (not maliciously, just by not prioritizing implementation).
• The “premature funding” concern suggests Jackie knows something about the cash flow that isn’t being said outright.

Why this matters for Dmitri:

• Christian will push to expand the scope (“While you’re doing this, can we also…?“)
• Jackie will push back (“No, we need to focus”)
• Dmitri should explicitly support Jackie in check-ins: “Jackie’s right, Phase 1 is about foundations. The fancy stuff is Phase 2.”

5.4 — How to Handle the Jackie Factor

In the proposal: Address her directly and specifically. Not “hi team,” but “Jackie — here’s what Phase 1 means for you.”

“Jackie, I know you’re carrying operations and marketing. Phase 1 is going to take some of that load off by building infrastructure that scales. You’ll get playbooks for automations so Catherine can own them. You’ll get a ClickUp setup that actually works for your team. And you’ll get a training plan so the new assistant doesn’t add to your burden. The goal is to make your job smaller, not bigger.”

In every check-in: Ask Jackie first. “Jackie, how’s this landing? Is this helping or hurting?” If she says “this is too much,” simplify. She’s your canary.

When scope creep happens: Reference Jackie’s priorities. “Christian, that’s a great idea. But Jackie’s right that we need to stay focused on Phase 1. Let’s add that to Phase 2 and come back to it next month.”

Post-Phase 1: Get a testimonial from Jackie specifically. Not just Christian saying “this was great” (of course he says that), but Jackie saying “This freed up my time” or “This actually works.” That’s credibility.

---

6. GO / NO-GO RECOMMENDATION

VERDICT: GO — With Strict Conditions

This engagement can succeed. But only if Dmitri implements every structural recommendation in this review. No shortcuts.

6.1 — Why GO

1. Revenue opportunity is real. 5,000-client database is $150K+ in dormant revenue. Systems that unlock that are worth real money.

2. Founder is serious. Christian has money, he’s willing to spend it, and he’s actively trying to solve the problem. He’s not a tire-kicker.

3. Case study potential is massive. If this works, Dmitri has a story to tell: “Helped a nonprofit consultancy unlock $150K from dormant clients through systems optimization.” That’s a differentiator.

4. Retainer lock-in. If Phase 1 goes well, Phase 2 and Phase 3 are very likely. This could be $20-30K of recurring revenue in year 1.

5. Network value. Christian is connected to David Meltzer, Marcus Lemonis, other high-net-worth people. One good referral is worth more than this engagement.

6.2 — Conditions (Non-Negotiable)

BEFORE the proposal goes out:

1. Send the boundary-setting email (Section 2.3, Step 1)
2. Define Phase 1 scope tightly (systems + security + 3 automations + assistant onboarding only)
3. Get explicit agreement on payment terms: 50% upfront, 50% on delivery, no exceptions
4. Clarify that weekly check-ins with both Christian and Jackie are required
5. Prepare change order template (reference existing template or create one)
6. Commit internally to maximum 8 weeks for Phase 1, not open-ended

IN the proposal:

1. List specific deliverables (not vague “advisory”)
2. Address Jackie directly by name
3. Explain the phased approach (Phase 1, 2, 3) clearly
4. Define what IS and ISN’T included in Phase 1
5. Include change order process and cost
6. Set timeline expectations (3-4 weeks for Phase 1)

BEFORE work starts:

1. Get 50% payment ($5K) in your account
2. Have signed SOW with both Christian and Jackie
3. Get access credentials securely (password manager, not email)
4. Schedule first weekly check-in (all three people)
5. Block out your calendar (don’t overcommit on other clients)

DURING Phase 1:

1. Weekly check-ins (30 min, all three people, same time every week)
2. Send recap emails after each check-in
3. Deliver outputs on schedule (don’t push Phase 1 past 4 weeks)
4. Escalate scope creep to change orders immediately
5. Get final payment 100% before declaring Phase 1 complete

6.3 — Maximum Investment Before Getting Paid

Dmitri should NOT invest more than X hours before getting the first 50% payment.

Given the scope, here’s the limit:

• Discovery: 2 hours (already done)
• Proposal: 3 hours
• Kickoff call + intake: 2 hours
• Total before first payment: 7 hours

That’s it. Once the first 50% comes in, Dmitri can start the heavy work (systems audit, security review, etc.).

If payment is delayed more than 2 weeks after the proposal, Dmitri should pause and reach out: “Christian, I want to move forward, but I need the first payment to come through before I start Phase 1. What’s the timeline on your end?”

This is not unfriendly. This is professional.

6.4 — Walk-Away Points

If ANY of the following happen, Dmitri should consider ending the engagement:

1. First payment delayed more than 3 weeks after SOW signature — something is wrong
2. Christian refuses to sign a written SOW — he’s not serious
3. Jackie gives explicit feedback that the scope is too much — trust her
4. Christian demands Phase 2 and Phase 3 be done in parallel with Phase 1 — scope is spiraling
5. More than 2 weeks elapse with no access to systems Christian promised — blockers are real, probably not Dmitri’s fault, but he should pause
6. Christian is consistently not showing up to weekly check-ins — he’s not committed

If any of these happen, Dmitri’s response:

“Christian, I want to deliver great work here, but I’m seeing [X]. Before we continue, let’s sync on whether this is still a fit. Here’s what I’m seeing from my end… What are you seeing?”

Then listen. If Christian can’t fix it, walk. Better to end it now than to be three months in with 100 hours of work and no payment.

---

7. WHAT A SEASONED CONSULTANT WOULD DO DIFFERENTLY

Let me walk you through the discovery call as I would have run it.

7.1 — Before the Call

What Dmitri did:

• Accepted a call with materials sent 5 minutes before
• Didn’t push back on the disorganized setup
• Didn’t require pre-call homework from Christian/Jackie

What I would have done:

• Received the message that materials were sent late
• Responded: “Hey Christian — appreciate the heads up. Jackie requested more prep time. Let’s reschedule for [date] so we can make sure Jackie has 24 hours to review. Better call that way.”
• Why? Because a bad discovery call is worse than no discovery call. If the client isn’t prepared, you get answers that are off-the-cuff instead of thoughtful. And you set a bad precedent that it’s okay to be disorganized.

7.2 — The First 10 Minutes

What Dmitri did:

• Started the call, acknowledged the chaos, moved on
• Said “no problem, brother” and adapted to the situation

What I would have done:

• Acknowledged the situation warmly
• Set a hard reset: “Okay, here’s what we’ll do. First 10 minutes, Jackie reads through the materials we sent. Christian, while she’s doing that, let me ask you a few clarifying questions so we don’t waste her time once she’s up to speed.”
• This shows leadership and respect for Jackie’s time

7.3 — The Middle 60 Minutes

What Dmitri did:

• Asked about the tech stack, business challenges, personal situation
• Let Christian drive the conversation
• Took lots of notes
• Didn’t push on budget or payment terms

What I would have done:

• Structured the call in phases:
  • Minutes 0-15: “So here’s what I know, here’s what I want to learn” (framing)
  • Minutes 15-35: Jackie’s perspective (dedicated time for her, not Christian interrupting)
  • Minutes 35-55: Systems and tech deep dive (with Jackie present, not after)
  • Minutes 55-75: Budget and decision-making clarity (hard questions)
  • Minutes 75-90: Proposal preview and next steps

Specific questions I would have asked:

1. To Jackie (alone, preferably): “Walk me through your typical week. What eats up the most time?”

2. To Christian: “If I had to pick the ONE thing that would make the biggest difference in the next 90 days, what would it be?” (Not all ten things. The ONE thing.)

3. To both: “Thinking about Iconic Impact separately — is that Christian’s project, or are you both going to build that together? I’m asking because it affects how I scope this engagement.”

4. To Christian: “You mentioned $30K cash on hand. What’s realistic to invest in an engagement like this without making you nervous? Let’s be honest about it.”

5. To Jackie: “You’ve got a new assistant coming on board. What do they NEED to have set up by day 1 to be successful?”

6. To both: “What does ‘success’ look like 60 days from now? If I deliver Phase 1 perfectly, what will have changed about how you’re operating?“

7.4 — The Budget Question I Didn’t See

Dmitri never asked: “What’s your realistic budget for Phase 1?”

Why this matters: Christian could say “I have $15Ktoinvest"andtheconversationwouldbetotallydifferent.Orhecouldsay"$3-5K max and that’s a stretch.” Either way, Dmitri would know how to position the proposal.

Instead, Dmitri is guessing based on “he has $30Kcash"and"helost$8K on the last hire.”

What I would have done: Near the end of the call: “Here’s what I’m thinking for Phase 1 scope. This is going to be roughly 50 hours of work. At standard consulting rates, that’s $8,500-$12,000. Does that ballpark feel realistic for you guys, or is that higher than you’re thinking?”

Then shut up and listen. If they say “$5Kmax,"Ipivottoareducedscopeordeferredmodel.Iftheysay"$15K is doable,” I propose the full scope.

7.5 — The Jackie Moment I Missed

The call notes say: “She asking for references/examples.”

What that means: Jackie is testing whether Dmitri has credentials. She’s not convinced yet.

What Dmitri should have done: In response to the reference question, say: “Great question. I’m actually building Solanasis, so this is our first formal client engagement. Here’s what that means for you: you’ll have my full attention, not a junior associate. You’ll be part of building my playbook, which actually means I’m highly motivated to make this perfect. And once we’re done, you’ll have a case study and testimonial. Fair tradeoff?”

Then I’d ask Jackie: “What would make you confident that I can deliver? Is it a reference? Is it a reduced scope first? Is it a success-fee model? Let’s figure out what feels right for you.”

This turns her skepticism into a partnership moment.

7.6 — Coaching Points

Where Dmitri showed inexperience:

1. Accepted disorganization instead of setting standards. A seasoned consultant reschedules. It’s not mean, it’s professional.

2. Didn’t structure the call. The call was organic and friendly, which is good for relationship, but bad for information. Discovery calls need guardrails.

3. Didn’t ask the hard budget question. Dmitri is now guessing at pricing, which means he’ll either underprice or overprice the proposal.

4. Didn’t separate Christian and Jackie for a moment. Jackie probably has a different perspective than Christian, and Dmitri didn’t hear it directly.

5. Let the call be driven by Christian’s energy instead of Dmitri’s agenda. A good discovery call has a structure. This one just happened.

6. Didn’t close with crystal clarity on next steps. The call should have ended with: “Here’s what I’m delivering: a proposal by [date] with pricing for Phase 1. You’ll have 48 hours to review it. We’ll sync on [date] to discuss. And before we move forward, we’ll have a conversation about payment terms and the SOW. Sound good?“

---

8. ENGAGEMENT STRUCTURE RECOMMENDATION

Here’s exactly how Dmitri should structure this engagement to protect Solanasis.

8.1 — The Proposal Format

The proposal should have these sections:

Section 1: Executive Summary

“Christian and Jackie — based on our call, here’s what I heard as the core challenge and opportunity. [1 paragraph]. Here’s how I’m recommending we address it. [1 paragraph].”

Section 2: Phase 1 Scope (Exact)

• What’s included (list specific deliverables)
• What’s not included (reference Phase 2)
• Timeline (e.g., “3-4 weeks, starting upon payment”)
• Hours (e.g., “~50 hours of work”)

Section 3: Phase 1 Deliverables

Deliverable	Format	Timeline	Owner
Systems Audit Report	2-page PDF	Week 2	Dmitri
Security Findings	3-page document	Week 2	Dmitri
Automation Playbooks (3)	PDF guides	Week 3	Dmitri
ClickUp Recommendations	5-page guide	Week 3	Dmitri
Assistant Onboarding Checklist	Spreadsheet + docs	Week 4	Dmitri + Christian

Section 4: Pricing

Deliverable	Amount
Phase 1 (3-4 week intensive)	$10,000
Payment terms	50% upon signing ($5,000)/50$5,000)

Section 5: Timeline & Engagement Cadence

• Week 1: Kickoff, access setup, systems inventory
• Week 2: Audit + security assessment, mid-check-in with team
• Week 3: Automation playbooks + ClickUp recommendations
• Week 4: Final deliverables + readout with Christian and Jackie
• Weekly check-ins: Every Thursday, 30 minutes, all three of us

Section 6: What’s Not Included (and What Phase 2 Covers)

• Data enrichment (Phase 2)
• Website staging (Phase 2)
• Agent system design (Phase 3)
• Iconic Impact advisory (separate engagement)

Section 7: Change Order Process

“If scope changes during Phase 1, we’ll document it as a change order. Change orders require mutual written agreement and will be priced separately (e.g., ‘Additional automation’ = $1,500). This keeps Phase 1 on track while allowing for flexibility.”

Section 8: Next Steps

• Christian and Jackie review proposal (48 hours)
• Sync call on [date] to discuss
• If approved, we’ll execute the SOW (provided separately)
• First payment due before Phase 1 begins

8.2 — The Statement of Work (SOW)

This is separate from the proposal. Once they agree to the proposal, they sign the SOW.

The SOW should include:

• Parties: Solanasis LLC, InstantNonprofit
• Services: Phase 1 (as described in the proposal)
• Fee: $10,000 (50/50 payment split)
• Effective date: Upon execution
• Timeline: 3-4 weeks from kickoff
• Scope: [Reference the exact deliverables from Section 4 above]
• Change order process: [Reference Section 7 above]
• Confidentiality: [Your standard NDA or mutual NDA]
• Termination: Either party can terminate with 5 business days’ written notice. If terminated, Christian pays for work completed pro-rata.

8.3 — Change Order Triggers

Define when a change order is needed. Examples:

Request	Change Order?	Example Fee
”Can you also set up Slack automation?”	YES	+$1,500
”Can you review our backup strategy in detail?”	YES	+$1,200
”Can you build the agent system while you’re at it?”	YES	+$5,000 (that’s Phase 3)
“Can you help me understand the ClickUp audit better?”	NO	(included in Phase 1)
“Can you adjust the onboarding checklist based on feedback?”	NO	(included in Phase 1)

The rule: If it’s new work that wasn’t in the original scope, it’s a change order. If it’s clarification/feedback on work we’re already doing, it’s included.

8.4 — Walk-Away Points (Built Into SOW)

If any of these happen, Dmitri can pause or terminate:

1. Payment milestone is more than 2 weeks late → Dmitri may pause work until payment clears
2. Christian/Jackie miss 2 consecutive weekly check-ins without rescheduling → Dmitri can request a reschedule or pause the engagement
3. Scope expands by more than 20 hours beyond Phase 1 → Dmitri will issue a change order; work continues only if signed
4. Timeline can’t be met due to client delays (e.g., missing system access) → Dmitri will adjust timeline by written notice; fee remains the same, but timeline shifts

These aren’t punitive. They’re protective.

8.5 — The Weekly Check-In Agenda

Every Thursday, 30 minutes. Same time. All three people.

Format:

• First 5 min: “What’s working?”
• Next 10 min: “What’s not working / blockers?”
• Next 5 min: “Scope check — anything new coming up?”
• Last 10 min: “Next week priorities / prep”

Example Week 2 Check-In:

• Dmitri: “I’ve got the audit halfway done. I found a few security gaps — nothing critical but worth addressing. Jackie, are you seeing any of these issues in your day-to-day?”
• Jackie: “Yeah, the shared email inbox is a mess.”
• Dmitri: “Great, that’s on my list to address. One thing that came up — Christian, your ClickUp workspace has 200+ uncompleted tasks. That’s going in my audit report. Do you want to clean those up, or should I note that as a separate project?”
• Christian: “Let me clean that up this week.”
• Dmitri: “Perfect. So next week I’ll have the playbooks ready. Jackie, can you block 2 hours to walk through them with me and give feedback?”
• Jackie: “Yeah, Thursday afternoon.”
• Dmitri: “Awesome. Next Thursday at 2 PM then.”

This is tight, structured, and moves the engagement forward.

---

9. FINAL VERDICT & SUMMARY

9.1 — Go Ahead, But Do This First

Before sending the proposal:

1. Send the boundary-setting email (Section 2.3) — this is non-negotiable
2. Define Phase 1 scope tightly to 4-5 deliverables
3. Commit to 50% upfront payment before touching a single file
4. Prepare the change order template
5. Block your calendar — don’t overcommit elsewhere

In the proposal:

1. Address Jackie directly by name
2. List specific deliverables (not vague advice)
3. Explain the phased approach clearly
4. Set timeline expectations (3-4 weeks)
5. Define what’s NOT included

Before work starts:

1. Get the first 50% in your account
2. Have signed SOW
3. Schedule first weekly check-in
4. Confirm system access is real

9.2 — The Real Risk

The real risk isn’t that the engagement fails. It’s that Dmitri does 120 hours of work for $8K because he couldn’t say no to scope creep and kept waiting for the final payment.

Avoid that trap by:

• Defining scope tightly
• Using weekly check-ins to catch creep early
• Implementing change orders immediately
• Refusing to start work without upfront payment

9.3 — The Real Opportunity

If Dmitri nails this engagement, he gets:

• First case study (priceless for credibility)
• Recurring revenue (Phase 2, Phase 3, retainer)
• Referral network access (Christian’s connections)
• Proof of concept for the Solanasis model

This isn’t just a $10K project. This is the project that validates the whole business.

So treat it like it’s the most important engagement you’ll ever do. Because it might be.

---

APPENDIX: PRO TIPS FOR DMITRI

1. The hardest conversation is the easiest prevention. Have the hard conversation about scope, budget, and payment BEFORE the proposal. It’s awkward for 5 minutes. Avoiding it creates misalignment for 3 months.

2. Weekly check-ins are magic. A 30-minute sync every week prevents 10 hours of wrong-direction work. This is the cheapest insurance policy you’ll ever buy.

3. “Not included” is as important as “included.” Spend as much time in the proposal defining what’s Phase 2 as you do defining what’s Phase 1. This prevents scope creep.

4. Always get the first payment before you start. No exceptions. Not even for friends. Especially not for friends.

5. Document scope changes immediately. If Christian asks for something new, say “Let’s add that to the change order” in real-time. Don’t wait until the end to remember what wasn’t in the original scope.

6. Jackie is your early warning system. Pay attention to what she says (and doesn’t say). If she’s skeptical, listen to her skepticism. She’s protecting both of you.

7. Delivery on time is better than delivery that’s perfect. Ship Phase 1 on the 4-week timeline with 90% quality instead of waiting 6 weeks for 100%. Clients respect you more for reliability than for perfection.

8. The second engagement is way easier than the first. You’re building the playbook on this one. Mistakes now become wisdom later.

---

END OF SENIOR CONSULTANT REVIEW

This review is internal only. Do not share with Christian or Jackie. Its purpose is to give Dmitri a clear-eyed assessment of the risks and how to mitigate them. Good luck.