Build and code: website development

You have an approved design in Figma and the site finally needs to go live on your domain. This is the stage where quality most often slips: spacing drifts, the animations from the mockup vanish, and a page that looked great on the designer's screen takes several seconds to load on a phone. Your customer will never see the design file. They see what loads in their browser, and that is what they judge your company on.

We code every view from scratch, following the approved UX/UI design down to the dimensions, states and motion in the mockup. We do not adapt ready-made themes, so the site carries no features nobody uses and loads only what is in the design.

The design can come from another designer or from your own team. Before we quote, we check the files: every button and form state, the phone and tablet views, the content for each page. If something is missing, you get a list of the gaps and a proposal for who fills them, us or your designer. The quote for the build is written only after that review, so no line items appear mid-project that were never discussed.

Four stages separate an approved design from a site running on your domain: the front-end code, the content panel, device testing and launch. We check each of them before acceptance, before your customers see the site.

We code so the site can be extended later. A blog, a second language, a store or booking can be added without rewriting the whole thing, because the components and content structure are built for it. Those stages are quoted when you need them, so the first invoice covers what you are ordering now. A standard build includes:

• Front-end in semantic HTML, Tailwind CSS and TypeScript that browsers, search engines and screen readers can all read.

• A headless CMS (Sanity or Storyblok) where you change text and images and add pages without a developer.

• A mobile-first layout, tested on real phones and tablets before you see the version for acceptance.

• Optimisation for Core Web Vitals

  images at the right size, lazy loading and scripts split into smaller chunks (code splitting).

• WCAG 2.2 AA accessibility, meaning contrast, keyboard use and screen readers, checked before handover.

• Launch on your domain, with the server, domain and hosting configured in accounts that belong to you.

A business or brochure site that has to present your offer and bring in enquiries is usually built on Astro: it produces light pages that load fast even on a weaker phone. Where the site needs more logic (a client area, a calculator, logins), we use Next.js and React. Rendering follows the content: pages that rarely change are generated statically (SSG), and where data has to be fresh we use SSR or ISR.

The content panel is usually Sanity or Storyblok, both headless CMSs. This site runs on Sanity as well. We deploy on Vercel or on hosting you already have. Stores are built on Shopify or as a headless setup, and applications on React, Next.js or Laravel; that scope is described separately under web app and PWA development.

The technology decision is made in the strategy phase, once we know who will edit the content, how often the site will change, which systems it has to connect to and how much traffic it has to handle. If you have hosting, a panel or a platform your team is used to, we take it into account. If that choice would hurt speed or running costs, you hear it on the first call, together with a proposed alternative.

Speed on mobile is one of our acceptance conditions. If the site scores below 85 on PageSpeed Mobile, it comes back to us and we work on it until it clears that bar. We build to Core Web Vitals: images load lazily and at a size that fits the screen, scripts are split into smaller chunks, and the layout does not jump while the page loads.

If the project includes animation and 3D elements, optimising how they load is included in the build. Models and scripts are fetched only when the visitor scrolls to the section that needs them, and with reduced motion enabled in the system the page stays static. The effect should impress once it has loaded and must never delay the first screen.

We check WCAG 2.2 AA accessibility in the same review: contrast, keyboard use, screen readers and reduced motion. We also test on different devices and browsers, because a layout that works in Chrome on a desktop can fall apart in Safari on an iPhone. You get the test version at a staging address and have time to send feedback before the site moves to its final domain and your customers see it.

The price of the build depends on the number of views and page templates, the CMS, the integrations and whether we migrate content from your old site. A simple contact form is an hour of work; booking, a quote calculator or a CRM sync is a separate stage with its own quote. If you order the whole site from us, design and code come in one package price from our pricing: a business-card site from PLN 3,000 net, a website with a content panel from PLN 4,500 net, an online store from PLN 8,000 net. You get a free quote with the scope and schedule written out within 48 hours of our call.

The build is part of the overall project schedule: a business website usually takes 2–6 weeks, an online store 3–12 weeks. Stage dates come with the quote, so you know when you will see the first version and when the site goes live on your domain. If you need it sooner, we check the calendar and propose an express track at a surcharge. Three standalone add-ons can be added to the build:

• Content migration from your old site. We move text, images and the URL structure, set up redirects so the site keeps its search rankings, and verify the data after the migration. From PLN 600 net.

• Performance testing and optimisation. After launch we run full Core Web Vitals tests and remove bottlenecks by hand instead of adding another caching layer. The goal is 90+ on PageSpeed for mobile. From PLN 1,000 net.

• CMS training. A two-hour video session with your team

  how to edit content and add pages without breaking anything. You keep the recording. From PLN 600 net.

After acceptance you have access to the code repository, the hosting panel and the CMS, and the domain, hosting, content panel and code belong to you. Custom solutions are documented in a README. If your team will maintain the site themselves, we add technical documentation written at their level: one way for a developer, another for someone in marketing.

For 30 days after acceptance, bugs caused by our code are fixed free of charge. What counts as a bug and what counts as a new feature is written into the contract, so there is no argument about it later. Once that period ends, you can move to ongoing website support and growth: updates, backups, monitoring and new features without starting a new project.

Kacper Baranowski runs the project personally, so a question about the code goes back to the person who wrote it. Every message gets a reply by the end of the next working day. And if you ever choose another developer, the documentation and access details let them take over the site without rewriting it from scratch.

Build and code is included in three offers: business websites, online stores and industry websites. When you order the whole site, the price for design and code together is on the offer page. With every build we also set up technical SEO and analytics: heading structure, metadata, the sitemap and conversion tracking, because the code is where the search engine learns what your site is about.

Have a finished design, a site that needs rewriting, or a theme your company has outgrown? Describe your situation in the form at the bottom of this page. We reply no later than the next working day, arrange a short online call, and within 48 hours of it you get a quote with the scope and schedule. You decide only then.