Readiness is deposits, agreements, and escalation paths, not just skills.
10 min readReadiness checklist (honest yes/no)
| Item | You need this |
|---|---|
| Written scope or SOW | Tasks, hours, exclusions |
| Rate and currency | USD, PHP, or both clear |
| Payment tool tested | Wise, PayPal, bank transfer |
| Invoice template | Due date, method, late rule |
| Deposit rule (projects) | Often 30 to 50 percent upfront |
| Revision limit | e.g. two rounds included |
| Escalation path | Who approves work |
| Backup savings | 1 to 2 months expenses |
If you miss three or more, pause before saying yes to big jobs.
SHIELD Protocol in plain terms
SHIELD is Salag's readiness frame:
- Scope in writing
- Hours capped on retainers
- Invoice terms upfront
- Escalation path named
- Limits on revisions and extras
- Deposit when risk is high
Run through it on every new client call.
Retainer vs project readiness
Retainer: weekly hour cap, task list, billing date, what happens if they skip payment.
Project: milestones, deposit, kill fee if they cancel early, final file handoff after last payment.
Same idea: nothing important stays verbal only.
Red flags that mean "not ready to start"
- "We will figure out scope as we go"
- "Pay you after launch when funding comes"
- "Just trust me, we are a startup"
- No single approver on a team of five
- Pressure to start today with no written terms
Use the client red flag checklist before you commit.
Common mistakes
| Mistake | Cost |
|---|---|
| Starting without payment method | Chasing money for months |
| No hour cap on "part-time" | Full-time pay at part-time rate |
| Skipping deposit on big project | Stuck mid-build if they ghost |
| Copy-paste contract you did not read | Surprise clauses later |
How Salag helps
- Client Red Flag Checklist: spot risky clients early.
- Rate Calculator: know your floor before quoting.
- Request Clarifier: turn vague briefs into clear tasks.
Move safer. Not faster.
In short
Skills get you hired. Readiness keeps you paid.
Before your next client, check: written scope, payment method, invoice terms, revision limits, and what you do if they go quiet. That is protection, not paranoia.
Common questions
Skills get you hired. Readiness keeps you paid. Before your next client, check: written scope, payment method, invoice terms, revision limits, and what you do if they go quiet. That is protection, not paranoia.
Check if you have written scope, payment terms, and a way to say no to unpaid extras before you take a new client.
Match global norms: invoice in USD if needed, confirm scope in email, and know your payment tool before day one.
At minimum, send a kickoff email both sides reply to. Bigger jobs need a signed agreement.
Explain that clear terms help you deliver faster. Offer a short scope doc, not a 20-page legal file.
SHIELD: Scope written, Hours capped, Invoice terms set, Escalation path clear, Deposits when needed, Limits on revisions.
Before you start work if payment method, scope, or approval chain is unclear. Fixing upfront is cheaper.
Yes. A confirmed kickoff email is your baseline protection.
Readiness checkers and agreement tools flag gaps before you say yes.
Bank or Wise account, invoice template, scope doc, and Salag readiness tools.
One hour to set up templates once. Five minutes per new client after that.
Retainers need hour caps and weekly rhythm. Projects need milestones and deposit rules.
Do not start billable work. Offer a one-screen summary to confirm or walk away.