AnnLibertas

The new technology so far stands only here — the projects below are classic bespoke architecture and show what I can build and how it looks once people are using it.

There is an assistant at the desk. She knows the offer and the prices, answers a question at two in the morning, and when she does not know something she says so and passes it on — instead of inventing an answer.

She can see when I am free. Not with whom, not what about, not where. The calendar is shared so that the details cannot reach her even if the code gets it wrong.

What she can do

• Answer questions about price, availability, or how a project runs.
• Explain what behavioural guidance or cookie-free analytics actually do, without the marketing gloss.
• Book a consultation — she offers free slots from my calendar and writes a provisional booking.

The booking stays provisional until I confirm it. Until then Google sends you no invitation — you are not a guest in the calendar, only a note in it.

What this means for your site

This is the same thing I build for clients. For a hair salon only the skills change: book a cut, quote a price, send a confirmation. The model is the same, the calendar is yours.

The online space is changing right now and there is a chance to be part of that — rather than blending into the mass of “modern” fonts, vibecoded layouts and rocket icons. A lot of those dancing elements are not there for the visitor; they are the developer’s circus act.

The page opens, waits for someone to click, and meanwhile asks permission to track them. There is far more to play with here, and a few things can be done differently.

Interfaces will stop being surfaces to be searched and become places that know someone has walked in. It will be as ordinary as a page fitting a phone is today.

I build sites that know somebody is there — they recognise a visitor who is looking and not finding, and show the way themselves. They measure it without keeping a record of anyone. And they need no consent banner to do it.

What every site gets from me

Built into the site from the start:

• Being findable, in search engines and by AI assistants. The content is in the HTML from the start, not after a script runs, and every page has its own title, description and structured data.
• Accessibility. Usable without a mouse, readable by a screen reader, enough contrast, and nothing important conveyed by colour alone or sound alone.
• Security. HTTPS, security headers, monitored dependencies, input validated on the server, and limits on anything that can be called from outside.
• Speed. Images in current formats and sizes, fonts hosted on your own domain, and nothing running in the background when it is not visible.
• Privacy. Nothing is stored that is not needed. If the site can be built without a consent banner, it is built that way.
• Extensibility. Texts and prices in one place, a new page or language is an added record rather than a new file, and every optional feature has a switch.
• A face of your own. Your branding, not a template you can tell is a template.

If in six months you change your mind about a feature you turned down at the start, the answer will not be “that would mean rebuilding the site”.

Smart additions

They can go in straight away, or at any point later. The base is built to take them, so adding one does not mean building again.

Guidance works best where there is somewhere to get lost. On a one-page site it is more of an effect than a help — which is also a reason people order it.

Analytics has two ends. One runs in the visitor’s browser, the other sits on a server receiving the numbers and adding them up. The second one runs all the time, which is why it belongs in the monthly rate.

Starting prices

A basic site with the guidance comes to 50,000 CZK. With cookie-free analytics on top, 57,000 CZK — together with the guidance it costs 7,000 instead of 15,000, because both measure the same things. The assistant is priced by what you need from it and how far the automation should reach. The monthly fee follows measured token consumption — what actually gets used.

What it is built with

React and Vite, Tailwind for the looks, deployed to Vercel or to your own server. The assistant runs on Anthropic’s Claude models, the calendar through the Google Calendar API, payments through Stripe, mail through EmailJS or Resend.

This site is also the demonstration: the house, the room zoom and the guidance are built from the same things I build for you. The design you get is cut to fit you and what you do.

How we work together

1. The brief — what the site has to do, who it is for, what should happen on it. Confirmed in writing, even if it was agreed over the phone.
2. The concept — strategy and a description of the implementation, scope, price, deadline. Free.
3. A conversation about the concept — by phone, in person, by e-mail or on WhatsApp, whichever suits you.
4. The contract.
5. The deposit — work starts on the day it is paid.
6. Materials from you — texts, photos, logo, access. With a deadline.
7. Implementation with ongoing consultation — you see the site as it grows and confirm it matches what you expected.
8. Testing before handover — speed, mobile, accessibility, forms.
9. Handover and training — half an hour to an hour on a call, and one written page: where everything is, what you can change yourself, who to call.
10. Maintenance, if you choose that option.

Step six has a date of its own, because both sides plan around it. Texts and photos are usually what takes longest to arrive, and implementation stops without them. With a day in the schedule, everyone knows when what is coming.

Why you will not get a mock-up up front

It has become common to have a visual mock-up generated before the first meeting, so the client sees something immediately. I do not do that, and here is why.

Deciding what a site should be takes longer than anything else in the process. Sometimes it takes days before the idea settles. Once it has, implementation is a fast ride and only deployment and thorough testing take time.

What you get instead is the concept: a description of what will be built and how it will work. Also free, just more useful.

When you pay

20 % on signing · 40 % once the design is approved · 40 % on handover

For a smaller project 30 / 70 is enough. Each instalment is tied to a finished part, not to the calendar.

The deposit counts towards the total price. If the collaboration ends before completion, everything delivered up to that point remains yours, including the source code.

Domain and server

The first year of the domain is included in the main package; the following years go by the provider’s price list. The domain is always registered in your name, not mine.

The server works the same way: the account is yours, you pay the provider directly (around 200 CZK a month at Hetzner), and you give me technical access to your project — access you can revoke at any time. Neither of us sees the other’s payment details.

Every client gets their own server. Projects from different clients are never mixed, even when they would fit — if you pay for computing power, you should not be sharing it with a stranger’s project.

Hosting and maintenance

What the monthly rate covers — spelled out, because otherwise you will compare it with two-dollar hosting and the comparison makes no sense:

• uptime monitoring and an alert when the site goes down
• dependency updates and system security patches
• regular backups, and once a quarter a rehearsed restore — a backup nobody has ever restored is not a backup, it is a hope
• certificate management, including checking that renewal actually happened
• and a person who fixes it

What you receive at handover

1. A running site on a domain registered in your name.
2. The source code in a repository that belongs to you — with its history, not a zip of the last version.
3. Access — domain, server, third-party accounts. Handed over securely, never by e-mail.
4. Documentation — how to run and deploy the site, where everything is, what you can change yourself and what you should not edit.
5. A handover record — what was delivered, what was tested, what is under warranty and what is not.
6. Third-party licences — fonts, images, sounds, and what obligations they put on you.

You get an unlimited right to use the work, change it and hand it to anyone else.

When something needs adding later

• Fixing a defect is free, even after handover. If something does not work the way it was specified, it is a repair.
• Something new is charged at an hourly rate, with an estimate up front for anything larger.
• A prepaid block of hours at a lower rate — so you do not have to negotiate a price over every small thing.

I code interfaces that think and breathe.

I design websites equipped for the near future — with behavioural guidance, cookie-free analytics and spatial effects that turn a visit into something people remember. With an emphasis on security, and on being useful rather than merely impressive.

This site serves as a modest demonstration of those technologies.

Who I am

I am a developer. I write sites and applications in code rather than clicking them together in a template — which is why it is possible to build something that cannot be clicked together.

What I enjoy is pushing what a website can do. I want the online world to be smoother, less frustrating and more welcoming — a page should not be an obstacle between a person and what they came for. Asked what I do, the honest answer is: I bring other people’s ideas to life so that they serve the people who click on them.

An occasional letter about what is changing in software and on the web, and what is worth your attention. No advertising, one click to unsubscribe.