A PDF resume gets skimmed. A portfolio link gets clicked. Recruiters and clients both told us the same thing: when they have 30 applicants, they open the 4 with live sites first — not because the site is fancy, but because it signals you can ship. With AI builders you can turn existing work into that link in one afternoon.

This guide is for two people: the freelancer who needs a portfolio that books meetings, and the job seeker who needs a resume site that gets interviews. The workflow is the same — the variables change.

Pick the right starting point

Two prompts, two jobs:

Portfolio — show work, not job titles. Use Build a Portfolio Website when your proof is what you made — case studies, shots, links, results:

Build a portfolio for [business_type — e.g., product designer, frontend dev, copywriter] featuring [portfolio pieces]. Pages: [pages]. Features: [filtering, lightbox, contact]. Stack: [stack]. Brand: [colors].

Resume / CV site — one page that replaces the attachment. Use Build a Personal Resume Website when your proof is what you did — roles, impact, skills:

Build a single-page resume site for [role]. Pages: [pages], features: [timeline, skills, contact]. Stack: [stack]. Brand: [colors].

Choose the portfolio if you sell services to clients. Choose the resume site if you sell yourself to employers. If you do both (most early-career folks), build the portfolio first — you can embed the resume as a page — or use Build an Agency or Consulting Website as a solo consultancy shell that includes both with team-of-one bios and case studies.

Stack pick: Plain HTML/CSS/JS hosts free on any static host and loads fastest — perfect for a link in an email signature or LinkedIn. Next.js + Tailwind if you'll add a blog, project MDX, or want image optimization for heavy portfolios. The builder prompts offer both — don't overthink it, pick the one you'll actually push to.

Structure the portfolio like a sales page, not a gallery

Galleries lose attention. Sales pages create it. Generate with this order in mind — most builder outputs follow it already, but verify:

  1. Hero — who you help and what changes. Don't write "Freelance designer." Write "I turn slow SaaS onboarding into activation that completes in one session." Use the hero constraint from our Homepage Hero Section prompt:

Write a homepage hero for [service] for [client type] where the primary benefit is [outcome]. Headline ≤8 words.

  1. Selected work — 3 case studies, not 12 thumbnails. For each project: Problem → your role → what you changed → result (metric or quote). Three deep beats twelve shallow. If you have more than three, add filtering — the portfolio prompt's features variable handles that.

  2. About — credibility, not autobiography. Two paragraphs: what you do best, and what you like working on. End with a human detail — "Based in Nairobi, async-friendly" is more memorable than "passionate about innovation."

  3. Contact — one action. One button, one form. Not "email or Calendly or Twitter or LinkedIn" — pick the one that books. The builder prompts put contact last for this reason; don't add a second CTA in the hero that competes with it.

Structure the resume site like an interview answer, not a database

Recruiters scan in layers: 10 seconds, then 60 seconds, then deep. Your site must work at each layer:

  • 10s: Name, role you want, one credibility line (e.g., "Shipped payments at [company] → 22% fewer failed checkouts"), and a contact button.
  • 60s: Timeline with verbs and results — not duties. "Led migration to Next.js, cut LCP from 3.1s to 1.1s" beats "Responsible for frontend."
  • Deep: Skills as evidence, not tags. Link each skill to the project that proves it.

Generate the resume site, then audit it with this quick test:

Would a stranger who reads only the hero and the first bullet of the first experience know what job I want and why I'd be good at it? If not, rewrite those two lines.

Turn proof into trust — the section most sites skip

Both portfolios and resume sites die without proof that someone else vouchs. Two prompts fill that gap in order:

First, get specific quotes. Before you build trust, you need material. Use Testimonial Request Email:

Ask a happy [client / manager] for a testimonial about [task — e.g., the redesign, the launch] in a way that gets a specific, usable quote, not "great service!"

The prompt's specificity is the point. "What changed for you after we shipped the checkout rewrite?" produces a paragraph you can quote. "Can you give a testimonial?" produces fluff.

Then, build the trust section. Use Trust & Social Proof Section:

Turn these into a trust section for [service/role] for [audience]: [testimonials, logos, numbers]. Present as evidence, not decoration.

Evidence language: "Helped [client] cut proposal time from 4h to 20min" — not "Loved by clients." Pair logos with a one-line outcome. Pair numbers with context. The builder prompts leave this section as placeholder — this is where you replace generic with real.

Copy tweaks that book more meetings

Two hero/CTA passes are worth more than a redesign:

Hero specificity. Run the same Homepage Hero Section prompt on your portfolio's hero and compare. The AI's constrained headline often beats your draft because it was forced to fit 8 words and a real benefit.

Fear removal. Ask this about your contact section:

A visitor wants to contact me but hesitates. What do they fear? Responses: "You'll be too expensive / too busy / too junior for this project." Add one line near the CTA that removes the biggest fear.

Example additions: "No retainer — start with one paid discovery day" or "Reply within 12 hours or I cover the first hour." One fear-removing sentence near the button lifts conversion more than a new layout.

From site to meeting — the outreach loop

A site that no one visits is a diary. Use the site as the attachment for outreach, not the destination you hope people find:

  • Link the portfolio/URL in your email signature, LinkedIn featured, and proposal footers
  • When you cold-email, paste one case-study result as proof, then link "Full story + process → [portfolio URL]/work/[slug]"
  • When you apply, replace the PDF attachment with "Resume + live site: [resume URL]" — many ATSs keep links, and humans certainly click them

You don't need SEO here — you need a link that turns a cold intro into a warm click. One good portfolio page per ideal project beats a site with twenty thin ones.

Ship today checklist

  • Pick portfolio vs. resume vs. solo agency shell
  • Run Website Information Architecture Planner if you have more than 3 pages (you probably don't)
  • Generate with Build a Portfolio Website or Build a Personal Resume Site — choose Plain HTML/CSS/JS for speed
  • Replace hero with 8-word outcome headline
  • Add 3 deep case studies or 3 results-led roles
  • Request 2 specific testimonials with the testimonial prompt, add via trust prompt
  • Ship to free static host, paste the link where people already look for you

Your work is already good enough — it just needs a URL. Start with Build a Portfolio Website and Build a Personal Resume Site, then add proof with Trust & Social Proof Section and Testimonial Request Email — all free in the Promptigo library. See also the full builder collection in 12 Prompts to Build Any Website.