The hardest client is your own company. A studio's site is both the work and the work sample at once: if it looks bad, that isn't one unhappy client, it's every future one. BITNEX is the company I work through — I design and build apps, AI agents, and websites on it — and this site doesn't have to sell a product. It has to show how I work.
So btnx.ai isn't a brochure. It's a demo of my standard. Whatever I promise a client, I demonstrate on myself here first.
The interface speaks the trade's language
Most dev-shop sites are either dry or full of agency noise. I wanted a third way: the developer world's own aesthetic, kept quiet. The logo is a terminal prompt (>_bitnex), the kickers are small monospace lines that start with //, the hero is a console mockup. One glance tells you who you've reached.
The visual language is deliberately terse: a single dark "console" background, cool tinted neutrals, no loud accent color. The weight is carried by typography and space — large, confident display headings and the air left around them. The manifesto band states the principle outright: the design is the product, the code is the proof.


The structure leads to one decision
The site is a single scroll, and every section answers a question a prospect would ask. What do you do? — services, from the website to the AI agent. How? — the process in four steps, from idea to launch. For whom? — references from closed projects. And does your own product actually work? — the in-house products, titkar.ai and Phora, in their own section. At the end, one task remains: the contact form.
No maze of subpages. The prospect scrolls down, and by the time they reach the bottom they've seen everything a decision needs.
The Console that runs across my work
The nav holds a ⌘K command palette — "Ask or search" — with site-wide search and an AI mode. It isn't decoration: it's the same Console pattern I built into my own portfolio and into several client sites (the Magnum-44 and Riczu sites). A recurring building block I solved well once and then made part of the stack — and reused solutions like that are exactly what the BITNEX site is about.
There's always a next level.
If you like what you see (whether you're building a product or a team) I'd love to hear about it.
