Back to the page
Back to the page

ITKAN Rabta · Plano, Texas
Sunday 20 September 2026

Virtual Employees

Automating the work nobody should be doing

Slides from the ITKAN Rabta session, 20 September 2026. Every person, business and number in these slides is made up.

Before anything else

  • Not a chatbot demo
  • Not "AI will take your job"
  • Not only for technical people

I am here about the work nobody should be doing.

By the time you leave

  • What to hand off
  • How far to let it go
  • How to stop it

9:04 PM · 2119 Silverleaf Ct #C

Text messages about a leak, Thursday night

She types what happened

A chat drafting a work request from her description

Again. And again.

The same background pasted into the chat again

She writes her rules once

A project with her rules written in one plain file

The wall

"If only it could see the maintenance queue."

The maintenance portal's list of open work orders

Now it can

The same work orders, with a new column reading each one against her rules

Friday. Already drafted, not sent.

A Friday owner update, drafted and not sent

The lines she drew

  • It never texts a tenant
  • It never approves over $200
  • It never tells an owner before she has read it

The bridge

Two things were moving.

Nobody told her they were separate.

How much of the job does it do?

01The text arrivesNotice it
02Unit, vendor, historyGather
03Under $200Decide
04Writes it. She sends it.Do it
05She still does thisTell people

Three and a half of five. She kept the rest on purpose.

How much does it do without asking you?

Show meWhat is in the queue right now
Draft itThe Friday owner updates, unsent
Ask meAnything over $200
Do itNothing leaves the folder on its own

Stopping is a decision. She made three.

They move independently

All of the job Does every step. Asks before each one. Slow, and completely safe. A good place to start.
One step Does one thing. Never asks. Narrow, and fully automatic. Also a good place to start.

Everything is on one page

itkan-rabta
.jazarilabs.ai

Open it now. You will need it after the break.

Malik Mansour · Thursday · one program manager

Six browser tabs and a tracker whose status column is spelled many different ways

Fifteen minutes of questions about his week

  • "I have been retyping the same document for eleven months."
  • "I owe four people a decision. Two of them for three weeks."
  • "Just the four things I have to decide, on a screen, in a font I can read across the table."
  • "Reading the tracker against the finance sheet. Nobody does it. We find out in October."

What came out of his week

  1. Rewrite the same Thursday roll-up from six tabs
  2. Check the ticket tracker against the finance sheet
  3. Scroll back through my mail to see who is waiting on me
  4. Meeting notes I never turn into actions
  5. Open the risk register, read ten stale entries, close it
  6. Approve a vendor invoice without checking what we agreed
  7. Rebuild the same four numbers for the steering deck
  8. Write the same orientation from memory, badly
  9. Two days finding a time five people can all make
  10. The four decisions I owe, on one screen

A tool, not an automation

A decision page: four cards in three columns

Two systems that never spoke

The ticket tracker checked against the finance sheet, row by row

Every Thursday, 7 AM, whether he asks or not

The Thursday roll-up, marked as a draft and not sent

How he stops it

  • Only one of the three runs by itself
  • Delete thursday.txt and it stops
  • He has done it twice on purpose

Check one

What breaks if it is wrong?

Rania

A tenant gets the wrong date and waits in for nobody.

Malik

A slide in a status deck is stale for a week.

Check two

Would you notice?

Rania

She reads every owner email before it goes. So yes.

Malik

He stopped reading the Thursday roll-up in week six.

Check three

Whose information is it?

Rania

Tenant phone numbers, and what they owe.

Malik

Salary bands. His employer has a policy about that.

Check four

Who else is counting on it?

Rania

Nobody. Three owners who do not know it exists.

Malik

Nobody, in week one. Six people, by week six.

How do you stop it?

  • You know it is running
  • You can find the switch without asking anyone
  • It stops in seconds, not days
  • Somebody is told it stopped

You can go as fast as you can genuinely stop.

What people actually hand off

Chasing people who went quiet

  • The second follow up nobody sends
  • An invoice that is thirty days late
  • RSVPs for the iftar
  • The contractor who stopped replying

Retyping the same thing

  • Portal to spreadsheet to email
  • The same form, again
  • Numbers trapped in a PDF
  • Two spreadsheets into one

The inbox you cannot keep up with

  • Five school apps, one child
  • A forty message thread
  • Catching up after a week off
  • What is actually urgent today

The report that comes every week

  • Friday status, from six places
  • The same four numbers, rebuilt
  • Timesheets and client summaries
  • Meeting notes that die as notes

Paperwork with a deadline

  • Prior auth, and chasing its status
  • Documents your CPA asks for
  • Claims and the statement that follows
  • Property tax protest season

Tools you do not have yet

  • A calculator for one job
  • A checklist that fills itself
  • One screen with today on it
  • A checker you paste into

Part two

How to start small, and how to know when to grow it.

Where we got to

  • How much of the job does it do
  • How much does it do without asking you
  • How do you stop it

The rest of today is: how fast should you move.

Crawl

By hand, with help. Build nothing.

  • You are still doing it
  • Nothing exists tomorrow morning
  • Most people should stay here for weeks

Walk

One sitting. One job. Done today.

  • Your rules, written down once
  • Or one small tool you open yourself
  • If it takes a weekend, it is too big

Run

It owns more, runs unattended, or someone depends on it.

Don't build a spaceship on your first go.

Graduate on conditions, not dates

  • I have done it the same way four times climb
  • I know exactly what wrong looks like climb
  • Somebody asked me for it twice climb
  • I stopped reading the output stop

The half nobody expects

Tools, not always automations

Not everything worth building has to run by itself.

Cheap, disposable, built for one problem

  • A page that answers one question
  • A form that does the math for you
  • A checker you paste things into

Built in an afternoon. Gone in a month. Fine.

You have been looking at one all morning

This.

  • Slides, a clock, and a list of what to cut
  • One file. No account, no internet
  • Built for today. It will never be used again

When your laptop is shut, it does not run

  • Starts on your machine, while you watch
  • Moves to a machine that stays on
  • Ends somewhere you do not own

This is the newest part. The page walks you through it.

Tonight

  • Open the page. Four steps, about five minutes
  • Answer its questions about your week
  • Take the smallest one. Do it by hand once

Questions

  • What should I hand off first?
  • How far should I let it go?
  • How would I stop it?