The original task
We needed a public page that states who we are, which three kinds of work we take, what the interface level looks like, the starting prices, and where to write. There should be no form — contact only through Telegram.
Internal team project
Radaev.dev
Internal team projectThe website is still being improved
This is the team’s own website, not client work. The page explains why it was needed and what state it is in. The site is still being improved.
Why the team needed a website
Without our own page it is hard to explain the focus and not look like a “we do anything” shop. The site records the boundaries: websites and web apps, bots, and automation. It presents a small project team rather than a personal blog or a faceless service catalogue.
The structure we chose
- 01Home — the offer, directions, demonstrations, process, starting prices, one Telegram CTA
- 02Solutions — a capability showcase with links to interactive examples
- 03Service pages — first-version scope, limits and price
- 04About and contact — how the team works and the channel
- 05Privacy — facts about the current build, without extra promises
- 06The internal case and lab demonstrations — kept apart from client work we will not invent
Russian and English
Russian is the default language with no prefix; English lives under /en/. Every public page has a pair, a canonical URL and hreflang. English copy is written for meaning, not as a word-for-word calque.
Services and prices
The site shows starting figures: a landing page from ₽40,000, a bot from ₽15,000, a web app from ₽100,000, support from ₽15,000 a month. A multi-page site and automation are priced by structure and integrations. This is not an offer and not a promise of a final total.
The mobile version
The light interface has to hold on a phone, including the menu. The toggle is not covered by the panel. The menu closes on a second tap, Escape, a link and a language change. After closing, the page scrolls again.
Interface work
Heavy interactive examples live on their own pages. Home and Solutions keep light previews. There is no WebGL, video background, remote font or embedded third-party messenger UI.
Performance
A static Astro build, local WebP/JPEG with known dimensions, lazy-loading below the first screen, and a small amount of vanilla JavaScript only where it is needed. Motion stops under prefers-reduced-motion and Save-Data.
Technical stack
- Astro, HTML and CSS
- a small amount of vanilla JavaScript
- local mockup images
- static hosting with no server-side form
- RU/EN dictionaries in the repository
Current status
The site is published as the team’s evolving showcase. The pages can already be read and reviewed. We do not publish unverified enquiry, revenue or conversion figures.
What is already in place
- Positioning as a small project team
- Three service directions, with practical AI features inside a product
- Honest starting prices
- A separate internal case that is not presented as a client
- Three interactive demonstrations on their own pages
- A light mobile menu with a complete close path
What will still be improved
- Wording after real conversations with clients
- Extra previews if new kinds of tasks appear
- A fuller privacy policy — separately, after the operator’s answers
- Infrastructure topics such as log retention — only after they are checked in production
Internal team project
How the site looks now
These are current screens, not a before/after story with an invented effect.
Telegram
Message in TelegramIf the task is already clear, write in Telegram.
A few lines are enough: what you want to simplify and how it works today. Replies are usually sent between 09:00 and 18:00 MSK.