Davit Arakelyan
← All work
Case study · Fictional brand concept · 2026

Haybeck Accounting Portal

Identity, a design system shared by four products, a homepage, a client portal, a tax-return flow and a staff tool for an accounting firm in Saskatoon that serves owner-run businesses and farms, in English and French.

Not a real company. Haybeck, its offices, people, clients and every figure in the mockups, including the pilot results, are fictional, made for this portfolio concept.

Haybeck cover: the mark on yellow, the line “One system, four products.” and product tiles for Portal, Tax and Advisory
Fig. 01Work cover: the mark on canola yellow and the same request card in three products.
Role
Brand identity, design system, product UI
Scope
Self-initiated concept
Year
2026
Deliverables
Identity, design system across four products, homepage in light and dark, client portal, tax flow, staff tool, phone screens in English and French, banners
01The brief

One design system, many products, two languages.

Accounting firms that serve owner-run businesses rarely sell one product any more. There is a public site, a client portal for documents and payments, a tax-return flow, advisory dashboards and the tools staff use behind them. Each tends to grow its own look, and the client feels the seams at the worst time of year.

So this concept is less a homepage and more a study in how I’d grow a system like that: one library that serves a client portal, a tax product, an advisory product and an internal staff tool, in light and dark, in English and French, without any of them forking.

  1. Open on a promise a business owner can act on, not on the latest news item.
  2. Make the client software the story: show what a document request looks like, why it’s needed and by when.
  3. Give every product the same parts, and let a product change only one accent colour.
  4. Treat French, dark mode and keyboard use as part of each component, not a later pass.
  5. Design the hard states first: a missing page, a locked signature, a first day with nothing in it.
  6. Keep every number honest: all figures here are invented and labelled as such.
02Naming

A name that sounds like a founding partner.

Accounting firms are usually named after people, so the name had to read like a surname, be easy to say in English and French, avoid sets of initials, and share nothing with any real firm or with the other brands in my portfolio.

I checked each finalist three ways: domain records for the dot-com, dot-net and dot-ca, web searches for accounting, tax and software companies with the same or a similar name, and a comparison by sound and spelling.

  1. Haybeck, chosen. “Hay” for prairie farms, “beck” an old word for a stream. All three domains were free when I checked, and I found it only as a family name.
  2. Lundquill, second. A quill on the land, but it reads like a misspelt surname.
  3. Corlander, third. Practical and rooted, but too close to a herb.

Several others fell at the first check because a small accounting firm or a piece of accounting software already used something close. I did not search the trademark registers, so a formal search is needed before any real use. These are concept names only.

03Identity

The double rule under every total.

The mark is an H standing on two lines: the double rule an accountant draws under a final figure. It is the one promise the firm makes, that you’ll know the total before it’s due. The tile is canola yellow, from a field in July; everything else is ink and paper.

The Haybeck mark, an H on a double rule, and the logo on four grounds
Fig. 02Mark and logo on paper, night, canola and frost.

The mark sits on a small square grid so it stays sharp at the size of a browser tab. Below the smallest size the lower rule merges into the upper one and the tile stays square.

Haybeck mark construction grid, clear space and sizes from tab to app icon
Fig. 03Construction, clear space and small sizes.

Every product keeps the same mark and name and gets a plain descriptor: Portal, Tax, Advisory and Workbench. A product owns one accent colour, used for its active state and badge and nothing else. Colour stays mostly paper and ink, with canola for the one thing to look at.

Four Haybeck product lockups and six colour swatches with their roles
Fig. 04Four product lockups, and the six colours with what each is for.

Bricolage Grotesque, bold and slightly condensed, carries headlines and big figures. IBM Plex Sans carries everything people read twice, with full French accents and tabular figures, so money lines up to the cent.

Haybeck type specimens with a small figures table
Fig. 05Type: display, text and figures.

Photography shows owners at work where the money is made: fields, ovens, garages and workshops. Daylight, real places, original colours. No coins, no piggy banks, no handshakes across a desk.

Seven photos of owners at work with photography rules
Fig. 06Photography: seven real photos and the rules behind them.

The voice says what we need, why and by when, in English and French written at the same time. Status always pairs a shape with a word, so nothing depends on colour alone.

Voice examples in English and French, an icon set and five status badges
Fig. 07Voice in two languages, icons and status.
04Design system

One system, four products. Built so the next one is cheap.

Tokens come in three tiers. Reference colours are named after the prairie and never used directly. Role tokens say what a colour is for, and light and dark map the same roles. Component tokens say what a part uses. Components read role tokens only, which is why a new product or a dark theme is a small token file, not a redesign.

