Overview
Cintesa is a site visitors can talk to. They ask. The project answers from its own published content and instructions — generative UI, composing the interface as it goes, not a bolted-on chatbot. You can run it as the full customer-facing site or embed it on a brand you already host.
A conventional marketing site shows the same pages to everyone, then adds a chat widget and a CMS that do not share facts. Cintesa keeps content, campaigns, and how people (and AI tools) find the business in that same project. Your team can follow the public guide at docs.cintesa.run.
Why MethodGate built this
Agencies need several client projects that cannot share one global script — each client keeps their own site. Marketers need campaigns without a separate stack. Visitors should be able to ask and get an answer from that project’s own content. Those constraints are why MethodGate built Cintesa as a product you can run. We keep supporting and growing it.
Implementation is available when you want MethodGate to stand the product up. Partnership is available when the same software should roll out across clients. The default is the product itself at cintesa.run.
How it works together
Operators — your editors and marketers — manage copy, media, and structure in the CMS: the place they edit the site. Branding sets how it looks. Multilingual projects keep language on sections and campaigns instead of duplicating a whole second product. Humans work in those screens; other AI tools can use the same project through public files instead of scraping a mystery sitemap.
When a visitor talks, Cintesa uses generative UI: it composes real blocks, grounded in this project — not a generic chat skin. That is the agentic-web surface: the site can answer now, and it is ready for other agents to understand the same content.
Conversion sits on that same stack. Marketing funnels unfold topics in order. Traffic rules route campaigns and referrers. Scheduling, Gmail and Google Calendar sync, and external CRM sync keep the next step in the operator’s existing tools. Campaigns can leave through the customer’s own SMTP. Hosting, custom domains, embed, and the rest of delivery are how the project actually reaches people. Logging and monitoring show what happened after it did.
That is one product, not a feature aisle: content, conversation, campaigns, and how people find the business, sharing the same project. For a brochure landing that should stay a page, see CloudPack or CloudTemplates.
Who it is for
- Digital agencies running several client projects that must not share one global script.
- Owners who want a branded visitor journey instead of a fixed sitemap.
- In-house marketers who need campaigns without a separate stack.
Live product
Canonical site: cintesa.run. Sign in and project setup are on the Cintesa app. Cintesa is live. MethodGate keeps supporting and growing it. Product pricing stays on the product site.
Related writing: The static site problem, The fulfillment bottleneck.
