How do you start using Lervos for free?

You can start using Lervos for free by signing up on lervos.com — the site states that no credit card is required to get started. The exact signup flow isn't documented in the available page evidence, so treat the steps below as a general walkthrough and follow whatever the live site shows. Lervos is built for freelancers who want proposals written in their own voice rather than generic AI output, so the setup is oriented around teaching it your background once, then reusing it.

What you need before you start

• A working email address (for account creation and login).
• Your real project history: past clients, project types, outcomes, and any numbers you can cite.
• A sense of your writing rules — tone, phrases you use, phrases you avoid, formatting habits.
• At least one job post you're actually applying to, so you can test the output immediately.

The value of Lervos depends on the quality of what you feed it. A thin profile produces thin proposals.

Step-by-step: getting to your first proposal

1. Create your account

Go to lervos.com and start the free signup. The site says no credit card is required, so you should not hit a payment wall at this stage. If you're asked for payment details during signup, stop and check the current terms on the site — the available evidence doesn't describe a paid tier.

Expected result: you land in the product with an empty or near-empty profile.

2. Load your career history

This is the step that separates Lervos from pasting your resume into a chat window. Instead of re-explaining your background for every job post, you enter your real projects once. Add:

• Project name and client type
• What you actually did
• The result, with numbers where you have them
• Any tools, platforms, or niches involved

Expected result: Lervos has a stored record of your work it can draw on later.

3. Define your writing rules

Tell Lervos how you write. This is what keeps output from sounding like default AI text. Useful rules to include:

• Sentences you'd never write ("I hope this message finds you well")
• Structural preferences (short paragraphs, bullet lists, no emojis)
• Tone (direct, warm, formal, casual)
• How you open and close a proposal

Expected result: a reusable style layer applied to every proposal.

4. Paste a job post

Take a real job posting and give it to Lervos. Because the product is described as "platform-aware," it should adapt to the conventions of the platform you're applying on — a short Upwork pitch reads differently from a formal email proposal.

Expected result: a draft proposal that references your actual projects and follows your rules.

5. Review and edit

Read the draft as if a client would. Check that:

• The project examples match what the post is asking for
• No invented experience slipped in
• The opening line earns attention in the first sentence

Edit anything that doesn't sound like you, then send it.

What "free" covers — and what it doesn't

Because pricing details aren't documented here, don't assume the free tier is unlimited. Verify current limits and any upgrade prompts directly on the site before you rely on it for high-volume applying.

Common snags and how to handle them

• Output sounds generic. Your writing rules are too vague. Add concrete banned phrases and a sample of your own past proposal.
• Proposals cite the wrong projects. Your project entries are too broad. Split them by client type or skill so the right one surfaces.
• It reads like ChatGPT. You skipped the voice setup. The whole point of Lervos is remembering your rules — fill that in before generating.
• You're unsure about cost. The evidence only supports "free to start, no card required." Confirm anything beyond that on the site itself.

Who this is worth doing for

If you apply to freelance jobs regularly and lose time re-explaining your history to a chatbot every time, the one-time setup pays off quickly. If you apply rarely, or you enjoy writing each proposal from scratch, the setup cost may not be worth it. Either way, starting free with no card means you can test it on one real job post and judge the output before committing to anything.