How to Build a Salesforce Portfolio

In the Salesforce world, your portfolio speaks louder than your resume. Recruiters want to see what you can do, not just read about what you studied. The problem is that most people don't know where to start.

And you know what Quack has seen happen many times? Candidates who show up with a practical portfolio — even a simple one — stand out immediately. It doesn't have to be perfect. It has to be real. So let's build yours.

Why a portfolio matters more than a resume

Certifications prove you know the theory. A portfolio proves you know how to apply it. And in the Salesforce ecosystem, application is everything.

When a recruiter sees that you built a functional CRM from scratch, with automations, reports, and validation rules, they no longer need to "believe" you know how to configure the platform. They can see it. The difference between "I have Salesforce knowledge" and "here's what I built" is the difference between a generic candidate and one who stands out.

Beyond that, the process of building projects is itself the best way to learn. You'll run into problems no course anticipated, research solutions in documentation and forums, make mistakes and fix them. That's exactly what happens in real work. An experienced recruiter knows this — and values someone who has already been through that experience.

Another point few people mention: building a portfolio prepares you for interviews in a way no practice exam can. When you know your project inside and out — because you built it — answering questions about it is natural. "Why did you choose a Master-Detail instead of a Lookup here?" You know because you made that decision. It's almost like a live duck debugging session — you explain your reasoning and the answer comes naturally.

Step zero: get a free org

Before anything else, you need an environment to build in. Salesforce offers two free options:

Developer Edition Org: A full, permanent org for development and testing. Go to developer.salesforce.com and create yours in minutes. This is the best option for a portfolio because the org doesn't expire. You can come back a year from now and everything will still be there.

Trailhead Playground: Created automatically when you do challenges on Trailhead. Good for exercises, but may expire after periods of inactivity. For a long-term portfolio, prefer the Developer Edition.

Important tip: create the org in English. Most real implementations use the platform in English, and having your portfolio in that language shows familiarity with the market standard.

5 projects for your portfolio

Here are 5 projects that cover essential skills and impress recruiters. You don't need to do all of them — start with whatever makes the most sense for the career you want to pursue.

Project 1: CRM for a fictitious company

Level: Beginner | Estimated time: 2–3 days

Build a complete CRM for a fictitious company (it can be a store, a clinic, an agency, a school). Choose a scenario you know — if you came from retail, build a CRM for a store. If from healthcare, build for a clinic. This makes the project more authentic and shows that you understand the domain.

Include:

