You come to us when something on your website or in your systems is broken, when something you need does not exist yet, or when your team still does by hand what a program could do. We take on the job and, when it is done, hand over the code and all the accounts. We stay on for support only if you want us to.
Each kind of work starts differently, but all three have a handover day, when the code and the accounts become yours.
What we build with
Our own code in TypeScript, Next.js and Node, with plain CSS for the design. No website builder and no locked template you are not allowed to open.
Where it is kept
In your own accounts: the repository (where the code is stored), the domain and the hosting. We have access to work on it, but you are the owner.
What you keep
The code, the logins and a written guide. You get them on the day the work goes live, without having to ask.
Three kinds of work
Which one you need usually becomes clear after ten minutes of looking at what you have now. In every case, the code and the accounts end up with you.
01
We fix what you already have.
Something on the site breaks, work gets done twice or by hand, or only one person knows how a thing works. It still runs, so replacing it all seems too much, but it costs you time every day. This is the most common reason people come to us, and usually someone else wrote the code.
First we study how it is built and tell you what we found, including what we would leave as it is. Then we make the change and write a short note on what it does and what it does not do.
What you get
The change itself in your own repository, a short note on what it does, and a way to undo it.
How it goes
You show us what is not working.
We study it and tell you what we found.
We make the change and show it to you.
The change goes live and belongs to you.
02
We build what does not exist yet.
A website, an online store, or a link between two programs that do not share data yet. We start from how you work now, whether that is a spreadsheet, a phone or a folder of photos, because the new thing has to be better than that.
We build in three languages from the start: Estonian, Russian and English. Adding a language later means redoing every page and every web address on the site.
What you get
The working site or system, its code in your repository, every account in your name, and instructions for changing it without us.
How it goes
We agree on what is included and what is not.
You can see it working before it is finished.
You check it on your own phone.
It goes live, and the accounts are already in your name.
03
We keep it working after launch.
Small things come up: something breaks, your price list changes, a new law or a browser update means something has to change. None of this is a project, but each needs someone who already knows how it is built.
After a fix or a new build, support can carry on month by month. It ends when you decide.
What you get
Someone who already knows how it is built, a short note on every change, and a monthly arrangement that ends when you decide.
How it goes
We agree on what support covers.
You write to us when something is wrong.
We fix it and tell you what we did.
It runs month by month until you decide to stop.
How we work
These rules apply to every project, including this website.
We study what you have before we change anything. The first thing you get from us is a description of what we found.
Nothing goes live until automatic checks pass. They test the code, open every link, and compare each page's title and description for search engines with what is live now.
We build the Estonian, Russian and English versions from the start, without a separate language plugin.
Everything has to work on a phone, with a keyboard alone, and for people who have turned animation off. We plan for this from the start.
We do not add someone else's code package where fifteen lines of our own will do. Every package has to be updated later, and that job may fall to you.
Next to the code, we write in plain words why it is there, so the next developer does not have to guess.
What this site is built with
The list is short on purpose. Every tool on it is used on this site, so you can see the result on this very page.
TypeScriptThe programming language every file is written in. It catches some mistakes while we write, before a visitor can run into them.
Next.js, App RouterThe framework the site runs on. Pages are built on the server, so search engines and older phones get a finished page straight away.
ReactUsed only for the parts a visitor interacts with. The rest is plain HTML that needs no scripts to show.
CSS on design tokensOne file sets the colours, spacing, fonts and animation. To change a margin, nobody has to learn a framework first.
NodeRuns our checks: the tests, the link check, the comparison of search data, and the image processing.
PlaywrightA real browser opens the finished site and reports what it saw.
Canvas and three.jsWe draw the flat graphics on this site in code ourselves. The 3D figure uses three.js and loads separately; if it cannot load, a still image stays in its place.
The Anthropic SDKRuns the chat assistant on this site. The AI model is Claude; the rules it follows are ours.
Hosting in StockholmThe server region closest to Tallinn. Anything that leaves it is described in the privacy policy: the chat's replies, for example, are generated in the United States.
What else we work with
These are the tools we use on client projects. Not all of them are on this site, because a studio's own pages need no payment system or database. For each project we pick what the job needs.
Next.js
React
TypeScript
Node.js
Tailwind CSS
PostgreSQL
Stripe
Vercel
Anthropic
Playwright
Figma
GitHub
What is yours when the work is done
You do not have to ask for it or agree on it separately. It is part of the work, and most offers leave it out.
The codeAll the code, with every change from day one, in a repository on your account. We only have access to it. If you remove our access, everything keeps working.
The accountsThe accounts your site or system runs on (domain, hosting, email, analytics) and the logins to them.
The documentationHow it is built and run, how to change the text, and what to do if something breaks. Written so that someone who is not a developer can follow it.
One project for now. This list only includes work that is delivered, dated and still running. Our other projects are on the portfolio page, and each case there says what was measured and what was not.
Usually yes. Most of our work is on code someone else wrote. We study it first and tell you what we found, including what we would leave as it is. If it makes more sense to rebuild than to patch, we tell you before you spend money on patching.
Who owns the code?
You do, from the first line of code. The repository is on your account and we only have access to it. If you remove our access, everything keeps working.
What happens if we stop working together?
Everything stays with you and works without us. That is why we hand over the accounts and write the instructions: so whoever takes over next can carry on.
Can you work with our own developer?
Yes. Sometimes the best result is a small change that your developer then looks after. We write code that other people can read, including your own team.
How long does it take?
It depends on what needs to be connected to what, so we do not name a date before we have seen the task. The calculator on this site asks the questions we would ask on a call and shows the stages of work and what each stage needs from you.
Describe the task, and we will tell you what it involves.
WebWay: Ask me about what WebWay makes: websites, online stores, AI agents, automation, getting found on Google. I answer from what is written on this site. If I don't know something, I'll say so and give you the address where a person will answer.