Optimize your Malt portfolio to convert: the complete method

Before structuring your portfolio, you must understand what a client really seeks when they open it.

The client seeks 4 things in 20 seconds: 1. "Has this freelancer already done a SIMILAR project to mine?" 2. "Have they delivered measurable RESULTS?" 3. "Does the visual/quality LEVEL appeal to me?" 4. "Can I PROJECT myself: could I be their next client?"

Your portfolio must answer the 4 questions, in this order, without effort from the reader.

What your portfolio must NOT be: - An exhaustive gallery of everything you've done (nobody will scroll 40 projects) - A dump of screenshots without context - "Personal projects" put at the same level as client work (the client doesn't care about your side projects, they want real) - A list of client logos without depth ("I worked for X, Y, Z" without detail = zero impact)

Golden ratio: 5 to 8 projects max, each structured as a 100-250 word mini case study with quantified result. Period.

Measured fact: Malt profiles that go from 15 catch-all projects to 6 structured projects see their contact rate rise 40 to 70% on average. Less but better.

Here's the exact template I use on my profile and have all coached freelancers apply.

Project title (mandatory): format "Deliverable + sector + result". E.g.: "B2B SaaS SEO overhaul — +180% organic traffic in 6 months". Not "Client A" or "2024 Project".

Cover image (mandatory): screenshot or visual showing in 1 image what you did. Pro quality, consistent format across all projects.

Context (2-3 lines): who the client is (sector, size, stage), why they contacted you, what the challenge was. E.g.: "Series A fintech scale-up (60 people), losing organic traffic after a technical redesign in 2024."

Mission (2-3 lines): what you did precisely. Action verbs, no vagueness. E.g.: "Full technical audit, rewriting of 40 pillar pages, internal linking restructuring, 3-month netlinking plan."

Quantified results (mandatory, 3 lines max): raw figures, KPIs, time. E.g.: "+180% organic traffic, 12 keywords in Google top 3, ROI measured 8x over 6 months."

Techs / tools used (optional): short list of tools. Useful for matching briefs. E.g.: "Semrush, Google Search Console, WordPress, Notion."

Client testimonial (bonus): 1 sentence from the client if you can. "Levan transformed our SEO in 6 months — CTO."

This 6-block template fills in 15 minutes per project, once habit is set. It doubles the average conversion rate. It's the best time-ROI of the entire Malt profile.

The question comes up all the time: "How many projects should I put?"

Quantified answer: 5 to 8 projects. No more, no less.

Why 5 minimum? Below 5, you look like a beginner or a low-activity profile. The Malt algo considers an incomplete portfolio as a weak signal and penalizes you in ranking.

Why 8 maximum? Beyond 8, no client scrolls. Projects in position 9 to 15 are never seen, they pollute the profile without ever contributing to conversion.

Special cases: - Beginner freelancer (less than 2 years): 4-5 projects suffice, of which 1-2 can be solid personal projects or well-presented volunteer missions. - Senior freelancer (5+ years): 6-8 projects, exclusively significant client missions. - Multi-profession: separate your projects by category (2-3 dev, 2-3 design for example) but stay in the total 5-8.

