"I've Been With You Two Years" Is Not a Rate Justification

The loyalty line almost every Filipino VA has typed

You open the chat. You type a version of this:

ScriptCopy

Hi [Name], I have been with you for two years now. I was hoping we could look at my rate...

It feels respectful. It feels earned. It often fails.

Why? Because the client can agree you have been loyal and still see no reason the package price must change. Years passed. The email never showed what changed in the work.

This post is a direct counter to that habit. Not because loyalty is fake. Because tenure is not a rate increase justification on its own.

Nearby posts (different jobs):

• What actually justifies a rate increase lists what counts vs what does not.
• The rate-increase message clients don't argue with gives the pasteable structure.
• This post rewrites the loyalty ask into an artifact-led case.

Salag documents agreement → deliverables → approval → invoice → payment. Salag does not certify that two years made you "senior."

---

Why tenure feels like proof (and why it is not)

In many PH workplaces, time served signals trust. That signal is real in human terms.

In freelance pricing, clients buy a package:

• Tasks
• Hours or output
• Speed
• Channels
• Risk they hand you

Time on the account can make that package smoother. It does not automatically change the price unless the package or the market terms change in writing.

Use tenure as a one-line thank-you. Do not use it as the spine.

---

What to replace the loyalty line with

Swap one sentence for five facts.

Old spine

I have been with you two years, so I deserve more.

New spine

ScriptCopy

Here is the original package, the current package, the delivery record, the payment record, and the new rate starting [date].

That is the artifact-led case.

---

Key concepts

Tenure ask: a raise request centered on time served.

Artifact-led ask: a raise request centered on documents and delivery history.

Loyalty pricing: keeping an old rate forever because the relationship feels close.

Scope drift: ongoing tasks added after the original deal.

Floor: Salag's recommended $5/hr minimum for professional USD VA work with clear scope.

---

ALIGN to rewrite a tenure ask

A: Acknowledge the relationship in one line.
Thank them. Then move on.

L: Lay out original vs current scope.
Dates help.

I: Include delivery and payment strips.
Short. Factual.

G: Give the new rate and slim option.
Hold $5/hr.

N: Need a written reply by a date.
No endless "whenever you can."

---

Step 1: Catch the tenure sentence before you send

Search your draft for:

• "I have been with you"
• "for two years"
• "for a long time"
• "because of my loyalty"
• "I hope you can increase"

Highlight those lines. Keep at most one soft thank-you. Delete the rest as your main argument.

Rewrite drill:

ScriptCopy

Before: I have been your VA for two years and my rate is still the same.

After: Since we set $[rate] in [Month Year], the ongoing package grew to include [tasks], and delivery stayed on the agreed timeline for [N] cycles. New rate for that package: $[new] effective [date].

---

Step 2: Build the then-vs-now card

One screen. Phone-friendly.

Then ([Month Year])

• Rate: $[old]
• Tasks: [A, B, C]
• Hours: [X]
• Channels: [list]

Now ([Month Year])

• Rate: still $[old]
• Tasks: [A, B, C, D, E]
• Hours: [X or X+]
• Channels: [list, maybe more]

If Then and Now are identical, your case is weaker. You can still propose a modest update with delivery reliability and floor math. Be honest about the weaker proof. Do not invent scope growth.

Tools: scope creep detector, project scope calculator, handling scope expansion.

---

Step 3: Attach a delivery strip, not a memoir

Tenure essays talk about struggle. Delivery strips talk about outcomes.

ScriptCopy

Delivery strip ([period]):

• [N] weekly deliverables on agreed day
• [N] month-end folders approved in email
• Priority messages handled inside [X] business hours

Use work receipt generator going forward so the next ask is easier. See document work clients can't dispute.

---

Step 4: Confirm money already moves cleanly

If invoices are late or unpaid, fix that path first.

ScriptCopy

Before we update pricing, please clear invoice #[s] and confirm terms: bill on [day], due in [X] days.

A loyalty story on top of unpaid work creates a messy fight.

---

Step 5: Send the artifact-led message

Full pasteable rewrite of the classic tenure ask:

ScriptCopy

Subject: Rate update for [Project] effective [Date]

Hi [Name],

