The Mind runs every customer-facing app
Most tools that build a website stop when the page exists. They hand a business a page and leave the posting, the sending and the keeping-it-current to a person. Giant Context runs those as well, from a decision layer called the Mind. It reads what a business is, works out what it should be saying, makes that content, and puts it where the customers are.
That is not one channel. The Mind runs every customer-facing surface the platform has, and each one is written and published without a person in the loop.
| Surface | What the Mind does | Status |
|---|---|---|
| Website | Proposes, drafts and publishes posts and pages | Running |
| Decides and sends one recipient at a time | Running | |
| Knowledge base | Writes articles and keeps them current as the source files change | Running |
| Developer docs | Writes the documentation from the SDK itself | Running |
| Social | Posts alongside a published page | Designed, not built |
The Mind and the switch
Every one of them works from the same things. The facts the Mind has pulled out of the business, the context of what the business does, the brand it has to sound like, and what the CRM holds about the person on the other end. Each stage is a decision made from what the Mind already knows.
Autonomy is a single setting that runs across the platform. With it on, the Mind takes a piece of content from the first idea to the published page with no one watching.
A business not ready to hand over all of it can require a person to approve at any of the four steps below. Told to wait at the draft, the Mind stops there until someone has read it. It is the same setting either way, and nothing is rebuilt to move between them.
In April I wrote that nothing would ship without the owner's yes, and at the time nothing did. Scale changed it. A business with ten thousand contacts cannot read ten thousand plans. So the sign-off became a setting the business places where it wants one, rather than a gate in front of everything.
The web
The website is the surface furthest along, because it is the one the Mind was built to run first. It proposes a post or a page, drafts it, and puts it live with no person in between. The moment the draft is done, the page is on the internet.
Email is the second surface that runs without a person. A page is made once and shown to everyone. An email is decided one recipient at a time.
The Mind holds every email a business might send, each marked in plain language with the moment it should go out, a description rather than a rule. Against that set it reads every contact one by one, the ones who came in through a form on the site and the ones who arrived through the platform's SDK, embedded in the business's own application. It weighs what the CRM holds on each person, what they have done, what they have already been sent and where they stand with the business, then works out which email, if any, is the right next one for them. That is a separate decision for every person rather than one campaign sent to a list.
Then it sends. Each message goes out at the moment the Mind chose for it, and never before it has checked the person still wants to hear from the business. Anyone who no longer does is held back.
The knowledge base and the docs
Two more surfaces run the same way. The knowledge base is written from the same files the pages come from and kept current as those files change, so an article that has gone stale gets a proposed rewrite instead of sitting wrong. The developer documentation is written from the SDK, so the docs move when the API moves rather than when someone remembers.
Both run the same four steps and the same autonomy setting, pointed at a different surface.
Social, not yet built
Social is not built. The design is that when the Mind publishes a page it also posts to the business's accounts and ties the post to the page, from the same grounding as everything above. The accounts a business would post under are already held. Nothing posts yet.
What the Mind is working from
Before the Mind writes a word it has read the business. Most of what it knows came from the files the business handed over, a document, a deck, a recorded call, an image. It pulls the words and the meaning out of each one and keeps them, so a fact stated once in a single file is a fact it can use in a page, an email or a future post without being told again.
Every page the Mind writes and every email it plans comes from those same things, so a page and an email and a help article read as one voice rather than three.
Any model can generate text. What is rare is a system that has read one business closely enough to act for it across every surface it has, making the content and sending it out with no one standing over it. That is what a business is buying.
The commercial case
Being seen means making the content, putting it where the customers are, and keeping it consistent as the business changes. That is more than most small businesses can staff. It is the work a marketing hire would do, and the Mind does it without the hire.
The larger market is the operator running many businesses at once. The platform is multitenant, so one company can stand up and run sites for hundreds of clients. When a client's marketing comes down to handing the Mind that client's documents and letting it run, an agency stops selling hours and starts running thousands of sites the way it would run one.
A website, an email tool, a help centre and a docs site, each run by a person, are four places for the truth to diverge and four chances for one of them to say something the others do not. One mind working from one understanding of the business cannot diverge from itself. A builder makes the page. This runs the marketing.
Building something like this
I'm Jesse. I build platforms end to end, and I'm open to work. If this is the kind of engineering you need, get in touch.