How much does a website cost?

There is no honest flat price for a website or web system: the budget follows scope. The drivers are the number of templates and unique screens, whether there is business logic and user accounts behind the pages, which integrations are in scope, and how much content and design exist before we start. We scope the work first, then give a fixed, itemized quote — what is included, what is excluded and what would change the number. We give a precise quote after one discovery meeting.

How long does it take to build a website?

A brochure site — 4 to 8 weeks. A more complex site — 2 to 4 months. A web platform — 3 to 6 months.

WordPress or custom development — which is better?

It depends. WordPress is great for content sites and blogs. For platforms, web apps, or advanced experiences — custom development with Next.js gives a faster, more secure, more precise result. We'll tell you straight what fits.

Does this include design?

Yes. For us, design and development are one process. A full in-house UI/UX team.

Does this include SEO?

Technical SEO — yes, built into every site we ship. Content optimization and authority building — ongoing work we can manage with you.

What about GEO — optimization for AI?

Yes. We build sites that appear in answers from ChatGPT, Claude, and Perplexity. In some niches it's already 30% of traffic — and only growing.

Does this include hosting?

We recommend modern hosting (Vercel, Cloudflare, AWS) and help with setup. The control and ownership stays with you.

Do you build multilingual sites?

Yes. Multilingual is something we do a lot: per-language URLs and hreflang, translations workflows, right-to-left support where needed, and dedicated SEO per language.

What about maintenance?

Monthly maintenance packages available — security updates, backups, small features, fixes. Or on-demand.

Who owns the code and the site?

You do. No "buts." Code, domain, hosting accounts — all yours.

I have an old site — can you upgrade it?

Yes. Sometimes a smart upgrade beats building from scratch. We'll audit, recommend, and execute.

Do you build content sites and blogs?

Yes. With a headless CMS for easy editing, and a structure Google and AI both love.

What is the difference between a customer portal and an internal system?

The user and the business action. A customer portal serves people outside the organization — they have had no training, they compare you with competitors, and their experience is part of the product; so it needs simple sign-in, self-explanatory screens and self-service. An internal system serves employees who can be trained, with multi-step processes, role-based permissions and management reports. Often both run on the same engine — with a separate interface for each audience.

How is data moved from an existing system into the new web system?

With a migration plan written before development, not after it: what moves, what stays in the old system, how mismatched fields are mapped, and how you verify everything arrived — usually with a trial run on a copy of the data, and sometimes a parallel-run period in which both systems operate side by side. The quality of the existing data is what determines the size of this work, which is why it is checked early.

Service · Websites & Web Systems

Websites &Web Systems

Your website is your best salesperson. Works 24/7. Never takes a vacation.

Most companies think of their website as a "digital business card." We think differently. Your site is the first — and sometimes last — touchpoint with a customer. It decides whether they stay or leave. Buy or look for a competitor.

In 2026, a site has to be fast, beautiful, clear, and adapt to every screen. But also something less talked about: it has to be built for an environment where AI bots crawl it and decide whether to surface it in their answers. We build from scratch. No templates. No shortcuts.

01 / What we build

What we build

From a brochure site to a full platform. From a landing page to a marketplace. Each one built for its specific goal.

01
Corporate websites
Your company's main site. Custom design, copy that converts, excellent performance. Not a template.
02
Landing pages that convert
Single pages focused on one action. Leads, sign-ups, purchases. Built-in A/B testing.
03
Online stores
Shopify, WooCommerce, or fully custom. From product to checkout — a smooth, frictionless flow.
04
Web systems & platforms
Systems users log into every day. SaaS, B2B, internal portals.
05
Content & media sites
News sites, magazines, blogs. Built for SEO and speed from the ground up.
06
Marketplaces
Two-sided platforms with payments, user management, ratings and reviews.
07
SaaS product sites
Your product's marketing site. What it does, how to sign up, how to pay. The full flow, end to end.

02 / Which site do you need

Brochure site, landing page, store or web system — which one do you actually need?

"Website development" covers five very different products, each with its own timeline and budget. Before anyone talks design, it helps to know which one you are building.

