The LIKIOMO team has something new.

Check out what's new

Worker documentation

Earning on LIKIOMO

This guide is for people who complete microwork: short, spec-driven tasks with clear rewards, escrow-backed budgets, and review before payout. You will see how to read briefs, submit proof, handle rejections and appeals, grow reputation, and stay safe from scams. Teams who post work should read the hirer guide instead.

Browse microwork jobs

Is microwork a fit for you? Payouts & safety FAQs support@likiomo.co.uk

Microwork pays when you treat each HIT like a mini contract: read the brief, meet the proof bar, respect deadlines, and use appeals with evidence—not arguments. Good standing unlocks harder categories and steadier throughput over time.

See what flexible tasks look like

Sample work

LIKIOMO lists short tasks—surveys, labeling, reviews, and similar HITs—with the reward, time estimate, and proof requirements shown before you accept.

Further down this guide we cover payouts and approvals, how quality affects your access to work, and safety practices on the platform.

What you actually do on LIKIOMO

LIKIOMO is built around human-in-the-loop microwork: short tasks a person can finish in one sitting with a defined outcome—surveys, labeling, moderation samples, transcription snippets, QA screenshots, ranking exercises, and similar HITs. Each posting states the deliverable, time estimate, reward, and proof format.

You choose tasks that match your skills and schedule. You are not an employee of LIKIOMO or of the requester; you are an independent participant completing defined work for an agreed price under the platform rules.

Three habits that protect your time

Read the instructions before you accept. Submit proof exactly as requested. Keep communication and files inside the product when the job requires it—off-platform handoffs are where disputes and scams concentrate.

Who microwork fits (and who should pass)

There is no single “ideal worker,” but patterns matter. Use the cards below to sanity-check whether this marketplace matches your goals before you invest hours calibrating on tough categories.

Students & career switchers

Top-up income between classes or interviews; build discipline with specs and deadlines. Expect async review, not instant approval on every submission.

Remote side earners

Stack small wins across evenings; diversify categories so one slow queue does not zero your week. Track hourly yield honestly after rejections.

Multilingual contributors

Locale-specific QA, translation checks, and cultural nuance tasks often pay a premium when eligibility is restricted—keep proof of language capability where the product asks for it.

When to skip

If you need guaranteed full-time hours, same-day pay on every HIT with no review, or tasks with no written acceptance criteria, microwork marketplaces will frustrate you—better to pass early.

Task types, proof, and quality bar

Most disputes come from ambiguous instructions or proof that does not match the brief. Your job is to reduce ambiguity on your side: quote the instruction line you followed when you appeal, and attach the evidence the rubric asked for.

  • Read before accept: unclear scope is a valid reason to skip—saving a rejection is cheaper than fighting one.
  • Proof formats: URLs, screenshots, uploads, or in-form fields—use exactly what the HIT names; crop screenshots so the reviewer can verify the claim.
  • Deadlines: late work may auto-decline depending on job settings; partial work rarely pays unless the brief explicitly allows it.
  • Original work: unless templates are allowed, duplicate or copy-paste submissions across accounts are treated as fraud.
  • Uniqueness checks: some jobs enforce IP, device, or account rules for research integrity—follow them; evasion risks suspension.
Quick self-check before you submit
  • Does my proof show every element the acceptance sentence requires?
  • Did I stay within prohibited content rules if the brief lists them?
  • If the task failed (empty model output, broken link), did I follow the stated failure-mode path?

Lifecycle from accept to payout (worker view)

  1. Discover & filter. Use reward, time, and eligibility filters that match your device and region.
  2. Accept. You commit to the posted terms; the hirer’s budget is typically held in escrow so unpaid work is less likely—still read the fine print.
  3. Execute once. Complete the atomic outcome; do not split one HIT across multiple interpretations unless instructed.
  4. Submit proof. Upload or link exactly as specified; add notes only where the form asks.
  5. Review. Requesters approve, reject with structured reasons, or request rework per their settings.
  6. Appeal (if offered). Use the window and attach evidence; cite instruction clauses, not tone.
  7. Payout path. After approval, earnings follow wallet rules shown in-product (pending periods, fees, withdrawal minimums).

