Contact

Website development, start to finish

Websites on our own code, built for your task — from the brief and design to launch and warranty. Fast, clear to search engines and AI, with no subscriptions and entirely yours.

08 services

Subsections

In short

We build websites on our own code — without site builders, ready-made engines or monthly subscriptions. Two specific developers work on your project, and design and front end are done by one person, so the idea reaches the browser undistorted. The finished site is fast, clear to search engines and AI assistants, edited through its own admin panel, and the domain, hosting and code are registered to you. The price is counted in hours for your task and fixed together with the scope before we start; after handover there is a month of warranty.

What we build

Services in detail

Service What’s included Who it’s for Link
Corporate Sites
  • Structure built around how buyers actually decide, not around your org chart
  • Design, hand-written front end, admin panel your team can use without training
  • Multilingual out of the box
  • Forms wired into CRM and messengers
  • Technical SEO from day one, not bolted on later
  • Speed budget set before design starts
  • Companies whose site is older than their current positioning
  • B2B teams whose sales deck is better than their homepage
  • Businesses tired of paying an agency to change a phone number
 Go deeper about Corporate Sites
Landing Pages & Promo
  • One page built to convert a single traffic source
  • Copy structure, offer hierarchy, forms and calls tuned for one action
  • A/B variants ready from launch
  • Analytics and event tracking wired in
  • Loads fast on 4G, because that's where the ad clicks come from
  • Product launches and campaigns with a paid budget running
  • Teams whose ads work but whose landing page kills the click
  • Events, courses, single-service businesses
 Go deeper about Landing Pages & Promo
Online Stores
  • Catalogue, cart, checkout, payments, delivery and stock
  • Custom-built where the boxed platform limits you, integrated where it doesn't
  • Sync with your accounting system, warehouses and marketplaces
  • Product feeds for ads
  • Search and filters that survive 10,000 SKUs
  • D2C brands outgrowing a marketplace storefront
  • Retailers whose current store breaks under its own catalogue
  • Businesses paying platform fees on every sale
 Go deeper about Online Stores
Catalogue Sites
  • Large product or service catalogue without online checkout
  • Fast faceted search and filters
  • Import from Excel, your accounting system or supplier feeds
  • Spec sheets, PDFs, downloadable documentation
  • A structure search engines and AI assistants can actually read and quote
  • Manufacturers and distributors selling through managers, not carts
  • Companies whose catalogue lives in a PDF nobody opens
  • B2B suppliers with hundreds of positions and no way to search them
 Go deeper about Catalogue Sites
Subscription Tools & SaaS
  • A working tool people pay to use — calculators, generators, checkers, databases, dashboards
  • Accounts, plans, free tier and paywall
  • Recurring payments, invoices and cancellation handled properly
  • Usage limits, quotas and API keys if you sell access
  • Admin panel showing who pays, who churns and what they use
  • Public pages built for search, so the tool sells itself
  • Launched as a first version that earns before it grows
  • Founders with a tool idea and no team to build it
  • Experts whose knowledge could be a paid instrument instead of a consultation
  • Businesses sitting on data — pricing, specs, registries — that others would pay to query
  • Existing free tools with traffic and no revenue
 Go deeper about Subscription Tools & SaaS
Telegram Mini Apps
  • A full interface inside Telegram — no install, no app store, no download friction
  • Native login, payments and notifications
  • Works alongside your site and shares its data
  • Bot and Mini App as one system, not two projects
  • Services whose audience already lives in Telegram
  • Stores wanting a second sales channel without an app budget
  • Communities, subscriptions and booking-based businesses
 Go deeper about Telegram Mini Apps
API & Integrations
  • Your site connected to the systems that run the business — CRM, accounting, payments, delivery, telephony, messengers
  • Custom APIs when a product needs to talk to something else
  • Data synced both ways, with logging so failures are visible instead of silent
  • Existing integrations fixed and documented
  • Companies whose site and CRM hold different versions of the truth
  • Businesses where orders are moved between systems by hand
  • Teams who inherited an integration nobody understands
 Go deeper about API & Integrations
Experience & Award-Level Sites
  • Sites built to be remembered — motion, 3D and WebGL, custom typography, scroll-driven storytelling
  • Concept and art direction, not just execution
  • Performance engineered so the graphics don't cost you the audience
  • Built for portfolios, launches and brands that can't look like everyone else
  • Brands whose competitors all use the same template
  • Studios, agencies and creators whose site is the portfolio
  • Launches where being noticed matters more than being conventional
 Go deeper about Experience & Award-Level Sites