• Custom objects (e.g., Products, Orders, Customers, Suppliers)
• Fields of different types (Text, Picklist, Formula, Lookup, Currency, Date)
• Page Layouts organized with clear sections and descriptive names
• Compact Layouts configured for mobile
• List Views with useful filters (e.g., "Pending Orders," "VIP Customers," "Low Stock Products")
• At least 2 validation rules (e.g., delivery date can't be earlier than order date)
• At least 1 formula field (e.g., automatic profit margin calculation)
• Sample data (at least 20–30 well-populated records)

Why it works: Shows that you understand the foundation of the platform — objects, fields, relationships, and usability. It's the most fundamental project and the one every recruiter expects to see.

Extra tip: Don't use generic names like "Object1" or "Test_Field." Use professional naming conventions as every real project requires. This demonstrates attention to detail.

Project 2: Automated approval process

Level: Intermediate | Estimated time: 1–2 days

Configure a complete approval process. For example: sales discount approval where discounts above 15% require manager approval, and above 30% require director approval.

Include:

• Custom object or discount field on Opportunity
• Approval Process with clear entry criteria
• Escalated approval steps (manager for discounts 15–30%, director for above 30%)
• Email notifications at each stage (submission, approval, rejection)
• Automatic field update on approve/reject (e.g., Status changes to "Approved" or "Rejected")
• Flow that triggers the process under the right condition
• Approval history visible on the record

Why it works: Automation is one of the most valued skills. Approval processes appear in practically every real implementation — sales, HR, finance, procurement. Showing that you know how to configure a process end-to-end is a huge differentiator.

Alternative scenarios: Vacation approval (HR), purchase approval above a certain value (finance), content publication approval (marketing).

Project 3: Executive sales dashboard

Level: Intermediate | Estimated time: 1–2 days

Build a dashboard that a sales director would use every day. The differentiator here isn't just knowing how to make charts — it's thinking about which metrics actually matter for decision-making. Explain it to me like I'm a duck... What information does a sales director need to see first thing in the morning to make good decisions?

Include:

• Pipeline by stage report (visual funnel showing how many opportunities are in each stage)
• Sales by region report (bar chart comparing regional performance)
• Goal vs. actuals (gauge chart showing how much of the target has been reached)
• Top 10 open opportunities (table with amount, stage, and expected close date)
• Sales by month (trend chart showing evolution throughout the year)
• Dynamic filters by period and team
• Alert indicators (opportunities stalled for more than 30 days, for example)

Why it works: Everyone wants data. Knowing how to build reports and dashboards that genuinely help with decision-making is a skill that separates a good Admin from a great one. Recruiters love to see beautiful, functional dashboards.

Tip: Populate with realistic data. A dashboard with 3 records is not impressive. Create at least 50–100 opportunities with varied dates, amounts, and stages so the charts tell a story.

Project 4: Custom app with Lightning App Builder

Level: Intermediate–Advanced | Estimated time: 2–3 days

Build a complete application using Lightning App Builder. Example: an internal company events management app.

Include:

• Custom App with its own navigation and a custom icon
• Custom home page with informational components (upcoming events list, counters, quick links)
• Record pages with layouts optimized for the user's workflow
• Relationships between objects (Event → Attendees → Feedback → Sessions)
• Automation with Flow (e.g., send an email reminder 1 day before the event, automatically create an attendance record)
• Contextual validation rules (e.g., don't allow registration after the deadline)
• App-specific reports and dashboards (attendance by event, average feedback score, attendance rate)
• Configured permission profile (organizers see everything, attendees only see their own records)

Why it works: Shows that you think systemically — not just configuring isolated pieces, but building a complete, coherent solution. This type of project demonstrates that you can take a business requirement and transform it into a functional app.

Alternative scenarios: Internal training management app, equipment tracking app, simplified project management app.

Project 5: Simple API integration

Level: Advanced | Estimated time: 3–5 days

For those who want to follow the Developer path or showcase technical skills:

• Use Salesforce Connect or a REST/HTTP Callout to integrate with an external API
• Example 1: Pull zip code data from a public API and automatically populate address fields when creating a record
• Example 2: Integrate with a weather API to show the weather forecast on the record page of an outdoor event
• Example 3: Consult real-time exchange rates to convert values in international opportunities
• Document the integration architecture (a simple diagram showing the data flow)
• Handle errors and edge cases (API down, invalid zip code, timeout)
• Write unit tests with a minimum of 75% coverage

Why it works: Integrations are the bread and butter of real Salesforce projects. No company operates in a vacuum — Salesforce always needs to talk to other systems. Showing that you know how to connect systems is a massive differentiator, especially for Developer roles.

How to document your projects

Having the project in an org is great, but you need to document it so recruiters can see it without accessing your org. Here's the format that works:

For each project, create a document (it can be a PDF, a Notion page, or a LinkedIn post) with:

1. Project name and context — "CRM for Fictitious Store XYZ" with a sentence explaining the business scenario. E.g.: "A clothing store with 3 branches that needed to centralize customer records and automate post-sale follow-up."

2. Problem it solves — What was the business need? Be specific. "The store was losing sales because it didn't follow up with customers who visited but didn't purchase."

3. Solution implemented — What you configured and why. List the objects, fields, automations, and reports you created. Explain your decisions: "I chose Master-Detail for the Order → Items relationship because I needed Roll-Up Summary to calculate the total automatically."

4. Screenshots — Prints from the org showing the objects, layouts, automations, dashboards. Screenshots are gold. Include at least: schema builder showing the relationships, page layout of the main object, a complete Flow, and the final dashboard.

5. Challenges encountered — What went wrong and how you fixed it. This shows professional maturity. "Initially I used a Workflow Rule, but I realized I needed more complex conditional logic and migrated to Flow Builder." Recruiters love this transparency.

6. Result — What the solution delivers (even if it's fictitious). "The system would reduce order processing time from 15 minutes to 2 minutes" or "The follow-up automation would ensure 100% of customers receive contact within 48 hours."

Tip: use Schema Builder to generate a visual diagram of your objects and relationships. It's visually appealing, informative, and shows that you know the tool.

Where to host and share

LinkedIn: Publish posts describing each project. Use screenshots and hashtags like #Salesforce #Trailblazer #SalesforceAdmin. The LinkedIn community is very active and engaged — your posts can reach hundreds of professionals in the field, including recruiters. Post during business hours to maximize reach.

GitHub: If you created code (Apex, LWC), put it on GitHub with a well-written README that explains the project, how to run it, and what each class does. Even for declarative projects, you can host documentation, screenshots, and diagrams in a repository. Having an organized GitHub shows technical professionalism.

Trailhead: Your public Trailhead profile already works as part of your portfolio. Make sure it's updated and public. Link your profile from LinkedIn and your resume.

Personal blog: If you have a blog, write about the process of building each project. Detail the decisions you made, the problems you ran into, and the solutions you applied. This shows communication skills, deepens your visibility, and creates content that recruiters can find through search.

Notion or Google Sites: If you don't have a blog, create a page on Notion or Google Sites with all your projects organized. It's free, easy to do, and generates a shareable link you can put on LinkedIn and your resume.

What truly impresses recruiters

Quack has talked with several hiring managers in the ecosystem and these are the patterns they mention:

Organization. Consistent naming conventions, clean page layouts, well-described fields with help text. It sounds like a detail, but it shows professionalism. If your fields are named "Creation_Date__c," "Dt_Update__c," and "finalDate__c," that signals carelessness. If they all follow the same pattern — "Creation_Date__c," "Update_Date__c," "Completion_Date__c" — that signals maturity.

Business thinking. It's not about creating 50 fields — it's about creating the right fields to solve the client's problem. Quality over quantity. A project with 10 well-thought-out fields impresses more than one with 40 random fields. Recruiters want to see that you understand the problem before you start configuring.

Automation. Those who show well-built Flows earn points. Automation is where real value appears — it's what transforms a glorified spreadsheet into an intelligent system. Show Flows with conditional logic, error handling, and clear documentation.

Documentation. Documented projects show that you know how to communicate what you did and why. This is essential in real work, where you need to explain solutions to non-technical people (managers, directors, end users). An Admin who knows how to document is worth more than two who don't.

Realistic data. An org with 5 generic records ("Test 1," "Test 2") is not impressive. Populate with data that tells a story. Create accounts with real company names, opportunities in different stages, contacts with varied roles. This shows you thought about the real-world use of the solution.

The portfolio evolution path

The portfolio doesn't need to be huge. Two or three well-done and well-documented projects are worth more than ten shallow ones. Here's a suggested progression:

Month 1: Complete Project 1 (basic CRM). Document and publish on LinkedIn.

Month 2: Complete Project 2 (Approval) or Project 3 (Dashboard). Document and publish.

Month 3: Complete a more advanced project (Project 4 or 5). Document and publish.

With each project, you'll be more experienced, faster, and more creative. And your LinkedIn profile will have a sequence of posts showing evolution — which recruiters love to see.

Start with Project 1, do it properly, document it, publish it. Then move on to the next. Quack it out — the best portfolio is the one that exists, not the one you plan to build "someday."

Your future employer is somewhere on LinkedIn. Show them what you can do.

---

Frequently Asked Questions (FAQ)

Can I use Trailhead projects as portfolio?

Yes, but with caveats. Trailhead projects show that you can follow instructions, which is good. But your own projects — where you defined the problem, designed the solution, and implemented it from scratch — impress much more because they demonstrate autonomy and critical thinking. The ideal is to combine both: Trailhead badges and Superbadges + original projects that show your ability to create solutions.

Do I need a paid org to build a portfolio?

No. The Developer Edition is free and permanent. It has limitations (5MB of data storage, 2 user licenses), but it's more than sufficient for portfolio projects. You don't need to spend anything except time. If you need more resources, you can create multiple Developer Editions.

How many projects do I need?

Two to three well-documented projects are sufficient to get started. A basic CRM project + an automation + a dashboard already covers the core skills recruiters look for. Quality matters far more than quantity. Quack has seen candidates with 1 impeccable project impress more than candidates with 5 shallow projects.

Can I show projects from previous jobs?

With care. Never share real client data or confidential information — that's a serious violation and can damage your reputation. You can describe the type of project in general terms ("I implemented an approval process for a financial sector company with 3 levels of hierarchy") and show screenshots of similar solutions recreated in your personal org. This approach demonstrates experience without compromising confidentiality.