Skip to content

© 2026 Serhii Lanchukovskyi

UA
sergius.design.ua@gmail.comTelegram opens in a new tabWhatsApp opens in a new tabLinkedIn opens in a new tab

Two kinds of work.

I handle both myself: research, design, the system, and for websites, the build too.

Product design

For teams building software people work in for hours — admin panels, customer portals with roles and permissions.

  • Research and competitor analysis

    I look at how others solve this, and where that would fail in your case.

  • Information architecture and user flows

    Where everything lives, and the steps a person takes to get a result.

  • Wireframes for the key screens

    Layouts without colour or type: we agree on what the screen says first.

  • Interface design — desktop and mobile

    Finished screens at both sizes — desktop and phone.

  • Roles and permissions, mapped screen by screen

    Who sees what and who can press what — written out role by role.

  • Every state: empty, loading, error, overflow

    The screen with no data yet, and long lists and tables, are drawn too.

  • Design system on tokens, light and dark themes

    Colours, type and spacing as a set of values, not a description in a document.

  • Handoff your developers can build from

    Files and notes your developer can build from without coming back to me.

I design it. Your team builds it.

The handoff is written so your developers don’t need me. For 30 days after handoff I answer their questions anyway. After that — by the hour, whenever you’re ready to start.

Websites, end to end

For a business that needs a working site — not a folder of mockups waiting for a developer.

  • Structure and information architecture

    How many pages, what goes on each, and the order they are read in.

  • Copy drafted together with you

    I ask the questions; we turn your answers into text, block by block.

  • Design

    Every page designed at both sizes — desktop and phone.

  • Next.js build

    I write the code myself — no handoff to another developer.

  • A CMS your team can edit without me

    You change copy and images yourself, without touching the code or needing me.

  • Two languages, if you need them

    The second language is built into the structure from the start.

  • Deploy, domain, analytics

    The site goes live on your domain, with analytics set up.

  • A month of support after launch — fixing what breaks

    If something breaks after launch, that is my job, not a new project.

I design it and I build it. One person from the first screen to the live site.

Starting prices. The exact quote comes after the brief.

First stage — audit and scope

from $500

A written scope, the information architecture, wireframes of two key screens, and a first draft of the copy for each block.

3–⁠5 working days.

If we continue, it comes off the project price. If not, the document is yours to keep.

Admin panel or customer portal

from $3,200

Design and the design system underneath it. Desktop and mobile, both themes, every state, roles mapped screen by screen.

Support · 30 days after handoff included, then $32/⁠hour

Website, 5–⁠10 pages with CMS

from $2,800

Structure, design, Next.js build, a CMS your team can edit, deploy, domain, analytics.

Copy · two rounds of revision included

Support · a month after launch, fixing what breaks

Landing page, end to end

from $1,200

One page, built and live. Same stack, same CMS, smaller scope.

Copy · two rounds of revision included

Support · a month after launch, fixing what breaks

Tell me about your project

What affects the price

  • How many screens, and how many of them are genuinely different
  • How many roles, and how far their permissions diverge
  • Whether the content exists or has to be made
  • Integrations — payments, analytics, anything with an API
  • Whether we keep an existing system or build a new one
  • One language or two

All of this gets written down in the first stage, before anyone commits to anything.

Timelines

Landing page
7–⁠10working days
Website, 5–⁠10 pages with CMS
16–⁠25working days
Admin panel or customer portal
from 20working days

The clock starts when the materials are in — copy, logo, photos, brand colours if you have them. Not on the day we agree.

Working days, not calendar days. If you reply within two working days, the schedule holds. If it takes longer, it moves.

For reference: a customer portal and an admin platform, ten-plus sections each. Both ran in parallel and took three to four months.

Common questions

Do you design mobile apps?

Not as a separate service. Mobile is part of the work when the product has an app — as it did with MusConv. If a mobile app is the whole project, write anyway and we’ll see if it fits.

Will you work with our existing designer or design system?

Yes. Extending a system someone else started is normal work — often more useful than replacing it.

Does every project need a design system?

No. Sometimes a style kit is enough, and I’ll say so before you pay for more than you need.

Do I have to pay for the first stage?

Yes, and it’s the cheapest way to find out whether we should work together. If we continue, it comes off the project price. If we don’t, the document is yours, and any other designer can work from it.

How does payment work?

50% before the start, 50% before launch. Project work is not billed by the hour.

What do you need from me before we start?

Copy, logo, photos, any brand colours you already use, and a couple of competitors you like. I don’t write copy from scratch and I don’t design logos. I take colour preferences as a direction and build the palette myself.

I don’t have copy and I don’t have a copywriter. What then?

We make a first draft together. I ask the questions, we turn your answers into text block by block, and you approve every line. I use AI for the draft, the same way I use it for code.

What stays with you: every claim, number, and promise in the text. I can’t verify facts about your business.

English is not my first language. For English copy I’d recommend a final read by a native speaker before launch.

Two rounds of revision are included. After launch you edit the copy yourself in the CMS.

I don’t have photos either.

Then we talk it through: you send them later, or I generate them. Generated images are a fallback. If you’d rather not use them, say so early and I’ll plan around it.

What if my team starts building six months later?

That’s fine. The 30 included days run from handoff, and once development starts, I’m available by the hour.

What about NDAs?

Yes, with one condition: I keep the right to show the work in my portfolio. If the project cannot be shown as it is, we agree in advance on an anonymised version — no client name, no numbers.

Can we talk on a call?

In Ukrainian, yes. In English I work in writing — email or Telegram — and reply within 40 minutes on weekdays.

Not sure which one you need?

Describe what you have and what’s missing. If it’s neither of these two, I’ll say so.

Tell me about your project