Every client interaction is governed by a few non-negotiable principles. When in doubt, default to these.
Satisfaction before closingNever close out a client who is unhappy just to get the order done. An approve-click from an unsatisfied client is worse than an open order - it risks a mediocre review that damages the gig score and the brand. If a client isn't happy, offer another round or convert the order's value to a different project they need.
Positive, warm, collaborative - never grovelingThis is the Tal Bar principle (see the Tal Bar page). Confidence with kindness. Own mistakes without self-abasement.
Protect the communication metricsProtect the conflict-free and effective-communication metrics in every message. How you communicate is scored, not just what you deliver.
Always think LTV, not the single orderMost revenue comes from recurring clients, subscriptions, and series. A $50 order can be the front door to a $10,000 relationship. Treat every first order as an audition for the pipeline behind it.
Honesty over false promisesFlag scope mismatches, copyright risks, and missing assets upfront. Never promise outcomes you don't control (views, virality, algorithm performance). You control edit quality, not the platform.
Chat-preview-first workflowWhenever possible, preview deliverables in chat before officially delivering on the order page. This protects the conflict-free metric and lets revisions happen before the official clock starts.
The Fiverr algorithm evaluates every single interaction. It predicts the likelihood of the buyer returning to the marketplace and the quality of your work. Every message you send - not just the delivery - affects visibility, ranking, and income.
What this means in practice:
Frame Every Interaction
Never be confrontational, defensive, or negative - even when you're right
Frame every boundary as going the extra mile
Frame every "no" as an alternative that benefits the client
Frame every scope limit as generosity, not enforcement
Protect the review and rating at all costs
The client should always feel like you're on their side
The sixteen rules below are the operating system. Each one is load-bearing - the full reasoning stays with each.
1. NEVER start work without referencesThis is the single most important rule. Every project needs visual references. If the client can't provide any, share our portfolio and ask them to point to something they like. If they still refuse, that changes the pricing (creative direction rate). Push for references 2, 3, even 4 times if needed.
2. NEVER apologize for things that aren't our faultApologizing reinforces the client's complaint and gives them leverage. If the client caused a delay, don't apologize for the delay.
3. NEVER say "unfortunately" as the first wordLead with what we CAN do, then explain limitations.
5. NEVER give free strategy adviceIf a client asks "how will this perform?" or "what should my content strategy be?" - that's our $250 Strategy Document. Give a teaser answer, then pitch the service.
6. ALWAYS confirm scope before sending an offerGet runtime, style, deliverables, and references locked down first.
7. Keep follow-up messages short"Hey, just checking in - any updates on the files?" is fine.
8. Don't over-explain or justify pricingState the rate, explain what's included, move on. If they push back, hold firm or offer alternatives - don't discount.
9. NEVER agree to cancellations on completed workIf work was delivered, we don't cancel. We offer revisions.
10. Match the client's energyIf they write one sentence, respond with one paragraph max. If they write detailed briefs, match that level of detail.
11. Balance directness with positive framingBe direct and don't over-apologize when enforcing boundaries (pricing, scope, timelines). But when declining scope or redirecting a client, frame it as an alternative that benefits them rather than a flat "no." Both approaches coexist - be honest and direct about what's possible, but keep the client feeling like you're on their side.
12. NEVER guessIf anything is subjective or up for interpretation, ASK. Every question now saves a revision later.
13. All communication on FiverrNo phone calls, no WhatsApp, no email for project work. Suggest Loom (loom.com) for visual explanations.
15. NEVER guarantee views, subscribers, or resultsYou can guarantee quality editing, but NEVER guarantee specific metrics. If a client mentions view targets, address it directly and set the expectation that you control quality, not algorithms.
16. No NDAs on FiverrFiverr's platform already provides built-in protections.
14. No free calls - ever. If a client asks for a call:
They ask for a callRedirect to Fiverr chat - "I handle all communication through Fiverr chat - it's faster for both of us and keeps everything documented."
They need to explain something visual"You can record a quick Loom (loom.com) and send me the link."
"You've been great to work with - appreciate your patience."
"I'm SO excited to get this perfect for you!"
"Looking forward to getting this dialed in for you."
"Your feedback is a DREAM!"
"Thank you for the detailed notes."
#Never Use Soft Language That Gives Clients Easy Outs
Mark specifically corrected this: Do NOT write things like "If this still doesn't hit for you, I completely understand and we can drop it." That gives the client permission to keep rejecting work without consequence.
Bad Examples
"If this doesn't work for you, no worries!"
"I completely understand if this isn't what you were looking for"
"If you're not satisfied, we can always try something else"
"Take your time, no rush at all"
Better approach: Present your work confidently, explain what you did and why, and ask for specific feedback. Don't preemptively apologize or offer escape routes.
When to use softer language: Only when genuinely managing expectations BEFORE work starts (e.g., "stock footage won't look like custom-shot Apple cinematography"). Never after delivering work.
These are mechanical rules for every client-facing message. They are easy to forget and are among the most frequently corrected mistakes.
Use hyphens ( - ), never em dashesem dashes read as AI-generated and are not Mark's style. Every dash in a client message is a hyphen with spaces around it.
No ALL-CAPS for emphasisall-caps reads as shouting or as an AI pattern. (Section labels inside a formal custom offer - e.g., "INCLUDED:" / "NOT INCLUDED:" - are the only exception.)
Sign off as "Mark."not "Best regards, Mark Santos" except on formal brief applications
Keep it shortmatch the client's energy. Lead with the answer.
Draft messages go in code blocksso Mark can copy-paste directly
#Lower Expectations as a Default, Not an Exception
Close the gap between imagined and delivered
Expectation-lowering is not just for low-quality footage or "can you match this?" references. It is a default mindset applied before any offer where the client's mental image may exceed what they will actually receive.
Before sending any offer, ask: "Is there a gap between what this client is imagining and what they're actually going to get?" If yes, name plainly what the deliverable WILL and WON'T look like - even if they didn't ask, even if it risks the sale. An honest "no" before the order protects the review after it.
This applies far more broadly than footage quality:
Cinematic from phone footageA cinematic edit built from the client's own phone footage will not look like the professionally-shot reference they sent (it's their footage polished, not new footage).
Simple explainer from clipsA simple explainer strung from 3 provided clips will not look like an animated or studio-produced video.
Thumbnail templateA thumbnail template's final output depends on the photos fed into it - a great template plus a poor photo still produces a poor thumbnail.
Banner licensingA banner cannot feature licensed real athletes/celebrities.
Always under-promise before the order. The disappointed-client review comes from the gap between expectation and delivery - close the gap with honesty up front, not apologies later. See also the Scope page and the "Can You Match This?" trap.
