Applications That Get Replies.

What this fixes

Views with no messages, ghosting after the first reply, and copy-paste fatigue

Target length

150 to 200 words. Two or three short paragraphs plus a closing line

Daily volume

Five tailored applications beats fifty pasted ones, every time

Biggest single lever

Applying as a specific role, not as "a VA"

What you end with

A format, 14 annotated rewrites, a tracker, and a follow-up script

Progress is saved in this browser only. Nothing is sent anywhere.

1. 01

   Why you get no replies

   You can name which of the four failure points is actually breaking your applications, instead of guessing.Time splitRed/green flags22 min

   • There are only four places an application dies: sourcing (wrong jobs), profile (they looked and left), message (they read and shrugged), or proof (they wanted evidence and found claims).
   • Track the stages and the broken one is obvious. Lots of views and no messages is a profile problem. Lots of messages and no interviews is a proof problem.
   • The most common structural mistake is applying as a generalist. A Filipino VA answering someone with zero replies put it flatly: "One mistake that every beginner does is they are all applying as a 'VA'. You have almost zero chance when you do this."
   • Volume without tailoring makes the numbers worse, not better, because low-quality applications also lower your response rate on the platforms that measure it.
   • Referrals convert far better than cold applications, and that is not a reason to stop applying. It is a reason to tell every person you know your exact offer.
   • You are competing on clarity, not on credentials. Most of your competition is sending the same three paragraphs about being hardworking and detail-oriented.

   Worked example — Two months of applications, diagnosed

   Sent 180. Profile views 96. Replies 4. Interviews 1. Offers 0.

   Read it backwards: the interview converted at 25 percent, which is fine, so interviewing is not the problem.

   Replies at 4 out of 180 is roughly 2 percent. Below the 5 to 10 percent you should expect from tailored applications.

   Views at 96 out of 180 means people are opening the profile, so the sourcing and the subject line are working.

   Verdict: the profile and the message are the leak. Fix the headline and rewrite the opener, then run 30 more before changing anything else.

   Without stage counts you would have concluded "the market is hard" and sent 180 more of the same thing.

   Where the hours go

   What happens to 100 applications on a typical job post

   A real-shaped funnel for a decent OnlineJobs.ph or Upwork post. Understanding where applications die tells you exactly what to fix.

   • Never opened past the first line52%

     Generic opener, obvious template, wrong role. Killed in under 3 seconds.

   • Opened, skimmed, discarded26%

     All about the applicant, nothing about the client's problem.

   • Read properly, no proof to back it up12%

     Good writing, but nothing to look at. Claims with no evidence.

   • Shortlisted7%

     Specific, relevant, and had something the client could click.

   • Interviewed3%

     The whole game is getting into this 3%. It's a writing problem, not a skills problem.

   Roughly half of your competition is eliminated by the first sentence. That's not depressing — it means the first sentence is where nearly all your leverage is, and it's the cheapest thing to fix.

   Red flag / green flag

   Spot the difference

   Same situation, two ways it can go.

   The opening line of your application

   Red flag

   "Dear Sir/Madam, I hope this message finds you well. My name is [name] and I am writing to apply for the Virtual Assistant position you posted. I believe I would be a great fit for this role."

   Thirty-eight words containing zero information. They know it's an application — they posted the job. Every one of the other 99 applicants opened this way, which means you've just made yourself indistinguishable from all of them.

   Green flag

   "You mentioned you're losing evenings to your inbox. I took a founder's inbox from 200+ daily to under 10 and gave him back two mornings a week — here's exactly how I did it: [link]."

   Names THEIR problem in the first six words, follows with a specific result and a number, and gives them something to click. They now have a reason to read line two.

   How you talk about your experience

   Red flag

   "I have 3 years of experience as a virtual assistant. I am hardworking, detail-oriented, a fast learner, and I can work with minimal supervision. I am proficient in Microsoft Office and Google Workspace."

   Every adjective here is unverifiable and universal. Nobody applies saying they're careless and slow. Claims without evidence are noise, and "proficient in Google Workspace" is the modern equivalent of listing 'can use a telephone'.

   Green flag

   "Three years running ops for a 4-person agency. Concretely: I rebuilt their client onboarding from a 12-day mess to a 3-day checklist, and cut invoice chasing from ~6 hrs a week to under 1 by automating the reminders. Both are in my portfolio."

   Same three years, but described in changes with numbers attached. Nobody can argue with a specific before and after, and nobody else's application will contain those exact sentences.

   Do this

   Build the tracker: date, company, role, source, rate asked, sent, viewed, replied, interviewed, outcome, and a notes column.

   Hand in: A Sheets tracker with your last 20 applications entered honestly, plus your conversion rate at each stage.≈ 40 min

   Check before you call it done

   • You calculated a percentage at each stage, not just totals
   • You named the single weakest stage
   • You wrote one hypothesis for why that stage is weak
   • The tracker takes under 30 seconds per new row

   Mark module done
