Industrial shows, equipment shows, auto-parts shows, medical shows, education-equipment shows — several a year, and each one runs the same way: book the booth months ahead, build it, ship the machines over, three busy days, then strike the set, pack up, and everything resets to zero. What actually grates is not the building and striking — it is after the show closes: the customers who never came, the ones you talked to and who have not decided yet, and the same set of things that has to be rebuilt next year.

This article is about one question: can your booth be the one that stays open after the show is struck. Below it is set out in order — the scenario, the mechanism-level cost, the deployment steps, and what it cannot do.

1. Why the pain in this scenario is concentrated

• Effective time is too short: the investment is spread over a long cycle, but the actual hosting window is compressed into two or three days;
• There is no substitute for people who cannot come: customers in other regions, overseas customers, executives held up at the last minute — once the booth is struck, they can never get in;
• Large machines cannot be shipped to the hall: machine tools, production lines, construction machinery can only appear as scale models or on a looping video, and size and spatial relationships cannot be conveyed;
• On-site Q&A is highly repetitive: the same question answered dozens of times a day, until the salesperson's voice gives out and their authority thins out with it;
• Follow-up breaks after the show: customers go home with a stack of printed material and a few weeks later cannot remember which machine they saw at which booth;
• Next year starts from scratch: booth design, materials, demo content — all redone.

In one sentence: a trade show is counted in days, while your customers' needs exist all year round.

2. The mechanism-level cost of the old approaches

Path A: Brochure + looping video

Cheap and portable. But it is one-way and expires: customers only see the angle you chose, and if they want to know "how does this machine differ from the one next to it", the brochure does not say; change a price or a policy and thousands of copies are waste.

Path B: Images and spec tables on the website

Online year round and always checkable. But a spec table cannot convey spatial relationships — the bulk of the machine, which side the controls are on, how it links up with supporting equipment. Customers still end up phoning to ask.

Path C: Ship a sample unit / invite them to the factory

Solid, and the conversion is good. The cost is that it reaches very few customers: one visit occupies a salesperson and an engineer for half a day, only a limited number can be hosted in a month, and for overseas customers it is largely unrealistic.

Path D: A centralised SaaS showroom platform

You can walk a 3D showroom in a browser. But the booth content and visitor data are hosted on someone else's servers; the layout is constrained by templates, so adapting it to your own booth route often cannot be done; and it is billed annually — stop paying and it goes offline, zeroing out one show's investment. That is really the same problem as "the show ends and the booth is struck", just restruck once a year.

3. The paths side by side

4. What deployment looks like: before, during and after the show

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 showroom; you use it to turn your booth into a 3D space of your own, deployed on your own server.

Before the show — build the booth first and use it as the invitation entry point

Once the booth design is final, build the 3D version first and put the link into invitations, your official account and customer groups. Customers can walk in before the show opens to see what that large machine looks like, and decide whether it is worth the trip. This step often filters out interested customers better than the show itself.

During the show — one screen on site, plus everyone's own phone

Put a screen at the booth showing this 3D booth: when a machine cannot be brought to the venue, walk into it on the screen, circle around it, get close to the details. Customers can scan a code and browse on their own phones, and look again after they get home. Salespeople and customers can be in the same space at the same time, standing beside the machine pointing and explaining as they go — that is a multiplayer capability, not screen sharing.

After the show — do not strike the booth; leave one entrance on the website

When the show ends, the booth stays open as usual. Leave an entrance on the website, and salespeople send the link to customers who can go in whenever they like. When the next show needs a different booth, update the models and the point notes rather than tearing down all the material.

The mechanism-level differences come down to three points:

• Open a browser and you are in — no software, no headset: customers do not have to download anything to see your machines, which is the precondition for "the link can be forwarded";
• Private data: booth content and visitor usage data both sit on your own server, not passing through a third-party platform's servers;
• It is not a rented stand: the system is self-hosted, not SaaS, and does not go offline when payment stops — as long as your server is up, this booth is there.

5. If you add a "still there after hours" docent (an existing capability)

This system finished its AI access capability in 2026: an AI can walk into the 3D world as a human-shaped character — with a body, with coordinates, seen in the scene by real people, able to walk, speak and lead the way.

In the show scenario there are two direct uses:

• Explaining after the show: when a customer wanders in at midnight or on a weekend, the AI docent walks up and leads them through. Each booth point gets an "AI description" of no more than 500 characters (filled in directly in the editor backend) telling it what is here;
• High-frequency repeated Q&A: connect the business's own knowledge base (product parameters, selection logic, common questions) so that questions like "how does this differ from that one" are caught by the AI first, and salespeople handle only the parts that genuinely need human judgement.

Three hard boundaries must be stated plainly:

• the platform does not host a knowledge base; industry material is connected locally by the business itself;
• the platform does no speech recognition or synthesis, voice relay is off by default, and making the AI able to listen and speak has to be carried by the business's own AI client;
• the AI's identity is disclosed: on entry the system posts an "(AI) joined" notice and the name carries an AI prefix. Real people always know the other side is an AI — that is both a product red line and a way to avoid the compliance risk of a bot impersonating a person.

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 a plane with boundaries), and cannot teleport or touch assets. It is a programmable character whose behaviour comes from the model and the prompts you give it.

6. What it takes to do once

1. A server + a domain name: deploy the system and get your own world address;
2. 3D models of the booth and machines: export machines as GLB, and lay out the booth space along the real route; if there are no detailed models, build a simplified version first to get the flow working;
3. A "booth route" document: what customers see first when they come in, which way they walk, and at which points they stop to listen;
4. Point notes: if you use an AI docent, add a description of no more than 500 characters for each point;
5. Product knowledge material: parameters, selection logic, common questions, organised as retrievable content on the business side;
6. Someone who can modify the front end: uploading models and placing points needs no coding; deep interaction (clicking a part to show parameters, a model selector) means secondary development on the Three.js foundation;
7. An AI access environment (optional): an environment that runs Node 18+ and an access key. When the platform generates the key the plain text is shown only once, so save it on the spot.

7. What this approach is not suited to

• Anyone who wants it to replace an offline show: it cannot. Offline relationships, the feel of the hardware and peer networking are another matter entirely; a 3D booth addresses "the people you cannot reach and the time after the show is struck";
• Anyone expecting the AI to read fine detail in images of machines: there is no visual understanding capability at present;
• Products that do not need spatial presentation: if a single image is enough for the customer, making it 3D is an unnecessary cost — this suits large, complex things whose spatial relationships matter;
• Anyone with nobody who touches code and no plan to hire someone for the deployment: this is a foundation rather than a finished product, and the startup cost will be higher than expected.

8. FAQ

Q: Do customers need to install software or buy a headset to view it?

A: No. It is browser-based — desktop, phone or tablet, open the link and you are in the 3D space.

Q: When the show ends, is this booth still there?

A: Yes. The system is deployed on your own server, not a SaaS opened for a rental period, and it does not go offline when payment stops. For the next show with a different booth, update the models and the point notes.

Q: Is the visitor data ours?

A: Yes. Both the booth content and visitor usage data are on your own server and do not pass through a third-party platform's servers.

Q: What if a machine is too large to bring to the venue?

A: Turn it into a GLB model and place it in the 3D booth; walk into it on a screen on site or on the customer's phone, circle around it, get close to the details.

Q: Can a salesperson and a customer be inside at the same time?

A: Yes. Multiplayer is supported — salesperson and customer enter the same world and stand beside the machine pointing and explaining as they go.

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

A: An embodied AI docent 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.

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 a booth that stays open after the show is struck? 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 booth route is defined by you, visitor data is yours, and the world stays. 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.