If something feels off—copy-pasted briefs, requests for passwords, or “pay us to unlock tasks”—stop and contact support. LIKIOMO does not run pay-to-unlock task scams.

Escrow, wallet, and payouts

When a hirer funds a task, funds are typically held in escrow until completion and approval. That protects you: the budget is committed before you invest time, provided the job was funded as shown in the UI.

After approval, balances move according to wallet settings—available vs pending, withdrawal rails, and any displayed fees. Timelines are shown in-app; they can vary by method and region.

  • Never pay an upfront fee to “unlock” tasks—walk away and report it.
  • Keep disputes inside platform flows; private settlement bypasses protections for both sides.
  • Save job IDs and submission IDs when chasing a payout question—support resolves faster with IDs.
What to include in a payout support email
  • Account email and approximate timestamp.
  • Job or batch ID and submission ID from your dashboard.
  • Expected vs actual balance movement.

Accounts, reputation, and fairness

Your account stores completion history, ratings where applicable, and signals that help requesters trust your work. Good standing unlocks access to higher-paying categories over time; sudden quality drops or policy violations can remove access to sensitive queues.

Requesters can approve, request revisions, or decline submissions that miss the posted criteria. If you disagree, use the appeal or support path in your dashboard—do not try to settle disputes off-platform with the hirer in ways that bypass marketplace records.

Consistently excellent work is not just “nice”—it compounds into priority access when demand spikes for a category you have already proven.

Safety, fraud, and device rules

Some jobs enforce uniqueness (IP, device, or account checks) to protect research integrity or ad spend. Attempting to game those checks can mean forfeited pay and suspension—the risk is not worth a single HIT.

Watch for phishing: LIKIOMO staff will not ask for your password or payment to “verify” your account. Report copied job postings, off-platform payment requests, or unknown binaries.

Red flags (non-exhaustive)

Requests for banking PINs, government ID sent over random chat, installation of unsigned desktop agents, or “send crypto first” are incompatible with safe microwork. Decline and report.

Is LIKIOMO microwork a fit for you?

Use this table honestly. If you land mostly on the left, you will likely enjoy the rhythm; if mostly on the right, consider other income paths or start with very small batches to validate.

Strong fit Pause and reconsider
You read specs carefully and follow checklists. You prefer unstructured creative work without acceptance criteria.
You are OK with asynchronous review delays. You need every pound released within minutes, every time.
You can provide crisp screenshots and structured proof. You dislike documenting your work for someone else’s audit trail.
You will keep work inside the platform when required. You want to move payment or files off-platform “for speed.”
You treat appeals as evidence-based, not argumentative. Every rejection feels personal; you want to debate in chat.

Help, appeals, and contact

Workers get fastest help when tickets include IDs and timestamps. For payout or account lockouts, use support. For harassment, scams, or illegal task content, report immediately—your report protects the next worker in the queue.

Worker support

Email support@likiomo.co.uk from your account email. Include job or submission IDs, what you expected, what happened, and any screenshots that are safe to share. General questions can go to info@likiomo.co.uk.

Email support

Contact form

Use the secure form if you prefer structured fields or cannot access email on this device. Pick the closest topic so routing stays accurate.

Open contact form

Public FAQs

Payout timing, devices, and safety basics are covered on the home FAQ—good first stop before you open a ticket.

Read FAQs
Worker FAQ — plain answers

Do I work for LIKIOMO?

No—you complete tasks for requesters under marketplace rules; you are not an employee of LIKIOMO.

Can I appeal every rejection?

Only where the product exposes an appeal window; cite the instruction text and attach the proof the rubric asked for.

Will every task pay the same hourly rate?

No—effective hourly rate depends on your speed, rejection rate, and queue mix. Track it honestly.