← Articles

How a portfolio became the first stage of the conversation with a client

5 min read (updated: August 24, 2026)

The site showed skills, but did not make the decision easier

The first version of my portfolio did what many technical sites do: it listed tools, showed projects and ended with a form. Someone from the industry could judge whether I knew a particular technology. A business owner still did not know whether I would take over an unfinished system, whether I would say plainly that an idea makes no sense, or what the first step of working together looks like.

The problem was not the look. It was the order of the information.

Where I started the rebuild

Instead of asking “what can I do?”, I wrote down the questions a client arrives with:

  • does this person understand a situation similar to mine,
  • can they repair something left by a previous contractor,
  • will they handle the whole thing without passing me from one person to another,
  • will they tell me the project is not worth doing,
  • what do I need to prepare before the first contact,
  • how do I know the result is not just a promise.

These questions set the new layout of the site.

First the promise, then the proof

The first screen is meant to say in one sentence what I do: I repair and build systems thanks to which a company works more efficiently. I do not try to summarize the whole offer in that spot.

Lower down I show the situations in which I help most often: an abandoned system, manual work in the office, a failed attempt with AI, errors with bookings or money. Only then do specific projects appear.

The technologies are still on the site, but they play a different role. They are proof of the workshop for someone who wants to check it, not the main language of the conversation with a company owner.

Case studies have to answer three questions

Every case study starts with:

  1. What was happening in the company?
  2. What decision did I make, and why?
  3. What changed after the project?

Only the second layer explains how it was done. Thanks to this a non-technical person can understand the result, and a specialist can still check the craft.

Numbers stay only when they have a source and a context. “21 changes” makes sense if the contract contained that many items and all of them were delivered. “14 minutes” makes sense if it is the measured time of switching over a running system. A big number alone, with no point of reference, does not build credibility.

Two ways to get in touch

Not everyone wants to schedule a call right away. Not everyone can write a full description of the matter either. That is why the site offers two equal entrances:

  • a direct message for someone who knows what they need,
  • a conversation with an assistant that asks one question at a time and organizes the material.

The assistant does not price the project and does not replace me. After the conversation I get a description of the problem, the current way of working, the systems in use and the expected result. On that basis I can decide whether a short quote is enough, or whether a conversation, a paid audit or a small demo is needed.

What I removed along the way

One of the earlier versions of the site had a paid consultation run by AI. Technically it worked, but it mixed up the roles: a client could pay for an analysis I had not yet seen personally. I removed it.

The fixed promise of a reply within 48 hours disappeared too. With a well-described, small task a quote can be prepared faster. With access to someone else’s code, data or contracts, an honest assessment takes more time. One number pretended to a precision that cannot be kept for every case.

I treated random counters, English process names and sentences written mainly for other developers the same way. The site is meant to speak the client’s language, not the language of the contractor’s tools.

Eight days and 58 saved changes — what these numbers actually say

The first big stage of the build took eight days and left 58 saved changes in the project’s history. These numbers are not a promise of pace for a client. They show something else: the site was not created as one perfect project. It was published, checked and improved in small steps.

It has changed again since then — which is one of the reasons this article has an update date. Describing your own process makes no sense if the text still advertises a feature that no longer exists.

Four takeaways

A service site should help make a decision

A nice look and a list of skills are needed, but the client comes for an answer: “will this person cope with my situation?”. The layout and the text should lead exactly there.

Technical language is worth moving lower

It does not have to be removed entirely. It is enough to first explain the effect for the company, and only then how it was done.

Automation should support contact, not pretend to be it

An assistant can collect information at any hour. Assessing the sense of the project, the risk and the price stays with the person who will be responsible for the delivery.

Removing a feature can be progress

The paid conversation with AI was more complex than the current process. Removing it simplified the client’s decision and fits better with the promise of working together directly.

See what the first step looks like today.

Have a similar problem?

Describe it in your own words — you do not need to know the names of technologies or prepare a specification.

Describe the problem