Context
Practices, clinics, shops and associations need a site that runs and that their teams can keep alive, without a technical lead. Every site rebuilt from scratch is expensive and ages alone. A single platform, operated daily, now serves around twenty sites.
A common base, distinct sites
Each site has its domain, its design, its content and its languages; all share the same base: static page generation, optimised images, schema.org markup, online editor. A security fix or an improvement benefits all of them in one update.
Automated content, reviewed before publishing
Assisted writing, classification, illustration, translation: an automated content chain (OpenAI, AWS Comprehend, Rekognition) prepares; a person reviews and publishes. Example in production: a restaurant’s weekly menu extracted by AI vision.
Publishing in three steps
Workspace, pre-production, production. Teams see before they publish; mistakes stay upstream. Performance is measured with public tools: between 88 and 100 in mobile performance, 100 in technical SEO on delivered sites.
Result
Around twenty sites in production, operated daily, which the clients’ teams edit themselves.
Frequently asked questions
Do clients depend on the platform?
The content is theirs and exports in open formats. The platform is an operations service, not a lock.
Who reviews the automated content?
A person, on the client’s side or mine depending on the agreement, before any publication. Nothing generated goes out without review.
Can a site be multilingual?
Yes, with content structured per language and hreflang tags. Several sites on the platform are bilingual or trilingual.
A comparable case on your side?
Tell me what costs you time; I get back to you within 24 business hours with a first read, no obligation.