Thank you for the steady partnership over the past [two years]. I am updating the rate for the package as it runs today.

Original package (set at $[old rate] in [Month Year]):

• [Task A]
• [Task B]
• [Task C]

Current ongoing package also includes:

• [Task D] (from [Month])
• [Task E] (from [Month])

Delivery for the last [N] cycles stayed inside our agreed turnaround, with approvals in email. Invoices and payments followed our terms.

New rate for the current package: $[new rate] per [hour/month], effective [Date].

Option B if you need a lower total: keep [A, B] only at $[rate], and pause [D, E] starting [Date].

Please confirm Option A or Option B by [reply-by date].

Best, [Your name]

Notice what is missing: begging, guilt, income promises, and "I deserve."

For more on message spine order, use the rate-increase message clients don't argue with. For the evidence checklist, use what actually justifies a rate increase.

---

Scripts for common loyalty pushbacks

Client: "But we've been together so long"

ScriptCopy

Yes, and I want the written package to match how we actually work now. Here is Then vs Now. Please pick Option A (current package at $[new]) or Option B (smaller package) by [date].

Client: "I thought loyalty meant stable rates"

ScriptCopy

Stable rates work when the package stays stable. The package changed when we added [tasks]. I can hold $[old rate] for the original list only.

Client: "Other VAs would be happy to stay at this rate"

ScriptCopy

Understood. My quote is for this package at $[new], with Option B listed. If neither works, we can close cleanly at the end of this cycle.

Client: "Can you wait another year?"

ScriptCopy

I can keep the current rate until [near date], then the update applies on [effective date]. If we wait a full year with no date, the package will keep drifting unpaid. Please confirm the date in writing.

You, to yourself, before cutting under the floor

If the only way to "keep loyalty" is going under $5/hr for full scope, the answer is cut scope or walk. Do not train disposable pricing.

---

Comparison: tenure ask vs artifact ask

---

Common mistakes when leaving the loyalty habit

1. Deleting the thank-you and sounding cold. Keep one warm line. Then facts.
2. Replacing tenure with aggression. Firm is not rude.
3. Listing every favor since 2024. Only ongoing package items.
4. Sending the artifact ask while scope is still undefined. Freeze the list first.
5. Accepting "we're family" as a pricing system. Warmth can stay. Rates still need writing.
6. Using Salag or certificates as a substitute for proof. Documents over labels.
7. Cutting to $4/hr "just this once." Salag recommends $5/hr as the floor. Sub-floor deals teach the wrong lesson.
8. Bringing relatives' opinions into the client email. Keep barkada advice offline.

---

Example: two-year Shopify VA

Jordan supported a Shopify store for two years at $10/hr.

Original deal: product uploads + basic inbox.

Now also: weekly KPI sheet, supplier follow-ups, returns macros.

Old message draft (weak):

I have been with you two years. Can we move my rate up? I really need it.

New message (artifact-led): used the pasteable template above with Option A $12/hr full package, Option B $10/hr uploads + inbox only.

Client picked A. The deciding section was Then vs Now, not the two-year line. The thank-you stayed one sentence.

---

Cultural note without shame

Loyalty is a strength in Filipino freelance relationships. Keep it.

Just stop asking loyalty to do a job it cannot do: set USD prices for growing remote packages.

You can be kind and still send a dated rate notice. Those are not opposites.

---

How Salag helps

When your path is visible (agreement → deliverables → approval → invoice → payment), you do not need a tenure speech. You can point to cycles.

Salag does not attest skill or quality after year one or year five. It helps you keep artifacts tidy so the next ask is shorter.

Helpful tools:

• Rate calculator
• Rate negotiator
• Rate evolution monitor
• Work receipt generator
• Scope creep detector
• Project scope calculator

Also hold the floor with why Salag recommends a $5/hr floor.

---

When to re-apply this rewrite

• Every time your draft leads with years served
• When a client answers a raise with "but loyalty"
• At renewals where scope quietly grew
• After you notice you are discounting to "protect the relationship"

If the package did not change and delivery is shaky, fix delivery and scope writing before another ask.

---

Definitions

Tenure ask: raise request based mainly on time served.

Artifact-led ask: raise request based on documents and delivery history.

