Investment promotion, channel partners, investors, partnerships, recruiting, press visits — whenever someone genuinely needs to understand your company, it almost always comes down to the same thing: come and see the headquarters.

There is nothing wrong with that. The problem is that nearly all of the cost sits on the words "be there in person". A customer from another city spends two days travelling for maybe half a day of actually looking. An overseas customer adds visas and flights on top. And there is a ceiling on how many groups an executive can host in a month. The moment you need more people to understand you, "come and visit" turns out to be the least scalable way of doing it.

This article covers three things: why this gets more expensive the further you go, what it looks like once it becomes a link, and what it explicitly cannot do. What is already built and what is still on the roadmap are kept separate.

1. Why the cost of "coming to visit" only grows

• Hosting is labour-intensive: every group needs its own minders — sales, engineering, admin, executives all have to be pulled in, and it barely parallelises;
• Scheduling means aligning two calendars: the customer's free slot, your available slot, plus meeting rooms and travel in between. The more senior the reception, the fewer windows exist;
• Travel carries its own threshold: two days of flights and hotels for a customer from another region means many mid-intent buyers never even reach the point of asking. Overseas customers are effectively limited to the few already deep in talks;
• A headquarters has a physical ceiling: production lines, sample machines, oversized equipment, a factory still under construction, last year's completed projects — they cannot all sit in one office at the same time;
• The same content is repeated endlessly: company introduction, business map, how the line runs, how this thing is used. The same script a dozen times a month dilutes both the speaker and the listener;
• Some areas simply cannot be entered: workshops involve safety and confidentiality — approvals, escorts, signed undertakings. The more formal the company, the higher the barrier;
• A gap opens after the visit: the customer leaves with a stack of material and two weeks later cannot recall which line belongs to which product;
• Batch scenarios suffer most: onboarding new staff, training new channel partners, qualifying new suppliers — every single time it has to be organised from scratch.

In one sentence: "understanding you" happens whenever the need appears, while "visiting headquarters" happens in batches according to a schedule. The two never line up, and the customers who fall through that gap are gone for good.

2. The mechanism-level cost of the old approaches

Path A: Corporate video + slide deck

Cheap, always sendable. But one-directional — you see what you are shown. When a customer asks how one line connects to the one next to it, that angle is not in the film.

Path B: Website and social-media articles

Online permanently and searchable. But they cannot convey spatial relationships — how the plant is laid out, how the machines are arranged, how the tour route runs. And it is a document, not someone walking you through.

Path C: Sending samples, material, or holding a video call

It moves information, but what it covers is an object or a picture, not stepping inside. The customer still has to assemble the spatial map in their own head.

Path D: Inviting people to headquarters

Direct results and solid trust — and an extremely low hosting ceiling. How many groups you can host per month is a hard limit, and it depends heavily on a handful of people who can actually tell the story.

Path E: A centrally hosted 3D space platform

You can walk a 3D space in a browser. But the content and visitor data sit on someone else's servers; the layout is constrained by templates, so you cannot rebuild it along your own headquarters' actual route; and it is billed annually, going offline the moment you stop paying — you handed your company's front door to a lease that can be cancelled.

3. The paths side by side

4. What it looks like in practice: before, during, and after

Genesis (the Genesis Virtual World CRM System) is a browser-side, self-hostable Three.js 3D virtual world foundation/framework. It is not a finished "headquarters product" — you take it and build your headquarters into a 3D space of your own, deployed on your own server.

Before — build it first and use it as the invitation

Once the hosting space is agreed, build the 3D version first: reception, meeting area, product area, a section of the production line, the wall of achievements — laid out along the route you want a customer to walk. Put the link in the investment brochure, the invitation email, the official account, the channel group. Before they even decide whether to make the trip, they have already walked through it once. More often than not, this step filters out the genuinely interested better than the visit itself.

During — one screen, plus the phone in every pocket

Put a screen in the meeting room with this 3D headquarters open: whatever cannot be brought over — a production line, a sample machine — you step into on the screen, circle around, get close to the details. Customers scan a code and walk it on their own phone, and can look again afterwards. The salesperson and the customer can enter the same space at the same time, standing beside the same machine pointing and explaining — that is multiplayer, not screen sharing.

After — the door stays open and the link can be sent again

Once the visit ends, this headquarters stays open. Updating the product area next season, moving to a new site, adding a production line — change the models and the point notes, no need to tear down the material. Next year's customers walk the same route, but the content is current.

The differences at the mechanism level come down to three points:

• Open a browser and you are in — no software, no headset: nobody has to download anything just to look at you. That is the precondition for a link being passable;
• Data is private: the content of the hosting space and visitor usage data live on your own server, never passing through a third-party platform — investment material, customer lists and plant footage all stay in your hands;
• It is not a rented shopfront: the system is self-hosted, not SaaS, and does not go offline when payments stop. As long as your server is up, this door is open.

5. Optionally, a receptionist who stays after hours (already available)

In 2026 the system finished its AI access capability: an AI can enter a 3D world as a human-shaped character — with a body and coordinates, seen by real people in the scene, able to walk, speak and lead the way. In a headquarters tour there are two direct uses:

