Websites for companies
I run the entire build, from analysis and copy through to deployment on a server, and then I grow the site with you every month.
I start with analysis
Not with a template. I work out who should land here and why, and the structure of the site follows from that.
I write the copy and build the site myself
Nothing gets handed off between a sales team, a designer and a developer.
The site is yours from day one
I share the code on request, so you can take the site with you.
The site is not left on its own after launch
Every month you get a pool of hours for content and for search visibility.
Who this page is for
I work with companies that sell to other companies and need a site that works for sales rather than one that just looks the part. Most often they are wholesalers, importers, manufacturers and service firms employing anywhere from a few to a few dozen people.
This describes your company if at least one of these is true:
- The site was built years ago, nobody has touched it since, and today you would be embarrassed to show it to a client.
- The site is there, but no inquiries come through it, and nobody can say why.
- There is no site at all, because referrals were enough until now, and they have stopped being enough.
How the work runs
Five stages, always in the same order. The first is a pre-implementation analysis. That stage is paid, and it ends with a document that stays with you even if the build never happens.
- [ 1 ]
Stage 1 · Analysis
I work out who should land on the site, what they are looking for there and what they should do. I go through your competitors and through the way clients reach you today.
What you are left with: a site map with a reason for every page.
- [ 2 ]
Stage 2 · Copy
I write the text for the needs we agreed and for search engines, including the answers generated by artificial intelligence.
What you are left with: a complete set of texts to approve before anything is drawn.
- [ 3 ]
Stage 3 · Design
I design the layout on finished copy, because the layout should serve what there is to say.
What you are left with: mockups of the home page and the subpages.
- [ 4 ]
Stage 4 · Build and launch
I build the site and set up the server, the certificate, the backups and traffic measurement.
What you are left with: a working site, and on your side the domain, the analytics tools and, on request, the code repository.
- [ 5 ]
Stage 5 · Growth
Every month we add content, improve visibility and measure whether inquiries are going up.
What you are left with: a report from the measurement and a list of changes.
The analysis can be ordered on its own. If you do not yet know whether you need a new site or fixes to the one you have, start with the analysis alone. You get a map of what has to be done, in order, with an estimate of the effort. You make the decision about building after it, not before.
The site is yours from day one
The code, the content and the domain belong to you from the moment the site goes live on the server, not from the moment a contract ends. The complete set of files, together with the history of changes, sits in a code repository that I share on request, so you can move the site to another supplier or host it yourself at any time, including after we stop working together. I do not build on a closed platform you cannot leave.
There is no limit on the number of pages here, and no list of things the template did not allow for. The structure comes out of the analysis, so if your sales need a separate page for every product group, that page gets built.
What it costs, and what exactly you pay for
Billing has two parts, and we agree both before we start.
The build is a fixed price. I give you the figure after the analysis, because only then is it clear how many pages there will be and how much has to be written from scratch. The fixed price does not change while the work is going on, so you know the cost of the build up front.
Growing the site is a fixed monthly fee with a pool of hours. Within that pool we add content, improve search visibility and make the changes you ask for. The fee also covers the server, the backups and the certificate. If a month needs more work than the pool covers, I say so before doing it and give you the rate for the extra hours.
The monthly fee is not technical maintenance. Merely keeping a site running costs a few hundred złoty a year, and nothing follows from it. The pool of hours is there so that the site grows by something every month, because visibility in search comes from work repeated over time, not from a single launch.
How it looks in practice
As of August 2026 Smaczaki: a wholesale website for an importer of dog treats
eight pages with a catalog of more than a hundred items, running as a static site on my server, with no database and no software fees. A month passed from order confirmation to launch, and the day after the site opened to search engines its home page was already in the Google index.
See the case study
As of August 2026 Spretech: a website and CRM on HubSpot
A website in three languages and a CRM on HubSpot's free plan for a spring manufacturer in Katowice. Six days passed from the pre-implementation questionnaire to a working site.
See the case study
You have a client who needs a site
If you run an agency, advise companies or sell SEO and you need someone to do the build, I come into the project as the builder. We agree how the roles split before we start, including who talks to the client and whose name the work is signed with.
A client you bring is your client. I do not talk to them outside the agreed scope. If you want, I work entirely on your side, and the client need never know that someone else is working on their site.
Frequently asked questions
How is a build with you different from a subscription site at a few hundred złoty a month?
The difference is in what you get for the monthly payment. In the subscription model you pay for a ready-made template, a limit on pages and a few hours of small fixes, and the site usually becomes yours only once a multi-year contract ends. With me the build is a separate, one-off cost, the site is yours from day one, and the monthly fee is a pool of hours spent on content and on search visibility.
Who owns the site, and can I take it with me?
The site is yours from the moment it goes live, together with the code, the content and the domain. All of its files, along with the history of changes, sit in a code repository that I share on request. You can move the site to another supplier or host it yourself whenever you like. There is no waiting period before ownership passes to you.
What does the monthly fee cover, and what happens when the hours run out?
The fee covers an agreed pool of hours spent on the site, plus the server, the backups and the certificate. The hours go to whatever matters most in a given month: new content, visibility work, or changes you have asked for. If a task goes beyond the pool, I tell you before I start it and give you the cost of the extra hours, so the bill is never a surprise.
Does a first conversation commit me to anything?
It does not. The first conversation is there to work out what you actually need, and whether I am the right person for the job at all. It does happen that after a conversation like that I advise against building a new site and point out what to fix in the current one.
Let's start with the analysis
Tell me briefly what your company does and what brings you to me. I will come back with a proposal for a first conversation, and after it you will have a specific scope together with a cost.