portfolio-building-plan

name	portfolio-building-plan
description	Builds a plan for creating a freelance or professional portfolio including content selection criteria, portfolio structure, case study format, and a 30-60-90 day publishing schedule. Produces a complete portfolio development plan document. Use when the user wants to build a professional portfolio, create a freelance portfolio website, select work samples, or plan a portfolio launch for career advancement or client acquisition. Do NOT use for personal brand strategy (use personal-brand-strategy), resume writing (use resume-bullet-writer), or website development (use web development skills).
license	Apache-2.0
metadata	{"author":"foundry-skills","version":"1.0.0","tags":"freelancing career planning template","category":"career-development","subcategory":"freelancing","depends":"","disclaimer":"none","difficulty":"beginner"}

Portfolio Building Plan

When to Use

Use this skill when the user's need centers on the portfolio artifact itself -- selecting, structuring, writing, and publishing work samples to attract clients or employers.

Trigger scenarios:

• User is a freelancer (designer, developer, writer, photographer, consultant, strategist, copywriter, illustrator, video editor, data analyst) who wants to attract inbound client inquiries through a portfolio
• User is a career changer who needs a portfolio to demonstrate competency in a new field without years of traditional experience
• User has existing work scattered across old employer servers, personal drives, and past client folders and needs a selection and organization strategy
• User is launching or relaunching their freelance practice and wants the portfolio to be the primary conversion tool for prospective clients
• User has a portfolio that is generating no leads and wants a systematic rebuild -- new case study format, updated project selection, or structural overhaul
• User is a creative professional (UX/UI designer, motion designer, brand strategist) where the portfolio IS the primary hiring credential, not the resume
• User needs a portfolio for a specific campaign -- a cold outreach to a niche industry vertical, a conference speaking opportunity, or a request for proposal (RFP) submission

Do NOT use when:

• User needs a full personal brand strategy beyond the portfolio itself -- their differentiator, positioning statement, and content marketing system (use personal-brand-strategy)
• User needs help rewriting resume bullet points or structuring work history for job applications (use resume-bullet-writer)
• User wants to actually build or code a website from scratch (use web development skills)
• User needs LinkedIn profile optimization as a standalone goal -- portfolio context may overlap but the output and criteria are different (use a LinkedIn optimization skill)
• User is asking about freelance pricing, contracts, client acquisition outreach, or business development beyond the portfolio as a conversion tool
• User needs help with a job application or cover letter tied to a specific posting (use job application skills)
• User wants a social media content strategy -- even though portfolios and social media intersect, this skill does not produce a content calendar or posting cadence

---

Process

Step 1: Gather Portfolio Context

Before producing any plan, collect the inputs that determine every downstream decision. Do not proceed with assumptions -- ask if missing.

• Profession and specialization: The type of work matters enormously. A UX designer's portfolio structure differs from a copywriter's, which differs from a data analyst's. Nail the specific service the user sells, not just a broad category.
• Portfolio purpose: Is the primary goal (a) attracting direct freelance clients, (b) supporting job applications at specific companies, (c) establishing public expertise to generate inbound interest, or (d) all three? Each goal shifts the content selection weighting and the language used in case studies.
• Target audience: Name the specific job title or role of the person most likely to evaluate this portfolio. "Hiring managers" is too vague. "Heads of Product at Series A SaaS startups" or "Marketing directors at mid-size e-commerce brands" is actionable. The target audience determines which projects to feature, which results to emphasize, and what vocabulary to use.
• Available work inventory: How many completed projects exist as candidates? Get a rough count by category (client work, personal projects, volunteer work, course projects, spec work). This determines whether the challenge is selection or creation.
• Confidentiality constraints: For each candidate project, is it (a) fully publishable, (b) publishable with client approval, (c) publishable only anonymized, or (d) unpublishable? Map this before selection -- it eliminates candidates early.
• Current portfolio status: Starting from zero, refreshing an existing portfolio that is underperforming, or doing a targeted addition of 1-2 new case studies? The phase determines the urgency structure of the 30-60-90 plan.
• Time budget per week: Get a real number. Five hours per week is common for active freelancers. Two hours per week is common for people with full-time jobs. Twenty hours per week is realistic for someone between contracts. The time budget sets the velocity of the schedule.
• Platform preference: Personal website (custom domain, hosted CMS), portfolio platform (Cargo, Squarespace Portfolio, Behance, Dribbble Pro, Contently, Journo Portfolio), PDF portfolio, or a combination. Each has different constraints on structure, interactivity, and SEO.

Step 2: Audit the Work Inventory and Apply Selection Criteria

Selection is the highest-leverage decision in portfolio building. Most portfolios fail because they include too much or the wrong things -- not because of design or writing quality.

