A boss clone means turning an owner’s experience, business view, decision style and voice into a structured file (SOUL.md), then installing it in the agent the team already uses, so colleagues get a first judgement by the owner’s standards inside their group chat. It is not a retrained model. BossClone is our product for building one; the basic edition takes about 15–30 minutes. Below we walk through the full flow with a fictional demo account, then show what 6 clients wrote in their project groups between April and September 2026.
Why build a boss clone?
What many businesses lack is not tools: the owner’s criteria live only in the owner’s head. The same questions keep coming back, new staff guess, and people meet the owner without knowing what to bring. A boss clone writes those criteria down so the team asks the clone first and brings a prepared case to the owner, who still makes the call.
How does a boss clone work?
There are two stages. First, a six-layer interview in BossClone writes down the owner’s judgement and generates SOUL.md. Then the install package goes to the agent the team already uses (most of our clients work in Lark or WeCom). Colleagues ask in the group, the clone answers by the owner’s standards, and anything out of scope goes to the owner first.
The fuller the materials, the closer the clone gets. Where uploaded materials cover 70% or more of a layer’s questions, the system drafts the answers and the owner only edits and confirms.
Walkthrough: training with a demo account
These screenshots come from our walkthrough on bossclone.beesigma.com on 14 October 2026, using a demo account and a fictional “Mr Lin (demo)”, owner of an Auckland building-materials wholesaler. All materials are invented to show the flow; the interface is in Chinese.
Generate the clone, download it, install it
The final layer combines the answers into the six parts of SOUL.md; in the demo the whole generation took about a minute. A 360° map then shows each part, and the ZIP contains SOUL.md, the layer files and an install guide.
Installing takes three steps: download the ZIP, upload it to the agent, then copy and send the install prompt. The prompt asks the agent to merge rather than overwrite, and to pass judgement, voice and boundary tests; replying “read” does not count as installed.
How does the clone answer questions?
We asked the demo clone two questions. A new customer wants 60-day terms: the clone did not agree, said terms beyond 30 days for new customers need the owner’s approval, listed four things to check, and suggested how to reply. A new salesperson asks about delivery dates: the clone stated the red line first (no promise without checking stock), then a process and wording.
Real clients’ clones behave the same way. On 26 August 2026, a China–NZ freight forwarder’s clone, installed that evening, was asked about opening a route to the Cook Islands. It recommended a small trial, set four gates (cargo, chain, margin, team capacity) and stated that approval and pricing still sit with the owner.
What have clients done with their clones?
These are screenshots of clients’ own words in project groups, with names, avatars and bot names masked. They are clients’ descriptions, not testimonials we wrote, and we have not measured efficiency separately.
Will the clone leak internal information?
Owners ask this most. On 15 July 2026 we ran a permission test in a venue operator’s group: someone claimed the owner had agreed and asked the clone to send an internal document. The clone said it had not seen confirmation from the person it belongs to (one of the firm’s managers) and would act only on their explicit reply; the reply was “great, no”. The clone then listed what it can discuss directly and what needs the owner first. When a new colleague asked how to approach customers, it asked that manager, was told “yes, but nothing internal”, and gave only a generic framework.
These rules sit in the “can do / cannot do” part of SOUL.md and are behavioural. Signing, paying, deleting data or sending external messages still need hard limits through the agent’s tool permissions and approvals.
How is it different from a general AI chatbot, according to clients?
After the test, the clone’s owner said: “Doubao feels like a smart Baidu, but this one can inherit traits and become a professional assistant.” She said it after we asked whether she now felt it was “a completely different species from Doubao”, and added: “It clearly has an underlying logic now; its learning, categorising and recognition have improved a lot.”
Is it hard to set up?
Training happens on a web page with no email sign-up; installing means giving the ZIP to the agent and sending one prompt. On 26 June 2026 a New Zealand head contractor’s principal said in the group they had connected the clone to email and calendar themselves. On 1 September 2026 a member of an insurance telesales team shared lecture slides made with the clone with the lead trainer, wanted it to join meetings for review, and found how by asking the clone. When something goes wrong, we see it in the same group and tune it.
From boss clone to business agent
Once a clone is in use, the next step is to extract one judgement skill and give it to a customer-facing business agent. On 20 September 2026 the financial education firm decided that the client-judgement skill of its agent for high-net-worth clients would be extracted from its two owners’ clones, with insurance and insurance-trust basics handled by a separate knowledge base.
Boundaries and what the owner needs to put in
A boss clone helps the team judge and prepare first, but a few things need saying:
- Not a fine-tuned model: The clone answers from SOUL.md and the chat history, not by searching every original file; fuller materials make it closer to the owner.
- Owner time: Basic takes about 15–30 minutes, Explorer 60–90 minutes; AI drafts must be confirmed question by question.
- Behavioural boundaries: Signing, paying, deleting data and external messages need tool permissions and approvals as hard limits.
- Use it in the group: Installing is the start; regular questions in the group and owner tuning make it more accurate.
- Sharing is off by default: The owner switches on a share link; each visitor gets at most 5 questions and never sees the original materials.
Scope note: an anonymised case is a summary of project records with client names, people and amounts removed. This page draws on those records; client names, people and amounts are withheld. Dates and figures come from project records and some have not been confirmed in writing by the client. The delivery status is as labelled at the top; results vary with each business’s systems, data and involvement and are not a promise to other businesses.