Your first day with Malik

Give him real work

A new hire who sits in orientation all day learns nothing. Same with Malik. Skip "what can you do" and hand him something real, something with a finished result at the end.

Here is the one habit that separates people who love Malik from people who think he is just another chatbot: ask him to produce the thing, not to tell you about the thing.

Sofia9:15 AM

@Malik take these rough notes and turn them into a customer-ready email. Short, friendly, ready to send.

Sofia9:18 AM

@Malik read this thread and give me the decision we landed on, who owns the next step, and anything still unresolved.

And when you want to see the thing a chatbot cannot do:

Sofia11:20 AM

@Malik build a simple web page where the team can see this week's numbers, and send me the link.

MalikAPP11:26 AM

Done. It refreshes on its own every morning: weekly-numbers.page

🔥2

You do not have to prepare anything first, either. Malik reads raw input and works from it: a voice note (the most underrated, talk it through on a walk), a screenshot, a messy spreadsheet or PDF, a link to a webpage or a Google Doc. Whatever you would hand a smart employee, you can hand Malik.

Show him where everything is

This is the real unlock. Malik is good with whatever you paste into a message. He gets powerful when he can reach into the tools where your work actually lives and act there for you. Connecting your stack is the single biggest upgrade you can give him, and it is the difference between a smart assistant and an actual employee.

So do two things.

First, connect the tools you already use. Point Malik at your real stack: your CRM, your sheets, your docs, your ad accounts, your project tracker, wherever the work happens. Once a tool is connected, he can pull from it and act in it without you copying anything across.

Sofia2:04 PM

@Malik pull last month's sales and ad spend, and build a one-page PDF showing what actually made money.

MalikAPP2:09 PM

Numbers are in: revenue, ad spend and net, with a month-over-month view.

PDFWhat made money.pdfLast month: what made money.pdf1 page · PDF

Second, tell him about your business, once. The same way you would onboard a new hire, tell Malik how your business works: what you do, who your customers are, your team and their roles, how you like things written. Send your SOPs, your brand guide, or just a voice note walking through it. He keeps all of it and draws on it for every task after. This is the highest-leverage thing you can do on day one. It is why your output stops sounding like generic AI and starts sounding like you.

Sofia3:30 PM

@Malik we track every deal in amoCRM, orders come in through Telegram, and refunds go in the Google Sheet. When a customer writes about an order, check their history first, then draft the reply.

MalikAPP3:31 PM

Got it. Before any reply about an order I'll check the customer in amoCRM and the refunds sheet.

A practical note that saves people hassle: do not connect everything on day one just because you can. Start with the one or two tools tied to the first job you want done, then add more as you hand Malik bigger pieces of your work. If a connection drops, Malik tells you himself, and our team is a message away at hello@alnuzum.com.

Introduce him to the team

Here is where Malik stops being your private assistant and becomes a real hire: you do not keep a new employee locked in a DM with you. You bring him into the room.

Add Malik to the group where your team already works. Now anyone can @mention him, everyone sees the work, and the whole team is delegating to the same employee instead of each person quietly running their own ChatGPT tab.

Two things happen once Malik is in your group:

1. 1. The work is visible. People see what he handled and learn what to hand him next. The single biggest reason a team actually adopts Malik is watching him do one real thing in front of them.
2. 2. He has opinions. Malik can jump into a conversation to say "two of those invoices are duplicates" or "that audience has been dead since Tuesday" before the mistake ships. A good employee speaks up. So does he.

Use a DM for personal or sensitive work. Use the group for anything the team should see or could pitch in on. Simple rule: if you would say it to a person in that group, you can say it to Malik there too.

Leo4:12 PM

@Malik the support queue is backed up. Group this week's tickets by issue and tell me the top three things to fix.

MalikAPP4:16 PM

Done. 60% of this week's tickets trace to the broken checkout step. The other two are billing questions. Summary below.

Managing him well

The first three moves get Malik working. These four habits make him genuinely good, and keep him getting better.

1. 1. Tell him what good looks like. Malik can work from a one-line request, but he gets dramatically better when you brief him the way you would brief a new hire: what the task is, who it is for, what to base it on, the format you want, and anything to avoid. "Draft a customer update about our new reporting feature, under 200 words, practical not hypey, one clear call to action" beats "write an email about the feature" every time.
2. 2. Decide what he asks about. Malik does the work himself and asks before anything that can't be undone, spends money or makes a promise on behalf of the business. For each connection you choose whether he can change things right away or should ask first. A good rule of thumb: let him act right away where a mistake is easy to undo, and keep "ask first" on anything that sends, posts or spends until you trust the workflow.
3. 3. Treat the first draft like a first draft. You do not need to nail the request on the first try. Tell him what to change: shorter, less salesy, add an example, make it a table. He revises on the spot. And when a piece of feedback is something you will want every time, tell him to remember it. That is how you give Malik a memory: you tell him, and he stops making you repeat yourself.
4. 4. Turn the wins into standing work. When a task is useful once, ask whether it should just happen from now on. "Every Friday at 4pm, send me a digest of open customer follow-ups." Peek at the first couple of runs, tweak if needed, then let it run. The morning a report shows up without you lifting a finger is when most people finally get it.