From the first sentence to the live site.
nileBlu builds the website a research group or an early-stage startup never quite gets round to building. We write the words, design the pages, build both halves and put the thing live — working from the paper, the deck, the README and the demo you already have.
Working from Amsterdam · replies within one business day
Words you have to write yourself
Brief across positioning, design, build and launch
Token layer every screen and component resolves from
You already have the site. It is just in pieces.
A deck, a README, a demo recording, a pricing thread, a logo somebody drew once. That is the raw material of a website, and it is already written — what is missing is the week nobody has to turn it into one. Drag the scrub and watch it land.
- 01Logo fileWordmark & favicon
- 02Deck, slide fourHeadline
- 03README introWhat it does
- 04Demo recordingProduct panel
- 05Pricing threadPlans
- 06Investor FAQObjections
Nobody sets out to not have a website.
Almost everyone we meet has already tried. The attempts fail in the same three places every time, and none of them is a failure of effort — they are seams in a route that was never one job to begin with.
Five things we hold to, and what each one costs us.
Every studio says it cares about craft. These are the ones we are willing to be held to, each stated with the practice it rules out — because a principle that forbids nothing is only a preference.
The words come first.
A layout holding placeholder text is not a design; it is a container waiting for the hard part. We write the positioning and the copy before a screen gets drawn, because a page can only be shaped around something it is trying to say.
Rules outLorem ipsum, and “send us your copy when it is ready”.
Nobody hands anything over in the middle.
Positioning, design, front end, back end and launch are done by the same people. There is no translation step between two vendors, which is where intent and scope usually go missing — and where a project quietly becomes somebody else's problem.
Rules outA design file thrown over a wall, and a build that reinterprets it.
Everything resolves from one layer.
Colour, type, spacing and radius are declared once and referenced everywhere. Changing your blue is one line rather than forty, and it stays one line six months after we have gone.
Rules outHard-coded values, and a site nobody dares edit after handover.
We only claim what the page can prove.
The performance panel on the home page reports that visit's real readings, and the standards panel audits the document you are actually looking at. If there is a number on this site, you can check it while you read it.
Rules outInvented percentages, borrowed logos, and awards nobody gave us.
You leave with the keys.
The repository, the domain, the hosting and the analytics are yours, and the deploy runs from a push to your own remote. Staying with us has to be a decision you make, not the only arrangement under which your site keeps working.
Rules outLocked exports, and a monthly fee to change a sentence.
One brief, and nothing briefed out.
We work from Amsterdam on European hours. Whoever wrote your headline wrote the endpoint underneath it, so there is nobody to brief and nothing to hand across — which is why the words, the design and both halves of the build move in the same week instead of queueing behind each other. It also means we take a limited number of builds at a time, and say so plainly when we are full.
Taking new builds
- Hours
- Mon–Fri, 09:00–18:00 CET · replies within one business day
- 01Positioning & Copy
- 02Design & Design System
- 03Front End & Back End
- 04Launch & Handover
Send the deck, the paper, the repo, the demo.
We'll send back a website.