How many projects should a portfolio website have?

Three, chosen to point at the work you want next. A client reads two or three items and leaves, so extra pieces do not add reach, they lower the average. Swap your weakest piece when a better one arrives instead of adding to the pile.

What do you write about each project in a portfolio?

The task, the constraint, the decision you made, and the result. The artefact proves you can produce a thing, while those four lines prove the judgement that produced it, and judgement is what a client is actually buying.

Can an AI agent build my portfolio website?

Yes, and that is the normal path here: you write the cases, the agent writes the page and publishes it to a live address. There is no editor to learn, and an update later is another sentence rather than a session in a builder.

Should a portfolio be one page or several?

One page until a single piece needs its own room. Three cases fit comfortably on one page, and a visitor who has to click into each project usually clicks into none. Once a case has a real story to tell, give that one a page and keep the overview short. The website layouts breakdown covers the portfolio grid.

What makes a portfolio look unprofessional?

Text baked into images, a first screen that does not say what you do, contact details only at the very bottom, and photos so heavy the page loads while somebody is deciding to leave. Reviewed examples with the same failures are in portfolio website examples, and the version for people without client work yet is student portfolio examples, where five of the fifteen widely cited portfolios we opened did not even load.

How to Make a Portfolio Website You Can Send to a Client

Q: How do you make a portfolio website with no experience?

Build one real thing for a real situation, then write it up with the same four lines: a local shop with no site, a friend's event, a tool you needed yourself. One genuine piece with a written result carries more weight than several course exercises or a redesign of a famous app.

Three pieces of work, each with a task, what you did, and the result

Contact details at the top. That is the shape of a portfolio that gets replies, and the rest of this page is how to make a portfolio website with it.

You describe the work to an agent connected to Birta, it writes the page and publishes. Then you send the link.

Pick three pieces, not twelve

Pick by the work you want next, not by what you finished most recently. Three pieces that all point at the same kind of job read as a specialism. Twelve that point everywhere read as a search history.

Someone deciding whether to contact you looks at two or three things and leaves. The fourth piece is not read, so its only effect is diluting the three that were.

If a piece embarrasses you, cut it. A portfolio is judged on its weakest visible item, because that is the one a client imagines receiving.

Write one case, then reuse the shape

Most portfolios show the artefact and stop. The artefact proves you can produce a thing. What a client is buying is the judgement that produced it, so write the judgement down.

Four lines per piece:

The task. What the client needed, in one sentence.
The constraint. The budget, the deadline, the legacy system, the founder who wanted it purple.
What you did. The decision you made, not the tools you opened.
The result. A number if you have one, an outcome if you do not.

Here is that shape filled in:

One case, written out

Bakery site, three weeks, no photographer. The owner had 40 phone orders a week and no way to take them outside opening hours. Budget covered one page, and every photo had to come from her phone.

I built one page around the order form and shot the products on a windowsill against paper. The menu became text rather than images, so it stays readable and takes seconds to update.

Phone orders dropped to about 15 a week. The rest arrive as forms overnight.

That is 90 words and it contains a problem, a constraint, a decision and a result. It is worth more than six screenshots.

When the work is thin or under NDA

Three situations, three honest answers.

Under NDA. Describe the problem and your approach without naming the client or showing the screen. "A logistics dashboard for a client I cannot name: 40 daily users, the brief was to cut a 12-click task to 3." Nobody needs the pixels to see the thinking.

Client work you cannot show at all. Redraw the artefact as a generic version. Change the brand, keep the structure, and say plainly that it is a reconstruction.

No paid work yet. Build one real thing for a real situation. A local shop with no website, a friend's event, a tool you needed yourself. One genuine piece with a written result beats five exercises from a course everyone else also took.

What does not work is filling the gap with mockups of famous apps. Every reviewer has seen the redesigned Spotify screen, and it tells them nothing about how you handle a brief.

Tell the agent what to build

Paste this with your three cases in it. The four lines per piece are the part that matters, so write them before you open the chat.

Build me a portfolio page and publish it on Birta.

Me: [name, what I do, city if it matters]
Contact: [email, and the one other channel you actually answer]

Piece 1:
- Task: [what the client needed]
- Constraint: [budget, deadline, whatever was hard]
- What I did: [the decision]
- Result: [number or outcome]
- Images: [file names, or none]

[Repeat for pieces 2 and 3.]

Rules:
- Contact details visible at the top, not only at the bottom.
- Each piece: the four lines as text, images second.
- Text stays selectable text, never baked into an image.
- Mobile first. I will look at it on a phone before anything else.

Ask it to show you the first case before it builds all three. If the shape is wrong you want to know once, not three times.

Publish it and check it like a stranger

Step 1PublishYou get a live address you can send to anyone.
Step 2Open it on a phoneCheck the first screen says who you are and what you do.
Step 3Check the imagesHeavy photos are the usual reason a portfolio loads slowly.
Step 4Click your own contactA mailto that does not open is a portfolio that gets no replies.

Open the live address on a phone, then hand the phone to somebody and ask what you do for a living. If they cannot answer in ten seconds, the top of the page is the problem and no amount of work further down fixes it.

Photos of work are usually the heaviest thing on the page. Ask the agent to resize them to the width they are actually displayed at, which is the difference between a portfolio that opens instantly and one that loads while somebody is deciding to leave.

Put your own domain on it

A portfolio at your own name reads differently from one on a shared address, and it is usually the first thing people upgrade. Connect a domain you own and the site answers there. That step is where the page becomes a real site with an address of its own, on Solo, the first paid plan.

The custom domain walkthrough covers the DNS records, which is the only part that can go wrong.

Keep it current without rebuilding it

Publishing again keeps the same address, so the link in your email signature never goes stale. When a new piece is better than your weakest one, swap them. That keeps the portfolio at three and keeps the average up.

Old versions stay where they are, so a rewrite you dislike takes a rollback rather than a rebuild.

Describe three pieces of work, get the portfolio

Your agent writes the cases into a page and publishes it at an address you can send.

Connect your agent to Birta