Work

DPK.bg: Making Bulgaria’s first VCC platform usable

DPK.bg is Bulgaria’s first platform for managing Variable Capital Companies, a brand-new business structure for startups and investors. Over six months I mapped the platform’s structure, gave new users a real way in, and rebuilt it on a system a small team could maintain, then redesigned the website that turned a legal concept almost nobody knew into paying users.

Role
Product design, information architecture & design system
Timeline
6 months
Tools
Figma, Adobe CC, Untitled UI
Domain
B2B SaaS, Bulgarian VCCs
The redesigned DPK.bg platform: the dashboard in front, the onboarding choice and the book of shareholders behind it

1. The brief

DPK.bg is Bulgaria’s first platform for managing Variable Capital Companies (VCCs), a new business structure built for startups and investors. It was the biggest change to Bulgarian company formation in 20 years, and almost nobody outside a small circle of lawyers had heard of it.

The core job was to make the platform usable: map its structure, give new users a way in, and rebuild it on a system a small team could maintain. A second problem sat in front of that, getting anyone to the platform at all, which the website redesign handled.

2. New users signed up, then vanished

The platform worked, but it never showed a new user how to start.

  • A dead-end first screen: a new user who registered landed on nothing. No first step, no guidance, so many never logged in again.
  • Confusing navigation: most of the sidebar stayed hidden until a company was connected, so new users saw only a fraction of the product.
  • Destructive actions out in the open: delete and remove buttons sat bright and prominent on the main pages, easy to hit by accident.
  • Nobody knew VCCs existed: the biggest change to Bulgarian company formation in 20 years was invisible outside a small circle of lawyers. The platform only mattered if people could reach it.
The original platform put company deletion on the main edit page, with the sidebar collapsed
The original platform: a bright deletion request on the company’s main page, sidebar collapsed.

3. Mapping the platform first

Before any screen, I mapped the platform.

VCCs, the admin who owns each account, the shareholders, accountants and co-managers they grant access to, and the people who belong to more than one company. The structure had to keep the active company obvious and let multi-company users switch without losing their place.

The platform’s information architecture, shown on the sidebar: the most used pages first (dashboard, book of shareholders, share transactions, general meeting, documents), company pages grouped below with the commercial register and subscription for the manager only, and the company switcher pinned to the bottom, linked to my account across all companies
The platform’s information architecture, mapped.

4. The first run, end to end

The flow that mattered most was the first one: from registration to a new user’s first real action.

In the old product it dead-ended on an empty screen. Mapping it end to end is what surfaced the three ways in (apply for a new VCC, add one that exists by its UIC, accept an invitation), a clear status while the DPK.bg team files the application, which takes up to three business days, and the first steps and tour on the dashboard.

The first-run flow: register and confirm the email, pick a way in (apply for a new VCC, add one that exists by UIC, or accept an invitation), the DPK.bg team files the application within three business days, a first-steps checklist on the dashboard, and a one-minute product tour, with an email at each hand-off
The first-run flow, from registration to the dashboard and its tour.
The first run for a new VCC: sign up, confirm the email, apply, then follow the registration from the profile. The dashboard opens once the VCC is registered.
A VCC that already exists goes straight to its dashboard, with a product tour: seven stops, from the menu to Help, in about a minute. It can be rerun at any moment.

5. Three decisions that made it usable

With the structure and first-run flow mapped, the redesign came down to three decisions: how to get around it, how to bring a new user in, and how to make destructive actions safe.

One clear navigation

Getting around was the biggest problem. Company switching lived on its own page, the active company was not always visible, and the marketing navbar and footer were still there after login, so the product felt like a logged-in homepage. Switching companies was the single most common support question.

I pulled the marketing chrome out of the app and rebuilt the sidebar as one clear navigation, with company switching pinned to the bottom so the active company is always in view.

The redesigned DPK sidebar on the book of shareholders: the most used pages on top, company pages below, company switching pinned to the bottom
A single, clear sidebar with company switching at the bottom.

Onboarding new users

Because a new user saw so little, the founders ended up walking every single one through the platform personally. I redesigned the first run around three things: a sign-up that asks what the user came to do, a first-steps checklist on the dashboard, and a one-minute tour that can be rerun at any moment.

The welcome offer over the dashboard of a company that was just added: a short tour of the platform, or not now
Once the company is added, the dashboard offers a short tour.

Safer destructive actions

Delete and remove buttons were everywhere, bright and easy to hit by accident. I moved them into a dedicated settings area, behind confirmation dialogs, and let them recede on the main pages so the primary actions lead.

Company and management: handing over the management of the VCC goes through a dialog and takes effect only when the new manager accepts
Handing over the management goes through a dialog, and it takes effect only once the new manager accepts.

6. The design system

The DPK component library: buttons, badges, inputs, selects, avatars and more, each shown in the states it ships in
The component set every screen is built from.
The DPK colour tokens: a brand indigo ramp and a neutral gray ramp, each step with its hex value
Colour tokens: the brand and neutral ramps.

7. The website: the front door

The old site was built for the wrong audience.

It assumed you already knew what a VCC was, so it skipped the teaching entirely and dropped visitors straight into long product demos they had no reason to sit through. For something almost nobody had heard of, that lost people fast.

The original DPK homepage, outdated and feature-first
Before: outdated, and written for people who already knew what a VCC was.
The original four pricing packages, with overlapping and inconsistent features
Before: four overlapping packages, sorted by feature count.

I rebuilt the homepage to start earlier: what a VCC is, who it is for, and how to begin in three steps, one scroll from “what’s this” to “this is for me.” Four inconsistent pricing packages became three clear tiers, and a blog plus an FAQ built from real user questions did the deeper teaching.

The redesigned DPK.bg homepage on laptop and phone: create and manage your VCC online
The homepage, on desktop and mobile.
The DPK.bg feature overview: creating a VCC and managing shares, explained in plain terms
What the platform does, in plain terms.
The DPK.bg getting-started section: create a profile, then register your company
How to start, in a few steps.
The DPK.bg pricing page with three tiers: Start, Pro and Premium
Three clear pricing tiers.

8. Outcomes

The design is complete and approved; engineering is scheduled for Q3 to Q4. Success will be measured on usability: whether new users can start on their own, switch companies, and manage access without calling the founders.

On the website, the payoff was concrete

  • The first paying clients ever, including foreign companies the Bulgarian-only site could not reach.
  • 24% of demos converting to paid, on a product that previously had none.
  • Registrations up 2.75x in the two months after the redesign versus the same two months before, though that window also ran social campaigns and online classes, so the redesign is one driver of several.
  • SEO at 100 on Lighthouse.

9. Takeaways

Mapping the structure and the first-run flow before touching a screen is what made the redesign coherent. The sidebar, the empty states and the demo mode all fell out of that one flow, and building on a ready-made system let a small team ship something consistent without a months-long component build.

What I would change: get the platform in front of real users earlier. It was validated with the founders and a few users, but running structured usability tests before the visual design, not after, would have caught friction sooner and given me real UX numbers to design against.

Next project

Technasium: a clearer yearly check for every school

basiseisenonline.nl is where more than 100 Technasium schools check themselves against the basiseisen every year. I redesigned how the new assessment is filled in: the flows and their edge cases, the navigation and the product copy.

Product designInformation architectureUser flowsUX writing