• Apply the five selection criteria in priority order:

  1. Relevance to target audience -- Does this piece demonstrate exactly the service the user is selling to their specific target client? A brand strategist targeting fintech startups should weight fintech projects far above equally strong work in other sectors. Relevance beats recency and beats quality.
  2. Demonstrability of process -- Can the user write a compelling challenge-approach-result story for this piece? A project where the outcome was excellent but the process was invisible (e.g., the client changed direction, the work was a small component of a larger effort) is harder to case-study than a messier project with a clear narrative arc.
  3. Measurability of outcome -- Does the piece have a result that can be expressed in numbers, before/after comparisons, or a clear qualitative win? "Increased trial-to-paid conversion rate from 6% to 11%" is always more persuasive than "improved the onboarding experience."
  4. Recency -- Work more than 3 years old requires justification for inclusion. Work more than 5 years old almost never belongs unless it is genuinely landmark (a widely-cited publication, a recognized award, a project still in active use at a major brand).
  5. Variety of skill demonstration -- Across the full selected set, do the pieces collectively show the range of skills the user wants to be hired for? A portfolio of five projects that all demonstrate the same competency is weaker than five projects that demonstrate five complementary competencies.

• The optimal portfolio size is 4 to 6 pieces. Research on portfolio review behavior shows that evaluators rarely look at more than 4-5 case studies before forming a judgment. Eight is the absolute maximum. Three is workable only if all three are exceptional. One or two is never enough -- it signals limited experience regardless of quality.

• Force-rank candidates by selection score. Score each candidate project across all five criteria (1-5 scale each, max 25 points). Take the top 4-6 scorers. This removes the subjective "but I worked so hard on it" bias.

• Identify the anchor piece. The anchor is the single strongest case study -- the most relevant, most measurable, most process-rich project in the set. This piece goes first and sets the quality expectation for everything that follows. Every other piece is evaluated partly by comparison to the anchor.

• Check for skill coverage gaps. After selecting by score, map the selected pieces against the user's full service offering. If the user sells user research, interaction design, and usability testing -- but all six selected pieces show only interaction design -- the portfolio creates a false impression of narrow competency even if all six pieces are excellent.

Step 3: Handle Confidential and NDA Work

NDA situations are common enough in professional portfolios that they require a specific handling framework, not just a general note.

• Tier the confidential work: Some NDA projects can be shown with client permission (request it in writing -- email confirmation is sufficient). Some can be shown anonymized. Some cannot be shown at all. Determine the tier before writing.
• Anonymization protocol: When showing NDA work without explicit permission, replace the client name with a descriptor that communicates industry and scale without identifying the company. Format: "[Industry] [Company Size] company" (e.g., "Enterprise healthcare software company" or "Series B e-commerce startup"). Remove any logos, product names, screenshots showing real UI with identifiable brand elements, or any proprietary data.
• Focus anonymized case studies on process artifacts, not final deliverables. Wireframes, journey maps, content audits, strategy documents, and process documentation are far less sensitive than final visual designs or shipped product screens. These artifacts often tell a richer process story anyway.
• Create a verbal/slide version for NDA-heavy portfolios. If most of the user's strongest work is under NDA, recommend building a presentation-format portfolio (a deck or PDF walkthrough) designed to be presented in context rather than viewed independently. This allows the user to narrate the work -- including sensitive context -- in a meeting where confidentiality can be maintained conversationally.
• Never recommend misrepresenting NDA status. If a client discovers their confidential work in a public portfolio without permission, it creates legal and reputational risk. When in doubt, anonymize or exclude.

Step 4: Design the Portfolio Architecture

Portfolio architecture is the navigation structure, page hierarchy, and the first-impression entry point. Most portfolio platforms force a similar structure, but the decisions within that structure matter.

• Homepage design: The homepage has one job -- convince the visitor to look at the work. The headline should be a one-line value proposition, not a job title. "I help SaaS companies design onboarding flows that activate users faster" is more compelling than "UX Designer." The intro should be 2-3 sentences maximum. The featured projects should be the anchor piece plus 2-3 additional strong pieces, shown with a compelling visual and one-line context (not a full description -- save that for the case study page).
• Project page architecture: Each case study page should follow the same structure for scannability. Visitors who like the first case study will skim the structure of the second to decide whether to read further. Consistent structure removes decision friction.
• About page: The about page is the second-most-visited page after the homepage on most portfolios. It should explain the user's professional background in 2-4 short paragraphs, articulate a working philosophy or approach (this is where personality becomes a differentiator), include a professional photo (this dramatically increases conversion on freelance portfolios -- clients hire people, not anonymous entities), and include a direct call to action linking to the contact page.
• Contact page design: The contact page should set expectations, not just provide an email address. Include: response time commitment (e.g., "I respond to all inquiries within 48 hours"), current availability status (especially for freelance -- "Currently available for projects starting in [Month]"), and a brief description of what kind of projects the user is taking on. Calendly integration or similar scheduling tools on the contact page reduce friction significantly.
• Navigation order: Lead with the work. Projects should be the first navigation item. The order that converts best for freelance portfolios is: Work (or Portfolio) > About > Contact. Optional sections like Testimonials, Services, or Blog can be secondary navigation or sections within existing pages.
• Platform-specific considerations: Personal websites give full control over SEO, typography, and interaction design but require more setup. Hosted platforms like Cargo, Squarespace Portfolio, or Format are faster to launch and often have better mobile default layouts. Behance and Dribbble function as platform-native discovery tools with built-in audiences but limit case study depth. The right choice depends on how much technical comfort the user has and whether SEO or platform discoverability is more valuable to their target audience.

