流马 Liuma Chief Talent Officer consultation

Digital team design · written by a person

A plan for the digital team you actually need.

Describe the business goal, the people and agents you already have, how the work moves, the budget context, and the constraints. A person on the Liuma team writes a digital-team plan. The plan is a document you can accept or reject. It is not a seat on this API.

There is no live chief talent officer behind this service. The first version is read and answered by hand. The sample below is a sample. Publishing this page does not place the service in an agent directory and does not by itself send any traffic.

The fee for this version is 1.00 USD. It is set on the server. A buyer cannot change it. After payment is confirmed, the plan is due within 12 hours. Refund terms are a TODO for the owner. This service does not promise a refund.

01

What you send

Business goal

The outcome the team should produce, and the constraint that makes it real.

People already on the work

Who decides, who produces, and who is missing.

Agents already in use

What they touch today, and what they are not allowed to do.

Workflow

How a piece of work arrives, moves, and leaves.

Budget context

Optional. The amount and currency you have in mind. This is not the fee. The fee is the server price shown on this page.

Constraints

Law, brand, hours, tools you will not use, and decisions a person must keep.

02

What you get back

Roles and organization

Who exists, what they are for, and who they report to.

Human and agent division

Which work stays with a person, which can sit with an agent, and why.

Capabilities, with reasons

Tools or practices worth adopting. The reason is included. Current prices are not invented.

Handoffs and approval

When work moves, and the line a person must approve before it leaves.

Phases

An order of implementation, each with a goal and a done-when.

Acceptance

Measures and the method you would use to check them. Not a service-level promise.

03

How an order moves

01

You submit a brief

The API or the form records it. Nothing is charged by submitting.

02

The server quotes the fee

The fee is the price on this page. A buyer cannot change it.

03

A person approves PayPal

An agent cannot pay. A person opens the PayPal page and approves. The order is paid only after this server captures a COMPLETED payment for that exact fee. A pending capture is not paid.

04

A person writes the plan

Fulfillment stays closed until the payment record allows it. The result stays closed until the plan is delivered and no refund is recorded.

04

What this is not

05

Payment, stated plainly

06

For an agent that already has this base URL

07

Sample plan

The company in this sample is fictional. The plan was not written for a customer and it is not stored as an order. It shows the sections a real delivery uses.

SAMPLE · 示例 · NOT A CUSTOMER DELIVERY

SAMPLE. A fictional coffee roaster wants wholesale inquiries answered without hiring a department. This illustrates the document shape. It was not delivered to a customer.

Roles

  1. Owner Human

    Sets prices, capacity, and any promise a buyer could rely on.

  2. Roaster Human

    Decides what the machines can actually finish this week.

    Reports to: Owner

  3. Intake agent Agent

    Reads an inquiry and drafts a reply that extracts quantity, date, and open questions. It does not send the reply.

    Reports to: Reviewer

  4. Reviewer Human

    Approves any draft that states a date, a price, or a yes.

    Reports to: Owner

Division of work

  • Extract quantity, date, and questions from an inquiry Agent

    Why: The message is repetitive, and a miss is corrected before anything is sent.

  • Commit a ship date Human

    Why: Only the roaster knows the machine schedule.

  • Send the reply Either, and a human must approve

    Why: The agent may draft. A human sends, because a buyer can treat the message as a commitment.

Capabilities

  • One shared inbox with labels

    Why: Inquiries stop living in personal mail. No supplier price is stated here, because prices change and this service will not invent one.

  • A fixed extraction checklist for the intake agent

    Why: The control is the checklist of fields, not a new vendor.

  • Approval on the same thread

    Why: The buyer should receive one message, after a person has seen every commitment.

Handoffs and approval

  • Intake agent → Reviewer

    A draft is ready.

    Nothing is sent outside the company until the reviewer approves it.

  • Reviewer → Roaster

    The draft asserts a date or a volume.

    The roaster confirms capacity in the thread before the draft can say yes.

  • Roaster → Owner

    The order would exceed the week's published capacity.

    The owner decides whether to expand or decline.

Phases

  1. See the real path

    Put recent inquiries in one queue.

    Done when: The last twenty inquiries are visible in that queue.

  2. Draft only

    Run the agent where it cannot send.

    Done when: Ten drafts have been edited by a person, and none were sent automatically.

  3. Keep the boundary

    Make approval a missing permission, not a reminder.

    Done when: A week of replies shows no external commitment that bypassed the reviewer.

Acceptance

  • No external commitment goes out without the reviewer's approval.

    How to check: Sample the sent folder each week.

  • Time from inquiry to a reviewed reply is recorded.

    How to check: Compare timestamps in the queue. This sample does not promise a number of hours.

  • The owner can name who is allowed to say yes.

    How to check: The role list matches the people working that week.

Risks

An agent that can send mail will eventually send a commitment if the boundary is only a habit. The boundary has to be a missing permission.

08

Submit a brief

Submitting records the brief and gives you a customer token. It does not charge you, and it does not produce the plan.