Costs
Editing content on a Q-Code site costs nothing, a change to a page costs about 16p, and a written and illustrated blog post costs about 47p.
These are measured figures from real runs, not a price list. Every task the platform performs is written to a ledger at the time it happens, so what appears here is what was actually spent rather than what it was expected to be.
Measured
| Action | Cost | What that covers |
|---|---|---|
| Editing content in a panel | Nothing | Testimonials, questions and answers, social links, the schedule, marking an enquiry read. These are database writes and never touch the build machine. |
| A change to a page | About 16p | One measured structure change through the chat box: 61 seconds, 16.1p, built to preview. Larger redesigns cost more because they involve more of the site. |
| A written, illustrated post | About 47p | Text is roughly 16p and each image roughly 7p. In-content images default to none, because they are the largest avoidable cost. |
| Publishing | Nothing | The build runs on a machine that sleeps when idle, and the published site is static files served from a global network. |
The reason
Adding one testimonial used to take 95 seconds. It woke a sleeping machine, ran an agent, committed a file, rebuilt the site and redeployed it, to append one entry to a list.
Nothing about that was broken. It was simply the wrong shape: the words on a page and the structure of a page had been treated as one kind of thing, so changing either cost the same as changing the harder one.
Separating them took the same edit to about a second, with the machine still asleep and nothing spent. The trade is stated rather than hidden: a visitor sees a content edit immediately, and a search engine sees it at the next publish, because the build-time copy is what a crawler receives.
Answers
Because they are different jobs. A testimonial is a row in a database, so changing it is a write that takes about a second and spends nothing. A post is a file with generated images, a feed entry and a sitemap URL, so producing one runs a model and a build. Splitting the two is what made most day-to-day editing free.
Images. Text for a post is roughly 16p and each image roughly 7p, so in-content images default to none and are switched on per post. A post with a hero image and nothing else is about 23p.
The published site is static files on a global network, so serving it costs nothing meaningful. The build machine sleeps when idle and wakes in about seven seconds when something needs building.
Between roughly £84 and £116, depending on whether each post carries one image or two. That is the figure the schedule panel is honest about before you switch it on, rather than after.