The same site for every person
Most marketing sites are a fixed tree. Home, product, pricing, about, contact. The order is the same for a returning operator, a first-time buyer, and someone who arrived from a footer badge. People scan menus, skip copy that is not for them, and guess which page applies.
Teams try to paper over that with a chatbot that does not know the CMS, a form that does not know the conversation, and landing variants that still cannot change emphasis in the moment. The visitor still does the routing work.
What we needed instead
MethodGate needed a product where this project owns persona, facts, and conversion path. Not a global script. Not a theme that pretends to be an agent. A site that can answer from published instructions and ingested content, compose generative UI in the moment, and offer a funnel when the visitor actually clicks into it.
That product is Cintesa: conversational generative UI with a CMS, campaigns, traffic rules, and agentic-web tools in one stack. The live platform is cintesa.run. How operators set it up is documented at docs.cintesa.run.
When a static site is still the right tool
A conversational platform is the wrong default for a brochure campaign that editors should ship from a visual CMS. For that we still build engines: CloudPack for full marketing sites, CloudTemplates for landing variants. Templates win on brochure velocity. Cintesa wins when the visitor should ask, and when operators need content, funnels, and AI-agent readiness on the same project.
What to do next
If you are evaluating Cintesa, start on the product site, then read the public guide. If fulfillment of unique sites is the pain, read the fulfillment bottleneck. If you are choosing an engine over a blank repo, read the velocity advantage.
