Most of Design Independent digital practice led by Oleg Zybailov Design · Build · Automate

Identity built as a system, not a logo.

I work from the visual logic through marks, typography, packaging, print and the rules that keep everything coherent once other people start using it.

My industrial-design background shows here: construction first, decoration second. A brand is not finished when the presentation looks good. It is finished when it still works in print, on packaging, in a partner deck and in another designer's hands.

You get the assets and rules the project actually needs — formats, type, colour, production guidance and a usable system. No oversized brand book unless there is a reason for one.

IdentityVisual systemsPackagingPrintGuidelines

Sites that ship, not decks about sites.

Design and build stay in the same loop, so less gets lost between the mockup and the browser. Structure, content, interaction and implementation are considered together rather than treated as separate stages.

Design and code are written in the same session, which is where the speed comes from — days where an agency quotes weeks. This site was built exactly that way, so the claim is one you can test before hiring anyone.

Responsive behaviour, accessibility, performance and real-world edge cases are part of the product — not decoration added once the desktop screen is approved.

Launch is not the end of the relationship. I can stay with the site for changes, new sections, maintenance and long-term support. When additional engineering capacity is needed, I bring in trusted collaborators while remaining accountable for the outcome.

DesignBuildResponsiveAccessibilitySupport

Digital products built around a job that needs doing.

I turn rough ideas, spreadsheet-heavy processes and awkward workflows into focused tools people can actually use: prototypes, MVPs, internal applications and purpose-built digital products.

The scope stays pragmatic. Start with the smallest useful version, put it into the real workflow, then add what proves necessary instead of designing an imaginary platform upfront.

A real example is a custom reporting generator already used in client operations.

PrototypesMVPsInternal toolsCustom applications

Automate the work that should not stay manual.

I look for repeated steps, duplicated input, recurring reporting and hand-offs between tools, then design a simpler flow around them. Sometimes the answer is an integration. Sometimes it is a small custom tool. Sometimes an entire manual step can disappear.

The point is not automation for its own sake. It is less repetitive work, fewer places for errors to enter and more time spent on the parts that still need a person.

The goal is not dependence on me. It is a system that keeps doing its job — with support available when the business, the data or the workflow changes.

WorkflowsAutomationIntegrationsReportingSystems

3D visualisation, modelling and animation for products, campaigns and digital experiences.

This is one of the longest-running parts of my practice, rooted in industrial-design training and years of Autodesk-based production.

The object, material, light, camera and movement are treated as one system rather than separate effects. The same construction-first thinking applies whether the output is a product render, a sequence or an asset built for the web.

You get finished frames or motion plus organised source scenes, so the next piece of work does not have to start from zero.

VisualisationModellingAnimationMotion