Type	When it is the right call	How we build it
Corporate / brochure site	A company that needs a professional presence, service pages and leads — without complex business logic.	Next.js + headless CMS, green Core Web Vitals, SEO and GEO from day one.
Landing page / campaign	One message, one audience, one action. Paid campaigns, launches, A/B tests.	Static and extremely fast, full measurement, variants for testing.
Online store	Selling products directly. Catalog, cart, checkout, shipping and inventory.	Shopify or WooCommerce when that is enough; a custom headless store when the experience or integrations demand it.
Web system / web app	Users log in and get work done: customer portal, admin system, internal tool, SaaS.	Fully custom — frontend, backend, permissions, integrations. At this point it is software development in every sense.
Platform / marketplace	Two or more sides (suppliers and customers), payments, ratings, complete business flows.	Architecture planned for growth, an operational back office, and a clear v2 roadmap.

Not sure where your product lands? That is exactly the first question in the discovery meeting — and it drives the budget more than any design decision.

03 / The approach

We don't build on templates.

Not because we're snobs — because templates don't serve you. They serve the company that sold them. A custom-built site runs faster, is easier to maintain, and actually reflects who you are.

2026 standards
Built for the right era
Core Web Vitals, accessibility (ADA, WCAG 2.2 AA), Schema.org, structure crawlable by AI agents — not just Google.
Design before code
Design first. Then code.
Changing a screen in Figma is cheap. Changing it after it's coded is expensive. Every site is fully designed before a single line of code.
SEO + GEO from day one
Found on Google and AI
Built for rankings from the foundation up — semantics, structure, schema, speed. AI bots find you, Google ranks you.

04 / Web systems and portals

A system for customers, employees or partners?

A web system is not a website with a login. It is a place where people get work done: submit, approve, compare, report. The first distinction is who the user is and what the business action is — because that decides the sign-in, the permissions and what has to be simple.

Most systems we build combine two or three of these types on one engine — a customer portal plus an admin system for the team, or an environment for suppliers alongside one for project owners.
System type	Who the user is	The business action	What it specifically requires
Customer portal	Existing customers — consumers or businesses — outside the organization	See a status, submit a request, pay, download a document, open a ticket	Simple sign-in, self-service, self-explanatory screens; zero training
Employee portal / internal system	Employees in different roles, sometimes field staff too	Run a process: draft → approval → execution → closure, with management reports	Role-based permissions, multi-step processes, organizational sign-in (SSO)
Partner / B2B portal	Suppliers, distributors, agents — other organizations with their own users	Submit a bid, update stock, order, report — against your data	Separation between organizations, user management on the partner side, a data interface (API) alongside the screens
Admin / back-office system	The team that operates the service	See everything, handle exceptions, approve, export	An audit log, search and reports, admin permissions separated from end users

What a portal includes — in practice

Sign-in
Email and password, an SMS code, a Google or Microsoft account, or organizational SSO — depending on the audience. Password reset and lockout after failed attempts are part of the baseline, not an extra.
Permissions
Who sees what, who changes what, who approves. By role, and sometimes by organization or branch. Actions that need two people are defined up front.
Documents
Upload, secure storage, versions, PDF generation, signing when required. Who may see each document follows from permissions — not from a link.
Processes and states
Each entity has a lifecycle: draft, pending, approved, closed. Who moves it between states, and what happens in exceptions — cancellation, rollback, change after approval.
Notifications
Email, SMS or an in-app alert when something is waiting for action. To whom, when, and how often — so they do not get ignored.
Reports
The questions management needs to answer from the system without asking a developer. An Excel export is almost always the first report requested.

How does the system connect to the business?

A web system almost never stands alone. Every integration has to answer three questions: what passes through, how often and in which direction, and what happens when the other side is unavailable.

Connecting to a system with a documented API is a completely different job from connecting to a legacy system with no interface. It is one of the first questions in discovery, because it drives scope more than most design decisions.
System	What passes through	Frequency and direction	What happens on failure
CRM	Customers, contacts, tickets	Two-way, real-time or every few minutes; the source of truth for the customer is defined up front	The system keeps working on the data it has; updates are queued and sent when the connection returns
ERP / accounting	Orders, invoices, inventory, price lists	Usually orders go out, inventory and prices come in; sync cycles are defined	An order does not vanish — it is marked 'pending sync' and someone sees it
Legacy system / files	Historical data, spreadsheets, documents	A one-off migration at the start, sometimes periodic imports until the old system is retired	An exceptions report: which rows were not imported and why, so they can be fixed and rerun
Messaging (email / SMS / chat)	Alerts, confirmations, codes	Outbound only, immediate	Automatic retry; the message is logged in the system even if the external provider fails
Organizational sign-in (SSO)	The user's identity and role	On every sign-in	No sign-in without authentication — but a clear message and a way to reach support

Users and permissions — an example

A table like this is usually the first document we write together. The example here is invented — a service portal for a company with business customers — not a client's data.

