How many hours an AI-built project takes
Our three latest projects, counted in hours. The smallest took about 15, the largest about 45. We show hours rather than amounts, because hours tell you how much work sits in a scope like this.
Three recent projects in hours
AI writes the code and the first draft of the copy. Our hours go into the plan, a review of every change, testing and deployment, and that is what these numbers measure.
webowiec.net
Two WordPress sites merged into one
- A new Next.js front end and a CMS with nine content types
- Posts and the catalogue moved over from two WordPress installs
- A blog with an archive and search, a two-level catalogue, comments
- Redirects for old addresses and a form protected against spam
about 15hourschrzescijanie-rzeszow.pl
A community site moved off WordPress
- Content migration, with the old addresses still working
- A song player with the vocal mix rendered on the server
- The Book of Enoch to read on the page and download in eight formats
- Bible quotes pulled from an open API
We count the build up to the end of August 2026. Articles written later are separate content work.
See the case studyabout 30hourstoprawdziwe.pl
A shop directory with a map and travel times
- A map on OpenStreetMap, with no Google Maps keys or fees
- Travel time computed in the browser, calibrated on 460 real routes
- Filters, search with a synonym dictionary, discount codes
- Mobile performance score raised from 81 to 91
Including a redesign in April, after the first version from February.
See the case studyabout 45hours
How we count: the hours come from the change history of the repositories, front end and API together. A work session runs from the first change to the last, plus half an hour to start. Automated library updates are left out.
We describe scopes like these as packages:
How we get to your number
- 1
A phone call
Twenty to thirty minutes. What the project is about, what it has to achieve, what already exists and what the deadline is.
- 2
A look at the project
The current site, the content, the data and the integrations. If there is code, we read the repository too.
- 3
An estimate in hours
The hours for the agreed scope, together with a list of what could change them.
How billing works
You pay for the hours you can see in the task system: what was done and how long it took. You have access to it for the whole project.
One rate covers the project, fixes and care. It starts at 60 euro net per hour (about 260 PLN), and we give the exact figure after a call. There is no rush surcharge as long as we agree the deadline together.
Common questions
Why so few hours?
AI writes the code and the first draft of the copy. Our hours go into what AI will not deliver on its own: the plan, a review of every change, testing, deployment and the fixes after it. We do not cut that, because that is what we answer for.
What drives the number of hours?
How much copy has to be written, how many pages there are, the state of the old site in a migration, integrations with outside services, and how many design decisions have to be made from scratch.
Will I get a fixed project price?
You will get an estimate in hours for the agreed scope, and the rate. If the scope changes, the new estimate comes before the work, not after it.
What do the hours include?
All the work: design, code, copy, deployment and fixes. Only external costs are separate when a project needs them, such as a domain or a paid service you run yourself.
Is care after launch mandatory?
No. We recommend the first three months included in the project, and after that it is your call. The promise that we stay after launch should be true, not compulsory.
How soon do we start?
We agree the date together, after the call and the project review. We will not promise a start tomorrow just to close the conversation.
Let's book a call
Write two sentences about the project and leave a number. We will call back, and after the call you get an estimate in hours.