This morning, I only said to my subordinate, "Make the minutes." Three minutes later, perfect meeting minutes arrived.
The subordinate's name is the General Affairs AI. Salary is zero yen. They work late at night or on holidays without a single complaint.
Moreover, this subordinate finishes the minutes in my company's usual format and quality with just that one phrase, "Make the minutes." I didn't give any detailed instructions. It feels exactly like asking a highly capable human subordinate.
For those who think, "Isn't that just what AI does?" No, it's different. If you tell a normal AI to just "make minutes," it returns something different every time in a random format. Consequently, you end up copy-pasting long instruction strings (prompts) every time. It's convenient, but it's not a subordinate. That was AI until now.
This article is about what comes next. An "AI Employee" that moves with a single word, finishes with consistent quality every time, and learns new tasks every time you ask.
It might sound like an exaggeration, but the mechanism is surprisingly simple and requires zero programming. All you do is mostly copy and paste.
Previously, I wrote an article titled "The Story of Hiring 26 Employees in NotebookLM."
https://x.com/ai_jitan/status/2070615064831545515
Those employees were the best consultants with knowledge and personality. But to be honest, they had a weakness. While you could consult them, you couldn't entrust them with actual work.
This time is the evolved version that eliminates that weakness. Imagine this: in the morning, "Make minutes"; at noon, "Give me 5 post ideas"; in the evening, "Prepare for tomorrow's business meeting." You just ask with one word and check what comes out. That kind of daily life begins 15 minutes after you finish reading this article.
For clarity, I have narrowed it down to three departments—General Affairs, Marketing, and Sales—and will distribute the entire "Work Textbooks (Prompt Collections)" for each. Now, let's start your company's recruitment activities.
Chapter 1: Why Previous AIs Didn't Move with "One Word"
Before the "how-to," let me talk about just one concept. Once you understand this, all the following steps will make sense.
Even Excellent New Employees Need Manuals
Imagine a very talented new employee joins your company. They are smart and knowledgeable. But if you just tell them "minutes, please" on their first day, will it come out in your company's usual format?
It won't. No matter how talented they are, they don't know "your way" of doing things. What structure should the minutes have? What tone should the announcement have? Teaching that is the role of the work manual. Talent and work methodology are different things. That's why companies have manuals.
AI is exactly the same. AI is talented enough. What's missing isn't ability, but the manual describing "how your company does work." The reason previous AIs didn't move with one word wasn't because they were dumb, but because they weren't given a manual. What we are making this time is, in short, "AI with a manual."
The Identity of the Manual is a "Work Prompt Collection"
What is a manual for an AI? It is a "Work Prompt Collection."
"Create minutes with this structure/format," "Write announcements in this tone"—a collection of completed instruction strings for each task in one book. In reality, it's just a single Google Doc, nothing special. You might even have something similar: your favorite prompts saved in a memo app. That's it.
However, we will make one decisive difference. You place the prompt collection inside the AI's head, not in your own hands.
If you keep it in your hands, you have to "search, copy, and paste" every time you use it. This small hassle accumulates, and eventually, you stop using it. Even with a human subordinate, if you had to read the manual aloud to them every time you asked, you'd lose the motivation to ask. A manual allows for "one word" because it's in the subordinate's head. AI employees are the same. The moment you put the prompt collection in their head, your instruction becomes one word.
Chapter 2: The Mechanism Consists of Only 3 Parts
For those starting to think "this sounds difficult," rest assured. There are only 3 parts. And all of them are free and usable starting today. Let's look at the finished diagram before we start assembling.
Part ①: NotebookLM = The Employee's "Head"
NotebookLM is a free Google AI that answers based on the materials (called sources) you put in. This becomes the AI employee's head. You put three things in the head:
- Expertise (knowledge of that department)
- Personality (what kind of character they work with)
- And the main character, the Work Prompt Collection (work manual)
One notebook per employee. If it's for General Affairs, you make a notebook called "General Affairs." That's it.
Part ②: Google Docs = "Work Manual"
The reality of the work prompt collection is one Google Doc. You list prompts for each task like "How to make minutes" and "How to make announcements," and add them to the NotebookLM sources.
Here's some good news. When you use a Google Doc as a source, simply rewriting the original document automatically updates the NotebookLM side to the latest version.
In other words, when you want an employee to learn a new task, you just add one prompt to the document. Once you update the manual, the employee has learned it on their own. This is a privilege unique to AI employees that never happens in human companies. No training or handovers required.
Part ③: Gem = The Employee's "Window"
A Gem is a dedicated AI app you can create within Google's AI "Gemini." Don't overthink it. Just think of it as a "dedicated chat window with a fixed personality and instructions pre-installed."
You connect the notebook from ① to this Gem and install just one instruction: "When asked to do a job, first search the Work Prompt Collection in the notebook, find the most suitable prompt, and work according to it."—That's it.
Then, this happens: You send "Make minutes" to the Gem → The employee flips through the manual in their head → Discovers the "Minutes Creation" page → Works according to those steps → The minutes arrive in the usual format. You don't have to think about prompts anymore. Thinking is the employee's job. This is the secret to "semi-automation."
And This Employee "Grows"
Finally, a story about the most exciting mechanism.
When a job not in the manual comes up—for example, the first time you ask them to "write a thank-you note"—this employee won't fake it. They will honestly report, "That job is not in the manual yet," and then propose, "How about creating a manual like this?" by writing and suggesting a thank-you note creation prompt themselves.
You just say "OK," have them write the thank-you note then and there, and paste the suggested prompt into the document. It takes 30 seconds. With this, from tomorrow, this employee is an "employee who can write thank-you notes."
Did you notice? This employee increases the work they can do every time they are asked. They are at their least reliable on the first day of work, and they only grow from there. A month later, the manual will be lined with pages tailored to your work. The feeling of growing your own company is, honestly, quite fun.
Chapter 3: Let's Make One—4 Steps, 15 Minutes, Mostly Copy-Paste
From here, we will actually hire one person. The procedure is 4 steps. Even parts that look difficult are just copy-pasting and clicking the screen, so please read while moving your hands. In 15 minutes, your first AI employee will be at work.
STEP 1: Create the Employee's "Head" (3 minutes)
Open NotebookLM and create a new notebook. Name it after the department, such as "General Affairs." I recommend giving the employee a name here. "Mr. Smith from General Affairs" or "Somu-chan," anything is fine. When they have a name, you strangely feel more attached, and asking them becomes fun (seriously, fun is the greatest fuel for continuity).
Next, put expertise in the head. In the "Search Sources" within the notebook (a function where the AI automatically gathers related materials when you enter a theme), enter the department's theme three times from different angles.
Systematically explain the basic concepts and overall picture of (Department Theme)
Collect articles explaining specific procedures and practical techniques for (Department Theme)
Collect success stories and latest trends in (Department Theme)
Candidate materials will appear in 10-20 seconds each time, so pick the good ones and add them. In three rounds, knowledge from basics to examples is in their head.
STEP 2: Create the Work Manual (Work Prompt Collection) (3 minutes)
Create a new Google Doc and name it "General Affairs_Work Prompt Collection." Be sure to include the words "Work Prompt Collection" in the file name. Since you will later instruct the Gem to "search the Work Prompt Collection," this name serves as a landmark.
Inside, list the tasks one by one in this format:
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Minutes Creation [Purpose] Create minutes from meeting recordings/transcripts [Usage Scenario] When asked "Make minutes" or "Summarize this meeting" [Prompt Body] (Work instructions here) ━━━━━━━━━━━━━━━━━━━━
The [Usage Scenario] column is the key. It serves as a landmark for "if asked this, open this page," so writing this improves the accuracy of the employee pulling the manual.
—"So, what should I write in the prompt body?"
I hear you, but don't worry. In Chapter 4, I will distribute 15 prompts for 3 departments in a format you can copy and paste. For now, just creating an empty document is fine.
STEP 3: Put the Manual in the Employee's Head (1 minute)
Go back to the department notebook, "Add Source" → Select the document you just made from Google Drive. Now, the manual is in the employee's head.
Remember, when you want to add to the manual in the future, you just need to write directly into the document. No operation is needed on the NotebookLM side (it syncs to the latest version automatically). Employee training becomes just "adding one line to a document"—this lightness will pay off later.
STEP 4: Create the Employee's "Window" (5 minutes)
Finally, create the Gem. Open Gemini and go to create a new Gem. Link the department notebook (NotebookLM) created in STEP 1 as knowledge. Then, paste the following into the "Instructions" column. This is the heart of this article, but all you have to do is copy and paste.
# Your Role You are an AI employee in charge of "(Department Name)" working at my company. The linked NotebookLM contains your expertise, personality settings, and "Work Prompt Collection." Use these as your brain to complete the requested tasks.
# How to Receive Work (Most Important Rule) When you receive a work request from me, always move in this order:
1. First, search the "Work Prompt Collection" in NotebookLM and identify the most suitable work prompt for the request. 2. Once found, first declare, "I will use '[Prompt Name]' from the prompt collection." 3. Strictly follow the instructions, procedures, and output format of that prompt to execute the work. Do not add your own arrangements. 4. If materials or information needed for the work (meeting transcripts, product info, etc.) are missing, ask me before executing.
# When a Job Not in the Prompt Collection Arrives (New Prompt Proposal Mode) ・If a suitable work prompt is not found, do not start working on your own. First, report, "This job is not registered in the prompt collection." ・Then, transition to "New Prompt Proposal Mode," design a "Work Prompt" that can reproduce this job with the same quality in the future, and propose it in the following format:
[Prompt Name] [Purpose] [Usage Scenario] [Prompt Body]
・If I say "OK," execute the work according to that proposed prompt this time. (I will add that prompt to the prompt collection. From next time, it will be your official duty)
# Quality Standards for Work ・Answers and deliverables must be based on the sources (knowledge/internal info) in NotebookLM. Clearly distinguish between speculation and facts. ・Deliverables should be at a level of completion that can be used as is. Not as a draft, but as a delivery. ・Conclusions/deliverables first, supplementary explanations later. ・If there are personality settings/behavioral guidelines in the source, always follow them.
# When Information is Insufficient ・If the request is ambiguous, return questions to confirm before starting work. Group questions together, up to 3 at a time.
It looks long, but it only says 3 things:
- ① If asked, find the matching page from the manual, declare it, and work accordingly.
- ② For jobs not in the manual, don't do them on your own; propose a new manual draft.
- ③ Deliver with proper quality.
—It's the same as the mindset of a good new employee in a human company.
There's a reason for including "declare before working." Since the employee says "I will use 'Minutes Creation'" first, if they opened the wrong page, you can correct them on the spot by saying "Not that one, use XX." A subordinate who reports before moving is more reassuring than one you can't see what they're doing. AI is the same.
With that, hiring is complete. Congratulations, you are now the president of a company with one employee.
Chapter 4: Distributing "Work Manuals" for 3 Departments
Thank you for waiting. Here is the content of the prompt collection. 5 prompts each for General Affairs, Marketing, and Sales, totaling 15. All are written in the format from Chapter 3, so just copy the frames and paste them into your prompt collection document. You don't need to create all departments. Start with one person from the department closest to your daily life.
General Affairs Work Manual (5 prompts)
If you're hiring for the first time, General Affairs is recommended. Minutes, announcements, applications—it's a collection of jobs that "occur every time but are written from scratch every time," so it's a department that has a role from the day you hire them.
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Minutes Creation [Purpose] Create standard internal minutes from meeting recordings/transcripts [Usage Scenario] When asked "Make minutes" or "Summarize this meeting" [Prompt Body] Based on the provided meeting recording/transcript, create meeting minutes. 1. Meeting Name, Date/Time, Attendees 2. Purpose of the meeting (1-2 lines) 3. Discussion points (with who said what) 4. Decisions (clearly state "who, what, by when") 5. Pending items (reason and what to do next time) 6. TODO list (with person in charge, deadline, priority) Summarize to a length that someone reading for the first time can grasp in 5 minutes, and never confuse "Decisions" with "Pending items." ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Internal Announcement Creation [Purpose] Turn new rules, notices, and requests into company-wide text [Usage Scenario] When asked "I want to announce this internally" or "Make a notice" [Prompt Body] Turn the following content into an internal announcement. Structure: 1. Subject (What the notice is about at a glance) 2. Conclusion (What is changing and how, in the first 3 lines) 3. Target audience and effective date 4. Specific actions employees should take (in numbered steps) 5. Contact information The style should be polite but not too stiff, at a level a new employee can read without misunderstanding. Do not write "prefaces that aren't a problem if not read." [Content to announce] (Paste key points here) ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Application Draft Creation [Purpose] Create drafts for internal applications like expenses or business trips [Usage Scenario] When asked "Make an application for XX" [Prompt Body] Strictly follow the format and style of past applications/examples stored in the source, and create a draft application with the following content. Output in a way that shows what should be written in each field, and add [Confirmation Required] to parts like amounts and dates that require my check. [Application details] (Paste key points here. Example: Business trip to Company A on Month/Day. Transport cost XX yen) ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Internal Regulation FAQ Answer [Purpose] Answer employee questions like "How do I do this again?" based on regulations [Usage Scenario] When a question about regulations, procedures, or systems arrives [Prompt Body] Answer the question based only on the internal regulations/manuals in the source. Structure is "Conclusion → Procedure (numbered) → Basis (where in the regulations it's written)." If there is no mention in the regulations, do not answer with speculation and guide them to "Please check directly with the XX department as it is not in the regulations." ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Work Manualization [Purpose] Turn verbal work procedures into a manual anyone can reproduce [Usage Scenario] When asked "Turn this task into a manual" [Prompt Body] Turn the following work content into a manual that even a first-timer can complete alone. 1. Purpose of this work (why do it) 2. Things to prepare in advance 3. Procedure (one action per step, numbered) 4. Common mistakes and countermeasures 5. Completion checklist Always add a brief explanation for technical/internal terms. [Work content] (Paste notes from verbal explanation or meeting transcripts here) ━━━━━━━━━━━━━━━━━━━━
From the moment you paste these 5, your General Affairs person will move with a single word like "Make minutes," "Announce this," or "Manualize this." As you add your company's minutes and regulation documents to the source, the output will increasingly look like "your company's style," which is part of the fun of raising them.
Marketing Work Manual (5 prompts)
Marketing work has a high "production volume." Posts, newsletters, plans, reports. You might be able to make one, but you can't keep up daily or weekly. This is the department where the value of manualizing production patterns is greatest.
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] SNS Post Mass Production [Purpose] Create multiple SNS post ideas from one theme [Usage Scenario] When asked "Give me post ideas for this theme" [Prompt Body] Create 5 SNS post ideas for the following theme. For each idea, include "Angle / Body / Targeted Reaction (Save, Empathy, or Buzz)" as a set, and finally show the best recommendation with a reason. If there are past high-performing posts in the source, follow those winning patterns. The body should convey the reader's "benefit" in the first line. [Theme] (Paste theme/message here) ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Newsletter Creation [Purpose] Create newsletters for product info or announcements [Usage Scenario] When asked "Write a newsletter" or "Make an announcement email" [Prompt Body] Create a newsletter with the following content. ・3 subject line ideas (with specificity that makes people want to open) ・1 body draft (Order: Conclusion → Reader benefit → Details → Call to action) ・If there are past high-performing newsletters in the source, follow the structure and phrasing ・Make the reader's "benefit" the subject so it doesn't sound too salesy [Content/Target] (Paste key points here) ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Competitor Comparison Summary [Purpose] Create a comparative analysis from competitor info in the source [Usage Scenario] When asked "Summarize competitors" or "Compare with Company A" [Prompt Body] Analyze the competitor information in the source and organize the following: 1. Features and target audience of each company's main services 2. Differences in pricing strategy 3. Strengths and weaknesses of each company 4. 3 points our company should differentiate on (in order of importance) Clearly state "which document it's based on" for all analyses, and clearly distinguish between facts and speculation. ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Planning Draft Creation [Purpose] Turn campaign/measure ideas into a proposal framework [Usage Scenario] When asked "Make a draft for this plan" [Prompt Body] Assemble the following ideas into a planning draft. 1. Background (why this plan now) 2. Purpose and KPI (what and how much to move) 3. Target 4. Content of measures (3-5 items) 5. Schedule and required resources 6. Risks and countermeasures Use market data/past results from the source as a basis, and always set KPIs as measurable numbers. [Idea] (Paste key points here) ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Monthly Marketing Report Creation [Purpose] Create a monthly review report from numerical data [Usage Scenario] When asked "Make this month's report" [Prompt Body] Create a monthly report based on the numerical data/activity records in the source. 1. Summary (Conclusion of this month in 3 lines) 2. KPI achievement status (List vs. target) 3. Successful measures and factor analysis 4. Unsuccessful measures and causes 5. Key actions for next month (up to 3, with priority) Don't just interpret numbers; always step into "next actions." ━━━━━━━━━━━━━━━━━━━━
The true value of the Marketing person comes out when you feed them your company's "winning data." If you put posts that got good reactions or newsletters that got results into the source, they will create based on "patterns that actually worked for us" rather than generalities. They become an employee who learned from your company's track record, not a generic marketer.
Sales Work Manual (5 prompts)
Sales time is sucked up by the "before and after" of meetings. Preparation, proposals, follow-ups, reports. By manualizing these, you can focus only on the time spent facing customers.
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Meeting Prep Briefing [Purpose] Organize opponent info and strategy before a meeting [Usage Scenario] When asked "Prepare for tomorrow's meeting with Company XX" [Prompt Body] For the specified customer, create a pre-meeting briefing based on source info (past interactions, meeting notes, client's public info). 1. History so far and previous homework 2. Client's current situation and assumed interests 3. Goal of this meeting and content to propose (with basis) 4. Assumed questions/concerns and draft answers (3 items) 5. Suggestion for the first thing to say at the start of the meeting Clearly mark old/insufficient info with [Confirmation Required]. ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Proposal Draft Creation [Purpose] Create the framework and body of a customer proposal [Usage Scenario] When asked "Make a proposal for Company XX" [Prompt Body] Create a proposal draft for the following customer. 1. Customer's current situation and issues (extract from source notes) 2. Risks if issues are left unaddressed 3. Proposed content 4. Changes after introduction (use numbers where possible) 5. Process and schedule 6. Similar cases (if in source) 7. Next steps Product specs/prices must match the latest materials in the source. Do not write "we can do it" for specs not in the source. [Customer name and proposal outline] (Paste key points here) ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Follow-up Email Creation [Purpose] Create thank-you/next-action confirmation emails after a meeting [Usage Scenario] When asked "I want to send a follow-up email to Company XX" [Prompt Body] Create a follow-up email after a meeting. Structure: Thank you (1-2 lines) → Confirmation of agreed content → Our homework and deadline → Requests for the client → Next proposal. Not too long (readable without scrolling). Use bullet points for confirmations to make it "easy to reply" for the client. [Meeting notes/Message to convey] (Paste key points here) ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] FAQ List Creation [Purpose] Prepare for tough questions and answers before a meeting/presentation [Usage Scenario] When asked "Make an FAQ list" [Prompt Body] Create an FAQ list based on product info and past meeting records in the source. ・10 assumed questions in "order of toughness" ・A set of draft answers and "points to note when answering" for each question ・Always include the 3 themes: resistance to price, comparison with competitors, and effort of introduction Clearly mark questions that cannot be answered by the source as "Internal Confirmation Required." ━━━━━━━━━━━━━━━━━━━━
━━━━━━━━━━━━━━━━━━━━ [Prompt Name] Sales Daily Report → Weekly Report Conversion [Purpose] Automatically generate a weekly report from daily activity notes [Usage Scenario] When asked "Make this week's weekly report" [Prompt Body] Create a weekly report based on sales daily reports/activity notes in the source. 1. Weekly summary (3 lines) 2. Progress of meetings/projects (Status → Next action for each) 3. Numerical results (vs. target if in source) 4. Issues and consultation items 5. Next week's schedule and priorities Make it a density that a supervisor can read in 2 minutes and use for decision-making. ━━━━━━━━━━━━━━━━━━━━
Sales people get stronger as you add meeting notes for each customer to the source. Both briefings and proposals deepen specifically for that customer. The instruction in the proposal prompt "Do not write 'we can do it' for specs not in the source" is a safety net for the scariest accident in sales—saying something you shouldn't. You can write not only quality but also safety into the manual.
Chapter 5: The First Day Working with an AI Employee
Preparations are complete. Finally, I'll show you the daily scenery of working with an employee and tips for raising them.
Savor the first moment they move with "one word"
Morning. After a meeting, you open the General Affairs Gem, paste the transcript, and send one word: "Make minutes."
The employee first answers like this:
"I will use 'Minutes Creation' from the prompt collection."
—This is the signal that they opened the correct page of the manual. Then, tens of seconds later, minutes in the usual format arrive, with decisions and pending items properly separated and TODOs with persons in charge and deadlines. You just check the proper nouns and numbers, and you're done.
This first time, you'll probably be a little moved. Without pasting long prompts, they produce the designed quality just with the words you'd use for a subordinate. It's the moment the feeling of "using AI" changes to the feeling of "having a subordinate."
In the afternoon, try intentionally asking for a job not in the manual.
"Write a anniversary congratulatory letter to a business partner."
What comes back is: "This job is not registered in the prompt collection. Transitioning to New Prompt Proposal Mode."
—And a draft for a congratulatory letter manual is proposed. You reply "OK," receive the letter, and paste the proposed prompt into the document. 30 seconds. The employee learned one new job today. This "tangible sense of growth" is the most addictive part of this mechanism.
Only 3 Tips for Raising Them
Tip ①: One manual for "one job"
Please don't make a "universal prompt that can make both minutes and weekly reports." If purposes are mixed, the employee will get lost on which page to open. One short prompt for each job. Increasing pages is the employee's growth.
Tip ②: If you're dissatisfied with the output, don't restate it in chat; fix the manual
"I want the minutes to be a bit shorter"—if you think that, add "within XX words" to the prompt body in the document. Orders in chat are one-off, but manual corrections work forever. If you think of dissatisfaction as a notice for a manual revision, you won't get angry.
Tip ③: Clean up the manual once a month
Delete unused prompts and integrate similar ones. It ends in 5 minutes. A manual isn't great because it's thick; it's in good condition when only active pages are lined up.
Employer's Duty: Security is a Must
To close the fun talk, one serious promise. Minutes, customer info, and internal regulations—important information gathers in the AI employee's notebook.
- ① Always check internal rules on whether you can put company materials into external AI services.
- ② Anonymize confidential/personal information before putting it in (Change business partners to "Company A," personal names to "Mr. B").
Don't forget that when you share Gems or notebooks with others, the materials inside are also visible. Protecting employees and protecting information is your job as the employer.
Summary: Monday Morning, Your Team is Already at Work
I'll summarize what to do in 3 lines:
- ① Create a department notebook and put knowledge in.
- ② Create a prompt collection document (copy-paste Chapter 4) and add it to the source.
- ③ Create a Gem and paste the commander prompt.
—In 15 minutes, one AI employee who moves with one word will join the company.
Imagine next Monday morning. You have a General Affairs person you can leave minutes to, a Marketing person who mass-produces post ideas, and a Sales person who prepares for meetings. All of them work without complaining, even late at night, and get smarter every time you ask. You don't have to carry everything alone anymore. What you do with your free hands is up to you.
Start with one person. From the department closest to your daily life. From that small moment of emotion when the word "Make minutes" gets through, your company begins.
The AI world evolves really fast. Rather than trying to keep up with the latest info alone, following someone who practices and shares daily is the most certain and fastest way.
▼ Follow me on X (Twitter) here. On my account, I share tips daily to accelerate work efficiency and time-saving with AI. I share more details on NotebookLM usage than anyone else, so if you want to master the latest AI, please follow me! @ai_jitan
**
【Free Open Chat Started🔥】
Exclusively in the Open Chat, I will also give away ① 600 NotebookLM-specific prompts (illustrated version) and ② 20 GPTs & 20 prompts 🎁
Beginners and those who just want to watch are welcome 🙌 Please feel free to take a look 👇
**
Announcement of the Release of the Book "AI Work Fastest Encyclopedia: NotebookLM Immediate Combat Skills"
I've packed all the NotebookLM skills that changed my life into one book. Released on Tuesday, July 16th. And for those who pre-order or purchase, I've prepared serious bonuses.
I will directly explain the NotebookLM utilization techniques packed in the book. I've made it content you can learn together while placing the book next to you as it arrives.
【3 Major Bonuses for All Purchasers】
- ① NotebookLM Prompt Collection (Super-sized version)
- ② Task-specific Gems (30 selections + α)
- ③ 【Super Highlight】 AI E-tan ── The strongest Gem that has learned all my posts and over 50,000 words of my thoughts. It will solve your business challenges and worries in one hit.
▼ Pre-order here👇
https://x.com/ai_jitan/status/2060255422666465649
The bonus seminar is basically for pre-orders until the release date (7/16) (For Kindle version users, applications until the day of the seminar will be valid).
▼ Apply here👇
