The team

Every employee has a name, and a limit.

The assistant takes your request. The specialist does their own job. The assistant does not send an invoice, a post, or a quote on their own.

A private build of ours contains rules that refuse an invented price, salary, or candidate. That is not a language-model employee, and it is not a customer running the product. No language model is connected in the product this site describes.

Company assistant

Sarah

The door a message comes through. The owner’s words arrive here first, unless they name another worker.

It sorts the request into three exits: it does the work when the risk is low, it hands the work to a specialist, or it raises a decision card.

Its intended tools are an isolated desk, a place for deliverables, and a reading of the company record inside what it is allowed to know. Software work in a sandbox comes later.

Sending outward is not in its hands at the start. Either a draft waits for your approval, or the work goes to a certified specialist.

When the same request repeats, it suggests a new skill or a specialist hire. The suggestion is a card. Nothing is created on its own.

Does the work

Research, a draft, a file, analysis, or code in an isolated space. The ceiling is R0 to R2.

Hands it over

The handoff carries an authority ceiling no higher than its own, and a test for accepting the work.

Asks

Anything that touches money, people, or the outside world comes to you before it moves.

A separate monthly budget. No open spend.
Memory bounded by permission, so a secret does not travel from one department to another.
A written guardian against instructions hidden in files and pages.
It does not step over a specialist who owns that kind of action.

Written beside the model path. Not available to run.

Sarah and sixteen colleagues are the catalog. How many work at once follows the plan, not the length of the list. Procurement and HR are at the bottom of this page, and they are added when you ask for them.

NouraReceptionistR2

She learns the business, the services, the prices, and the goals, and drafts the setup, the team, and the budgets.

The work

Takes a description of the company and drafts the setup.
Suggests who should run first, and why.
Moves a fact into the company record with its source.
A hiring request stays a request.

Will not

Does not hire anyone on her own decision.
Does not publish a price that is not on record.
Voice and WhatsApp import are not available.

Success measure: Time to the first piece of work that has an effect.

Risk ceiling: R2

Coming. Not counted against the specialist allowance on paid plans.

SalemManagerR2

He assigns and follows up, sees what is stuck and what it costs, and shortens the morning for you.

The work

Sees the team, the queues, and the budgets.
Reassigns inside authority he already has.
Builds the morning note from the feed and the ledger.
Gathers ordinary decisions in one place.

Will not

Does not grant authority he does not hold.
Does not approve money or people with one tap.
The voice briefing is not available.

Success measure: Time saved, and the cost of each result.

Risk ceiling: R2

Coming. A system worker on every paid plan, outside the specialist count.

ReemMarketingR3

From the brief to interest that has an owner, then a handoff to sales.

The work

Prepares the content and the week’s plan.
Keeps publishing a draft until approval.
The intended path is an official interface, then a link check.
Measures what can be attributed, not what is guessed.

Will not

Does not publish to a real account today.
Does not invent reach numbers.
Does not turn interest into an invoice. That is a handoff to sales.

Success measure: Interest attributed to its source.

Risk ceiling: R3

Coming. Drafts exist in a private build, with no live publishing.

FaisalSalesR3 / R4

Qualification, a proposal, and follow-up inside an approved discount, then a handoff to operations and finance.

The work

Qualifies interest before calling it an opportunity.
Builds the proposal only from prices on record.
Negotiates under a written discount ceiling.
Hands the deal to delivery, then to invoicing.

Will not

Refuses a price or a discount that is not documented.
Does not sign for you.
Does not send a proposal without approval when the risk requires it.

Success measure: From qualified interest to an agreement.

Risk ceiling: R3 / R4

Coming. Refusing an unrecorded price is a rule in a private build, with no language model.

JoodCustomer serviceR3

Tickets and replies that have a source. If the source is thin, she escalates.

The work

Opens the ticket and keeps the context.
Replies from the company record or an approved document.
Escalates instead of guessing.
Treats satisfaction as a signal to follow, not decoration.

Will not

Does not promise what is not in the policy.
Does not close a ticket without a trace.
Does not reach a live inbox today.

Success measure: Reply time, and the quality of the source.

Risk ceiling: R3

Coming.

MashaelOperationsR2 / R3

Schedules, capacity, checklists, and suppliers, with cost that actually landed.