2. 02

   Read the post like the person who wrote it

   You can extract the real pain, the hidden requirement, and the one line worth quoting back, in three minutes per post.Workflow1 template26 min

   • Job posts are written by tired people describing a bad week. Find the bad week and you have found your opening line.
   • Separate the must-haves from the wish list. Anything mentioned twice, or attached to a number, is a must-have.
   • Look for the tell: an oddly specific complaint, a tool named in passing, a deadline, a sentence in a different tone. That is the human breaking through the template.
   • Note what they did not say. No mention of hours, rate, or reporting line usually means they have not thought it through, which is an opportunity to look organised.
   • Screening instructions buried in the post are a filter. Ignore them and you are auto-rejected regardless of quality. Follow them exactly, first line.
   • Decide fit before you write. If you cannot state the outcome they want in one sentence, you cannot write a good first line, so skip the post.

   Worked example — Harbor and Pine's post, decoded

   Before

   "Looking for a reliable admin/ops assistant for our small interior design studio. Must be organised and proactive. Duties include managing our project tracker, coordinating with vendors and contractors, processing invoices in QuickBooks, and handling client emails. We're growing fast and things fall through the cracks. Must overlap with Mountain Time mornings. Please start your reply with the word 'Aspen'."

   After

   Real pain: things fall through the cracks. Not admin. Follow-through.

   Must-haves: project tracker ownership, vendor coordination, QuickBooks invoices, client email, Mountain Time morning overlap.

   Hidden requirement: they will need you to chase contractors, which is confrontation work, which is why the last person quit.

   Screening filter: the reply must start with "Aspen". This alone removes most of the pile.

   Quotable line: "things fall through the cracks". Use their words, not yours.

   Unsaid: no hours, no rate, no mention of who you report to. Offer structure and you look like the safe hire.

   Three minutes of reading produced an opening line, a proof piece to attach, and a question that makes you sound experienced.

   Workflow

   Reading a job post properly, in four minutes

   Before writing a single word of any application.

   1. 1

      Find the pain, not the task list

      Somewhere in the post is a sentence written in frustration. "Things keep falling through the cracks." "I need someone who won't need constant reminders." That sentence is what they're actually buying.

   2. 2

      Note the exact words they use

      If they say "clients" not "customers", or "deals" not "projects", mirror it. Echoing someone's vocabulary is the cheapest rapport there is.

   3. 3

      Find the hidden requirement

      Timezone overlap, a specific tool, an industry. These are usually mentioned once, in passing, and they're the actual filter.

   4. 4

      Spot the screening trap

      Many posts hide an instruction — "start your reply with the word BANANA", "tell me your favourite book". Missing it is an instant, automatic rejection and it's the easiest filter to pass.

   5. 5

      Judge who wrote it

      A founder writing at midnight, an HR person, or an agency recruiter? Each wants a completely different tone. Founders want directness; HR wants the requirements matched.

   6. 6

      Decide honestly whether to apply

      If you match under half the real requirements or the rate is under your floor, skip it. Applying to everything is how you get a 2% reply rate and conclude the market is bad.

   Where this breaks: Skimming for the job title and rate, then writing from a template. The four minutes spent reading properly is what produces the specific first line, and the specific first line is the whole application.

   Copy-paste

   Steal this

   Swap the bracketed bits and send.

   Job post decode sheet

   Fill this in before writing. Two minutes, and the application almost writes itself afterwards.

   Copy template to clipboard

   POST: [title] | Company: [name] | Rate: [posted] | Source: [board]
   
   WHAT THEY LITERALLY ASKED FOR
   1. [requirement]
   2. [requirement]
   3. [requirement]
   
   WHAT THEY ACTUALLY WANT (the pain underneath)
   The line that gives it away: "[quote it exactly]"
   What that means: [e.g. "the last VA needed managing, and managing them cost more time than they saved"]
   
   THEIR VOCABULARY — mirror these words
   [word] not [word] · [word] not [word]
   
   HIDDEN REQUIREMENTS
   Timezone: [what they need]
   Tool they named: [tool]
   Industry knowledge: [any]
   Screening instruction buried in the post: [find it — reread the last paragraph]
   
   WHO WROTE THIS
   [ ] Founder — be direct, lead with outcomes, keep it short
   [ ] HR/recruiter — match the requirements explicitly, be a bit more formal
   [ ] Agency — emphasise reliability, process, and low management overhead
   
   MY ANGLE
   The one thing I'll lead with: [the single most relevant proof I have]
   The gap I have: [be honest] → how I'll address it: [one line, no excuses]
   
   APPLY? [Y/N]
   Rule: skip it if I match under half the real requirements, or the rate is below my floor.
   Applying anyway "just in case" is what makes the funnel numbers meaningless.

   Do this

   Decode five live job posts in your lane using the six headings above: pain, must-haves, hidden requirement, screening filter, quotable line, unsaid.

   Hand in: A decode sheet with five rows, one per post.≈ 45 min

   Check before you call it done

   • Each pain is written in the client's own words
   • You found at least one screening instruction across the five
   • You marked at least one post as a skip, with the reason
   • No hidden requirement is just a restatement of a listed duty

   Mark module done