Loyalty pricing: old rate kept forever because the bond feels close.

Then vs Now card: short comparison of original vs current package.

Effective date: when the new rate starts.

---

---

A 20-minute rewrite drill

Take your last unsent tenure draft. Run this drill once.

Minute 0-5: Highlight every time-served phrase. Count them.

Minute 5-10: Write Then vs Now in ten bullets total.

Minute 10-15: Write a four-line delivery strip from real weeks.

Minute 15-20: Paste the artifact-led template and replace brackets.

If you cannot fill Then vs Now, you are not ready to ask. You are ready to document.

Save the weak draft in a notes app if you want. Do not send it.

---

What clients hear when you lead with years

You mean: I have been reliable and patient.

They often hear: Please raise my pay because time passed.

Those are different requests. The second one has no handle for a busy client. The first one still needs proof.

When you lead with artifacts, they hear: Here is the package price update. Choose A or B.

That is a decision, not a favor.

---

Family language, friendship language, and invoices

Some clients say "we're family." Some VAs say it too. Warmth is fine.

Invoices are not family chores. Invoices are package prices.

A clean reply:

I care about this working relationship. I also need the written package and rate to match the work. Here are Option A and Option B with dates.

You are not cold for separating care from pricing. You are preventing quiet resentment.

If a client punishes you for documenting scope, that is data about fit. It is not proof you should stay underpaid forever.

---

Building artifacts if you have nothing saved

Start this week even if the raise waits one cycle.

1. Send a current-package confirmation email.
2. Issue a work receipt each Friday.
3. When a new task appears, reply with a price or a "phase two" note using out-of-scope request scripts.
4. Log adds in a simple sheet.

Thirty days of artifacts beat two years of undocumented loyalty when it is time to update a rate.

---

Manager energy vs freelancer energy

In some offices, tenure unlocks step increases. Freelance USD clients rarely run that system.

You are not an employee waiting for HR. You are a supplier updating a package price.

That mindset shift alone removes half of the guilt from the rewrite.

Keep being kind. Stop waiting for a tenure ladder that is not in the contract.

---

Second example: social VA, three years, same rate

Aya posts content and replies to comments for three years at $6/hr.

Adds: community Discord moderation, monthly performance notes, creator collab sheets.

Weak ask she almost sent: three-year loyalty paragraph + "I need a raise."

Artifact ask she sent: Then vs Now, delivery strip for 12 weeks, $8/hr Option A, Option B without Discord + collab sheets at $6/hr.

Client chose Option B first month, then moved to Option A after seeing Discord load in writing. The tenure line never carried the deal. The task list did.

Note: both options stayed at or above Salag's $5/hr floor.

---

Third example: no scope growth, still rewriting tenure

Ben did the same bookkeeping package for 18 months. Scope did not grow. Delivery was clean. Payments were clean. His costs rose.

He cannot claim expansion. He can still avoid a tenure speech.

ScriptCopy

Hi [Name], I am updating my rate for the same bookkeeping package listed below, effective [date]. Delivery and approvals stayed on schedule for the last [N] cycles. New rate: $[new] per month. If the total is tight, Option B is [fewer entities / fewer reports] at $[rate]. Please confirm by [date].

Weaker than a scope case, still clearer than "I have been here 18 months." Keep the increase modest and the package exact. Hold $5/hr.

---

Teach your future self: ban the sentence

Add a personal rule:

If my draft's main reason is time served, I rewrite before send.

Put it in your notes app. Share it with a freelance friend who will call you out.

Loyalty can stay in your values. It should not stay as your pricing argument.

---

Link the system so you do not slide back

1. Evidence rules: what justifies a rate increase
2. Message spine: rate-increase message clients don't argue with
3. Scope tools: scope creep detector, project scope calculator
4. Rate tools: rate calculator, rate negotiator, rate evolution monitor
5. Proof tools: work receipt generator

Use the chain. Do not improvise a loyalty essay under stress.

Final thoughts

"I've been with you two years" can be true and still fail as a rate case.

Tenure is not a rate increase justification. Artifacts are. Write Then vs Now, add delivery and payment proof, name a rate at or above $5/hr, set the date, and offer a slim option.

Keep the loyalty. Upgrade the evidence.