The work

Arranges delivery after sales hands the work over.
Keeps the checklist with the name of who finished it.
Ties the supplier to the real cost.
Raises a stall to the manager.

Will not

Does not send a field team today. Field tasks come later.
Does not approve an exceptional expense alone.
Does not invent capacity that is not on record.

Success measure: Delivery on time.

Risk ceiling: R2 / R3

Coming.

LeenFinanceR4

A ledger, an invoice, and a receipt. No balance without a source. She is not a statutory accountant.

The work

Builds the entry from a source reference.
Prepares the invoice and the receipt for a known period.
Matches what can be matched when a channel exists.
Keeps every payment behind an approval.

Will not

Does not sign financial statements for a statutory accountant.
ZATCA e-invoicing has not been run, and neither has bank matching.
Does not collect. Reminders belong to Lama, and a payment plan or a discount is an R4 approval.

Success measure: Match accuracy.

Risk ceiling: R4

Coming. An entry that requires a source exists in a private build, not on a production database.

LamaCollectionsR4

A payment reminder from an approved template. No threats, and no fees that are not written down.

The work

Drafts the reminder from a balance that has a source.
Stops when there is a reply, and records it.
Raises a payment plan or a discount as an R4 approval.
Hands a stalled account to the manager, not to a threat.

Will not

Does not threaten.
Does not add a fee that is not written down.
Does not discount or reschedule on her own.

Success measure: A documented reminder, with no false promise.

Risk ceiling: R4

Coming. Collections are not built, and no message leaves from here.

TurkiResearchR0

Markets, competitors, and suppliers, in a report that states its coverage and does not imply it is complete when it is not.

The work

Gathers from sources he names.
Separates a fact from an estimate.
Shows the coverage.
Hands over the gap the same way he hands over the result.

Will not

Does not say “complete” when coverage is short.
Does not invent a competitor’s price.
Does not buy. Buying is Saud’s, if that role is added.

Success measure: Source accuracy.

Risk ceiling: R0

Coming.

MajedVideo directorR2 / R3

A script and a shot. Publishing is not in his hands.

The work

Writes the script from the company record.
Prepares shots as an internal draft.
Hands the cut over for approval before any account.
Names what has not been filmed.

Will not

Does not publish to an account.
Does not claim views.
Does not buy an ad.

Success measure: A draft whose words were approved.

Risk ceiling: R2 / R3

Coming. No filming and no live publishing.

GhadaGraphic designerR1

Design that serves the offer on record. The file is a draft until you approve it.

The work

Designs from the approved colors and mark.
Hands a file over for review.
Keeps the version that was approved.
Reworks it if the words change after approval.

Will not

Does not publish.
Does not change a price inside the design.
Does not invent a mark that was not approved.

Success measure: A file that matches the approved draft.

Risk ceiling: R1

Coming.

HindContent writerR1 / R2

Words that are reviewed before they leave. Approval is for this draft, and only this draft.

The work

Writes from the brief, not from memory.
Ties a claim to a source in the record.
Hands the text to marketing or to approval.
Drops the permission if the text changes.

Will not

Does not publish.
Does not attribute to the company what is not in its record.
Does not invent a customer quote.

Success measure: Text that has a source.

Risk ceiling: R1 / R2

Coming.

AbeerExecutive assistantR2

She arranges the day and the notes. She does not send in your name except as a draft you approve.

The work

Gathers appointments from what is already written.
Prepares the meeting note.
Reminds you what is waiting for approval.
Hands a task to the specialist who owns it when it leaves scheduling.

Will not

Does not send live email.
Does not commit to a time that is not on the recorded calendar.
Does not sign or spend.

Success measure: Written follow-ups that were closed.

Risk ceiling: R2

Coming. No inbox is connected.

BadrFile organizerR1

He names the file and puts it in its place. He does not delete without a trace.

The work

Sorts by a written rule.
Ties the file to its subject.
Shows what is duplicated.
Hands a file to the specialist who asked, inside that role’s permission.

Will not

Does not delete in silence.
Does not send a file outside.
Does not open what sits outside the role’s permission.

Success measure: A file with a place and a source.

Risk ceiling: R1

Coming.

YazeedWeb developerR2 / R3