What you get

Not a set of technologies, but a working tool for your business. Here is what that means in practice.

  1. 01

    A site built for your task

    The structure follows what the site has to do, not what a template allows. The code is written for your project from scratch.

  2. 02

    Fast on a phone

    Speed is numbers, not a wish: the loading budget is agreed before design starts. Fonts and images are optimised, there is no extra code.

  3. 03

    Visible in search and AI answers

    Clean markup, metadata, a sitemap and structured data are part of the architecture: search engines and AI assistants understand the site from day one.

  4. 04

    Its own admin panel

    You edit texts, products, orders and settings yourself. Each employee has their own rights, and you can see who changed what.

  5. 05

    Connected to your services

    CRM, payments, delivery, accounting: data is exchanged through an API with a log, so an integration never breaks silently.

  6. 06

    Security in the code

    Forms do not let harmful data into the database, passwords are stored as hashes, and brute force and spam run into a limit.

  7. 07

    No subscriptions

    No monthly payments for themes, plugins and licences. You pay for the development and the hosting — that is all.

  8. 08

    Everything is yours

    Domain, hosting, repository and source files belong to you. Along with the site you get a document on how it is built.

Why we chose this method: CMS vs own code

Ready-made engines (WordPress, Drupal, Joomla, Shopify, Magento) and site builders like Wix and Squarespace are a stage we have passed and outgrown. The reasons are simple: the engine dictates the structure instead of following it; half of the loaded code is never used; every non-standard task runs into a plugin or into the absence of one; the page is heavier and therefore slower; and the more service clutter there is in the markup, the worse search engines understand it — with near-zero visibility in AI answers, which today bring people no worse than search, and in the future search will move there entirely. It is already happening.

At every step a CMS loses to clean code: someone else's architecture instead of your task, kilobytes of extra code for a two-line feature, a ceiling on speed that no plugin can break through, and markup that search engines read worse — such a site will always lose in SEO to one built on clean code. Add the endless monthly payments for themes, plugins and licences. Your own code belongs to you entirely and forever, and any new feature is written into it without limits rather than begged from an engine.

We keep the stack current and update it as the global web environment changes.

  • No paid subscriptions
  • Fast loading
  • Upgrades without limits
  • Better SEO and AI visibility

Site builder, CMS or own code: a comparison

Three ways to make a website, side by side — so it is clear what you are paying for.

CriterionSite builder (Wix, Squarespace)CMS (WordPress, Joomla)Own code
Launch days, from a template weeks: a theme and plugins longer: everything is built for the task
Loading speed average, a lot of extra code lower: heavy themes and plugins high: only the code that is needed
SEO and AI visibility limited by the platform depends on the theme and plugins best: clean markup
Non-standard tasks within what the builder allows through plugins — or their absence no limits
Monthly payments a platform subscription themes, plugins, licences none — hosting only
Who owns it the site lives on the platform the code is yours, the architecture is not entirely yours
When it makes sense to test an idea in a couple of days when your team already works with that engine when the site is a working tool of the business

How the work goes