Step 5: Write the Case Study Template

The case study is the core unit of portfolio value. A well-written case study does three things: demonstrates competency, builds trust by showing process, and helps the prospective client self-identify ("this person has solved my problem before").

• Case study length target: 400-600 words for the narrative text. This translates to a 3-5 minute read. Shorter than 300 words and the case study lacks enough detail to build confidence. Longer than 800 words and most visitors stop reading before reaching the result.
• The challenge section (2-3 sentences) must establish stakes. Not just "the client needed a new website" but "the client's existing checkout flow had a 78% drop-off rate at the payment step, costing an estimated $40K/month in lost revenue. They needed a redesigned flow ready to ship before their peak season in Q4." The challenge section earns the reader's attention for everything that follows.
• The approach section (3-5 sentences) is where competency is proven. It must describe specific decisions and their rationale, not just a list of activities. "I conducted 8 user interviews" is a task. "I conducted 8 user interviews to surface the specific trust signals that caused users to abandon at the payment step -- a question the analytics data couldn't answer" is a decision. Show reasoning, not just activity.
• The result section (2-3 sentences) must be as specific as possible. Use numbers when available. If hard metrics are unavailable, use qualitative results with specificity: "The client reported a 40% reduction in support tickets related to onboarding within 60 days of launch" or "The project led directly to a second engagement -- a full platform redesign." If there are no results at all (e.g., a personal project that was never shipped), acknowledge it honestly and frame the learning.
• Visuals selection: Include 3-6 images or assets per case study. The most valuable visual types, in order: before/after comparisons (fastest proof of transformation), final delivered work (the hero image), process artifacts (wireframes, journey maps, research synthesis), and annotated screens (showing decision rationale directly on the design). Do not include every screen or every iteration -- select visuals that each add new information.
• Skills tags: End each case study with 3-6 skill tags that name the specific competencies demonstrated. These tags serve double duty: they help visitors quickly identify relevant skills, and they help with SEO if the portfolio is on a personal website.
• Role and context clarity: Always state the user's specific role on the project. "Led end-to-end UX design" is different from "contributed interaction design to a 4-person team." Honesty about role scope builds more trust than inflation -- evaluators often ask clarifying questions in interviews or calls, and inconsistency destroys credibility.

Step 6: Build the 30-60-90 Day Schedule

The schedule must be calibrated to the user's available weekly hours. A 5-hour-per-week plan looks completely different from a 15-hour-per-week plan. Do not produce a generic schedule -- calculate tasks against real available time.

• Phase 1 (Days 1-30): Foundation and Minimum Viable Portfolio (MVP)

  • Goal: Get something live. A published portfolio with 3 solid case studies and an about page is dramatically more useful than a perfect portfolio that is 80% done and unpublished.
  • Core tasks: Select final project list, set up the platform and domain, write the anchor case study (the strongest piece, written first while motivation is highest), write a second case study, write the about page, configure the contact page, publish.
  • Quality gate before publishing: Run the portfolio past 2 trusted peers -- ideally one who knows the user's work and can evaluate accuracy, and one who is closer to the target audience and can evaluate appeal. Ask them: "Does this make you want to hire this person? What is unclear? What is missing?"

• Phase 2 (Days 31-60): Expansion and Refinement

  • Goal: Complete the full project set, deepen the supporting content, and optimize for conversion.
  • Core tasks: Write the remaining 2-3 case studies, collect and add 2-3 testimonials (email past clients or colleagues with a specific request -- a vague "would you write me a testimonial?" produces vague testimonials; ask for something specific: "Could you write 2-3 sentences about what the project outcome meant for your team and what it was like to work with me?"), refine the homepage headline based on peer feedback, add client logos if available, optimize page titles and meta descriptions for search if using a personal website.

• Phase 3 (Days 61-90): Promotion and Measurement

  • Goal: Get the portfolio in front of the target audience and establish a feedback loop.
  • Core tasks: Update LinkedIn profile URL and About section with portfolio link, add portfolio link to email signature, send a brief personal note to 5-10 past clients or contacts announcing the portfolio (not a mass email -- individual messages), share a LinkedIn post explaining what you built and why (this performs well as a "process story" post), submit to any relevant community directories or freelance platforms, set up basic analytics (Google Analytics or Fathom if privacy-focused) to track which pages get the most engagement.

• Weekly time allocation guidance:

  • At 5 hours/week: Write one case study per week (2.5 hrs), handle platform and design setup (1 hr), and peer review/revisions (1.5 hrs).
  • At 10 hours/week: Write two case studies per week, complete setup and about page in week 1, begin promotion in week 3.
  • At 15+ hours/week: Can compress the entire MVP to 2 weeks; use remaining time in weeks 3-4 for full case study set, testimonials, and early promotion.

Step 7: Define Ongoing Maintenance Triggers

A portfolio that is published and then forgotten degrades in relevance faster than most users expect.

