How we built our agency website in a weekend and spent two weeks adding features

We already had a site on Tilda, and it served us fine right up until it became obvious: an agency website isn't a business card, it's a tool. It needs to evolve every week — new cases, new articles, new service sections, SEO work. On Tilda all of that is possible, but at some point it stops being fast.

One Friday evening we sat down and built aimap.am from scratch. By Sunday evening ten service pages, the homepage, a request form and SEO markup were in production. Over the next two weeks the cases section appeared, a blog with its first article launched, and new projects went straight into the portfolio.

This article is about how the process works, how long each part took, and why this is the format we sell to clients.

Why we left Tilda

Tilda is a good tool, and we keep using it for client work where it fits. But for our own agency site we wanted three things that are hard to get from a builder.

Speed of edits. Any structural change on Tilda is manual UI work: open it, click, drag, save. When you need to add a tenth service page with the same logic as the first nine, the builder loses to code with components.

SEO without workarounds. Builder-based sites have a ceiling on markup control: microdata via hacks, load speed bottlenecked by someone else's render, and moving the project to another domain is its own saga.

Full control over the source code. We sell vibecoding as a service, and it would be weird to keep our own storefront on a closed builder. The client has to see that we work on ourselves the same way we build their project.

The stack

No magic — the standard toolkit any developer owns:

• VS Code + Claude Code — the editor and the AI agent that writes and edits code in the repo
• React + Vite — frontend with no extra dependencies, builds to static in seconds
• Tailwind CSS — styles without separate CSS files
• Static hosting — the site is served instantly

A few words on the choice. We know about Astro and other SSG frameworks — for content-heavy sites they're great by default. But we have more than three years of React experience, and Vite builds plus a static deploy cover both speed and SEO. When a team has deep experience with a tool, switching to something less familiar for "theoretically better" doesn't pay off. Use the stack your team knows at a reflex level.

Friday: structure and skeleton with AI

An important point that usually gets glossed over: we've been working with AI tools for years. Claude knows perfectly well what AI MAP does, what services we offer, how we write, which blocks we use on landing pages and decks. Over that time we've built up a library of prompts, page templates and internal standards — all of it lives as markdown files that get loaded into context.

So on Friday we weren't starting from a blank page. We set the structure: ten services, each with its own set of blocks (headline, numbers, process, FAQ). Claude quickly generated a first skeleton for every page in line with our style and our messaging. By Friday night we had a skeleton app with routing, components, and first-draft content for each service.

This isn't "the neural net pressed a button and it's done". This is development where the routine part — markup, repeatable blocks, first-draft text — gets done by the AI under the supervision of a human who knows what the result should look like.

Saturday: content

Saturday morning we sat down with the copy. The AI prepared a decent baseline, but the selling message, the emphasis, the wording for specific audiences — that's human work. We went through all ten pages, made micro-edits: rewrote a headline here, restructured the numbers block there, added a missing block somewhere else.

The upside of vibecoding in this exact edit mode: you don't open a builder admin panel, you don't hunt for the right block, you don't worry about breaking the layout. You tell Claude "on the chatbots page in the numbers block, swap items one and three" — and it happens in seconds.

By Saturday evening all ten pages were content-complete: our messaging, our numbers, our wording for every service.

Sunday: polish and launch

Sunday went to the technical part. Wrapped up responsive design, tested on phones and tablets, hooked up the request form with a Telegram notification, plugged in Yandex.Metrika, wrote the privacy policy, deployed to hosting.

By Sunday evening the site was in production at aimap.am — with ten service pages, correct rendering on every device, and a working form.

Two weeks after: the site grows alongside projects

This is where it gets interesting. Once the base structure exists, adding to it is a matter of hours, not days. And in those two weeks, real projects were running in parallel and instantly turning into content for the site.

A project for the Fabula coworking space — became a case

We work out of the Fabula coworking space in Yerevan, and they had a simple problem: residents were booking Skype rooms and meeting rooms on paper sign-up sheets. We shipped them a Telegram bot for bookings. The project took a few days, and on our site it turned into a card in the "Our cases" section — a short blurb with the gist and the result.

The Kōkasoku portal — became its own blog article

Around the same time we wrapped up a big project — a portal for the Eurasian Riichi Mahjong Association. Started as a platform for two countries, became a platform for five in less than a month. It got interesting enough that it grew past a case and became a full-on blog article: How we vibe-coded an international portal and turned it into a Eurasian association in a week.

That piece became the first article in our blog — and set the template for everything that follows. Publishing a new case now is a matter of writing a markdown file and committing it.

DevRating.ru — a separate product, also a case

In parallel we launched DevRating.ru — an independent portal reflecting the chatbot and builder development market in Russia. It's a standalone project with its own audience, but for aimap.am it became another card in the cases section: proof that we can do more than landings — we can launch industry portals with data.

SEO: work search engines actually see

This is the part that separates "a site on the internet" from "a site that brings in clients". Every page has:

• unique titles and descriptions matched to the service's semantics
• a correct heading hierarchy (H1, H2, H3)
• Schema.org microdata for organization, services, breadcrumbs
• sitemap.xml and robots.txt that refresh on every build
• load speed in the green on PageSpeed — the site is served as static, JS is minimal

Search engines see the site as structured, fast and semantically marked up. Two weeks after launch, pages started getting indexed in Yandex and Google.

How long it actually took

Let's break it down by hours so it's clear where the time goes.

Total — about 50 hours for a full agency website with a blog and cases. For comparison: the same project at a classic agency takes a month and a half to two months on the calendar, with a budget starting at 200,000 RUB. Tilda gets you up faster, but you give up markup control, the ability to scale structure without manual work, and you hit a ceiling on SEO.

What this means for clients

We sell the same playbook as a service. When a client comes in with "we need a site", we answer with concrete timelines:

• A simple landing with a tight focus — in 1 day. When the client has a clear audience, one product, one offer and one traffic channel — you can ship a page in a day for 10,000 RUB. We've got a case like that.
• A landing with deeper messaging and design — in 2–3 days.
• A multi-page agency or company website — in 10–14 days, end to end.
• A product MVP with authentication — in 2–3 weeks.
• An online store with a cart — in a week.

This isn't a promise that "the neural net will do it overnight". It's a promise that the human work on a site — content, messaging, decisions — stays, but the routine of layout and coding shrinks by an order of magnitude. The result — a site that:

• has its source code in your repository
• has SEO working from day one
• takes edits quickly
• lets you add new pages and sections without rebuilding the whole project

Where vibecoding doesn't fit yet

Honestly — technically it fits almost everywhere. But there are industries where AI-assisted development is treated with caution right now, and we respect that.

Healthcare. Patient PII, software certification requirements, liability for mistakes. Until the market settles on practices for AI-written code inside the medical perimeter, we don't push vibecoding for medical clinics or clients with medical data.

Legal services. Here the issue isn't technical, it's reputational. Lawyers value emphatically classic reliability — and a site built "with AI" can read to clients as not quite solid enough. That will change in a year or two, but for now it's worth keeping in mind.

Banking and fintech. Regulator requirements for development, code audits, compliance procedures. For business-card sites and marketing landings there are no limits, but for product solutions inside the regulated perimeter — that's a separate conversation.

Everywhere else — from e-commerce and EdTech to HoReCa, HR-tech, media and B2B services — vibecoding works just as well as classic development, only faster.

What's next for our site

Once a week we add a new article to the blog — writing about real projects and tools. Once a month we update the cases section. Step by step we're building up the semantic layer for SEO: keyword research, search-traffic work, internal linking.

A site is a living system, not a monument. And vibecoding is the approach where growing a system is as fast as creating one.