At 9.27 on a Monday morning in a Baner office in Pune, the conference-room laptop is already warm. It is a shared ThinkPad that belongs to nobody, runs PowerPoint and Chrome and very little else, and has a strip of masking tape on the lid that says MEETING ROOM 2 DO NOT TAKE. Priya (a composite), who runs operations at a 60-person B2B SaaS company, is standing over it with a pen drive, because the Monday review starts at 9.30 and her fifth slide, the one with the asks, is still a text box that says “asks”. The founders walk in at 9.29. Two people from the Hyderabad office are on the TV screen, muted, waiting.
The deck is five slides. It took her two hours on Sunday night.
Indian offices run on “put it in a PPT”. The phrase gets said at startups with 40 people and at IT services firms with 40,000, and what it usually means is the Monday review, the weekly client check-in, the sprint summary the CEO wants before Monday, the three-vendor comparison for the new payroll software, the leave policy HR has to explain before someone explains it wrongly on WhatsApp. Five slides. Most of them should take twenty minutes, and most of them take Sunday night, which is the gap these tools are useful for.
Five slides, twenty minutes
Priya’s two hours went where everybody’s go. Finding last week’s file (Monday_Review_v7_final2.pptx). Deleting last week’s numbers. Scrolling the #ops-weekly Slack channel for this week’s numbers, which three people had posted in three formats. Resizing a text box because the new number had one more digit. Hunting for a chart that looked like the one the founders liked in August. Rewriting a headline four times because “Collections improved” sounded wrong and “Collections up” sounded worse.
The version she runs now starts by copying the Slack thread. The whole thread, from Friday’s “numbers please” to the last reply, pasted into Quillbot’s ai presentation maker as source text, under a prompt she wrote once in September and has not changed since. Slide count set to five. Generate. The tool returns five slide titles with speaker-ready text under each, pulls the week-on-week comparison into a chart on the first slide because the prompt asked for one, and offers a few layouts and a theme she has stopped thinking about. She edits for about ten minutes: sharpens two titles, deletes a sentence that restated the chart, drags the risk slide above the asks slide because the founders will want to argue about the risk first. Then she shares the link.
It is labelled Beta on its page, it is free to use, and what it produces is a competent first draft of a document whose first draft was never the interesting part.
A standing prompt is the whole trick
The prompt is the part people skip, and it is the part that turns a twenty-minute job into a twenty-minute job that is also the same job every week. A fresh prompt every Monday produces a fresh-looking deck every Monday, and the founders then spend the first three minutes re-learning the layout instead of reading the numbers. A standing prompt, saved in a note and pasted in whole, means slide 3 is always the slipped items and slide 4 is always the risk.
Priya’s reads roughly like this:
Weekly ops review, exactly five slides, for the two founders and five functional heads of a 60-person B2B SaaS company. The audience knows the business, so no background and no definitions. Tone: plain, short sentences, no adjectives. Slide 1: the three numbers that moved this week versus last week (new MRR, collections, open support tickets), with one chart comparing this week against the previous four weeks. Slide 2: what shipped or closed, one line each. Slide 3: what slipped, with the owner named next to each item. Slide 4: the one risk that would hurt most next week and the decision we need from this room. Slide 5: asks, each with a name and a date. Use only the pasted thread below as source. Where the thread does not give a number, write TBC rather than guessing. Pasted thread follows.
Two details in that prompt do the work. “Where the thread does not give a number, write TBC rather than guessing” is there because a generator fed a thread with a gap will fill the gap with something plausible, and a plausible wrong number on a Monday morning costs more than a blank one. And “the decision we need from this room” is there because a review with no decision in it is an email.
What happens to a 600-word update email?
The engineering manager at the same company used to send the CEO a Friday email about the sprint. It ran to 600 words most weeks, nobody read past the second paragraph, and on Monday the CEO would ask questions the email had answered. In October the CEO asked for it as a PPT instead, five slides, for the same Monday review. The email survived as the source text. One of them, lightly disguised, opened like this:
Hi Arjun, quick update on Sprint 42 before Monday. Overall the sprint went reasonably well although we had a few blockers mid-week which I will explain below. The payments reconciliation feature is now in staging and QA has started, though we found two edge cases around partial refunds which the team is looking at. On the mobile side the login redesign is about 70 per cent done, the remaining work is mostly the OTP flow, which depends on the SMS vendor change we discussed. Hiring: four interviews, one offer out, two more from the Nashik college placement drive lined up for next week. Also, the AWS bill came in roughly ₹1.4 lakh over budget this month, mostly from a staging environment that was left running over the Diwali week…
It continues for another 470 words, including a paragraph about the office Wi-Fi. Pasted into the generator with the standing prompt and a slide count of five, the same material came back as:
- Sprint 42: reconciliation in staging, login redesign at 70%, one offer out
- Shipped: payments reconciliation to staging; two partial-refund edge cases found in QA, fix due Wednesday
- Slipped: OTP flow, blocked on the SMS vendor switch; owner: mobile lead; vendor decision needed by Tuesday
- Risk: ₹1.4 lakh AWS overspend from staging left running; auto-shutdown script this week, owner: DevOps
- Asks: approve SMS vendor; one backend hire; Sprint 43 scope review Thursday 4 p.m.
The engineering manager changed two things before the meeting. The slip on slide 3 had a different cause from the one the thread implied, a spec that changed twice, and he said so. And the Wi-Fi paragraph did not make it onto any slide, which was the correct editorial call and one the tool made on its own because the prompt had told it what the five slides were for.
The recurring meetings and what the tool drafts
| Recurring meeting | Slide count | What the AI drafts | What the owner adds |
|---|---|---|---|
| Monday ops review | 5 | Titles, week-on-week numbers from the pasted thread, one trend chart | The decision the room needs to make, and which number is a worry |
| Weekly client check-in (customer success) | 4 | Status summary from the email chain, open items as a list | The one thing the client asked for last week that is still pending, and what to say about it |
| Sprint summary for the CEO | 5 | Shipped and slipped structure from the stand-up notes | Why the slip happened and what it costs |
| Vendor comparison (three payroll quotes) | 6 | A criteria table from the three quotes pasted as text, a comparison chart | The recommendation, and the price the team will walk away at |
| HR policy change | 4 | Plain-language summary of the attached policy .docx, what changes and from when | Who to ask, the exceptions, and the tone that stops a WhatsApp rumour |
The company’s new hybrid policy, three days in office from January, was a four-page .docx written by a lawyer, and the HR manager attached it, asked for four slides for the all-hands, and got a draft that said what changed and when in language people would read. She rewrote the tone of slide 4 twice, mostly to take the lawyer out of it. Nobody rewrites the lawyer’s .docx twice.
Who owns the numbers
The shared link matters more than any layout option. In most offices the person making the deck does not own the numbers on it: the finance lead owns collections, the support lead owns ticket counts, and the deck-maker is a courier who gets blamed when the figure is wrong. Quillbot’s tool allows real-time collaboration by email invite or shared link, so Priya’s Friday-evening routine ends with the link going to those two people, and by Monday 9.00 the collections figure has been corrected by the person who knows it, in the draft, before the deck exists as a file anybody could forward.
Then it becomes a file, because the conference-room laptop runs PowerPoint and the TV in the room is driven by an HDMI cable older than the company. The same generator sits behind Quillbot’s ppt maker page, which is the door to use if what you need at the end is a PowerPoint file: that page lets you review and adjust the outline (topics, order, level of detail) before the slides are built, pick a theme, adjust layouts and typography, give it the company’s brand colours as a reference, and download the result as a PPTX. Priya exports the PPTX to the pen drive and a PDF to the Hyderabad team’s WhatsApp group, and that is Monday.
Where it falls short
No speaker notes, no animations and no slide transitions come out of the tool. If the founders want the risk to appear on click, that gets added in PowerPoint afterwards, and in a five-slide Monday deck it mostly should not be added at all.
It cannot know this week’s actual risk. If the risk that matters is that the largest client’s CFO has gone quiet since the renewal call, and nobody typed that into the thread, slide 4 will carry a tidy rephrasing of whatever worry did get typed, which is usually the smaller one. The tool reads text. It was not on the renewal call.
Confidential data is a policy question before it is a tooling question. A weekly client check-in deck is built from a client’s numbers, and many startups’ contracts with enterprise clients restrict where that data can be sent. Check the company’s policy, and the client agreement, before pasting a client’s thread into any external tool, this one included. Several teams I know keep client decks to a summarised version of the figures for this reason alone.
Google Slides export is listed as coming soon; the route today is export PPTX, upload to Slides. And the GIF export has exactly one use in that office, which is the all-hands joke slide.
Habits that undo the twenty minutes
Regenerating instead of editing. Hitting generate four times hoping for a better deck produces four decks of the same quality. Edit the second one.
Pasting the whole channel. Three thousand words of #ops-weekly, including the lunch poll and the birthday wishes. The slides will pick up the lunch poll. Paste the thread, not the channel.
Asking for ten slides for a five-minute slot. The PPT maker page mentions up to 10 slides at once, which is a ceiling rather than a target.
Changing the theme every week. Pick one in September and keep it until the founders complain. The Monday deck should look like last Monday’s.
Presenting a number its owner has not seen. The shared link exists so the finance lead can fix collections on Friday. Skipping that step and apologising on Monday is the old workflow with a new tool.
Sending PNGs to WhatsApp and nothing else. Someone will ask for the editable version by lunchtime. Export the PPTX too, every time.
Quick answers
Can it read our Slack or email directly? No. Paste the thread as text, or attach the source as a file: a .docx of notes, a PDF export of the email chain, last week’s .pptx, or a dashboard screenshot all go in through Attach Files.
Will it follow our brand template? The PPT maker page says it can take existing templates or brand colours as a reference. Check the fonts after export; the conference-room laptop may not have them.
How many slides can it make in one go? The PPT maker page talks about generating up to 10 slides at once. For the everyday deck, set it to five and resist.
Do we need PowerPoint at all? The shared link opens in a browser, and PDF export exists. For a room with a shared laptop and an HDMI cable, PPTX remains the safe format.
This Friday at 5.30
Write the standing prompt once, this week, while the shape of your Monday review is fresh. Save it in a note. On Friday at 5.30, paste it with the week’s thread, set the slide count to five, generate, and send the link to the two people whose numbers are on slide 1. Open it again at 9.00 on Monday. The deck will be wrong in two places, both of which you will already know about, and that is a Sunday night back.
