Company websites and landing pages — a studio from Gdańsk

A company website usually breaks in one of two ways: either every text change needs a developer, or somebody made everything editable and six months later no two subpages look alike.

A good company website is one base and a handful of things that can be changed inside it safely. The rest — speed, accessibility, language versions, structured data — should be done once and then need no attention.

Simplified illustration: the page editor, a selected block and the language versions. An illustration, not a screenshot from a deployment. The photographs in this visualisation were generated by artificial intelligence. They do not show real products, real interiors or a real company — they serve only to illustrate the interface.

What the scope covers

  • Design and copy arranged around one question: what should the visitor do
  • A block editor — you change the content yourselves, without a developer and without breaking the layout
  • Language versions on one base: switching the language changes the text, not the layout
  • Speed measured before launch, not after a complaint
  • Accessibility: contrast, keyboard operation, screen reader
  • Structured data, a sitemap and a link preview in messengers
  • A contact form with a consent mechanism that satisfies GDPR
  • Hosting, SSL certificate, backups and monitoring configured within the implementation
  • No cookies and no external scripts wherever they can be avoided — fewer consents to collect
  • Documentation, handover of accesses and full ownership of the code

Hosting, the SSL certificate, backups and the technical side of GDPR duties are configured as part of the implementation — they belong to the agreed price, not to a separate line item. Ongoing care of a running system, meaning updates, monitoring and support, is a separate subscription, quoted at handover.

How we work

  1. The purpose of the site

    We settle what the visitor should do and how we will know they did it. Without that, a visual design is a matter of taste rather than a decision.

    What we need from you A decision on who the audience is and what should happen after they arrive.

  2. Copy and structure

    We lay out the pages and the texts before any graphics. A design built for finished copy looks different from copy written into a finished design.

    What we need from you Materials: descriptions, photographs, company details. This is the most common cause of delay.

  3. Design and build

    We design and build the site together with the block editor, from the start in both phone and desktop versions.

    What we need from you One person with authority to decide on your side — notes from five sources contradict each other.

  4. Checks before publication

    Speed, accessibility, structured data, forms and language versions. It is the same set of checks our free audit runs.

    What we need from you Approval of the copy in every language version.

  5. Publication and care

    Launch, handover of accesses and a short training on the editor. Care is a separate agreement.

    What we need from you Access to the domain — the one thing that cannot be worked around.

Page speed and sales — your numbers, not averages

Work out the difference in sales under your own assumption about what a second is worth.

The time the largest element on screen appears. Measure it with our free audit.

This is your assumption — ideally from your own test. We have no number to put here and deliberately do not invent one.

Fill in every field — without them there is nothing to calculate. We substitute no default values, because each of them would be our assumption rather than yours.

This is arithmetic from the assumptions you entered, not our forecast. Every number in the result comes from the fields above — there are no market averages and no estimates of ours in it.

Open the full calculator →

Common questions

Will we be able to change the content ourselves?

Yes, and that is the point of the block editor. You change texts, photographs and the order of sections, while the layout and the typography stay consistent, because they are not handed over for editing.

Will the site be on WordPress?

Usually not, and we say why. WordPress makes sense for a large, frequently changed site built on plugins; for a company website you pay for it in updates and vulnerabilities. If in your particular case it is the better choice, we will say so instead of selling our own solution.

Will you build language versions?

Yes, on one base: switching the language changes the text, not the layout. You can supply the translations yourselves or commission them separately — we do not machine-translate without your agreement, because the content is yours to answer for.

What PageSpeed score will we get?

We measure speed before publication and treat it as part of the scope, but we do not promise a particular number of points: it also depends on your photographs and content, and it moves with every update of the Google tool. You can check the result at any time with our free audit.

Will the site have a cookie banner?

Only if there is anything for it to cover. Consent is required for non-essential storage on the device — with no analytics tools and no external embeds there is nothing to ask about. The site you are reading right now stores no cookies at all.

Who pays for the domain and hosting?

Configuring hosting, the SSL certificate and backups is part of the implementation scope. We recommend registering the domain to your own company — whose site it really is depends on that. Ongoing care is a separate subscription.

How long does a website take?

A business-card site is usually the fastest of our projects, but the number of subpages and the readiness of the content can move the schedule more than the build itself. We set the date together with the scope and the fixed price, before work begins.

Let us talk about your project

Pick a time for a call or leave your number — we call back during working hours.