The main stages of the work. Every stage can be seen and judged — along the way, not at the end. Responsibility of each side is spelled out

  1. 01Brief and questions

    You fill in the brief, I come back with questions. Usually the questions matter more than the answers: they show where the task is still vague.

    Needed from youA filled brief, references — what you like and what you do not, access to whatever already exists. The more detailed the answers, the closer the result to what you want, and the less time it costs both sides. Working blind is the longest and most expensive path.

  2. 02Specification and estimate

    The specification records everything the site must have: the work follows it and the result is accepted against it. Whatever cannot honestly be estimated at the start goes in as a separate line with a price range. Fixed price for a fixed scope — no hourly surprises at the end.

    You getA specification written for your project, delivered as a PDF

    Needed from youApproval of scope and dates, prepayment to start

  3. 03Structure and prototype

    The approach depends on scale. On big projects: pages, blocks and routes before any graphics — changing them here is cheap, later it is expensive. The structure goes up on a test domain right away, and you can walk through it like a finished site. Small sites with obvious logic skip this stage and go straight to design.

    Needed from youTexts or their drafts, product data, one round of comments. Timely feedback is what keeps the schedule.

  4. 04Design

    Key screens are agreed first, then the rest. You see the design live on a test domain, not as static layouts. One round of edits is included; a second one means the brief was wrong and we go back to it. Redesigns push the final price up.

    Needed from youTimely feedback. Comments gathered in one place — a file or a shared document, with screenshots marking the spot and a description of the change.

  5. 05Build

    The code is written for your project from scratch, on our test domain you can open at any moment. Progress is visible daily, in real time, not on demo day. While the work goes on the site is closed from search engines and opens only after it moves to your domain and hosting.

    Needed from youFinal texts and images. Access to everything the site connects to: the mail account the analytics is registered on, keys and logins for API synchronisations, the accounts of the CRM, payments, delivery, hosting and domain.

  6. 06Launch and handover

    Before the switch everything is checked: how the site works, speed, the mobile version, forms and search settings. Then it is deployed to your domain and hosting. You receive a finished site, every access to it and a document explaining how it all works.

    You getA README guide to the project and, separately, a short document: where everything is, how to deploy it, how the scripts and additional modules work

    Needed from youFinal check and payment: until the project is handed over your changes and wishes go in as part of the work, afterwards they count as extra and are paid separately. Accept and pay for the finished work within five working days. Hand over access to the hosting and the domain records. Decide on ongoing support.

  7. 07Warranty and what comes next

    The site is tested thoroughly before handover, but if something breaks after launch, I fix it for free. The warranty runs for a month from the handover date and covers what broke by itself: a form stopped sending, a page returns an error, the layout slipped on a device we checked. Noticed something — write straight away.

    You getFixes within a month of handover, an answer within a working day

    Needed from youA description of the problem: what you did, what you expected, what happened — with a screenshot and the page address

How much a website costs

There is no price list: every project is estimated for its task, in hours. Here is how the sum is built and how payment works.

  1. Price — by hours and scope

    Fixed price for a fixed scope, split into stages. If the scope changes mid-way, we agree the difference separately — you always know the number before the work, not after. The price is built on the cost of an hour of our work: it reflects the skill and the speed with which the task gets done here. So an estimate is a count of hours, and the scope is always fixed together with the price. Projects with an undefined scope that surfaces along the way we do not take: working time is a resource that cannot be stretched, only shared between tasks.

  2. Payment by stages

    Thirty per cent to start, the rest by stages as they are ready — usually three payments: advance, interim and on completion. Big projects with a long timeline are billed monthly. The terms are agreed before the work starts and written into the contract.

  3. Deadlines

    Each stage has its own date. Delays on your side move the dates — that is stated up front so nobody is surprised: waiting for texts is the most common reason projects slip.

  4. Edits

    One or two rounds per stage are included. Rework caused by a changed decision is estimated separately — not as a penalty, but because it is genuinely new work. Anything reasonable we simply do, without discussion. Repeated changes of the same information are not our responsibility and are paid for by the hours they take.

  5. The estimate is free

    We look into the task and advise for free, without obligation — even if you end up building it with someone else. The exact sum comes after the brief and the specification.

What we build websites with

A tool — and what it is for. Everything is chosen for the task: a simple site does not need a heavy stack.

Front end

  • Semantic HTML — read by search engines and AI assistants alike
  • CSS on a token system — colours, spacing and fonts in one place
  • Modern CSS: grid, container queries, :has — adaptive layout without libraries
  • Vanilla JavaScript, React with TypeScript — when the interface becomes an application

Back end

  • PHP 8.5 without a framework — sites, catalogues, admin panels
  • Go — services where response time and load matter
  • PostgreSQL, MySQL or SQLite — the database is chosen for the scale of the project
  • REST API and webhooks — exchange with CRM, payments and accounting systems

AI layer

  • AI on hand — it takes the monotonous part: parsing exports, tagging, merging tables, moving content
  • Models picked per task — Claude, GPT, local ones when data cannot leave the perimeter
  • A second pass over the checks — the machine finds part of the mistakes. Human in the loop: nothing a model produces reaches the project except through a person
  • Your data is not used to train models — the work goes through the API, where the provider's terms forbid it

Design in code

  • Design-in-code — static mockups are left out of the process on purpose: one person does both design and front-end. Editing the design in code or in a Figma file takes the same time.
  • The designer's visual idea reaches the browser undistorted, without a markup developer in between
  • Figma is a sketchpad — for drafting an idea and checking the composition
  • Graphics are built with a set of tools
  • AI graphics and prompt engineering for the project style: selected and refined, not taken as it comes

