--- title: Guest Mode description: We are replacing the traditional Thinking Cap website with Guest Mode inside the actual Thinking Cap administration console. created: 2026-09-14 updated: 2026-09-21 authors: ThinkingCap R&D topics: [Guest Mode] status: published canonical: https://console.thinkingcap.com/rd/Guest-Mode/Guest-Mode_-Building-the-Front-Door-for-the-Agentic-One date: 2026-09-14 --- # Guest Mode We are replacing the traditional Thinking Cap website with Guest Mode inside the actual Thinking Cap administration console. This is partly a website project. Mostly, it is an experiment in how two organizations might meet in an AI-mediated world. ## The agentic web may be a very short chapter Today's web assumes people visit websites. A software company publishes pages about features, security, pricing and integrations. A prospective customer reads some of them, fills out a form and eventually talks to sales. AI is already changing that. Increasingly, an AI will arrive with a set of requirements and questions on behalf of an organization. It doesn't particularly care about our navigation. It wants to know: - Can you do this? - Where is this data stored? - Do you support this standard? - How would you handle this use case? - What evidence do you have? - What are your limitations? We suspect the **agentic web**... agents navigating websites built for humans... is transitional. What comes next may be the **agentic one**. Organizations exposing enough knowledge and capability that their agents can deal directly with one another. Guest Mode is one of the places where we are experimenting with that idea. ## Start with the real product We don't think we need a separate glossy website sitting in front of Thinking Cap. Our customers already use an administration console. So that will increasingly become our front door. Arrive anonymously and you enter as a guest. Confirm your identity using a corporate email account and we know which organization we are talking to. As the relationship develops, the system can expose more. Eventually we can give you a sandbox and let you test what we have been discussing. The progression becomes: **Ask → Understand → Establish trust → Explore → Try** ## The relationship window This introduces a problem we find much more interesting than building another website. **How much should our system tell you right now?** We call that the **relationship window**. It isn't simply a login permission. It is an envelope around the current relationship between two organizations. An anonymous visitor gets one window. A verified corporate identity gets another. An organization that tells us what it is trying to accomplish may get another. An established customer gets a very different one. And we are working on making that envelope responsive to the conversation itself. ## Measuring the conversation turn by turn This connects Guest Mode to other R&D work underway inside Thinking Cap. When a message arrives, we don't want to treat it as simply a blob of text to hand to a language model. We are working on parsing incoming messages into a structured understanding of intent, context, requested actions and the information required to satisfy them. At each turn we can also evaluate the relationship envelope. Who is asking? What are they asking for? What have they told us? What do we know about their organization? What is the apparent use case? What information have we already disclosed? What additional information would be reasonable to disclose now? The envelope can therefore evolve with the conversation. That makes Guest Mode less like a collection of public and private pages and more like a negotiated information boundary. ## Trust should be reciprocal Transparency does not mean blindly answering every question. If you want to understand Thinking Cap, we don't necessarily need to know your budget, your buying process or whether somebody has labelled you a "qualified lead." We do want to understand **what you are trying to do**. If your AI arrives with twenty detailed technical questions, great. But when those answers depend on your use case, we may ask you to explain the use case. If everything about your organization, intentions and requirements must remain secret while you ask us to disclose increasingly detailed information about ours, the relationship window may stop expanding. That isn't a sales tactic. It is reciprocity. **You don't have to tell us everything. Neither do we.** Trust develops through useful exchanges between the two organizations. ## Markdown first The knowledge underneath this should be boring. That is intentional. Simple Markdown files. Clear headings. Minimal formatting. Plain language. Evidence and links where appropriate. Easy for our people to maintain. Easy for humans to read. Easy for machines to parse. Instead of designing hundreds of pages for every possible path through our company, we maintain knowledge and let the interface assemble the appropriate experience. ## Eventually, stop asking and try it At some point there is little value in continuing to describe software. So we intend to let the relationship progress into a sandbox. If you want to know whether Thinking Cap can support your use case, eventually the best answer is: **Try it.** The same relationship envelope can govern what the sandbox exposes and what the guest is permitted to do. The website, documentation, procurement conversation and product trial begin collapsing into the same environment. ## A dance between two organizations This is the larger experiment. Your organization has requirements, constraints, policies, systems and problems. Our organization has capabilities, constraints, evidence, systems and answers. Increasingly there will be AI on both sides. Our job isn't to make our AI sell something to your AI. It is to let the two sides discover whether there is a useful fit. That requires something more interesting than a chatbot. It requires identity, intent, evidence, permissions, tools and a relationship envelope that can change turn by turn. A dance between two organizations. And if at some point in that dance a human talking to another human becomes the best tool available, we'll introduce you. Until then, we aren't going to chase you around the Internet or fill your inbox because you asked us a question. Transparency is our brand. We think the machinery behind transparency is worth building.