What people actually paid me for
In July 2026 I read every client review and LinkedIn recommendation I had, from 2016 to 2025. They paid for understanding before drawing, judgment on what to build, and hard technical work made easy to use.
On 4 July 2016 I took an urgent one-page design job from a client on Upwork. His previous designer had used up two weeks and left. He had already promised a deadline to a partner. By 14:00 we were already working. The final files went out at 20:12 the same day.
His review said: “Yuriy saved us when our previous designer left us in the cold.”
A month later he came back on his own and invited me to a bigger job. From 2016 to 2021 he gave me five contracts in all. The last one was a long project on a self-service and back-office app. At least 3,607 of the 4,116 hours I logged on Upwork went to him. On paper I sold him design files.
Where the words come from
The base: 7 recommendations on my LinkedIn, from 2018 to 2025, and every review on my Upwork profile, from 2016 on. I had never read the recommendations together, though they had been on my profile since 2018.
From 2016 my freelance clients came through Upwork. That stopped in 2022, when I went full-time and stopped looking for clients.
What they said and what they bought
The table uses 5 of the 7 recommendations and 3 Upwork reviews: six people in seven rows, and the first three rows are one client. The right column is my reading of what they bought.
| Who, when | What they said | What they bought |
|---|---|---|
| Upwork client, 2016 | “saved us when our previous designer left us in the cold” | A deadline kept after someone else dropped it |
| The same client, on a 2016-2018 contract | “wants to know everything about the customer needs and problems before he starts work” | Understanding before drawing |
| The same client, now founder and CEO, 2022 | “simplifying the screens”, “discipline to do this remotely” | A complex domain made simple, without anyone managing me |
| Product lead, 2023 | “bringing together complex technical implications with an easy to use design”, “with confidence” | Hard technical work made easy to use, delivered with confidence |
| Senior director of product, 2024 | “great sparring partner when discussing the overall conception” | Judgment on what to build |
| Engineering leader who founded and sold a software company, 2024 | “significantly increased the value we deliver to our customers”, “commitment to measurable outcomes” | Value that reached his customers, with outcomes that could be measured |
| Upwork client, 2018; senior frontend developer, 2025 | “dual skills as a designer and frontend designer”, “first-class designer and project manager” | Design, code and leading in one person |
Of about 13 different clients on Upwork (some had several contracts), 8 started with a small first job and came back for more. One wrote in 2018: “we still work together.”
The one word I would put under the table is judgment: deciding what to build before drawing it.
What I thought I was selling
My Upwork jobs had titles like “PSD design for web application”, and the judgment behind the files came as a bonus. In September 2023, writing a line for my CV, I noted: “SaaS dashboards are the client’s product, not mine. I make design that increases profit and client satisfaction.” Still, until July 2026 my clients had put my value into words more clearly than I had. In June 2026 I noted that I had not shown my strengths or put them into words.
I also believed my sales were weak because my portfolio was weak. When I went through all my Upwork contracts in July 2026, no sale came from the portfolio. The long client came from my reply to an urgent job post, and most clients came in through a small test task.
How I work now
My job today is at WebPros, on Riva, an AI-visibility product (search and visibility in AI assistants). I have worked on it since its first version.
In October 2026 I wrote down what design is for me: a business talking to its users, so that they see the value of the product and pay for it. The person who runs the business brings me that communication task, and I solve it. My first job is to work out the goal with that person until it is clear. A person may see the goal only roughly, or pick a means that will not get them there. With a new client I start with a diagnosis: an honest picture of how things work now, from facts rather than from what the team says about itself.
Then I build it myself. The one line on my site says: “I find what a product’s users will pay for, and I build it until it works: with the owner on the money, with the engineers in the code, with no handoff in between.”
I am the designer, the prototype front-end and the researcher on the same piece of work, so nothing waits for a handoff between them. Since 2014 I have built prototypes in code myself. On a short-term apartment rental product, where I worked from 2014 to 2018, I built an HTML prototype in 25 iterations. The product I built this way, alone, is Say in Place, voice typing for Mac: read the case.
My condition: I join a team where one lead holds the product and answers for the result. I say so before a deal. Where the process exists for its own sake, I am the wrong person.
What I do not know yet
The data leans on one client. He gave me at least 3,607 of my 4,116 Upwork hours, so the pattern rests on him more than on anyone else. Since 2022 no client work has come to me through a platform, and no deal has tested my current rate yet.
If you are hiring a design engineer for an AI product, or you own a product and want this, write to me: yuriybalaka@gmail.com.