‹ All work
Enterprise SaaS · Design Systems ·
Bectran ·
2026
Building Bectran’s platform design system
I built the single Figma source for Bectran’s credit platform, then linked about 17,000 hard-coded values in live product files back to it.
Company
Bectran
Role
Product Designer, owner of the design system
Team
Me, plus 2 frontend developers
Timeline
Oct–Nov 2026 (about 4 weeks)
Platform
B2B credit and AR SaaS · Figma + CSS


The short version
1 min
Problem
Every screen hard-coded its own colours, spacing and type, so developers rebuilt the same parts differently.
What I did
Defined tokens around what the product actually uses, built base components and 22 credit-application patterns, and set up a token-to-CSS handoff with engineering.
Result
185 tokens, about 30 base components and 22 patterns. One pass linked about 17,000 hard-coded values and 4,000 text layers in the main product file to the system.
My role
Owned it end to end: audit, tokens, components, patterns, migration and developer handoff.
Context
Bectran is B2B credit management and accounts-receivable software. Its main surface is the Credit Application: five tabs from Credit Request to Credit Decision. Screens were designed one at a time, so new parts piled up inside product files with no shared source.
My role
I owned the system as the product designer. I wrote the UI standard, built the library, designed the components and patterns, and migrated the live product files. Our frontend developer built the CSS from it, and the dev lead signed off on the alignment.
Research
I audited the Credit Application, Settings and Usage files against the live CSS. Credit screens were HTML captures full of raw hex values. Settings screens didn’t match each other. The CSS was written from Figma but didn’t map to tokens.
185
design tokens
~30
base components
22
credit-application patterns
No single source
Every product file hard-coded its own values and kept its own copies of parts.
Too many tokens, too few in use
Designs only used the semantic layer plus status, radius and spacing. The rest was noise.
Design and code drifted apart
CSS values didn’t map to tokens, and there was no layer from primitives to semantic tokens.
Approach
Build for the product people use today and simplify until the system is easy to use in a real file.
Write the standard
Created a UI consistency cheat sheet for cards, corners, spacing, text colours, borders, buttons and tables, then a developer one-pager the CSS was built from.
Simplify and layer tokens
Merged overlapping tokens, fixed spacing and radius scales, hid unused ones, and layered CSS from primitives to semantic tokens with --bec- names.
Build in layers
Built foundations, then base components, then patterns, so a change to Button or Table/Row reaches every screen.
A system is judged by how easy it is to use in a real file, not by how many options it has.
Solution
The library brings together 185 tokens, 16 Open Sans text styles, 62 icons, about 30 base components and 22 patterns across the five Credit Application tabs. The visuals move from colour, typography and spacing foundations into buttons, flexible cards and accordions, reusable credit patterns, and the UI consistency standard shared with engineering. One important trade-off came from the table: after trying a do-everything container and separate components per table type, I settled on a minimal row with State, Checkbox and Divider, leaving columns for designers to define. Giving Card and Accordion a Content slot replaced 20+ accordion copies with one flexible component.


01 / Colour foundations — A shared palette gives product screens named, reusable values instead of disconnected hex codes.


02 / Type, spacing and radius — Text styles and consistent scales reduce one-off decisions across screens.


03 / Buttons — Documented component states and conventions help designers and frontend developers work from the same specification.


04 / Cards and accordions — Content slots let the same component hold different screen content instead of multiplying variants.


05 / Credit Application patterns — Reusable assemblies bring the base components into the actual five-tab workflow.

06 / UI consistency cheat sheet — Practical rules for borders, corners, spacing, buttons and tables turn the library into an implementation reference.
Result
hard-coded values linked to the system
~4,000
text layers moved to text styles
20+ → 1
accordion copies replaced by one component
In the main Credit Application file, scripts linked about 17,000 colour, spacing and radius values and 4,000 text layers to the system. Design and CSS now read the same --bec- tokens. I also swapped 21 local icons for library icons. Next: publish the library and rebuild the five credit tabs from patterns. Screens migrated and development time saved aren’t measured yet.
What I learned
Most of the impact came from linking thousands of existing values, not from adding new tokens. The table taught me to cut properties: designers know their columns, and the system shouldn’t guess them.