• Add new case studies within 30 days of project completion, when the details are fresh and the client relationship is warm enough to request a testimonial and confirm any publication permissions. Waiting longer than 60 days means details blur, assets become harder to locate, and the window for a natural testimonial request closes.
• Enforce the 4-6 project cap actively. When adding a new case study that ranks higher than the weakest existing piece, remove the weakest piece. It is tempting to keep everything, but each additional weak piece dilutes the perceived quality of the set.
• Review the entire portfolio every 6 months against the target audience definition. If the user's ideal client type has shifted (e.g., moving from e-commerce clients to SaaS clients), the selection criteria change and some previously strong pieces may no longer be the most relevant.
• Update availability status on the contact page within 24 hours of going from unavailable to available or vice versa. Prospective clients who visit and see stale availability information either assume the portfolio is inactive or feel misled when they reach out.
• Refresh testimonials annually. Recent testimonials carry more weight than ones from 3-4 years ago. Actively collect new testimonials at the close of each successful project.

---

Output Format

Produce this complete document. Replace every bracketed field with specific, researched content based on the user's inputs. Do not leave placeholder text in the output.

## Portfolio Building Plan

**Date:** [Current date]
**Profession:** [Specific role and specialization]
**Purpose:** [Specific goal -- clients, jobs, expertise positioning, or combination]
**Target audience:** [Named role/title at named company type -- not generic "potential clients"]
**Platform:** [Specific platform choice with brief rationale]
**Available hours per week:** [User's stated number]

---

### Work Inventory and Selection

**Candidate projects reviewed:** [Total number]
**Confidential/NDA projects:** [Number and handling approach]

**Selection criteria weights for this portfolio:**
1. Relevance to [target audience] -- highest weight
2. Demonstrability of process and decision-making
3. Measurability of outcome (metrics, before/after, qualitative wins)
4. Recency (prefer last [X] years)
5. Skill variety across the full selected set

**Project Selection Score Matrix:**

| Project | Relevance (1-5) | Process Story (1-5) | Measurability (1-5) | Recency (1-5) | Variety Contribution (1-5) | Total (/25) | Status |
|---------|----------------|---------------------|---------------------|--------------|---------------------------|-------------|--------|
| [Project A] | [score] | [score] | [score] | [score] | [score] | [total] | Selected / Excluded |
| [Project B] | [score] | [score] | [score] | [score] | [score] | [total] | Selected / Excluded |
| [Project C] | [score] | [score] | [score] | [score] | [score] | [total] | Selected / Excluded |
| [Project D] | [score] | [score] | [score] | [score] | [score] | [total] | Selected / Excluded |
| [Project E] | [score] | [score] | [score] | [score] | [score] | [total] | Selected / Excluded |

**Final selected portfolio pieces:**

| Display Order | Project | Client/Context | Anchor Skill | Why This Position |
|--------------|---------|---------------|-------------|------------------|
| 1 (Anchor) | [Project name] | [Client or anonymized descriptor] | [Primary skill] | [Why first -- strongest piece, most relevant, sets quality bar] |
| 2 | [Project name] | [Client or context] | [Primary skill] | [Why second -- reinforces anchor theme or adds key skill] |
| 3 | [Project name] | [Client or context] | [Primary skill] | [Why third -- adds variety or shows different context] |
| 4 | [Project name] | [Client or context] | [Primary skill] | [Why fourth -- rounds out skill coverage or industry range] |
| 5 | [Project name] | [Client or context] | [Primary skill] | [Why fifth -- optional; adds depth] |

**Skill coverage map:**

| Skill/Service | Demonstrated By |
|--------------|----------------|
| [Skill 1] | [Project name(s)] |
| [Skill 2] | [Project name(s)] |
| [Skill 3] | [Project name(s)] |
| [Gap identified] | [Note if a key skill has no demonstration -- plan to fill] |

**Excluded projects and reasons:**

| Project | Reason for Exclusion |
|---------|---------------------|
| [Project X] | [Specific reason: outdated, NDA/cannot anonymize, weak outcome, not relevant to target audience, skill already covered by stronger piece] |
| [Project Y] | [Specific reason] |

---

### Portfolio Architecture

**Site structure:**

| Page | URL Slug | Primary Job | Key Elements |
|------|----------|------------|-------------|
| Homepage | / | Convert visitors to case study readers | [Specific headline], 2-sentence intro, [3-4] featured project cards |
| [Project 1 Title] | /work/[slug] | Prove competency on anchor skill | Case study: challenge, approach, result, 4-6 visuals, skills tags |
| [Project 2 Title] | /work/[slug] | Demonstrate [specific skill] | Case study with [specific visual type] |
| [Project 3 Title] | /work/[slug] | Demonstrate [specific skill] | Case study with [specific visual type] |
| [Project 4 Title] | /work/[slug] | Show [industry/context range] | Case study with [specific visual type] |
| About | /about | Build trust and personality | [2-4 paragraphs], photo, working philosophy, CTA to contact |
| Contact | /contact | Convert interest to inquiry | [Contact method], response time commitment, availability status |

**Homepage headline recommendation:**
[One-line value proposition written in plain language: "I help [target client] [specific outcome] by [specific service]." -- not a job title]

**Platform setup checklist:**
- [ ] Custom domain purchased and connected
- [ ] SSL certificate active (https://)
- [ ] Mobile layout tested on iOS and Android
- [ ] Page load time under 3 seconds (images compressed)
- [ ] Analytics installed (Google Analytics or Fathom)
- [ ] Contact method tested (form submission or email link verified)

---

### Case Study Template

Apply this structure to every project page. Word count target: 400-600 words of narrative text.

---

**[Project Title]**

**Client:** [Client name OR Industry + Size descriptor for anonymized work]
**My Role:** [Specific role -- "Led end-to-end UX design" not just "UX Designer"]
**Duration:** [Timeframe]
**Skills demonstrated:** [Tag 1] | [Tag 2] | [Tag 3] | [Tag 4]

---

**The Challenge**

[2-3 sentences. Include: What was the client's situation? What specific problem needed solving? What were the stakes if it went unsolved? Use numbers or context that makes the problem feel real.]

**The Approach**

[3-5 sentences. Include: What decisions did you make and why? What methods or frameworks did you use and why were they the right choice for this situation? What constraints shaped the approach? Show reasoning, not just activity.]

**The Result**

[2-3 sentences. Include: What was the measurable or observable outcome? What changed for the client? What happened next (renewal, referral, implementation, publication)? If metrics are unavailable, explain what success looked like and how it was recognized.]

---

**Visuals** [Select 3-6 from the following types, in this preferred order]:
1. Before/after comparison (most immediately persuasive)
2. Final hero image (the deliverable at its best)
3. Key process artifact (wireframe, research synthesis, content audit)
4. Annotated screen or annotated detail (showing decision rationale)
5. In-context image (product in use, live environment screenshot)

---

### 30-60-90 Day Publishing Schedule

**Adjusted for [X] hours/week available.**
**MVP target:** 3 case studies + about page live by end of Day 30.

#### Phase 1: Foundation (Days 1-30)
**Goal:** Launch minimum viable portfolio. Done and published beats perfect and private.

| Week | Hours Available | Primary Task | Secondary Task | Deliverable |
|------|----------------|-------------|---------------|-------------|
| Week 1 | [X] hrs | Platform setup + domain + homepage skeleton | Draft anchor case study challenge section | Platform live at domain; anchor case study 30% complete |
| Week 2 | [X] hrs | Complete anchor case study (approach + result + visuals) | Begin second case study | Anchor case study published |
| Week 3 | [X] hrs | Complete second case study | Write about page draft | Two case studies live; about page drafted |
| Week 4 | [X] hrs | Complete third case study + contact page | Peer review pass + revisions | MVP live: 3 case studies + about + contact |

**Phase 1 quality gate:**
Before promoting, confirm with 2 trusted reviewers:
- Does the homepage headline clearly communicate who you help and how?
- Does the anchor case study feel credible and specific?
- Is the about page human and not generic?
- Does every link and form work correctly?
- Does it look correct on a phone?

---

#### Phase 2: Expansion (Days 31-60)
**Goal:** Complete full case study set, add social proof, optimize conversion.

| Week | Hours Available | Primary Task | Secondary Task | Deliverable |
|------|----------------|-------------|---------------|-------------|
| Week 5 | [X] hrs | Write fourth case study | Email 3 past clients for testimonials | Case study 4 drafted |
| Week 6 | [X] hrs | Complete and publish case study 4 | Refine homepage with feedback from Phase 1 | Case study 4 live; homepage updated |
| Week 7 | [X] hrs | Write fifth case study (if applicable) | Add received testimonials to about/contact page | All case studies live |
| Week 8 | [X] hrs | SEO titles and meta descriptions for all pages | Review skill coverage map for gaps | All pages optimized; testimonials live |

**Phase 2 quality gate:**
- All [X] case studies published
- At least 2 testimonials added
- Skill coverage map fully addressed
- Analytics showing which pages receive most engagement (even if traffic is low, the pattern matters)

---

#### Phase 3: Promotion (Days 61-90)
**Goal:** Get the portfolio in front of the target audience. Establish a feedback loop.

| Week | Hours Available | Primary Task | Secondary Task | Deliverable |
|------|----------------|-------------|---------------|-------------|
| Week 9 | [X] hrs | Update LinkedIn: add portfolio URL, update About summary | Add portfolio to email signature | LinkedIn and email signature updated |
| Week 10 | [X] hrs | Send personal portfolio announcement to 5-10 past contacts | Post LinkedIn process story about building the portfolio | 5-10 personal outreach messages sent; LinkedIn post published |
| Week 11 | [X] hrs | Submit to relevant directories or freelance platforms | Review analytics: which case studies get the most time-on-page? | Platform profiles updated with portfolio link |
| Week 12 | [X] hrs | Respond to any interest generated; refine based on feedback | Set maintenance calendar reminders | Feedback incorporated; maintenance schedule set |

**Phase 3 quality gate:**
- Portfolio link in LinkedIn profile, email signature, and at least one freelance platform profile
- Personal outreach sent to past clients/contacts
- Analytics baseline established (note traffic and engagement numbers to compare in 90 days)

---

### Maintenance Schedule

| Trigger | Action | Timing |
|---------|--------|--------|
| Complete a strong new project | Write case study while details are fresh; request testimonial within 1 week of project close | Within 30 days of project completion |
| New case study added | Review weakest existing piece; remove it if new piece ranks higher | Same day as new publication |
| Portfolio exceeds 6 pieces | Apply selection score matrix; remove lowest scorers | Immediately |
| Career goal or target audience shifts | Re-apply selection criteria; may need to retire relevant pieces and add new ones | Within 2 weeks of goal shift |
| Availability status changes | Update contact page availability note | Within 24 hours |
| Every 6 months | Full portfolio audit: recheck all project ages, refresh about page, collect new testimonials if possible | Calendar reminder: [Month] and [Month] |
| Portfolio generates no inquiries after 90 days of active promotion | Reassess homepage headline (most common failure point), then case study relevance to target audience, then platform/SEO reach | At the 90-day mark |

---

Rules

1. Never produce a plan without specific project-level recommendations. Generic "include your best work" guidance fails the user. Every selected piece must have a stated reason for selection tied to the specific target audience, and every excluded piece must have a stated reason for exclusion. Vague plans do not help users make hard decisions about what to cut.

2. The optimal portfolio size is 4-6 pieces. Never recommend fewer than 3 or more than 8. Below 3, the portfolio signals limited experience. Above 8, quality perception drops -- each piece past 6 dilutes the average. When a user insists on including more, use the selection score matrix to make the trade-off visible rather than arguing directly.

3. The anchor piece must always be displayed first and must be identified explicitly. The first project a visitor sees sets their quality benchmark for the entire portfolio. If the strongest piece is buried third or fourth, the first impression is underselling the work. Always name the anchor piece and explain why it holds the anchor position.

4. Always calibrate the 30-60-90 schedule to the user's stated weekly hours. A plan that requires 20 hours per week for someone who has 5 available will be abandoned. If the time budget is very limited (2-3 hours/week), extend the phases -- 30-60-90 days becomes 60-90-120 days -- rather than cramming the same tasks into fewer hours.

5. Case study writing must emphasize decisions and reasoning, not activity lists. "Conducted user interviews" is an activity. "Conducted user interviews to identify why qualified leads were dropping off at the pricing page -- an insight the existing analytics could not explain" is a decision with stakes. Portfolios fail most often because the case studies describe what the user did without explaining why those choices were correct. Train the case study language toward reasoning.

6. NDA work must follow the anonymization protocol -- never recommend omitting NDA projects entirely when they are the strongest work. If the best work a user has done is under NDA, anonymized case studies using the industry/size descriptor format are standard professional practice. They provide the process evidence that clients need while protecting client identity. Recommending their omission results in portfolios that underrepresent the user's actual capability.

7. The homepage headline must be a value proposition, not a job title. "UX Designer" is a label. "I design onboarding experiences that cut time-to-activation for SaaS products" is a promise. The headline is the portfolio's conversion mechanism -- it answers "why should I keep reading?" in under 10 seconds. Always draft a specific value proposition headline in the output, never leave it as a placeholder.

---

Edge Cases

User Has No Professional Work to Show (Career Changer or Student)

When the user has no paid client work, the portfolio must be built from alternative sources -- but these must be presented honestly, never misrepresented as client work.

• Acceptable alternative sources, in order of persuasiveness: (1) Volunteer or pro bono work for real organizations (a nonprofit website redesign, a community event brand identity, a local business's content strategy); (2) detailed personal projects with a real problem statement (redesigning the UX of an existing app with documented research); (3) course or academic projects that involve real methodology and deliverables; (4) speculative or "unsolicited redesign" projects where the user picks a real product or brand and applies their process to improve it.
• Frame every piece accurately. "Volunteer project for [Org Name]" and "Speculative redesign of [Product]" are honest labels that do not damage credibility -- evaluators understand them. What destroys credibility is implying client work that did not happen.
• Prioritize process depth over outcome polish. Career changers often cannot show impressive final metrics, but they can show rigorous process. A case study that documents discovery, synthesis, iteration, and decision-making is persuasive even without a live product or a measurable business result.
• Include at least one piece that demonstrates the exact type of work the user wants to be hired for -- not just the type of work they can most easily document. If the user wants to be hired as a content strategist but their only available pieces are blog posts they wrote, create a speculative content audit and strategy document for a real brand as a portfolio centerpiece.

All or Most Work Is Under NDA

When the majority of the user's best work is confidential, use a layered approach that still produces a compelling portfolio.

• Tier 1 (preferred): Contact past clients for written permission to show the work. Many clients grant permission for case studies that focus on process and outcome without showing proprietary internal data or unreleased features. Email them within a week of the portfolio project starting -- do not wait.
• Tier 2: Anonymized case studies using the industry/size descriptor format. These are standard in professional portfolios -- a hiring manager who sees "Enterprise healthcare SaaS company" understands exactly what it means and does not need the company name to evaluate the work.
• Tier 3: Process-only case studies that show research artifacts, wireframes, and decision documentation without showing final deliverables. These focus entirely on the "approach" section of the case study format and can be highly effective for demonstrating method.
• Tier 4: If most or all work is completely unpublishable, fill the portfolio with 1-2 strong personal or speculative projects that demonstrate current capability, and reserve the NDA work for private presentation in client calls (a PDF deck shown live, not published). In this scenario, the portfolio becomes a door-opener and the real portfolio lives in a meeting context.
• Never cobble together a portfolio of weak public work just to avoid showing any NDA pieces. A portfolio of five mediocre public projects is weaker than a portfolio of three anonymized case studies from strong NDA projects.

User Has 15+ Strong Candidate Projects (Selection Paralysis)

When the problem is abundance rather than scarcity, the selection process becomes the most time-consuming part of the plan.

• Apply the scoring matrix without mercy. Score every candidate on all five criteria and let the math drive the initial cut to a shortlist of 8-10. Do not allow "but I worked really hard on this" to override objective scoring.
• Apply the target audience filter as the final cut. From the top 8-10 scorers, ask: "If I could only show my target client ONE project to prove I understand their problem, which projects are strongest?" The 4-6 projects that answer that question most directly form the portfolio.
• Build a "bench" of 6-10 high-quality pieces that do not make the main portfolio. The bench serves two purposes: (1) context-specific swaps -- if pitching a healthcare client, swap in healthcare-relevant pieces; if pitching an e-commerce client, swap in e-commerce pieces; (2) insurance -- if a featured piece becomes outdated or needs to be retired, bench pieces are ready to promote without building new case studies.
• Do not build a "full archive" or "all work" section. The instinct to let visitors self-select from a large library of work sounds democratic but performs poorly in practice. Evaluators do not browse -- they scan the first few items and make a judgment. An archive section signals curation failure.

Portfolio Is for a Highly Visual Field (Graphic Design, Photography, Motion Design, Illustration)

In visual fields, the portfolio itself is a portfolio piece -- the curation, layout, and design quality of the portfolio communicate as much as the individual projects.

• The portfolio must be designed with the same rigor as client work. Typography, whitespace, color usage, and image presentation quality are all evaluated implicitly. A graphic designer with a sloppily designed portfolio signals that their standards for their own work are lower than their standards for client work.
• Image quality is non-negotiable. Export images at 2x resolution for retina displays (@2x). Use WebP format for web portfolios to balance quality and file size. Never show compressed, pixelated, or poorly cropped images. Images should occupy at least 60-70% of the visual space on case study pages in visual fields.
• Include process documentation even in highly visual portfolios. Showing only final deliverables positions the work as output rather than craft. Including sketches, concept exploration, rejected directions, and the evolution from rough to final demonstrates a design process that differentiates a professional from someone who just executes.
• Sequence images within a case study intentionally. The hero image (final, most impressive version) should appear first to establish quality. Then follow with process artifacts. Then supporting details. End with the impact statement or in-context image. Reverse-engineering from outcome to process is more compelling than chronological process documentation.
• Consider platform-specific audiences. Behance and Dribbble have built-in audiences of designers who appreciate craft and will discover work organically. Personal websites provide better SEO reach for clients searching for specific services. For visual fields, a two-platform strategy -- Behance or Dribbble for discoverability, personal website for depth -- often outperforms either alone.

User Wants a PDF Portfolio Instead of a Website

PDF portfolios have a specific use case: situations where the portfolio will be emailed to a specific recipient or presented in a live meeting, not discovered through search or platforms.

• Optimal structure for a PDF portfolio: Cover page (name, title, contact info, a single powerful image); 3-4 case study pages (one case study per page, compressed to fit); a closing page (brief summary, availability, contact CTA). Total page count: 5-7 pages maximum.
• Compression format for one-page case studies: Reduce each case study to one powerful project image (half the page), a 3-line challenge statement, a 3-line approach summary, and a one-line result with a metric. This is a teaser format, not a full case study -- it is designed to prompt a conversation, not replace one.
• Always include a link to the full online portfolio on the closing page and on each case study page. The PDF is an entry point; the website is where the full case study lives. Label it explicitly: "Full case study at [URL]".
• PDF files must be under 5MB. Larger PDFs get flagged by email spam filters and are frustrating to open on mobile. Compress images to 150-200 DPI for PDF (higher than web but lower than print). Test the file in Gmail and Outlook before sending.
• Build both a PDF and a website if resources allow. The PDF is for active outreach (cold email, RFP submissions, direct referrals). The website is for passive inbound (search, social sharing, platform discovery). They serve different stages of the same funnel.

User's Existing Portfolio Is Generating Zero Inquiries

When the portfolio is already live but not converting, the diagnosis must precede any rebuilding prescription.

• Check the four failure modes in order:
  1. Reach failure: The target audience is not seeing the portfolio at all. Check analytics -- if monthly unique visitors are fewer than 50-100, the portfolio has not been distributed enough. No amount of content improvement will fix a distribution problem.
  2. Headline failure: The homepage headline is either too generic (a job title instead of a value proposition) or too clever (obscure language that the target audience does not use). This is the single most common conversion failure point. Ask whether someone in the target audience would immediately understand who the portfolio is for.
  3. Relevance failure: The selected projects are strong work but not the right work for the current target audience. A portfolio built to attract agency clients will not convert direct brand clients even if the work quality is identical. Re-evaluate project selection against the current target audience.
  4. Case study failure: The case studies describe activity without demonstrating decision-making or results. A viewer does not finish reading and therefore does not reach the contact page.
• Do not rebuild everything at once. Fix the highest-leverage failure mode first. If it is reach failure, spend a week on distribution before touching a single word of the content. If it is headline failure, update the headline and test for 4 weeks before doing deeper rewrites.
• Add a conversion element if none exists. If the portfolio has no clear call to action on the homepage or at the end of each case study, visitors who are interested have no obvious next step. "Interested in working together? Get in touch" with a linked button converts significantly better than a portfolio that ends with the last project image and no direction.

---

Example

Input: "I'm a freelance UX designer with 3 years of experience. I want to build a portfolio to attract more clients, especially in the SaaS space. I have about 8 projects I could include, but 2 are under NDA. I can spend about 5 hours per week on this. I want to use a personal website."

---

Output:

Portfolio Building Plan

Date: [Current date] Profession: UX Designer -- specialization in SaaS product design Purpose: Attract direct freelance client inquiries from SaaS companies Target audience: Heads of Product, founders, and senior product managers at Series A-C SaaS startups, where product experience is a primary growth lever and design is typically sourced freelance or contract Platform: Personal website (custom domain, recommended: Cargo or Framer for design-forward aesthetic that communicates craft without requiring extensive development time) Available hours per week: 5 hours Schedule adjustment: At 5 hrs/week, each case study requires approximately 1.5-2 weeks to complete properly. Phase 1 (MVP launch) is set at 6 weeks rather than 4.

---

Work Inventory and Selection

Candidate projects reviewed: 8 Confidential/NDA projects: 2 (handled via anonymization protocol -- see notes)

Selection criteria weights for this portfolio:

1. Relevance to SaaS product teams -- highest weight (SaaS context is the primary filter)
2. Demonstrability of process and decision-making (especially user research and interaction rationale)
3. Measurability of outcome (activation rates, retention metrics, NPS changes, support ticket reduction, or qualitative business impact)
4. Recency (last 3 years preferred for a 3-year career)
5. Skill variety across selected set (research, interaction design, information architecture, usability testing)

Project Selection Score Matrix:

Project	Relevance (1-5)	Process Story (1-5)	Measurability (1-5)	Recency (1-5)	Variety Contribution (1-5)	Total (/25)	Status
SaaS dashboard redesign (Client A)	5	5	4	5	4	23	Selected -- Anchor
Onboarding flow redesign (Client B)	5	4	5	4	4	22	Selected
NDA: Enterprise SaaS nav overhaul	5	5	3	5	3	21	Selected -- Anonymized
Landing page + pricing page redesign (Client C)	4	3	5	4	4	20	Selected
Mobile app UX -- personal project	3	4	2	5	5	19	Selected
NDA: B2B checkout flow	4	2	3	5	2	16	Excluded
E-commerce website redesign (3.5 years old)	2	3	3	2	3	13	Excluded
Brand identity project (not UX)	1	3	2	4	2	12	Excluded

Final selected portfolio pieces:

Display Order	Project	Client/Context	Anchor Skill	Why This Position
1 (Anchor)	SaaS dashboard redesign	Client A (SaaS analytics company)	Information architecture, data visualization	Strongest SaaS case study; clear before/after; measurable outcome; sets quality bar
2	Onboarding flow redesign	Client B (project management SaaS)	User research, interaction design	Builds on anchor's SaaS theme; demonstrates research depth that dashboard piece does not
3	Enterprise SaaS navigation overhaul	Enterprise SaaS company -- anonymized	IA, stakeholder management, enterprise UX	Shows scale and enterprise context; anonymization handled; adds seniority signal
4	Landing page + pricing page	Client C (SaaS subscription tool)	Conversion optimization, visual design	Adds conversion and visual design skills; strong before/after metrics
5	Mobile app UX -- personal project	Personal project (task management concept)	Mobile UX, prototyping, self-directed research	Rounds out mobile/native skills; framed honestly as personal project

Skill coverage map:

Skill/Service	Demonstrated By
User research (interviews, synthesis)	Onboarding flow redesign (Project 2)
Information architecture	Dashboard redesign (Project 1), Enterprise nav (Project 3)
Interaction design	Onboarding flow (Project 2), Mobile app (Project 5)
Data visualization design	Dashboard redesign (Project 1)
Conversion optimization	Landing/pricing page (Project 4)
Enterprise/stakeholder UX	Enterprise nav overhaul (Project 3)
Mobile/native UX	Mobile app personal project (Project 5)
Usability testing	Not yet covered -- note for next case study addition

Excluded projects and reasons:

Project	Reason for Exclusion
NDA: B2B checkout flow	Process documentation is thin -- cannot write a compelling approach section; the interaction design skill is already covered by stronger pieces
E-commerce website redesign	3.5 years old; e-commerce is not SaaS; visual design standards have advanced since this project; irrelevant to target audience
Brand identity project	Not UX work; including it dilutes the UX specialization signal and confuses target clients about what the user sells

---

Portfolio Architecture

Homepage headline recommendation: "I design SaaS product experiences that help users reach value faster." (Specific to target audience -- SaaS PMs and founders understand "time to value" as a core activation metric and will immediately recognize the relevance.)

Site structure:

Page	URL Slug	Primary Job	Key Elements
Homepage	/	Convert visitors to case study