Haybeck token tiers: reference palette, role mapping, component tokens and a product token file
Fig. 08Three tiers of tokens, and the token file for the Tax product.

This is the core of the concept. Each tile below is the same markup with a different product and theme. Portal is canola, Tax is flax, Advisory is spruce and the staff Workbench is slate, each in light and dark.

Eight small product tiles, four products in light and dark, built from the same components
Fig. 09Same components across four products and two themes.

Money and dates are formatted by locale, never by hand. French amounts put the dollar sign after the number and use a space for thousands, and every table uses tabular figures.

Haybeck type scale beside a table of English and French number and date formats
Fig. 10Type scale, and money and dates in English and French.

Every interactive part has its rest, hover, keyboard focus and unavailable states drawn and built. Field errors say what is wrong and how to fix it: business numbers have nine digits, you entered eight.

Haybeck buttons in four states, business number fields, choices, status badges and notices
Fig. 11Buttons, fields, choices, status and notices with their states.

The document request is the most-used part of the system. One card has five states, and the same card appears in the client portal and in the staff Workbench, so both sides of the conversation share words.

Five request card states for the client, with the matching staff view below
Fig. 12The request card in five states, from the client side and the staff side.

Totals get the double rule from the logo. Deadlines show the date first and the countdown second. French runs about a third longer, so every component is tested with the French string before it ships.

A figures table, deadline list, key figure card and English and French component pairs
Fig. 13Money and dates, and the bilingual rules. All figures are invented.

A system only works if teams can grow it. Product teams propose, a weekly crit reviews, design and code are built together, releases come with plain notes, and the system team pairs with each product to adopt the change. The adoption numbers are invented to show what I’d track.

Five contribution steps, an adoption table by product and release notes
Fig. 14How the system grows: five steps, adoption by product and release notes. Numbers are fictional.

Each component gets a page that a designer or developer opens before using it: anatomy, options, do and don’t, and how it behaves with a keyboard and a screen reader.

Request card anatomy with numbered parts, options, do and don’t, and keyboard notes
Fig. 15A component page for the request card.
05Homepage

Know what you owe before it’s due.

The homepage opens on the promise and the product together: a grower checking her tablet, a “Return filed” tag and the phone screen that asks for one missing page. Below it, a strip of firm facts carries a “fictional firm, invented figures” label.

Haybeck homepage hero with a grower photo and a phone showing a document request
Fig. 16Homepage at desktop width: the promise, one main action and the product. Figures are invented.

Three services, each tied to the product that delivers it, then industries shown through the people who run them.

Tax, accounting and advisory cards, then four industry photo cards
Fig. 17Three services and four industries.

The canola section shows the portal itself, then the year-end in five dated steps so an owner always knows what comes next.

A yellow portal section with the requests screen and a phone, then a five-step year-end timeline
Fig. 18The client portal section and the five year-end steps.

A named advisor rather than a queue, then French as an equal: the same screens with locale formats for money and dates.

An advisor photo with an invented quote, then English and French phone screens
Fig. 19The advisor section and the bilingual section. The quote is invented.

The proof band is a fictional pilot, and it says so in its label. The page closes with one clear action and a footer that calls the whole thing a fictional concept.

A dark band with three invented pilot figures and a quote, a call to action and the footer
Fig. 20Fictional pilot figures, the closing call to action and the footer.
Haybeck homepage on a phone, light
Fig. 21Mobile, light: the same page in one column.
Haybeck homepage on a phone, dark
Fig. 22Mobile, dark: colour swapped, layout unchanged.
Haybeck homepage in dark mode
Fig. 23Dark mode at desktop width: hero, facts, services and industries.
The yellow portal section and the year-end steps in dark mode
Fig. 24Dark mode keeps the canola portal section as the brightest thing on the page.
06Client portal

What’s due, what we need, and what your advisor thinks.

The portal home is built for an owner with five minutes: four figures they actually check, a to-do list, the deadlines coming up and a note from their advisor. The client, a bakery in Saskatoon, and every figure are invented.

Portal home with cash, money owed, the next tax payment and a to-do list, light
Fig. 25Portal home, live. Light.
Portal home with cash, money owed, the next tax payment and a to-do list, dark
Fig. 26Portal home, live. Dark.

When one missing page blocks the return, it goes to the top in plain words with a single action. The alert keeps its shape and wording in dark mode, not just its colour.

Portal home with a banner saying the return is waiting on one document, light
Fig. 27Waiting on one document. Light.
Portal home with a banner saying the return is waiting on one document, dark
Fig. 28Waiting on one document. Dark.

The first day is designed too: four set-up steps and the advisor’s name from the first minute, instead of empty charts.

