The Knowledge Base is the foundation of your Lancer setup. It tells the system who you are, what services you provide, and what jobs are suitable for you. By keeping it precise and concise, you’ll enable Lancer to filter out irrelevant jobs, save connects, and improve your reply and win rates.
Think of it this way:
Campaign filters remove 90% of jobs automatically based on keywords and settings.
The Knowledge Base handles the final 10% by contextually analyzing whether a job actually fits your profile.
If your Knowledge Base is too vague or filled with marketing speak, Lancer will struggle to qualify jobs. If it is short, specific, and to the point, suitability ratings will be far more accurate (up to 95–99%).
How to Fill the Knowledge Base
1. Profile Overview
This section introduces who you are and what you offer.
Bad Example (too vague and abstract):
MVP Masters is a tech partner dedicated to assisting entrepreneurs in successful developing their products. They specialize in end‑to‑end product development, streamlining workflows, integrations, and data analytics...
→ This uses marketing language with no clear focus. The tool cannot tell if you’re doing software, design, or consulting.Good Example (clear and specific):
Google Ads specialist with 9 years of experience in ROI‑focused campaigns for US and European e‑commerce businesses. Managed $31M in ad spend across 200 clients.
→ This is still slightly wordy, but far clearer. It says exactly what services are offered and to whom.
Guideline:
Be concise, eliminate fluff, don’t use abstract terms. Say plainly what you do and who you serve.
2. Core Services and Specialties
List exactly what you provide.
Bad Example: Lean engineering, scalable technologies, user‑centric design, product workflows…
Good Example: Google Ads Management, PPC Campaigns, Analytics, SEM, Consulting.
Guideline:
Keep it in a bullet list. No buzzwords. One service per line.
3. Tools, Skills, and Technologies
Provide the technical tools you actively use.
Example: Google Ads, Meta Ads Manager, Google Analytics, UGC Content, Tag Manager.
Guideline:
Just list them. No explanations needed unless the tool name is uncommon.
4. Ideal Client Profile (ICP)
Describe your target customers briefly.
Good Example: US and European e‑commerce and service businesses looking for ROI‑driven PPC campaigns.
Bad Example: Engagement‑based multi‑year strategic partnerships in product design and scaling. (Too vague, unrealistic for freelancing platforms.)
5. Projects to Avoid
This field is critical because it disqualifies unsuitable jobs.
Example: Finance industry, PR, SEO projects, small bug fixes, maintenance work, consulting-only jobs without execution.
Guideline:
Be explicit about what you don’t want. This helps Lancer filter out edge cases.
6. Spoken Languages
Add only the languages you actively work in (e.g., English, Spanish).
7. Case Studies (Optional)
If relevant, link to one or two case studies. Structure them with:
Challenge
Role
Solution
Outcome (key measurable results)
Keep it short. One strong result is enough.
Best Practices for Knowledge Base Setup
Use simple, direct language. Pretend you’re filling out a form, not writing marketing copy.
Avoid unnecessary details like total earnings, job success rates, or “great marketing speak.” The AI does not weigh these.
Use campaign filters (include/exclude keywords) for broad exclusions rather than overloading the Knowledge Base.
Treat it as a living document — update it regularly as campaigns run and you learn what jobs are being qualified or missed.