Two rows in this table save most of the arguments later: who approves, and what management does not see by default.
Role	Sees	Creates / edits	Approves
Customer (a user at the client organization)	Only their own organization's tickets, orders and documents	A new ticket, a new order, contact details	—
Manager at the client	Same as customer, for all users in their organization	Adding and removing users in their organization	Orders above a defined amount
Service rep	Tickets and orders of the customers assigned to them	Ticket status, replies to the customer, internal notes	—
Team lead	All tickets and orders, workload per rep	Assigning customers to reps, reply templates	Credits and cancellations
Management	Aggregate reports; no access to individual tickets by default	—	—
System admin	Everything, including the audit log	Roles, permissions, integration settings	Permission changes for other users

Testing, migration and handover

Acceptance criteria per process
For every process in the system we write down in advance what counts as 'working': who does what, with which data, and what the result is. Testing — ours and yours — is done against that list, not against a feeling.
Data migration
What moves, what stays, how mismatched fields are mapped and how it is verified. A trial run on a copy of the data before the real cutover, and an exceptions report for anything that did not import. When needed — a parallel-run period.
Rollout and adoption
A pilot with one user group before opening to everyone; training for the people who will work with the system; and measurement of what is actually done in it during the first weeks — because a process nobody uses is a process to fix, not to explain.
Handover and maintenance
The repository in your name, cloud accounts and domain in your ownership, operating and configuration documentation, and a list of what was built against the specification. Maintenance after that — monitoring, updates, incident handling — under a separate agreement, within the scope and service hours it sets.

What this looks like in a real system

KICK AI is a real-time web system with two faces: a mobile-first game for players and an admin platform for the operators — rounds, formats, content and live control — on the same backbone, with permissions that keep each side where it belongs. Dividandy adds a third: a back office that runs tournaments, wallets and growth for a product that lives on iOS, Android and the web. Both case studies describe how the operating side was built into the system.

05 / Sites and systems we built

Websites and web platforms we built — and that work

Three web products you can open today: a two-sided tender platform, an employee-onboarding system and a real-time gaming layer. What we built in each — in the full case study.

06 / Technology

Our stack

A full stack — from modern frontend, through headless CMS and commerce, to CDN, search and analytics. We pick the right tool for each site.

Frontend

Next.js
React
Vue
Astro
Remix
TypeScript

CMS

Sanity
Contentful
Strapi
Headless WP

E-commerce

Shopify
WooCommerce
Medusa

Hosting & Edge

Vercel
Netlify
Cloudflare
AWS

Algolia
Meilisearch
Elasticsearch

Analytics

Google Analytics
Plausible
PostHog

Performance

Edge Functions
CDN
Image Optimization
ISR

SEO & Schema

Schema.org
OG
Sitemaps
Hreflang

07 / How we work

How we work

01
Understand the goal
Brochure, sales site, platform? Who's the audience? What's the single most important action? Everything else builds from there.
02
Structure & UX
Sitemap, information architecture, user flow. Three clicks max to the goal.
03
Custom design
Our designers start every site from a blank Figma page. No templates, no "what everyone else is doing."
04
Frontend & backend dev
Two-week sprints. Something to see at the end of each one. No surprises, no "we'll show you in two months."
05
SEO & speed optimization
Pre-launch: Core Web Vitals, accessibility, on-page SEO. All green. No compromises.
06
Launch & migration
Move from staging to production. Domain, SSL, analytics — all handled.
07
Ongoing support
A site isn't "ship it and forget it." It needs updates, new features, optimization. We stay with you.

08 / Who it's for

Who this is for

B2B companies
Need a site that signals trust and expertise from the first second.
Startups
Need a launch site before a funding round or going to market.
Established businesses
With an old, slow site that needs a serious upgrade.
Stores
Want to launch online commerce — or upgrade what they have.
Founders
With a platform idea — and a need for someone to build it from scratch.

09 / Why us

Why us

Design + dev under one roof
A full UI/UX team in-house. You won't need an outside designer who doesn't speak code.
Obsessive about speed
Our PageSpeed scores are green. Because every second of slowness is a customer walking away.
SEO from day one
Built for rankings from the foundation. Not bolted on after the fact.
Service that doesn't end at launch
Monitoring, alerts and fixes — within the scope and service hours set in the maintenance agreement.

FAQ

Frequently asked questions

Let's talk

Need a website that actually works?

A 30-minute intro call. No strings attached. We'll figure out together if we're a fit.

Straight. To the point. On time.