Portal home on the first day with a four-step set-up list, light
Fig. 29First day. Light.
Portal home on the first day with a four-step set-up list, dark
Fig. 30First day. Dark.
07Tax return

A draft in plain numbers, three questions, then sign.

The Tax product swaps the accent to flax and nothing else. The draft return shows the numbers that matter with the double rule under the balance, and the advisor asks three yes-or-no questions instead of sending a long organiser.

Draft corporate return in plain numbers beside three questions from the advisor, light
Fig. 31Ready to review. Figures are invented. Light.
Draft corporate return in plain numbers beside three questions from the advisor, dark
Fig. 32Ready to review. Figures are invented. Dark.

If a document is missing, signing stays locked and says exactly what unlocks it, next to what has already been received.

Tax return locked, listing the missing statement page and the documents already received, light
Fig. 33Signing locked by one missing page. Light.
Tax return locked, listing the missing statement page and the documents already received, dark
Fig. 34Signing locked by one missing page. Dark.
08Document requests

One list of everything we need.

Each request has a reason and a date. A fix says what is wrong and what would make it right, and uploads happen from a phone or a desktop and are checked by a person. Files stay in Canada.

Request list with one statement needing a fix, three more requests and an upload area, light
Fig. 35Open requests with one fix. Light.
Request list with one statement needing a fix, three more requests and an upload area, dark
Fig. 36Open requests with one fix. Dark.

An empty list says what happens next, not just that there are no items.

Empty request list explaining when the next request will come, light
Fig. 37All caught up. Light.
Empty request list explaining when the next request will come, dark
Fig. 38All caught up. Dark.
09Workbench

The same card from the staff side.

Workbench is the internal product. It uses the same components and words as the portal in a denser queue, with a slate accent that marks it as a staff tool. Staff see exactly what the client sees before they send a fix.

Staff queue of client requests with a detail panel showing what the client sees, light
Fig. 39Requests across clients. All clients are invented. Light.
Staff queue of client requests with a detail panel showing what the client sees, dark
Fig. 40Requests across clients. All clients are invented. Dark.
10On the phone

Most documents arrive from a phone camera.

The phone screens are the same system at its smallest: the home screen, then fixing a missing page by photographing it. French is built at the same time, with locale formats for money and dates.

Four phone screens in light mode, two in English and two in French
Fig. 41Phone, light: home and fixing a document, in English and in French.
Four phone screens in dark mode, two in English and two in French
Fig. 42Phone, dark: the same four screens.
11Research and results

What changed, and how I’d measure it.

The research is a fictional study written for this concept: four invented interviews with owners and advisors, each tied to a change in the product.

Four invented interview quotes, each with the product change it led to
Fig. 43What research changed. Interviews and people are invented.

The after-ship note shows how success would be measured: fewer emails per return, a shorter path from first request to signature, and missing pages caught within a day. The numbers are invented and labelled that way.

Three invented pilot figures on a dark band, labelled as a fictional note
Fig. 44A fictional after-ship note. These are not real results.
12Banners and social

One idea, from the cover to the feed.

The banners reuse the product, not a stock illustration: real photos, the request card and the phone screen, with one short line each.

Banner with the headline, a grower photo and a phone showing a document request
Fig. 45Hero banner.
Yellow banner with the requests screen and a phone
Fig. 46Campaign banner: every request in one list.
Wide banner with the tax return screen and a French phone screen
Fig. 47Wide case image with the tax return and a French phone screen.
Social banner with a baker photo, a headline and the portal home
Fig. 48Social post: a named advisor, not a ticket queue.
Yellow square post with two phone screens, one in French
Fig. 49Square post: page 3 of 4 is missing.
Portfolio cover with a farmer photo and eight product tiles in light and dark
Fig. 50Portfolio cover with the eight product tiles.
Dark cover with the headline, the portal home and a phone
Fig. 51Dark case cover.
13

What I’d test next

  1. Whether owners act sooner on a request that names the exact page and reason than on a generic “documents outstanding” message.
  2. Whether the locked “Continue to signing” button, with its reason beside it, reduces calls to the advisor or just moves them.
  3. How French-speaking owners rate the French screens against the English ones, and where translated strings still feel second.
  4. Whether a fifth product can be built from the token file and the shared library alone, and what it had to add.
  5. How the request card holds up in the staff queue at peak season, with hundreds of open requests and many fixes at once.
  6. Whether the canola accent still stands out for people with colour-vision differences, given that shape and word carry status too.
Next project

Wendsum Pay Later

Consumer payments concept

View case study →
Wendsum Pay Later cover
Contact

Let’s get in touch.

Open to remote roles. Let’s talk.

davitarakelyan92@gmail.com