SEO and AI visibility from day one

Basic optimisation is built into the architecture of every site we make. Promotion is separate work after launch: it goes on for months and depends on the competition in your niche.

  1. 01

    Clear markup

    Headings, sections and navigation are marked up so that search engines and AI assistants understand what each page is about.

  2. 02

    Metadata and previews

    Every page has its own title, description and image for social networks and messengers.

  3. 03

    Structured data

    Services, articles, questions and breadcrumbs are described in the schema.org language — that is how a site gets into rich answers.

  4. 04

    Sitemap and robots.txt

    Search engines see every page that matters at once and do not waste time on service pages.

  5. 05

    Speed and the mobile version

    The main quality signals search engines look at are built into the layout, not added after launch.

  6. 06

    Languages and addresses

    For multilingual sites — correct language versions and clean page addresses.

What we will need from you

The better the starting materials, the faster and more precise the result. Here is what comes in handy along the way.

  1. 01

    A brief and references

    Answers about the task and examples of sites you like and dislike.

  2. 02

    Texts

    At least drafts by the structure stage, final versions by the build. Waiting for texts is the most common reason deadlines slip.

  3. 03

    Photos and a logo

    Source files in good quality. If you do not have them, we will tell you how to get or put them together.

  4. 04

    Access

    The mail account for analytics and the accounts of your CRM, payments, delivery, hosting and domain.

  5. 05

    One person who decides

    Someone who makes the decisions and gathers comments in one place.

  6. 06

    Timely feedback

    Comments in one list with screenshots — that is what keeps the schedule.

Full freedom of action

A format where you hand the task over and only accept the result

We can build the project without you taking part at all: it is enough to describe the task in a few sentences. Everything else is on us, and you only sign off the result. Such projects often turn out better than those built to a specification — there we are boxed in by the brief, here the decisions are ours.

Who it suits

  • Those who have no time to get into the process, gather information and sit through approvals
  • Those ready to rely on our taste and experience
  • Those ready to pay for changes if the result needs reworking afterwards
  • Returning clients who already know how we work

Who it does not suit

  • Companies with departments, where many people take part in approvals
  • Those who want something specific but skip the brief, hoping we will guess
  • Those looking to save: without a structure and starting data the work takes longer, and time is what the price is made of

Warranty and after launch

What the warranty does not cover and what technical support after handover includes

The site is tested thoroughly before handover, but if something breaks after launch, I fix it for free. The warranty runs for a month from the handover date and covers what broke by itself: a form stopped sending, a page returns an error, the layout slipped on a device we checked. Noticed something — write straight away.

Not a warranty case

  • The information changed: new prices, texts, products, staff — that is a content update, not a fault
  • The code was edited by you or another contractor — the warranty no longer covers what was touched
  • It turned out something else needs building, and it was not in the specification
  • Something has to work differently in the admin or technical part than the specification said
  • Trouble on the hosting side: outages, attacks, viruses, a compromised server
  • Domain problems: not renewed, records changed, certificate revoked
  • Third-party services changed: a CRM updated its API, a payment provider switched protocol, a widget was shut down
  • Consequences of your own content: a long heading broke a block, a heavy photo slowed the page down
  • Requests to move, recolour or add a block — that is an improvement, not a fault
  • Search positions and the number of enquiries — algorithms, the market, ads and competitors decide those

Support and improvements after handover

  • Content updates: texts, prices, products, photographs, new articles
  • New pages, blocks and sections as the business grows
  • Connecting services and integrations that were not in the first scope
  • Keeping the code current: PHP version, dependencies, server environment. Backups and recovery after failures
  • Monitoring of uptime, errors and certificates with alerts
  • Help with hosting and the domain: moving, renewal, mail settings
  • SEO support: a set of tools and settings kept running month after month. The tighter the competition in the niche, the deeper and longer the work — it is not the base optimisation done at launch
  • Reworking what the site itself showed to be wrong once real people started using it
  • By the hour, by the task or a monthly arrangement — whichever suits the load

How we work with people

What contracts do not say, but what decides everything

Your project is handled not by a studio with a rotating staff, but by two specific solo developers working under their own names — we answer for the result with our reputation, and we have only one.

We love what we do — the work is our hobby. You do not have to ask for quality. We do not save time on a project and do things properly even where nobody will ever check: if a client does not know development, that is no reason to do it the easy way instead of the right one. Every project is treated as our own, and we are here for a long working relationship, not a single order.