Selection principle: your portfolio isn't your complete history, it's your commercial storefront. You display only projects that: - correspond to what you WANT to sell (not what you sold in the past) - have quantifiable results - are from the last 2-3 years (beyond, it's dated) - show sectors or clients that reassure your target prospects

Test: ask yourself for each project "If a target prospect opens this, what do they think?". If the answer isn't "wow, they can do the same for me", remove the project.

The cover visual of a project is what triggers (or not) opening the details. A bad visual = zero conversion, even if the text content is excellent.

What converts: - Product screenshots with context (the screen in a laptop/mobile mockup, not just the raw screen) - Before / after side by side (redesign, SEO overhaul, transformation) - Data visualizations showing results (audience graphs, revenue, conversion) - Client logos in elegant overlay (social reassurance) - Photos of physical deliverables for non-digital professions (packaging, print, events)

What makes people flee: - Blurry screenshots, badly framed, low resolution - Raw screens without staging (empty mockup, no context) - Placeholder "image not available" or default Malt visual - Generic Unsplash images with no link to the project - Inconsistent visual textures between projects (each project in a different style = amateur)

Visual coherence: all your portfolio visuals must have a coherent style. Same image format (16:9 landscape ideal), same background color palette if you use mockups, same typography treatment for titles.

Tools to create pro visuals fast: - Cleanshot X (macOS) for clean screenshots - Rotato for animated 3D mockups - Mockuuups Studio for device mockups - Figma to compose covers - Canva Pro for non-designers

Invest 3-4 hours once to redo all your visuals cleanly. It's a huge ROI over the next 12 months.

"Levan, my client didn't give me exact figures, what do I do?" Question #1 in coaching. Here are the solutions.

Solution 1 — Shared partial figures. If the client gave you figures even incomplete, use them. "Traffic multiplied by 2.5 in 4 months" is enough.

Solution 2 — Measurable qualitative figures. "From 3 to 12 qualified leads per week", "Time-to-market reduced from 6 to 2 months", "Client onboarding cut from 3h to 20 min". These operational figures are often more speaking than a %.

Solution 3 — Process figures. "Overhaul delivered in 8 weeks with 4 sprints", "Design system of 80 components", "250 pages migrated without SEO loss". This shows project size, even without business ROI.

Solution 4 — Testimonial figures. If the client doesn't give you a business figure but writes you a positive testimonial, extract the implicit figure: "According to the client: our best growth quarter", "The CTO estimates team time savings at 30%".

Solution 5 — Comparison figure. "SEO overhaul comparable to a project having generated +180% traffic on a similar mission in my portfolio (see project A)." Refer to another project whose figures you have.

To absolutely avoid: invented figures. On Malt, you risk your reputation. A client can ask to see the source, or ask you in a call to detail how you measured. If you can't explain the method, you're burned.

Safe formula: when you're not 100% sure, specify "according to client measurements" or "estimate based on internal KPIs" rather than asserting a raw figure.

The Malt portfolio displays as a grid. The top 3 projects are visible without scrolling. They decide whether the prospect continues or not.

Order rule: 1. Project #1 = your dream mission. The type of mission you want to sell most. The client instantly understands your positioning. 2. Project #2 = your most impressive result. The wow figure, the known brand, the spectacular result. 3. Project #3 = your proof of mastered versatility. A project different from #1 but in the same skill family, to show your breadth without dispersion. 4. Projects #4-8: varied, covering complementary sectors and mission types.

Not to do: display your projects in chronological order. Your first projects are often your worst. A prospect who sees your student thesis in project 1 closes the tab.

Rotation frequency: reorder your portfolio every 3-6 months. Highlight projects matching your current commercial targets. If you pivot from e-commerce to B2B SaaS, your top 3 projects must become B2B SaaS, even if you did more e-commerce historically.

SEO trick: each project title is indexed by Malt and Google. By putting your 3 key projects first with titles stuffed with target keywords ("B2B SaaS", "AI SDK", "design system"), you reinforce your main SEO signals.

Here are 5 concrete examples, real or inspired by observed Malt SuperMalter profiles.

Example 1 — Front-end developer Title: "Fintech app front rebuild (Next.js 15) — Time-to-load divided by 3" Context: B2B fintech scale-up (Series B), 40,000 active users, legacy React 16 app with critical performance issues. Mission: Progressive rebuild to Next.js 15 App Router, strict TypeScript migration, Cache Components setup, WCAG 2.2 accessibility audit. Results: Time-to-load 3.2s → 1.1s, checkout conversion rate +18%, internal product team NPS +25 points. Stack: Next.js 15, TypeScript, Tailwind, tRPC, Vercel.

Example 2 — UX Designer Title: "Industrial design system — HR SaaS scale-up (120 components delivered)" Context: HR scale-up, 3 products, lack of design coherence, 2-year design debt. Mission: Existing UI audit, tokens definition, creation of 120 Figma components in 12 weeks, dev handoff doc. Results: Product shipping cycle accelerated from 6 weeks to 3 weeks, 100% adoption by dev teams in 2 months.

Example 3 — SEO Consultant Title: "Edtech SEO migration (500k URLs) — 0% traffic loss" Context: Edtech platform with 500,000 pages, technical migration from Symfony platform to Next.js. Mission: Migration plan, 301 redirects mapping, real-time monitoring, emergency recovery plan. Results: 100% of traffic preserved, +12% in the 3 months following migration thanks to Core Web Vitals optimization.

Example 4 — B2B Writer Title: "SaaS CEO LinkedIn ghostwriting — +25k followers in 12 months" Context: CEO of a B2B SaaS startup, almost non-existent LinkedIn presence, thought leadership goal. Mission: 2 posts per week, 1 long article/month, editorial angles, quarterly planning. Results: 3k → 28k followers in 12 months, 3 qualified inbound leads/month attributed to posts.

Example 5 — Growth Consultant Title: "B2B cold outreach — 45 qualified meetings in 3 months for consulting agency" Context: B2B consulting firm, dependent on word-of-mouth, need to diversify acquisition. Mission: LinkedIn Sales Nav ICP sourcing, multi-touch Lemlist sequences, A/B-tested scripts. Results: 45 qualified meetings over 3 months, 12 proposals sent, 4 new clients signed.