3. 03

   The profile they check before they reply

   Your profile answers the three questions a client has in the eight seconds after your message lands.Red/green flags1 template26 min

   • They read your message, then they check your profile, then they decide. A great message with an empty profile dies at step two.
   • Your headline is not your job title. It is your offer: what you do, for whom, and the result. "Admin and ops support for small design and build studios: trackers, vendors, invoices" beats "Virtual Assistant | Data Entry | Social Media".
   • On OnlineJobs.ph, ID Proof is a real gate. Fill in everything the site asks for, including a photo, government ID, your Facebook URL, your address with a supporting bill dated within the last three months, and written skill descriptions. More verified detail means a higher score, and many employers filter out low scores before reading.
   • Skill descriptions should be sentences about work you have done, not a keyword list. Keywords help you get found and sentences get you hired.
   • Use one professional photo where your face is clear. Not a group shot, not a filter, not a logo.
   • On LinkedIn, write the headline for the recruiter's search box. If nobody searches for the words in your headline, nobody finds you.

   Worked example — Headline and summary, before and after

   Before

   Headline: "Virtual Assistant | Hardworking | Data Entry | Social Media Manager | Canva"

   Summary: "Hi! I am a passionate and hardworking virtual assistant with strong attention to detail. I am willing to be trained and can work with minimal supervision. I am proficient in MS Office, Google Workspace, Canva, and social media platforms."

   After

   Headline: "Admin and ops support for small design and construction studios. Project trackers, vendor chasing, QuickBooks invoicing."

   Summary: "I keep small project-based businesses from losing work in the gaps. For a six-person studio that means the tracker is current every morning, vendors get chased before the client notices a delay, and invoices go out on the same day each week rather than whenever someone remembers. I work 7am to 12pm Mountain Time, reply within two hours in that window, and send a Friday summary of everything moved, stalled, and waiting on a decision. Tools: Asana, QuickBooks, Google Workspace, Slack. Samples in the link below."

   The rewrite makes no claims about being hardworking. It describes a week. A client can picture buying that.

   Red flag / green flag

   Spot the difference

   Same situation, two ways it can go.

   Your profile headline

   Red flag

   "Virtual Assistant | Data Entry | Social Media | Customer Service | Admin Support | Lead Generation | Graphic Design"

   A list of everything is a claim to nothing. A client looking for an ecommerce ops person sees a generalist and moves on, because someone whose profile says "Ecommerce Ops" looks more likely to be good at it.

   Green flag

   "Ecommerce Ops VA — Shopify + Amazon | I keep stores from running out of stock and customers from waiting"

   One lane, and the second half describes the outcome the client cares about rather than the tasks you perform. Narrow feels like it's shutting doors. It's actually the only way to be chosen.

   Your profile photo and intro video

   Red flag

   No photo, or a heavily filtered selfie, or a group photo cropped down. No video at all.

   Hiring someone across the world is an act of trust, and there's no photo of you. The absence reads as either inexperience or something to hide. Most applicants skip the video, which is precisely why it works.

   Green flag

   A clear, well-lit photo of your face against a plain wall, taken on a phone. Plus a 60–90 second video: your name, your lane, one specific thing you did, and your working hours. No script read aloud.

   A video removes almost all of the client's uncertainty about your English, your setup, and whether you seem like a functioning professional. It's the single highest-conversion asset you can build, and it takes an afternoon.

   Copy-paste

   Steal this

   Swap the bracketed bits and send.

   Profile rewrite worksheet

   Do this once properly, then use the same wording across OnlineJobs.ph, Upwork and LinkedIn.

   Copy template to clipboard

   HEADLINE (under 70 chars)
   Formula: [Lane] VA — [tools] | [the outcome you produce]
   e.g. "Executive Assistant — inbox & calendar | I give founders their mornings back"
   
   Test it: could 50 other applicants use this exact headline? If yes, rewrite.
   
   OVERVIEW — first two lines are all most people read
   
   Line 1: The problem you solve, in their words.
   "Most founders I work with are losing 2 hours a day to an inbox they're scared to close."
   
   Line 2: What you do about it, with a number.
   "I run inbox and calendar so that stops. Last client: 200+ unread daily down to under 10, held there for 8 months."
   
   Then:
   • What you specifically do (4–6 bullets, all outcomes, no adjectives)
   • Tools you'd be happy to be tested on
   • Your hours, in the CLIENT's timezone
   • One line of personality — you're a person, not a service
   
   Close with a clear next step:
   "Portfolio: [link]. 90-second intro: [Loom]. Happy to do a paid trial task."
   
   WORDS TO DELETE ENTIRELY
   hardworking · detail-oriented · fast learner · passionate · dedicated · team player
   "I can do anything you need" · "minimal supervision" · "I hope this finds you well"
   Every one of these appears in the majority of applications, so they carry no information.
   
   WORDS THAT WORK
   Numbers. Tool names. Timezones. Specific outcomes. The client's own vocabulary.
   
   THE PHOTO
   Plain wall, face lit from the front, phone camera, no filter, slight smile. 20 minutes.
   
   THE 90-SECOND VIDEO — script skeleton (talk it, don't read it)
   0:00 "Hi, I'm [name], I'm a [lane] VA based in the Philippines."
   0:08 "I work with [type of client] on [the specific thing]."
   0:20 "Here's an example: [one concrete story with a number]."
   0:50 "I work [hours] [client's timezone] and I'm on [speed] fibre with a backup connection."
   1:05 "Portfolio's linked below. Happy to do a paid trial so you can see how I work."
   
   Record it 5 times, use take 4. Do not script it word for word — it always sounds read.

   Do this

   Rewrite your headline and summary for your chosen lane, then complete every field on OnlineJobs.ph and check your ID Proof score after a day.

   Hand in: Screenshots of the old and new profile, plus your ID Proof score before and after.≈ 60 min

   Check before you call it done

   • The headline names a buyer type and at least two concrete deliverables
   • The summary describes a normal week, not your personality
   • Every ID Proof field is filled, including address with a recent bill
   • The photo is a clear head and shoulders shot
   • Your samples link is public-view and tested in a private window

   Mark module done
4. 04

   The four-paragraph format

   You can write a 180-word application in ten minutes that reads as if it took an hour.2 templates30 min

   • The skeleton: their problem in their words, the specific thing you would do about it, one piece of proof, then a low-friction close.
   • Paragraph one is the whole game. Do not open with your name, your years of experience, or the word "passionate". Open with the outcome they want.
   • Paragraph two must contain something only someone who read the post could write. A named tool, a named constraint, a first-week action.
   • Paragraph three is proof, and one link beats four. Say what the link is and what it shows.
   • Paragraph four gives them the easiest possible yes: your availability window, your rate if requested, and one question they can answer in a sentence.
   • Upwork's own guidance is the same shape: address the client's specific needs in the opening lines, include relevant samples, keep it to two or three short paragraphs. Everyone knows this and almost nobody does it.

   Worked example — The full application to Harbor and Pine

   After

   Aspen.

   "Things fall through the cracks" is usually a follow-up problem rather than an admin problem, and it is the part I am good at. For a six-person studio, the fix is a tracker that is current before the owner opens it and a chase list that runs on a schedule instead of on memory.

   In my first week I would take over the project tracker, add a last-touched date to every vendor and contractor line, and start a daily 15-minute chase pass on anything untouched for three days. Invoices would go out the same day each week in QuickBooks rather than in a batch when someone notices.

   Here is a chase tracker I built for a fictional design studio, with the formula that flags anything silent for 72 hours: [link]. Same folder has a one-page Friday summary in the format I would send you.

   I work 7am to 12pm Mountain Time and reply within two hours in that window. One question: when a contractor goes quiet, do you want me chasing them directly under my own email, or drafting for you to send?

   One hundred and eighty words. It quotes them, names their tools, commits to a first week, links one artefact, and ends with a question only a real candidate would think to ask.

   Copy-paste

   Steal these

   Swap the bracketed bits and send.

   The four-paragraph application

   The whole format. Under 200 words. Longer applications do not perform better — they perform worse.

   Copy template to clipboard

   [No "Dear Sir/Madam". Use their name if you can find it, otherwise no greeting at all.]
   
   PARAGRAPH 1 — THEIR PROBLEM (1–2 sentences)
   Prove you read the post. Name the specific pain, using their words.
   "You said things keep slipping between the cracks when you travel. That's usually a follow-up problem, not a calendar problem."
   
   PARAGRAPH 2 — PROOF YOU'VE SOLVED IT (2–3 sentences)
   One specific example with a number. Not your whole CV. One.
   "I ran the follow-up system for a 4-person agency for two years. Every commitment made in a meeting went into a tracker with an owner and a date, chased 3 days early. Nothing was dropped in 18 months, including during two directors' parental leave."
   
   PARAGRAPH 3 — WHAT I'D DO IN WEEK ONE (2–3 sentences)
   Free thinking. This is the paragraph almost nobody writes, and it's why it works.
   "First week I'd build your waiting-for list from your sent folder — everything you've asked someone for that hasn't come back. That's usually 15–20 things nobody is tracking. Then a daily EOD note so you know where everything stands without asking."
   
   PARAGRAPH 4 — LOGISTICS + ONE CLEAR NEXT STEP (2 sentences)
   "I'm available 6am–2pm PST, [n] hrs a week, at $[n]/hr. Portfolio's here [link] and there's a 90-second intro if useful [link] — happy to do a paid trial task on a real piece of your inbox."
   
   [Screening word if the post asked for one — put it exactly where they said.]
   
   RULES
   • Under 200 words total. Count them.
   • Their name in the first line if you can find it. Check the website's About page.
   • One number minimum, ideally two
   • One link they can click without signing up for anything
   • A specific rate. "Negotiable" reads as "I don't know what I'm worth."
   • Never attach a CV unless asked. It's a reason to stop reading.
   • Read it out loud before sending. If you'd be embarrassed to say it, rewrite it.

   Three openers that get read

   The first sentence does 80% of the work. Pick the shape that fits what the post revealed.

   Copy template to clipboard

   1. THE PROBLEM MIRROR — when they described a pain
   "You mentioned [their exact pain]. That's almost always [your diagnosis], and it's fixable in about [timeframe]."
   
   Example: "You mentioned the last VA needed constant reminders. That's usually a documentation problem rather than an attitude one — a person with a checklist doesn't need reminding."
   
   2. THE RESULT OPENER — when you have a close-matching win
   "[Specific result with a number]. Here's how, in case it's useful for [their situation]: [link]"
   
   Example: "Took a Shopify store's support queue from 3-day replies to under 4 hours without adding headcount. Wrote up exactly how here, in case it's useful for your 600-orders-a-month setup: [link]"
   
   3. THE OBSERVATION OPENER — when you've actually looked at their business
   "[Something specific and true you noticed]. [What it means]. [What you'd do.]"
   
   Example: "Your product pages don't have a size chart, and three of your recent reviews mention sizing confusion. That's usually worth a couple of points of conversion and it's a one-afternoon fix."
   
   ⚠ The observation opener is the strongest by a distance, and the riskiest.
   It requires you to genuinely look at their business for ten minutes.
   Be helpful, never smug. "You've made a mistake" loses; "here's something free" wins.
   Never open by criticising something they're obviously proud of.
   
   NEVER OPEN WITH
   "I hope this email finds you well"
   "My name is..." (it's in the From field)
   "I am writing to apply for..." (they know)
   "I came across your job posting..." (obviously)
   "I am the perfect candidate for this role" (you can't know that yet)

   Do this

   Write three applications to three live posts using the four-paragraph skeleton. Time yourself on each.

   Hand in: Three applications, each under 200 words, with the time taken noted.≈ 50 min

   Check before you call it done

   • No application opens with your name or your years of experience
   • Each contains one detail that could only come from reading that post
   • Exactly one proof link, described in the sentence before it
   • The closing question is answerable in under ten words
   • The third one took you under twelve minutes

   Mark module done
5. 05

   Fourteen rewrites

   You have a library of annotated before-and-after lines and you can spot the failure mode in your own drafts.Red/green flags1 template34 min

   • Most bad applications fail in one of six ways: they are about you, they are generic, they are too long, they beg, they overclaim, or they make the client do work.
   • The fastest fix for any weak opener is to delete the first sentence. It is almost always throat-clearing.
   • Never use the phrase "I am the perfect fit". Show the fit and let them conclude it. Asserting it is what people with nothing to show do.
   • Do not apologise for lacking experience. Substitute proof. "I have not worked in real estate, but here is a CRM cleanup I built on sample data" is a strong sentence. "I have no experience but I am willing to learn" is a weak one.
   • Enthusiasm is not a qualification. Exclamation marks do not raise your reply rate, and three of them lower it.
   • Cut every sentence that would survive a copy-paste into a different application. If it fits everywhere it persuades nowhere.

   Worked example — Fourteen lines, annotated

   Before

   1. "Hi! My name is ___ and I am a passionate and hardworking virtual assistant."

   2. "I saw your job post and I am very interested in this position."

   3. "I am a fast learner and can work with minimal supervision."

   4. "I have 3 years of experience in various administrative tasks."

   5. "I believe I am the perfect fit for this role."

   6. "I don't have experience in real estate, but I am willing to be trained."

   7. "Please consider my application. It would mean a lot to me and my family."

   8. "I am proficient in MS Office, Google Workspace, Canva, and CRM tools."

   9. "I can start immediately and I am available 24/7."

   10. "Attached is my resume for your review."

   11. "I am willing to accept any rate you offer."

   12. "I have helped many clients grow their business."

   13. "Looking forward to your positive response. God bless!"

   14. "Let me know if you have any questions."

   After

   1. "Aspen. Your tracker being out of date by Wednesday is the thing I would fix first." Opens on their problem, not your name.

   2. "You mentioned invoices go out whenever someone remembers. I would move them to a fixed Thursday run." Interest is proven by specificity, never announced.

   3. "I learned Follow Up Boss in a weekend and rebuilt a 400-contact pipeline on sample data: [link]." Replace the claim with the evidence for it.

   4. "For three years I ran the vendor chase list for a construction firm, average response time down from 6 days to 2." Three years of what, producing what.

   5. Delete entirely. Nothing replaces it. The client decides fit; your job is to make the decision easy.

   6. "New to real estate, so I built the thing first: a CRM cleanup and speed-to-lead SOP on sample data: [link]." Answer the objection with an artefact.

   7. "Happy to do a paid first week so you can judge the work rather than the application." Need is not persuasive. Reduced risk is.

   8. "QuickBooks for invoicing, Asana for the tracker, and I will use your Slack conventions rather than mine." Name their stack, not the alphabet.

   9. "7am to 12pm Mountain Time, replies within two hours in that window." 24/7 reads as desperate and unsustainable, and both are true.

   10. "One link, not attachments: [folder]. Top item is a two-minute Loom of how I would run your first week." Make it one click on a phone.

   11. "$8 an hour for the scope in your post, and I will tell you if something you add should change that." A number reads as a professional. Anything reads as a warning.

   12. "For one client that meant 38 quotes a month answered inside an hour instead of a day." One client, one number, one timeframe.

   13. "One question: chase contractors under my email, or draft for you?" End with a door, not a blessing.

   14. Delete. Replace with a specific question. "Any questions" pushes the work back to the person with less time than you.

   Every rewrite does the same two things: it removes a claim about you and adds a fact about them or a link they can click.

   Red flag / green flag

   Spot the difference

   Same situation, two ways it can go.

   Applying when you don't meet every requirement

   Red flag

   "I don't have direct experience with Klaviyo, but I'm a very fast learner and I'm confident I could pick it up quickly. I'm sure I could figure it out."

   Three hedges in two sentences, and no evidence. "Fast learner" is what everyone says, and "figure it out" tells the client they'll be paying for your learning time.

   Green flag

   "I haven't used Klaviyo on a paid account. I've built the same flows in Mailchimp — abandoned cart, welcome series, post-purchase — and I spent this weekend building a Klaviyo test account with those three flows so I could see the differences. Here's the screenshot [link]. I'd expect a week to be genuinely fast in it."

   Honest about the gap, proves the transferable skill, shows you did unpaid work to close it, and gives a realistic timeline. This beats an applicant who actually has Klaviyo experience but describes it vaguely.

   Following up after no reply

   Red flag

   "Hi, just following up on my application. Did you get a chance to review it? Looking forward to hearing from you." — sent every two days for two weeks.

   Adds no information and creates work for them. Repeated content-free follow-ups actively move you down the list, because now you're a person who will pester.

   Green flag

   Once, after 5–7 days: "Following up on the EA role. Since applying I put together a quick version of the waiting-for list I mentioned, using a fake inbox — [link]. Should give you a sense of how I'd approach week one. Happy to leave it there if you've filled the role."

   One follow-up, and it carries new value rather than a request. The graceful exit line removes any pressure, which paradoxically makes people more likely to reply.

   Copy-paste

   Steal this

   Swap the bracketed bits and send.

   Rewrites: the same sentence, weak and strong

   Read your draft and search for these patterns. They're in almost every rejected application.

   Copy template to clipboard

   ❌ "I am hardworking and detail-oriented."
   ✅ "I ran a 340-row product import with zero errors by testing 3 rows first — the checklist I used is in my portfolio."
   
   ❌ "I have experience with social media management."
   ✅ "I ran two IG accounts for 14 months, 12 posts a month each, and grew DM enquiries from 8 to 40 a month on the larger one."
   
   ❌ "I am a fast learner and can pick up new tools quickly."
   ✅ "I learned Gorgias in a weekend on their free tier and built 7 macros. Screenshot in my portfolio."
   
   ❌ "I can work with minimal supervision."
   ✅ "I send an EOD summary daily — done, decided, blocked, needs you. You'd never need to ask where something is."
   
   ❌ "I am available to start immediately and flexible with hours."
   ✅ "I work 6am–2pm PST, Mon–Fri. That's a 5-hour overlap with your morning. I can start Monday the 14th."
   
   ❌ "I would love the opportunity to work with your company."
   ✅ "Happy to do a paid trial on a real task so you can see how I work before committing."
   
   ❌ "Please find my resume attached for your consideration."
   ✅ "Portfolio's here: [link]. Three worked examples, takes about four minutes."
   
   ❌ "I have excellent English communication skills."
   ✅ [Delete this and record a 90-second video instead. Claiming good English in writing is the weakest possible proof of it.]
   
   ❌ "My rate is negotiable."
   ✅ "$8/hr, or $1,200/month for 35 hrs/week."
   
   ❌ "I hope to hear from you soon. Thank you for your time and consideration."
   ✅ "If it's useful I'll send over how I'd handle your first week — just say the word."
   
   THE TEST FOR EVERY SENTENCE
   Could a bad applicant write this exact sentence honestly?
   If yes, it's doing no work for you. Cut it or make it specific.

   Do this

   Take three of your own past applications and mark every sentence with one of the six failure modes. Then rewrite them.

   Hand in: A before and after document with your annotations visible.≈ 50 min

   Check before you call it done

   • Every original sentence is labelled with a failure mode or marked as fine
   • At least a third of the original words are gone
   • No rewritten line could be pasted into a different application unchanged
   • You cut every exclamation mark

   Mark module done
6. 06

   Proof that does the arguing for you

   You can build a two-hour mini-audit or sample that makes the reply almost automatic.WorkflowRed/green flags1 template30 min

   • The highest-converting attachment is unpaid work aimed at their actual business, capped at two hours. Not a free month. A sample.
   • A mini-audit has three parts: three things you noticed, one you would fix first, and how you would measure that it worked. Half a page.
   • Do not send a critique that makes them feel stupid. Frame it as "here is what I would do in week one", not "here is what is wrong with you".
   • For any lane you can build a sample on invented data in an afternoon: a CRM cleanup, an inbox taxonomy, a content calendar, a returns workflow, a keyword map.
   • One VA who hires described how clients read portfolios: they scan for about thirty seconds and want to see the work, not read about it. Lead with the artefact, not the explanation.
   • Label everything simulated as simulated. Passing off invented results as a real client's is the one lie that ends a career in a market this small.

   Worked example — The two-hour mini-audit for Tolliver Roofing

   Noticed 1: your contact form sends to a shared Gmail with no auto-reply, so a homeowner hears nothing until someone opens it.

   Noticed 2: your Google Business Profile has 31 reviews and 4 unanswered, the newest from March.

   Noticed 3: the quote request form asks for eight fields including budget, which is where most people abandon a roofing form.

   Fix first: speed to lead. An auto-reply within 60 seconds with a booking link, then a human reply inside an hour during working days.

   Measure: time from form submission to first human reply, tracked weekly. Baseline it in week one and report the median.

   Attached: the auto-reply copy and a one-page tracker template, both ready to use whether or not you hire me.

   Two hours of work, no access required, and it changes the conversation from "can you do admin" to "when can you start on speed to lead".

   Workflow

   Building proof when you have no clients yet

   The chicken-and-egg problem. You need experience to get hired, and hiring to get experience.

   1. 1

      Build for a fictional client, and label it clearly

      A practice scenario shown in full beats a real client you can't discuss. The honesty is itself a selling point — say "practice scenario" and clients respect it.

   2. 2

      Fix something real for a real business, unasked

      Find a local business, spend an hour, send them the improvement for free. Even if they ignore it, you now have a genuine artefact about a genuine business.

   3. 3

      Do one small job cheap, deliberately, once

      One underpriced project purely to generate a testimonial and a case study. Once. Not a strategy — a transaction where the payment is the proof.

   4. 4

      Show the thinking, not just the output

      A pretty deliverable proves you can use Canva. A note explaining why you made the tradeoff proves you can think, which is what actually gets you hired above $6/hr.

   5. 5

      Record a walkthrough of everything

      Three minutes on a Loom talking through your work converts better than the work sitting silently in a folder.

   6. 6

      Put it all behind ONE link

      A view-only Notion page or Google Doc. One link, in the first paragraph of every application, forever.

   Where this breaks: Waiting until the portfolio is impressive. Three modest, clearly-explained artefacts published today beat a perfect portfolio you're still building in six months.

   Red flag / green flag

   Spot the difference

   Same situation, two ways it can go.

   How you present practice work

   Red flag

   Presenting a practice scenario as though it were a paid client, hoping nobody asks. Or hiding it entirely because "it's not real work".

   Getting caught inventing a client ends the conversation and the reputation instantly. And hiding it means you're applying with nothing at all, which is worse than applying with honest practice work.

   Green flag

   "Note: Mara Villaflor is a practice scenario from my training, not a paid client — which is exactly why I can show you every artefact in full rather than a redacted summary."

   Turns the apparent weakness into an actual advantage. Real client work is usually confidential and can only be described vaguely. Practice work can be shown completely, and completeness is what convinces.

   Copy-paste

   Steal this

   Swap the bracketed bits and send.

   Case study format

   One page per artefact. Situation, action, result, thinking. The last section is the one that gets you hired.

   Copy template to clipboard

   [TITLE — describe the RESULT, not the task]
   ❌ "Inbox management project"
   ✅ "212 unread emails to 6, held there for a month"
   
   [If practice work, say so in the first line. Always.]
   Practice scenario from my training. Not a paid client — so I can show you all of it.
   
   THE SITUATION (2–3 sentences)
   [What was broken and why it mattered. Concrete. "A founder with 212 unread emails who'd stopped opening his inbox before 11am because it made him anxious. Two client questions had gone unanswered for over a week."]
   
   WHAT I DID
   1. [Action] — [why this first]
   2. [Action] — [why]
   3. [Action] — [why]
   
   [Screenshot or embed of the actual artefact]
   
   THE RESULT
   Before: [number] → After: [number]
   [Second measure]: [before] → [after]
   Time it took: [n] hours
   Ongoing time to maintain: [n] mins/day
   
   THE THINKING — the section that actually matters
   [The judgment call you made and why. This is what separates you from someone who can follow a tutorial.]
   "The tempting move was to reply to everything. I didn't — I sorted all 212 first without writing a word, because replying as you read means spending 40 minutes on email #3 and never reaching the urgent one at #90. Sorting first took 20 minutes and made the rest obvious."
   
   WHAT I'D DO DIFFERENTLY
   [One honest thing. Nobody believes a flawless case study, and admitting a limitation makes the rest more credible.]
   
   [Loom walkthrough: link]

   Do this

   Pick one real business in your lane and build a mini-audit on public information only. No logins, no guessing at private data.

   Hand in: A half-page audit plus one usable template, both clearly marked as unsolicited and free to keep.≈ 2 hours

   Check before you call it done

   • Everything you noticed is verifiable from public information
   • The fix names a metric and a baseline
   • Nothing in it insults the owner
   • The attached template is usable without hiring you
   • You capped yourself at two hours

   Mark module done
7. 07

   Interviews, tests, and trial tasks

   You can handle the screening call, answer the rate question, and tell a fair trial from free labour.Red/green flags2 templates30 min

   • The first call is mostly a check that you are real, you communicate clearly, and your setup works. Test your audio beforehand and sit somewhere quiet.
   • Have three stories ready in the shape of situation, what you did, and the result. Recycle them. Interviewers are not comparing notes with each other.
   • When they ask about a gap or missing experience, answer in one sentence and pivot to evidence. Long explanations sound like guilt.
   • The rate question is answered with a package, not a number in the air: "For the scope in your post, roughly 20 hours a week, my rate is $X an hour and I invoice biweekly." Then stop talking.
   • A fair trial task takes one to three hours, is scoped in writing, and is paid or clearly agreed as unpaid in advance. An unfair one is a real deliverable for a real client with a real deadline.
   • Ask your own questions: who else does this work today, what does a good first month look like, and how will you know I am doing well. Candidates who ask these read as senior.

   Worked example — The rate question, three ways it goes

   Before

   Client: "So what's your rate?"

   You: "Um, what's your budget? I'm flexible, whatever works for you."

   After

   Version A, they asked first: "For the scope in your post, around 20 hours a week covering the tracker, vendor chasing and weekly invoicing, my rate is $8 an hour and I invoice biweekly." Then say nothing.

   Version B, they push back: "I hear you. At $6 I would keep the tracker and the invoicing and drop the vendor chasing, since that is the piece that eats the hours. Which shape do you want?" Reduce scope, do not discount.

   Version C, they name a number first and it is low: "That works for the tracker and invoicing only. If you want vendor chasing included it is $8. Both are real offers, your pick."

   In all three you gave a number, kept a boundary, and never once said the word sorry.

   Reflecting the question back with "what's your budget" tells the client the price is whatever they say. You will never recover from that opening.

   Red flag / green flag

   Spot the difference

   Same situation, two ways it can go.

   They ask you to do a trial task

   Red flag

   Accepting a 6-hour unpaid "test project" that is obviously real client work with a real deadline, because you don't want to seem difficult.

   Some clients split one real job into unpaid "tests" across several candidates and get it done for free. The tell is real deliverables, real deadlines, and real client names.

   Green flag

   "Happy to do a trial — it's the best way for both of us to check the fit. For something this size I'd charge [rate] for the [n] hours. If it's a shorter sample, say 30–45 minutes on something anonymised, I'm glad to do that free. Which works for you?"

   Agrees enthusiastically to the principle, draws the line at scale rather than at the idea, and offers a free alternative. A real client says yes to one of those. A free-labour operation goes quiet.

   The interview asks about your weakness or a mistake

   Red flag

   "My weakness is that I'm a perfectionist and I work too hard." Or: "I can't really think of any mistakes."

   The first is a non-answer everyone recognises and it signals you're managing them rather than being honest. The second is either untrue or means you haven't done enough to have made mistakes.

   Green flag

   "I used to under-communicate when I was stuck. I'd try to solve it alone to avoid looking incompetent, and a deadline slipped because of it. Now I flag anything blocked within 2 hours, with what I've already tried. It felt like admitting weakness at first and it turned out clients much prefer it."

   A real weakness, a real consequence, a specific behaviour change, and evidence it stuck. This answer builds more trust than any strength you could name.

   Copy-paste

   Steal these

   Swap the bracketed bits and send.

   Interview prep sheet

   Fill this in before every interview. Twenty minutes, and you stop improvising under pressure.

   Copy template to clipboard

   COMPANY: [name] | ROLE: [title] | INTERVIEWER: [name, role] | [date/time + BOTH timezones]
   
   RESEARCH — 15 minutes, no more
   What they sell: [one line]
   Who to: [one line]
   Something specific I noticed: [a recent post, a product, a page — proves I looked]
   Their likely biggest operational headache: [my guess]
   
   MY THREE STORIES — have these ready, don't recite them
   1. A time I fixed something: [situation → what I did → number]
   2. A time I made a mistake: [what → impact → what changed → evidence it stuck]
   3. A time I handled a difficult person: [situation → how → outcome]
   
   MY NUMBERS — say these without hesitating
   Rate: $[n]/hr or $[n]/month for [n] hrs
   Absolute floor: $[n] (do NOT say this out loud, just know it)
   Hours available: [specific, in THEIR timezone]
   Start date: [date]
   
   QUESTIONS I'LL ASK — always have 3+. Not asking any is a red flag to them.
   1. "What does the first 90 days look like if this goes well?"
   2. "What did the last person in this role find hardest?"
   3. "How do you prefer to communicate — and how quickly do you expect replies?"
   4. "What's the thing that's most likely to go wrong here?"
   5. "Who else would I be working with day to day?"
   
   TECH CHECK — 10 minutes before, every time
   [ ] Audio tested (record 10 seconds, play it back)
   [ ] Light on my face, not behind me
   [ ] Plain, tidy background
   [ ] Phone silenced, family warned, dog dealt with
   [ ] Backup: hotspot on standby, their phone number saved in case it drops
   [ ] Portfolio link open in a tab, ready to paste
   
   AFTER
   [ ] Thank-you message within 4 hrs, referencing one specific thing we discussed
   [ ] Logged in the tracker
   [ ] Note what I fumbled, so I fix it before the next one

   Post-interview follow-up

   Within 4 hours. Short, references something specific, adds one small piece of value.

   Copy template to clipboard

   Hi [name],
   
   Thanks for the time today — genuinely enjoyed it.
   
   The thing you said about [specific thing they mentioned] stuck with me. [One sentence of a useful thought about it, or a small offer.] "You mentioned the handover from sales to onboarding is where things get dropped — I've put a rough version of the checklist I'd use for that here: [link]. Yours regardless of how this goes."
   
   To confirm what we discussed: [hours], starting [date], at [rate].
   
   Happy to do a paid trial task if that'd help you decide.
   
   [Your name]

   Do this

   Record yourself answering five questions on Loom: tell me about yourself, why this role, a time something went wrong, what is your rate, and what questions do you have.

   Hand in: One Loom under six minutes, watched back once with three notes on what to change.≈ 45 min

   Check before you call it done

   • The self-introduction is under 45 seconds
   • The failure story ends with what you changed, not with an apology
   • You said a rate number out loud without hedging
   • You asked at least two questions of your own
   • You watched it back, however painful

   Mark module done
8. 08

   The system: volume, follow-up, and knowing when to change

   You run applications as a repeatable weekly process with a rule for when to change strategy instead of despairing.WorkflowToolsRates1 template26 min

   • Five tailored applications a day, five days a week, is 100 a month. That is enough data to make a real decision.
   • Follow up once, five to seven days later, and add something new: a link, a thought about their business, an updated availability. Never send "just following up".
   • Silence after a reply is normal and is not personal. Hiring stalls for reasons that have nothing to do with you. Keep the row in your tracker and move on.
   • Change one variable at a time. If you change the lane, the headline and the format at once, you learn nothing from the next 30 applications.
   • Set a review date before you start, not when you are demoralised. Thirty days, 100 applications, then read the tracker like a stranger would.
   • Keep applying after you get hired. The VAs who stay stable treat client search as a permanent low-level habit, not an emergency response.

   Worked example — The follow-up that gets a reply

   Before

   "Hi, just following up on my application. Please let me know if you need anything else. Thank you!"

   After

   "Hi Dana, following up on the ops assistant role. Since applying I put together the Thursday invoicing checklist I mentioned, in case it is useful either way: [link]."

   "Still available for the 7am to 12pm Mountain window, and happy to start with a paid first week if that is easier than deciding now."

   The second one gives them something and reduces their risk. The first one asks them to do emotional labour for a stranger.

   Workflow

   The weekly application system

   Every week until you're hired. Treat it as a job with hours, not a mood.

   1. 1

      Monday: harvest 25 posts, don't write anything

      Separate finding from writing. Filter hard — 25 you actually match beats 100 you don't.

   2. 2

      Tue–Fri: 5 applications a day, 20 minutes each

      Four minutes reading, twelve writing, four checking. Batching this way stops it eating your whole day.

   3. 3

      Log every single one, immediately

      Date, company, rate, what you led with. Without the log you can't diagnose anything and you'll draw conclusions from feelings.

   4. 4

      Follow up once at day 5–7, with something new

      One follow-up, carrying value. Then stop, permanently, and don't take it personally.

   5. 5

      Friday: read the funnel numbers

      Applications → replies → interviews → offers. Fix the stage where the number collapses, not the stage you feel worst about.

   6. 6

      Change ONE thing per week and measure it

      Change five and you learn nothing. Change the opener this week, the portfolio link next week. Two weeks of data per change.

   Where this breaks: The binge-and-crash cycle: 60 applications on Sunday, nothing for nine days, then despair. Consistency beats intensity, and the log is what keeps you honest about which one you're actually doing.

   Tool comparison

   Where to actually apply

   Each board is a different market with different rates, competition and client quality. Applying the same way everywhere is why the funnel numbers look bad.

   Swipe the table sideways →

   Tool	Best for	Learning curve	Cost	Verdict
   OnlineJobs.phLearn first	Volume. Employers who specifically want to hire Filipino staff long-term.	Easy	Free for jobseekers	Biggest source by far, and the lowest rates. Worth it because employers here expect a long relationship. Get your ID verified — it visibly moves you up their rankings.
   Upwork	Higher rates, and escrow protection with clients you don't know.	Medium — the algorithm matters	Free, 10% fee on earnings	Hard to start (no reviews = no jobs), excellent once you have 3–4 good ones. Apply to fewer, better jobs — connects are limited and that's actually a feature.
   RemoteOK / We Work Remotely	Salaried remote roles rather than freelance gigs.	Easy	Free	Fewer listings, much higher pay, far more competition from everywhere in the world. Worth applying to a couple a week as a long shot with a real upside.
   Indeed	Companies hiring remote staff who aren't thinking 'VA' specifically.	Easy	Free	Underused by VAs. Search job TITLES like 'operations coordinator' rather than 'virtual assistant' — same work, better pay, less competition.
   LinkedIn	Being found rather than applying. Inbound beats outbound.	Medium — needs consistency	Free	Slowest to pay off and the best long-term. Post once a week about your lane for six months and clients start messaging you. Almost nobody does this.
   Direct outreach	The best clients, who never post a job at all.	Hard — low hit rate	Free	Highest rates and zero competition, because you're the only applicant. Send 20 genuinely useful, researched emails and expect 1–2 conversations. Worth doing weekly.

   This table has 5 columns and scrolls horizontally on small screens.

   What this pays

   What a working application funnel looks like

   Benchmarks so you can tell whether you have a volume problem or a quality problem. Most people diagnose the wrong one and just apply harder.

   Swipe the table sideways →

   Experience	Hourly (USD)	Monthly (USD)	What changes it
   Copy-pasted, no portfolio	1–3% reply	~1 interview per 100	Where most people are. Applying harder does not fix this.
   Personalised first line only	8–12% reply	~4 interviews per 100	One sentence of real effort roughly quadruples the reply rate.
   Personalised + portfolio link	15–20% reply	~8 interviews per 100	The link is what turns a reply into an interview.
   Personalised + portfolio + Loom	20–30% reply	~12 interviews per 100	Very few applicants do all three. That's exactly why it works.
   Sustainable pace	5/day	~100/month	Five properly personalised beats fifty copy-pasted, and you can keep it up.

   This table has 4 columns and scrolls horizontally on small screens.

   Directional benchmarks, not guarantees — reply rates vary hugely by lane, rate and season. Use them to spot which stage of YOUR funnel is broken, not as promises.

   Copy-paste

   Steal this

   Swap the bracketed bits and send.

   Weekly funnel review

   Fifteen minutes every Friday. This is how you improve instead of just enduring.

   Copy template to clipboard

   WEEK OF [date]
   
   THE NUMBERS
   Applications sent: [n]  (target: 25)
   Replies: [n] → [n]%
   Interviews: [n] → [n]% of replies
   Offers: [n]
   Time spent: [n] hrs
   
   DIAGNOSIS — find where it collapses
   Reply rate under 8%?
     → The APPLICATION is the problem, not the volume. Stop sending more.
     → Fix: is the first sentence about THEM? Is there a number? Is there a link?
     → Also check: am I applying to roles I actually match?
   
   Replies but no interviews (under 30% of replies)?
     → Your PROFILE or PORTFOLIO isn't backing up the pitch.
     → Fix: add the Loom. Check the portfolio link actually opens for a stranger — test it in a private window.
   
   Interviews but no offers (under 20%)?
     → Interview performance, rate, or genuine mismatch.
     → Fix: prep sheet before every one. Practise your rate out loud. Ask every rejection for one piece of feedback.
   
   Offers but all below your floor?
     → You're fishing at the bottom of the market.
     → Fix: apply to the top 20% of posts and accept a lower reply rate. Fewer, better.
   
   WHAT I CHANGED THIS WEEK
   [One thing only]
   
   WHAT I'M CHANGING NEXT WEEK
   [One thing only]
   
   HONEST NOTE
   [Did I actually do 25, or did I do 9 and feel bad about it all week?
   The feeling of applying is not the same as applying. Write the true number.]

   Do this

   Build your weekly application routine as a calendar block, plus a follow-up rule and a written review date with a change plan.

   Hand in: A one-page operating plan: daily counts, sourcing list, follow-up rule, review date, and the one variable you will change if it fails.≈ 40 min

   Check before you call it done

   • The daily count is written as a number and lives in a calendar
   • The follow-up rule specifies days and what new information gets added
   • The review date is a real date
   • You pre-committed to changing exactly one variable
   • You listed two sources you have never applied through before

   Mark module done

Keep learning.

Hand-picked and free. These open in a new tab — official docs, academies and channels that go deeper on what this track teaches. No affiliate links, no sign-up walls.

• Hemingway Editor

  ↗

  Run every application through it. Shorter sentences get read.

• Grammarly

  ↗

  The free tier catches the typos that get applications silently binned.

• OnlineJobs.ph blog

  ↗

  Written for employers too — read it to see what the other side is told to look for.

• Purdue OWL — job search writing

  ↗

  A university writing lab, free, with the fundamentals of letters that get replies.

Six situations that come up in real work. Pick an answer for each, then check. Nothing is recorded.

1. 01You have 200 applications sent, 120 profile views, and 2 replies. Where is the leak?

   ASourcing: you are applying to the wrong jobsBThe profile and the message: people look and leaveCInterviewing: you need practiceDNothing, the market is just hard

2. 02A job post ends with "start your reply with the word Aspen". You have a brilliant opening line. What do you do?

   AUse your opening line, they will notice the qualityBMention Aspen at the end so it still appearsCWrite Aspen first, then your opening lineDSkip the post, gimmicks are a bad sign

3. 03Which opening paragraph is strongest?

   A"Hi! My name is Joy and I am a passionate VA with 3 years of experience."B"I saw your post and I am very interested in this position."C"'Things fall through the cracks' is a follow-up problem more than an admin one, and that is the part I am good at."D"I believe I am the perfect fit for this role and would love the opportunity."

4. 04A client asks your rate on a first call. Best answer?

   A"What's your budget? I'm flexible."B"For the scope in your post, around 20 hours a week, my rate is $8 an hour and I invoice biweekly."C"I usually charge more but for you I can go lower."D"Whatever is standard for this kind of work."

5. 05You are asked to do a trial task: rebuild their entire 400-contact CRM by Friday, unpaid.

   ADo it, the experience alone is worth itBRefuse and end the conversationCOffer a scoped alternative: 20 contacts unpaid as a sample, or the full job as a paid first weekDDo half and see if they pay

6. 06Five days after applying, no reply. What is the best follow-up?

   A"Just following up on my application, please let me know."BA short note attaching the checklist you mentioned, restating your availability, and offering a paid first weekCNothing, following up looks desperateDApply again to the same post with a different message

Walk away when you see these

Not every one of these is a scam. Some are just clients who will cost you more than they pay you, which ends the same way.

• The trial task is a full client deliverable with a deadline

  That is not a test, that is a job you are doing for free. Offer a paid first week instead.

• They ask for your ID, selfie with ID, or bank details before any contract

  Documents come at contract stage, to a company you can verify. Before that it is identity harvesting.

• Interview happens entirely over chat and you are hired within an hour

  The speed is the scam. Real hiring involves at least one person's face.

• The post promises a very high rate for entry-level admin

  The number exists to switch off your judgment before the request for money arrives.

• They ask you to apply through a link that wants your email password

  No legitimate application ever needs your password to anything.

• The job post has no company name and refuses to give one

  You cannot verify a ghost, and you certainly cannot chase one for unpaid invoices.

• They want you to sign an exclusive agreement before any paid work

  Exclusivity is something you sell, not something you give away for the chance to be considered.