ArkaCara

One site carrying a holding company and its three divisions

A parent company and three divisions on one page, each with its own remit and its own front door.

Visit the live site
Worked with
ArkaCara
Type
Web Platform
Role
Product design, full-stack build, copy
Duration
6 weeks
Year
2026
ArkaCara: the interface we built

The challenge

ArkaCara is one company running three divisions that share nothing but a standard: AdhiLokha manages villas, NataJivva does academic work, and Aksadhara builds software. A holding company's site has a specific way of failing. Say too little and it reads as a shell with three logos on it. Say too much about each division and it competes with the sites those divisions already have. And a visitor arrives wanting one of two incompatible things: either the company behind the three, or the one division they actually came for, with no way to signal which.

Our approach

So the site answers the second question first and the first question properly. Every division is reachable from the top of the page and again from the footer, each with a one-line remit and a link out to its own site, because a reader who came for AdhiLokha should not have to read about the parent to leave for it. What stays on the page is only what the divisions cannot say for themselves: why they exist as divisions rather than separate companies, what the shared standard actually is, and who answers for it. It is one page with anchored sections rather than four thin ones, since the whole argument is that these belong together.

  1. Routing before explaining

    Most visitors arrive for one division, not for the company above it. So the three are listed within the first screen, each with the sentence that distinguishes it and a link to its own site, and they appear again in the footer for anyone who scrolled past. The parent makes its case underneath, to the readers who stayed. A holding company that makes you read about itself before it will point you at the division you came for has mistaken its own page for the destination.

    The three divisions are named within the first screen, above anything the parent says about itself.
  2. Saying what a division is for

    Each division gets a block of the same shape: its field, a sentence on what it actually does, the four kinds of work it takes on, and the address of its own site. Uniform structure is the argument: three genuinely different crafts, presented as equals under one standard rather than as a ranked list with a favourite.

    Every division gets the same block: field, remit, four service lines, own address.
  3. The part only the parent can say

    What is left is the reasoning the division sites have no room for: that a division starts inside the company with the funding and the patience to get good before it is asked to grow, that hiring and the definition of finished work are the same in all three, and that the company stays operator rather than investor. Four principles carry it, stated as commitments that cost something rather than as values that cost nothing.

    Four principles stated as commitments that cost something.
  4. One page, anchored

    Company, divisions, about, and contact are sections of a single page rather than four routes. The site's claim is that the three divisions are one company, and splitting that across separate pages would have the navigation quietly arguing the opposite. Anchors give each section a linkable address without breaking the read.

  5. Contact that admits it is the wrong door

    The contact section says plainly that ArkaCara handles partnerships, new divisions, and company-level matters, and that anyone with day-to-day work should call the division that does it, then lists all three again. Sending an enquiry to the right place is worth more than capturing it at the top.

    The contact section names what ArkaCara handles, then points everything else at the division that does it.

The outcome

ArkaCara has a front door that routes to the right division in one click and states the company's position for the readers who came for it: how divisions are started, what standard they share, and what the company is willing to wait for.

More images

Built with

  • Next.js
  • TypeScript
  • Tailwind CSS

Have a problem shaped like this one?

Tell us what you're working on. We'll tell you honestly whether we're the right fit.