We advise for free and bind you to nothing: we will look at the task even if you end up building it with someone else. Tell us the idea — we will find the solution and the tools for it. Our reach is not limited, and you are welcome to use it.

We respect your time: the process is arranged so that feedback is convenient and deadlines hold. If something goes wrong on your side, warn us in advance and we will work it out. The human factor and force majeure happen to everyone — we take that with understanding. The relationship rests on mutual respect.

We value your budget too: we offer the affordable options first and say where you can save and where you should not. We do not haggle over trifles — a happy client matters more than our own inconvenience.

Common mistakes when ordering a website

  1. Starting without a task

    “Make it look nice” is not a task. Without a brief the contractor guesses, and guessing is the longest and most expensive path.

  2. Leaving the texts until the end

    Design without texts is a frame without a picture. When texts arrive at the end, half the layout gets redone.

  3. Registering the domain to the contractor

    The site should be yours from day one. Otherwise, when you change contractors, you risk losing the address and the data.

  4. Choosing by the hourly rate

    A cheap hour multiplied by many hours costs more. Compare the total scope, the deadlines and what you get at the end.

  5. Too many people approving

    When a committee makes the decisions, each round of edits takes a week. You need one person who gathers the comments and decides.

  6. Forgetting about life after launch

    Prices, products and texts will change. Decide in advance who will run the site: you through the admin panel, or with ongoing support.

Glossary: the terms in plain words

Words you will hear while a website is being made — briefly and without jargon.

Domain
The address of the site on the internet, like rimma.dev. Bought from a registrar and renewed once a year.
Hosting
The server that stores the site’s files and database and serves them to visitors.
CMS
A ready-made site engine like WordPress or Joomla: the site is assembled from its templates and plugins.
Admin panel
The closed part of the site where you change texts, products and settings yourself.
Responsive layout
The site adjusts itself to the screen of a phone, tablet or computer.
SSL certificate
The padlock in the address bar: the connection to the site is encrypted.
Landing page
A one-page site for one service or product; its goal is an enquiry.
Prototype
A scheme of pages and blocks without design: the logic is checked on it before anything is drawn.
Specification
A document listing everything the site must have. The work follows it and the result is accepted against it.
API
The way the site exchanges data with other services: CRM, payments, delivery.
Indexing
When a search engine walks through the site and adds its pages to the results.
Core Web Vitals
Measures of a page’s speed and convenience that Google uses to rate a site.

Questions about website development

How much does a website cost?

There is no price list: the price is counted in hours for your task and fixed together with the scope before the work starts. The estimate and consultation are free.

How long does it take?

It depends on the scope: each stage has its own date, written down before the start. Projects go fastest when texts and materials arrive on time.

Can I change texts and products myself?

Yes. The site gets its own admin panel: you edit texts, prices, products and orders yourself, without a developer.

Who will own the site?

You do. Domain, hosting, repository and source files are registered to you and handed over at launch. Nothing is held hostage.

Why don’t you build on WordPress or site builders?

A ready-made engine dictates the structure, drags in extra code and monthly payments, and the site turns out heavier and harder for search engines and AI to read. Your own code is faster, belongs to you and can be extended without limits.

What if something breaks after launch?

For a month after handover we fix for free anything that broke by itself: a form stopped sending, a page returns an error. After that — ongoing support by agreement.

Can you improve my old site?

We do not edit someone else’s code: it is usually faster to build a new site than to dig through outdated, tangled code. The texts and materials of the old site can be used in the new one.

Can the site be made without my involvement?

Yes, in the full-freedom format: describe the task in a few sentences, we take care of the rest, and you only sign off the result.

How does payment work?

Thirty per cent to start, the rest by stages as they are ready — usually three payments: advance, interim and on completion. Big projects with a long timeline are billed monthly. The terms are agreed before the work starts and written into the contract.

Do you sign an NDA?

NDA on request before the launch. Under an NDA the project is not shown anywhere at all. In any case we pass no materials or information about your project to third parties and never reuse them in similar projects for others.

Do you do promotion?

Basic optimisation for search and AI is part of every site. Promotion is a separate service after launch: SEO support goes on for months, and its scope depends on the competition in the niche.

Online form

Discuss
your project

Tell us about the task in a few sentences — we will look into it and suggest a solution. The consultation is free and commits you to nothing.

Or write to [email protected]