For agencies and freelancers

Priced per site, not per seat.

Twenty client sites are twenty ordinary subscriptions at €19 or €79 each — no reseller tier, no minimum commitment, no volume threshold to qualify for, and no cap on how many sites one account can hold. Each site has its own panel, its own plan and its own API key, and you cancel them one at a time as clients come and go.

The per-site model was not chosen to be generous. It is the only structure that lets a client leave without unpicking a bundle, and the only one where your margin does not depend on renegotiating a contract every time you win work.

What changes about the work

The tool part is ours. The judgement is yours.

Nothing here replaces knowing a client's market. What it removes is the six hours per site of technical setup that you cannot bill for at a rate anyone is happy with.

Production, not assembly

Form to eleven finished pages in under three minutes, with the structure confirmed up front so pages link to each other and the menu is never empty. Then you edit — which is where your time is actually worth billing.

The technical layer, once and for all clients

Sitemap, robots.txt with the AI crawlers named, llms.txt, IndexNow, canonical, hreflang, structured data, mobile hygiene enforced by code. Per site, every publish, without a checklist. The full list.

Something to show at the review

Search Console and Bing figures, PageSpeed, first-party analytics, conversions and form submissions — per site, in one panel. The audit produces a list of proposed actions, which is a far better retainer conversation than “we monitored it”.

Automation over MCP

Every site issues its own API key. Drive it from Claude Code, a terminal, or Claude and ChatGPT over OAuth — and the reasoning bills to your assistant subscription, not to our AI budget. How to connect it.

Your client's property stays theirs

The Search Console property is created in the client's own Google account, in their name, with their sixteen months of history. You are not holding a hostage, and you never have to explain why you are.

Import, do not rebuild

Take over an existing client site without retyping it. Content comes across, head tags are localised on the way in, and 301 redirects are managed from the panel.

The arithmetic

What the margin actually looks like.

Your numbers, not ours — but this is the shape of it, and it is the reason the per-site price is where it is.

Per client siteYour costWhat you can bill for
Platform€19 / month (Pro)Pass through, or absorb into the retainer
Build timeMinutes of generation, then your editingThe build fee, at a much better hourly rate
Technical SEO setup€0 — it is automaticIncluded, and it actually gets done
Monthly upkeepApproving audit actionsThe retainer, with a list to point at
AI generationInside the plan, or your own key, or your Claude / ChatGPT subscription—

If you generate heavily, connect your own OpenRouter or Gemini key: the platform's monthly AI budget stops applying entirely, because you are paying the provider directly. Or write the pages through your assistant and pay nothing extra at all.

Before you commit a client

Where the gaps are.

These are the things an agency will hit in the first month. Better here than in front of a client.

The admin panel is Timbaly-branded

The published site carries no Timbaly branding on any paid plan — no badge, your client's domain, your design. But the panel your client logs into says Timbaly, and there is no reseller-branded or custom-domain admin today. If your model requires the tool to be invisible, this is the gap that matters.

No shared team accounts per site

Access is per account, and there is no per-site role model for handing one client's site to one colleague without giving broader access. Workable at freelance and small-studio scale; worth checking against your process before you move twenty sites.

Pages, not applications

Booking engines, configurators, members' areas and live ERP integrations are not what this builds. If a client needs software, this is the wrong tool and saying so early costs you nothing.

Generation is not deterministic

Roughly one page in ten fails on a model loop in a large batch. It stays in the plan with a Retry and the rest is unaffected — but if you are building at volume, expect to click Retry rather than to walk away mid-run.

Agency questions

The commercial ones.

Is there a reseller or agency tier?

No, deliberately. Pricing is per site, so twenty client sites are twenty ordinary subscriptions at €19 or €79 each — nothing to negotiate, no minimum, no volume threshold, and no bundle to unpick when a client leaves. The plan comparison.

Whose name is the client's Search Console property in?

Your client's own Google account. An agency cannot afford to be the registered holder of its clients' search properties, and a platform that made itself the holder would be selling a hostage. Multiple verification tags coexist on purpose, so you and your client can each hold one without silently disconnecting the other.

Can I white-label it?

The published site, yes — no badge on any paid plan, your client's domain, your design system. The admin panel, no: it is Timbaly-branded, with no custom-domain admin today. That boundary is stated above rather than discovered.

Can I automate production across many clients?

Yes. Each site issues its own API key and the MCP connector exposes the management surface to Claude Code, a terminal, or Claude and ChatGPT over OAuth. Pages written that way go through exactly the same publishing pipeline — same link sanitisation, same versioning, same SEO fields — so they are not second-class. Setup details.

What if a client wants to leave?

They take the domain, the content and their Search Console history. You cancel that one subscription; the other nineteen are untouched. Cancellation is end-of-period, never mid-month.

Try it on one real client site.

Build it on the free plan first — no card, and you can show the client before anyone commits. Then €19 a month puts it on their domain, indexable.

English Italiano