Landings & websites

Built by the team that launched thirty of them for its own portfolio.

We are not a web studio that also does Web3 – we are the team that has shipped the site alongside the product, the token and the campaign, thirty times over. That is why the copy, the design and the analytics arrive together instead of being three suppliers arguing about a deadline.

See the portfolio
  • 30+
    Sites shipped for portfolio projects
  • 4
    Languages shipped as standard, RTL included
  • 13+
    Years in the market, since 2013

What we build

Four shapes, one team. Which one you need is usually obvious within ten minutes of the first call.

Landing page

One page with one job: a launch, a round, a campaign or a waitlist. Written, designed, built and measured.

Product site

Several pages around a product that is still changing – features, pricing, docs, changelog – on a CMS your team can actually edit.

Corporate site

The site a company is checked against: who you are, what you have shipped, where you are registered, how to reach you.

Redesign of a site you have

We start from where the current one leaks rather than from a blank canvas, and keep whatever is already working.

How it runs

Six steps, in this order, every time. Pick one to see what happens inside it.

Discovery

Who the page is for and what it has to make them do.

  • Audience, objections and the one action the page exists for
  • Competitor and comparable review
  • Audit of the current site where there is one, with the leaks named
  • Sitemap and the scope that comes out of it

Structure & copy

The argument, written before anything is drawn.

  • Page structure, section by section
  • Copy written to the positioning rather than filled in after the design
  • Wireframes at the fidelity that settles layout, not taste
  • SEO: titles, descriptions, heading structure

Design

Applied brand, not decoration.

  • Desktop, tablet and phone, designed rather than scaled
  • Design system so later pages cost less than the first
  • Illustration, iconography and motion where they carry meaning
  • Dark mode where the product has one

Build

Nuxt, static where it can be, fast because of it.

  • Nuxt with static prerendering – no server to go down
  • Core Web Vitals treated as a requirement, not a report
  • Accessibility: keyboard, contrast, reduced motion
  • Four languages including RTL, from the same codebase

CMS & content

So the next change does not need us.

  • A CMS your marketing team can edit without a developer
  • Blog, news, careers and case sections where they earn their keep
  • Content migration from the old site
  • Editor handover and documentation

Launch & analytics

The part most sites skip, and then cannot explain their numbers.

  • Analytics and conversion tracking wired in before launch
  • Search Console, sitemap, robots and structured data
  • A/B testing where there is traffic to test with
  • Support and iteration after launch, not a handover and silence
Stack
  • Nuxt.js
  • TypeScript
  • Tailwind CSS
  • Static prerendering
  • Headless CMS
  • GA4 / GTM

Portfolio

The same projects we engineered are the ones we packaged, funded and listed. That overlap is the whole argument.

All cases
Start

Send us the site you have, or the one you need

A URL is enough to start. You get back what we would change first and what it would take – before anyone talks about a scope.

One business day · a URL is enough