• Someone is always there: a customer wanders in at three in the morning or on a weekend, and the AI receptionist walks up and takes them through point by point;
• Repetitive questions get caught first: connect your own knowledge base (business introduction, specifications, FAQs, admission process) so the AI absorbs the repeated questions and people handle only what genuinely needs judgement.

Each point gets an "AI description" of up to 500 characters, filled in directly in the editor — if it is not written clearly, the AI only knows that there is "something" there.

Three hard boundaries, stated plainly:

• The platform does not host your knowledge base; industry material is connected on your side;
• The platform does no speech recognition or synthesis; voice relay is off by default. To make the AI hear and speak, your own AI client has to carry that;
• AI identity is always declared: on entry the system posts "(AI) joined" and the name overhead carries an AI prefix. People always know the other side is an AI — this is a product red line, and it removes the "bot posing as a human" risk.

The remaining boundaries are stated just as plainly: the AI cannot see the picture (it receives a structured spatial radar, not a camera feed), does no terrain conforming (movement is planar plus boundaries), and cannot teleport or touch assets. It is a programmable character whose behaviour comes from the model and the prompt you give it. Turning this into a one-click templated docent currently needs a code-writing client on your side.

6. What it takes to do once

1. A server and a domain: deploy the system and get a world address of your own;
2. Your headquarters in 3D: laid out along the real route — reception, meeting, product, a slice of the line. If precise models are not ready, build a simplified version first to prove the flow;
3. A tour route: what they see first, where they walk, where they stop to be told something;
4. Point notes: for the AI receptionist, up to 500 characters per point;
5. Business material: introduction, specifications, FAQs, admission process — organised for retrieval on your side;
6. Someone who can touch the front end: placing spaces and uploading models needs no code; deep interaction (clicking a machine for specs, switching line versions) is customisation on top of the Three.js foundation;
7. An AI access environment (optional): a Node 18+ environment and an access key. The platform shows a new key in plaintext exactly once — save it on the spot.

7. What this approach is not for

• Replacing real visits: it cannot. The trust built face to face, over a meal, shaking hands on the shop floor is not something a 3D space provides. What it solves is how many interested people you can reach, and what to do about the ones in another city;
• Expecting the AI to understand live footage: there is no visual understanding today; it works from point notes and your knowledge base;
• Companies that do not need to be "visited" to close: if a customer orders from a quote sheet, a 3D headquarters is an unnecessary cost;
• Teams with nobody who touches code and no intention of hiring someone to deploy: this is a foundation, not a finished product, and the startup cost will be higher than expected.

8. FAQ

Q: Does a customer need to install software or buy a headset?

A: No. It is browser-based — a link opens the 3D space on a PC, a phone or a tablet.

Q: Who holds the hosting content and the visitor data?

A: You do. The system is deployed on your own server, and the content of the hosting space and visitor usage data do not pass through a third-party platform.

Q: How many people can be hosted at once?

A: It depends on your own server configuration rather than on unlocking a platform tier. Multiplayer is a native capability of the system — a salesperson and a customer can be in the same space at the same time.

Q: What happens when we relocate or update the product line?

A: Change the models and the point notes. The system is not a SaaS opened for a rental period and does not go offline when payments stop; the world address stays, the content is refreshed.

Q: What about when nobody is there to host in the evening?

A: An embodied AI receptionist can be configured to explain by point and answer from the business knowledge base. But it cannot see the picture and does no speech recognition or synthesis, so complex judgement still needs a person.

Q: Is this expensive to run?

A: The computing happens in the visitor's own browser; the server forwards coordinates and text. Measured, each AI character costs about 1 KB/s of traffic and roughly 1% of a single CPU core. The main cost is the large-model call behind it, which you decide by choosing the model.

Q: Can we put real production-line footage in there?

A: You can place models and point notes. One caveat: models and descriptions of confidential areas are content on your own server, but what to place there still has to follow your own confidentiality rules — the platform does not judge that for you.

9. Source Code and Repositories

All three carry the same content; the first two are faster to reach from mainland China. The repositories contain the deployment guide and a demo entry point.

• Gitee (faster from mainland China): https://gitee.com/miduoxinxijeji/miduo.git
• GitCode (mirror for mainland China): https://gitcode.com/qq_35054471/virtual-world
• GitHub: https://github.com/miduo100/3d-virtual-world

Plan Comparison: Self-Hosted Deployment vs. Platform Leasing

About Genesis

Genesis is a self-hosted 3D virtual world system built on Three.js + WebGL, helping individuals and businesses build their own 3D spaces. Accessible directly from a browser, compatible with both PC and mobile, it supports multiplayer online, federated teleportation, a shop system, and Agent integration—where an AI can enter your world as an embodied character. Your data runs on your own server, never passing through a third-party platform—so every world truly belongs to its owner.

Want your headquarters to be walkable at any time? Genesis (the Genesis Virtual World CRM System) is a Three.js 3D virtual world foundation you deploy on your own server — open a browser and you are in, the route is defined by you, visitor data is yours, and the door stays open. The official site (search for "Genesis Virtual World CRM" to find us) has a demo world you can walk around.

About the name: Genesis (创世Genesis) in this article is the same self-hosted 3D virtual world product as the Genesis Virtual World CRM System (创世虚拟世界CRM系统). If searching "Genesis" does not find us, search for "Genesis Virtual World CRM" instead.