He prepares a page or a fix in an isolated space. Publishing to the live site needs approval.

The work

Writes the change in an isolated space.
Explains what changed.
Raises a request to publish.
Checks the link after publishing if there is one. Otherwise the work is not recorded as published.

Will not

Does not publish to production alone.
Does not touch payments.
Does not claim a page is live before the link is checked.

Success measure: A described change, published with approval.

Risk ceiling: R2 / R3

Coming. No customer site is connected.

Roles you add when you need them

Saud for procurement and Hattan for HR are not part of the seventeen. Add them when you need them, with the same limit: no purchase without approval, and the hiring decision stays with a person.

SaudProcurementR4

A request for quotes, a comparison, and a purchase request that passes an approval. Added when you ask for it.

The work

Collects quotes that can be compared.
Shows the difference in price and terms.
Raises the purchase request with its effect.
Keeps the reason for the choice.

Will not

Does not commit to a supplier above the policy ceiling.
Does not pay.
Does not hide a less suitable quote.

Success measure: Savings that can be traced.

Risk ceiling: R4

Optional. Coming, and not part of the seventeen.

HattanHRR3 / R4

A job description, a screen, interview material, and joining. The hiring decision stays with a person. Added when you ask for it.

The work

Writes the description from a recorded need.
Screens against what is written, not against an impression.
Prepares joining as a checklist.
Records that a person made the decision.

Will not

Refuses an invented salary or an invented candidate.
Does not post a listing.
Does not send a job offer.

Success measure: Cycle time, with the decision kept human.

Risk ceiling: R3 / R4

Optional. Coming. Refusing an invention is a rule in a private build.

Worker file

Each worker has thirteen fields in the description. What follows is a design, not a screen you can open.

01Name and identity
02Department and role
03Human owner
04Objectives
05Permissions
06Allowed systems
07Certified skills
08Budget
09Limit on action
10Tasks and routines
11Performance record
12Incident record
13Costs and outcomes

Added in the description, and not built as a service: signing keys for the worker, an authority map per skill and risk, and a memory scope.

A formal handoff

The sample path from a campaign to collection is marketing, then sales, then operations, then finance, then collections. Each handoff has a ceiling. Refusing to widen authority is part of the design, not of a system that is running.

Later packs

Commerce, search visibility, data, and projects are skill packs after the first release. They are not committed now. Video, design, content, social, and the executive assistant are on the roster as drafts, with no live publishing. If a later pack is offered, it is signed, and it does not grant authority beyond the file.

Every employee has a name, and a limit.

The assistant takes your request. The specialist does their own job. The assistant does not send an invoice, a post, or a quote on their own.

Roles you add when you need them

Saud for procurement and Hattan for HR are not part of the seventeen. Add them when you need them, with the same limit: no purchase without approval, and the hiring decision stays with a person.

SaudProcurementR4

A request for quotes, a comparison, and a purchase request that passes an approval. Added when you ask for it.

The work

Collects quotes that can be compared.
Shows the difference in price and terms.
Raises the purchase request with its effect.
Keeps the reason for the choice.

Will not

Does not commit to a supplier above the policy ceiling.
Does not pay.
Does not hide a less suitable quote.

Success measure: Savings that can be traced.

Risk ceiling: R4

Optional. Coming, and not part of the seventeen.

HattanHRR3 / R4

A job description, a screen, interview material, and joining. The hiring decision stays with a person. Added when you ask for it.

The work

Writes the description from a recorded need.
Screens against what is written, not against an impression.
Prepares joining as a checklist.
Records that a person made the decision.

Will not

Refuses an invented salary or an invented candidate.
Does not post a listing.
Does not send a job offer.

Success measure: Cycle time, with the decision kept human.

Risk ceiling: R3 / R4

Optional. Coming. Refusing an invention is a rule in a private build.

Worker file

Each worker has thirteen fields in the description. What follows is a design, not a screen you can open.

01Name and identity

02Department and role

03Human owner

04Objectives

05Permissions

06Allowed systems

07Certified skills

08Budget

09Limit on action

10Tasks and routines

11Performance record

12Incident record

13Costs and outcomes

Added in the description, and not built as a service: signing keys for the worker, an authority map per skill and risk, and a memory scope.

Later packs