Manus is an autonomous general AI agent that runs in the cloud: you hand it a goal in plain language and it plans, works across many steps, and returns a finished deliverable — a research report, a spreadsheet, a slide deck, a working site, or a video. The prompts that get great results are not one-liners. They are delegation briefs: one clear goal, hard constraints, an exact deliverable format, and audit rules.
Every prompt below follows that shape. Each names a goal, pins down scope, timeframe, budget, and sources, specifies the exact deliverable (spreadsheet columns, slide count, report sections), and adds audit rules — cite every claim with a URL, leave fields blank rather than guess, tag uncertain claims High/Med/Low. Where it helps, they call real Manus features: Wide Research, Scheduled Tasks, the Browser Agent, Manus Slides, and 1.6 Max. Fill in the [bracketed placeholders] and paste.
Want to go deeper on a category? See the focused packs for Manus deep research and lead generation, or read how to prompt Manus for agentic tasks for the full brief-writing method.
Deep Research & Wide Research
Manus shines when a task means reading dozens of real sources and coming back with a sourced report. Give it a tight question, the exact sections you want, and audit rules — and reach for Wide Research the moment your task becomes a list of many items.
1. Competitive landscape scan
Research the competitive landscape for [product category] in [target market/geography]. Scope: only players active as of the last 12 months; ignore discontinued products. For each competitor identify positioning, target customer, pricing model, and 2-3 differentiators. Deliverable: a research report with these sections — Market Overview, Competitor Profiles (one per player), Positioning Map (described in text), Gaps & Opportunities, Sources Appendix. Rules: cite every claim with a source URL; if a data point is not public, write "not disclosed" rather than guess; tag any estimate with a confidence level (High/Med/Low). Use Manus 1.6 Max.Why it works: It fences the scope to the last 12 months and names the exact report sections, so the autonomous run doesn't wander — and the blank-not-guess rule keeps the output verifiable.
2. Wide Research on 100 companies
Use Wide Research to profile these [100] companies: [paste list or describe the set, e.g. "Series A-C fintech startups founded after 2021 in the EU"]. Run one sub-agent per company in parallel. Build a spreadsheet with columns: Company, Website, HQ Country, Founded Year, Employee Count, Funding Stage, Total Funding, Primary Product, Target Customer, Source URL. Rules: one row per company; leave a cell blank if the fact isn't found on an official or reputable source rather than guessing; put the citation URL in the Source URL column; stop when every company has a row.Best for: Any large, uniform list — Wide Research fans the job across parallel sub-agents so 100 profiles finish in the time one would take serially.
3. Academic literature review
Produce a literature review on [research topic/question]. Scope: peer-reviewed papers and reputable preprints from [2021]-present; prioritize highly cited and recent work. Deliverable: a report with sections — Question & Scope, Key Findings (grouped by theme), Points of Disagreement, Methodological Notes, Open Questions, and a References table (Title, Authors, Year, Venue, URL). Rules: cite every finding to a specific paper with a link; note sample size or study type where relevant; flag any claim you could only find in a single source as Low confidence.Why it works: Grouping by theme plus a structured references table turns a sprawling body of work into something you can actually cite and defend.
4. Deep dive on one company
Do a deep-dive research report on [company name] ([website]). Cover: business model and revenue lines, funding and investors, leadership team, product portfolio, recent news from the last 12 months, customer sentiment, and known risks. Deliverable: a one-document report with a one-paragraph executive summary up top, then a section per topic, then a Sources Appendix. Rules: cite every fact with a URL; separate confirmed facts from rumor/estimate and label estimates Med/Low; if financials aren't public, say so explicitly. Use Manus 1.6 Max for the reasoning.Best for: Sales prep, investment diligence, or a partnership check where you need one trustworthy, sourced dossier.
5. Regulatory and news monitor brief
Research recent regulatory and policy developments affecting [industry] in [region] over the last [6] months. Scope: official regulator pages, government sites, and major trade press only — no forums or social posts. Deliverable: a briefing with sections — What Changed, Effective Dates, Who It Affects, What To Do, and a dated Source List. Rules: every item must have a date and an official-source URL; if a rule is proposed but not yet in force, label it clearly; leave "Effective Date" blank rather than inventing one.Why it works: Restricting sources to official and trade press keeps a compliance-sensitive scan clean, and the "What To Do" section makes it actionable, not just informational.
6. Product comparison research
Compare these [5] tools for [job to be done]: [Tool A, Tool B, Tool C, Tool D, Tool E]. Weight the decision: capability 40%, price 30%, integrations 20%, support 10%. Deliverable: a comparison spreadsheet with columns — Tool, Starting Price, Key Features, Integrations, Free Tier (Y/N), Best For, Weighted Score, Source URL — plus a short verdict paragraph naming the winner for a [team size / use case]. Rules: pull pricing from each official pricing page and link it; leave a cell blank if not published; note the date you checked pricing.Best for: Buying decisions — the explicit decision weights force Manus to score consistently instead of writing vague pros and cons.
Lead Generation & Prospecting
Manus can build real prospect lists by browsing live sources with the Browser Agent and fanning big lists out with Wide Research. Give it a precise ICP, the columns you want, and a stop condition so it returns clean rows, not a wall of text.
7. ICP company list builder
Build a list of [50] companies that match this ICP: industry [X], headcount [50-500], region [region], and showing signals of [hiring for role / using tool / recent funding]. Deliverable: a spreadsheet with columns — Company, Website, Industry, Headcount, HQ Location, ICP Signal (which one and evidence URL), LinkedIn URL. Rules: only include companies you can verify against a real source; put the evidence link in the ICP Signal column; leave blanks rather than guess headcount; stop when you have 50 verified rows. Use Wide Research to run these in parallel.Why it works: Requiring an evidence URL for the ICP signal means every company earns its place on the list — no padding.
8. Decision-maker contact list
For each company in [paste list of companies / attach sheet], find the person most likely to own [buying decision, e.g. "marketing tooling"]. Deliverable: a spreadsheet with columns — Company, Contact Name, Job Title, LinkedIn URL, Public Email (if listed), Source URL, Confidence (High/Med/Low). Rules: use only publicly available business contact info; never fabricate an email — leave it blank if not published; set Confidence to Low if you inferred the role owner rather than confirmed it; cite where you found the person.Best for: Outbound prep — the confidence column tells your reps which rows to trust and which to double-check before sending.
9. Event attendee prospecting
Use the Browser Agent to pull the exhibitor/sponsor list from [event name and URL]. For each organization, capture what they do and whether they fit our ICP: [describe ICP]. Deliverable: a spreadsheet with columns — Organization, Website, Booth/Tier (if shown), What They Do, ICP Fit (Yes/No/Maybe), Reason, Source URL. Rules: only include organizations actually listed on the event site; cite the exact page; mark ICP Fit "Maybe" and explain when you're unsure rather than forcing a Yes/No.Why it works: Pointing the Browser Agent at the live event page means the list reflects who's actually there this year, not a stale cached roster.
10. Job-posting intent signals
Find companies in [industry / region] currently hiring for [role, e.g. "RevOps" or "Head of Data"], which signals they may need [our product]. Deliverable: a spreadsheet with columns — Company, Job Title, Posted Date, Job URL, Website, Headcount, Why This Is A Signal. Rules: only include live or recently posted roles (last [30] days); link the actual job posting; leave Posted Date blank if the listing doesn't show one; do not include reposts of the same role twice.Best for: Timing outbound to intent — a fresh job posting is a strong, dated buying signal, and the link lets reps reference it.
11. Enrich an existing lead list
Take my attached lead list [attach spreadsheet] and enrich each row. Add columns: Website, Industry, Headcount Range, HQ Country, Funding Stage, Recent News (one line + date), Source URL. Do not change my existing columns. Rules: only fill a new cell if you can verify it from a reputable source and cite it; leave blank rather than guess; flag any row where the company name was ambiguous or you found multiple matches, so I can resolve it. Use Wide Research to process rows in parallel.Why it works: The "do not change existing columns" and ambiguity-flag rules protect your source data while adding trustworthy enrichment on top.
Market & Competitive Analysis
Turn "understand this market" into a concrete deliverable: a teardown, a pricing table, a SWOT, or a sizing model. Naming the framework and the output columns is what keeps the autonomous run rigorous.
12. Competitor teardown report
Do a full teardown of [competitor name] ([website]) versus us, [your company]. Cover: product and feature set, pricing and packaging, positioning and messaging, target segments, go-to-market channels, strengths, and vulnerabilities we can attack. Deliverable: a report with a section per topic, a side-by-side feature table (Feature, Them, Us, Notes), and a "Where We Win / Where We Lose" summary. Rules: cite every claim about the competitor with a URL; label anything inferred from marketing copy as interpretation; leave pricing blank if not published. Use Manus 1.6 Max.Best for: Sales enablement and product strategy — the "Where We Win / Where We Lose" summary converts research into talking points.
13. Pricing comparison table
Build a pricing comparison across these [6] competitors: [list]. Deliverable: a spreadsheet with one row per plan and columns — Company, Plan Name, Monthly Price, Annual Price, Key Limits (seats/usage), Notable Features, Free Trial (Y/N), Pricing Page URL, Date Checked. Rules: read each official pricing page with the Browser Agent and link it; record prices in [currency]; if a plan is "contact sales," write that instead of a number; leave any unlisted field blank. Add a short paragraph noting where we sit in the price range.Why it works: Reading live pricing pages with the Browser Agent and stamping a "Date Checked" gives you a table you can trust and re-run later.
14. SWOT on a rival
Produce a SWOT analysis of [competitor] in the context of [market/segment]. Deliverable: four sections — Strengths, Weaknesses, Opportunities, Threats — each as bullet points, every bullet backed by evidence with a source URL, plus a closing paragraph on the two moves we should make in response. Rules: keep Strengths/Weaknesses to observable facts (product, funding, team, reviews) and Opportunities/Threats to market forces; tag speculative bullets as Low confidence; no bullet without a citation or a clearly labeled inference.Best for: Strategy offsites — a citation-per-bullet rule keeps a SWOT from becoming a list of opinions.
15. TAM/SAM/SOM market sizing
Estimate TAM, SAM, and SOM for [product] targeting [customer segment] in [geography]. Show your work: state each assumption, the number you used, and the source. Deliverable: a report with a Methodology section, a sizing table (Segment, Population/Count, Avg Spend, Total, Source), the three headline figures, and a Sensitivity note showing how the SOM changes if the key assumption moves +/-20%. Rules: cite every input; label modeled figures as estimates with Med/Low confidence; never present a derived number as a hard fact.Why it works: Forcing every assumption to be stated and sourced makes the model auditable — you can challenge one input without redoing the whole thing.
16. Feature and positioning gap map
Map the feature and positioning gaps between us, [your company], and these [4] competitors: [list], for the [use case] segment. Deliverable: a feature-coverage matrix (rows = features, columns = each vendor, cells = Yes/Partial/No with a note), plus a short list of "white space" opportunities where no vendor is strong. Rules: derive coverage from official docs, changelogs, and pricing pages and cite each cell's source; mark "Partial" with an explanation; leave a cell blank and flag it if you couldn't verify.Best for: Product roadmap prioritization — the white-space list points straight at underserved needs you could own.
Data Analysis & Spreadsheets
Attach a file and Manus will clean it, analyze it, and build a dashboard — writing and running real code to do it. Tell it the questions to answer, the metrics to compute, and the exact output so you get decisions, not just charts.
17. Analyze an uploaded CSV
Analyze the attached dataset [attach CSV/Excel]. First, summarize what's in it (columns, row count, date range, obvious data-quality issues). Then answer these questions: [Q1], [Q2], [Q3]. Deliverable: a report with a Data Summary, one section per question with the supporting chart and the number, a Data-Quality Notes section, and a short "So What" list of the top 3 takeaways. Rules: state any assumption you made (how you handled nulls, outliers, duplicates); don't drop rows silently — report what you removed and why; show the exact figures behind each chart.Why it works: Making Manus report its data-cleaning choices means you can trust the takeaways instead of wondering what it quietly threw away.
18. Build a KPI dashboard
From the attached data [attach file], build a KPI dashboard for [team/purpose]. Metrics to show: [metric 1], [metric 2], [metric 3], each with the current value, the trend over [time period], and a comparison to [target or prior period]. Deliverable: an interactive dashboard with a chart per metric and a one-line insight under each. Rules: define each metric's formula in a Definitions section; use only the attached data — do not invent numbers; flag any metric where the data is incomplete instead of extrapolating.Best for: Recurring reporting — a defined-formula dashboard is something you can hand off and trust across periods.
19. Clean and dedupe a spreadsheet
Clean the attached spreadsheet [attach file]. Tasks: standardize formats (dates, phone, country names, casing), split/merge columns as needed for [describe], remove exact and fuzzy duplicates, and flag rows with missing required fields [list required fields]. Deliverable: a cleaned spreadsheet, a separate "Changes Log" sheet listing every transformation and how many rows it touched, and a "Needs Review" sheet for ambiguous rows. Rules: never delete a row without logging it; when merging duplicates, keep the most complete record and note which fields were combined.Why it works: The Changes Log and Needs Review sheets give you full traceability, so a bulk clean-up never silently loses data.
20. Cohort and churn analysis
Run a cohort retention and churn analysis on the attached subscription data [attach file]. Group customers by signup month, compute monthly retention for each cohort, and identify where churn spikes. Deliverable: a retention cohort table (heatmap-style), a churn-rate-over-time chart, and a findings section naming the worst cohort, the likely drivers you can see in the data, and 3 hypotheses to test. Rules: state your definitions of "active" and "churned"; note the sample size per cohort; label small-cohort figures (under [30] customers) as Low confidence.Best for: SaaS retention reviews — pinning down "active" and "churned" up front prevents the classic definition-mismatch argument.
21. Survey open-text theming
Theme the open-text responses in the attached survey export [attach file], column [name]. Group responses into themes, count how many mention each, and pull 2-3 representative verbatim quotes per theme. Deliverable: a spreadsheet with columns — Theme, Mention Count, % of Respondents, Representative Quotes, Sentiment (Pos/Neg/Neutral) — sorted by count, plus a one-paragraph summary of the top 3 themes. Rules: quote verbatim, don't paraphrase; put responses that fit no theme in an "Other" bucket rather than forcing them; report the total response count analyzed.Why it works: Verbatim quotes plus counts give both the "how many" and the "in their words," which is what makes voice-of-customer land with stakeholders.
Slides, Decks & Documents
Manus builds finished slide decks with Manus Slides and writes structured documents end to end. Give it the audience, the narrative, and the exact slide or section count so the output is presentation-ready, not an outline.
22. Manus Slides pitch deck
Create a [12]-slide investor pitch deck for [company] using Manus Slides. Audience: [seed/Series A] investors. Narrative arc: Problem, Solution, Product, Market (with sizing), Business Model, Traction, Competition, Team, Ask. Deliverable: a 12-slide deck, each slide with a clear headline takeaway and minimal body text, and a speaker-notes line per slide. Rules: use only the facts and figures I provide here — [paste your key metrics] — and mark any slide where you need a number I didn't give with a [FILL] placeholder rather than inventing it.Best for: Fundraising — the [FILL] rule stops Manus from fabricating traction numbers, so the deck is safe to send.
23. One-page executive brief
Write a one-page executive brief on [decision/topic] for [audience, e.g. the leadership team]. Structure: a two-sentence recommendation up top, then Background, Options (with pros/cons each), Recommendation & Rationale, and Next Steps with owners and dates [I'll fill owners]. Deliverable: a single-page document, scannable, with bold key terms and no filler. Rules: lead with the recommendation; keep it to one page; if a fact is needed that I haven't provided, flag it as an open question rather than guessing.Why it works: Recommendation-first, one-page structure matches how executives actually read — and forces Manus to prioritize instead of dumping context.
24. Board-ready quarterly report
Draft a quarterly report for [company] covering [Q_ YYYY], using the attached metrics [attach file]. Sections: Executive Summary, KPIs vs Plan (table), Wins, Misses & Why, Product Update, Financial Summary, Risks, and Priorities for Next Quarter. Deliverable: a polished document plus a matching [8]-slide Manus Slides summary. Rules: pull all numbers from the attached file and cite the sheet/cell context; never soften a miss — state it plainly with the cause; mark any figure I haven't provided as [FILL].Best for: Board and investor updates — generating both a document and a slide summary from one brief saves the usual double-formatting.
25. Sales one-pager
Create a sales one-pager for [product] aimed at [buyer persona] in [industry]. Include: the core problem, our solution, top 3 differentiators, a proof point or two [I'll provide], typical results, and a clear call to action. Deliverable: a single-page document with a strong headline, short scannable sections, and a customer-facing tone. Rules: use only claims I can back up — mark any stat or logo I need to supply as [FILL]; avoid hype words; keep every section to two or three lines.Why it works: Marking unverified stats as [FILL] keeps a customer-facing asset honest and compliant while still giving you a finished layout.
26. Training deck from a document
Turn the attached document [attach file] into a [15]-slide training deck for [audience] using Manus Slides. Break the content into logical modules, one concept per slide, with a headline takeaway, 3-4 supporting bullets, and a "check your understanding" question every few slides. Deliverable: a 15-slide deck plus a one-paragraph facilitator note per module. Rules: stay faithful to the source document — don't add facts that aren't in it; if the source is thin on a topic, flag the gap rather than filling it with generic content.Best for: Onboarding and enablement — turning an existing doc into a structured deck is exactly the kind of mechanical work worth delegating.
Websites, Apps & Automation
Manus writes and runs code to ship working sites and prototypes, and its Browser Agent drives real websites — filling forms, clicking through flows, and scraping live data. Be specific about the pages, fields, and behavior you want.
27. Landing page build
Build a responsive one-page landing site for [product]. Sections: hero (headline + subhead + CTA button), 3-feature row, social proof strip, a short FAQ (5 questions), and a footer with a signup form. Style: [clean/modern, brand color #hex, sans-serif]. Copy: [paste or say "write it from this description"]. Deliverable: a working, mobile-responsive page I can preview and download. Rules: make the CTA button prominent above the fold; use placeholder [LOGO] and [FORM ENDPOINT] where I need to plug in my own; keep load-light — no heavy libraries.Why it works: Naming every section and the exact CTA behavior means you get a shippable page, not a vague mockup you have to re-brief.
28. Interactive prototype web app
Build a working prototype web app: [describe, e.g. "a ROI calculator where a user enters team size, hours saved, and hourly cost, and sees monthly and annual savings"]. Deliverable: a functioning app I can interact with in the browser, with clean inputs, live-updating results, and a mobile layout. Rules: validate inputs and handle empty/invalid entries gracefully; show the formula used somewhere on the page; keep all logic client-side; leave a clearly marked spot for me to add branding.Best for: Validating an idea fast — a real interactive prototype beats a spec doc for getting feedback.
29. Browser Agent form-filling
Use the Browser Agent to complete [task, e.g. "submit our product to these 10 startup directories"]. For each site in [paste list of URLs], fill the submission form with the details I've provided [paste company name, URL, description, category, contact email]. Deliverable: a tracking spreadsheet with columns — Site, URL, Status (Submitted/Blocked/Needs Login), Confirmation/Screenshot, Notes. Rules: never create accounts or agree to paid plans without asking me first; if a site requires login or payment, mark it "Needs Login" and skip; screenshot each confirmation page.Why it works: The "ask before paying or creating accounts" guardrail lets Manus automate tedious form-filling without taking risky actions on your behalf.
30. Browser Agent price scrape
Use the Browser Agent to collect current prices for these [20] products from [retailer site(s)]: [paste product list or URLs]. Deliverable: a spreadsheet with columns — Product, URL, Price, Currency, In Stock (Y/N), Date/Time Checked, Notes. Rules: read the live product page for each item and link it; record the price exactly as shown including any strike-through and sale price in separate columns; leave blank and note if a page is unreachable or the price is hidden behind login; do not guess prices from cache.Best for: Competitive price monitoring — pair this with a Scheduled Task (prompt 40) to track prices over time automatically.
31. Internal tool dashboard
Build a simple internal dashboard web app that reads the attached data [attach file] and lets me filter [dimension, e.g. by region and month] and see [key charts/tables]. Deliverable: a working app with filter controls, 3-4 visualizations that update on filter change, and a data table below. Rules: keep it read-only (no editing of source data); handle empty filter results gracefully with a friendly message; note anywhere the underlying data is incomplete; make it usable on a laptop and a tablet.Why it works: A filterable read-only dashboard is a common internal need that Manus can ship in one pass instead of a BI-tool project.
Content & Marketing
From SEO plans to full campaigns, Manus can research the landscape and produce the assets. Give it the audience, the goal, the channels, and the exact deliverable so you get a plan you can execute, not generic advice.
32. SEO content plan
Build a 3-month SEO content plan for [website] targeting [audience] in [niche]. Research the topics and keywords real buyers search, cluster them into pillar-and-supporting groups, and prioritize by intent and difficulty. Deliverable: a spreadsheet with columns — Cluster, Working Title, Target Keyword, Search Intent, Funnel Stage, Priority (1-3), Internal Links, Notes — plus a one-paragraph strategy summary. Rules: base topics on real search behavior and cite where you saw the demand signal; don't invent search volumes — if you can't verify a number, label the priority qualitatively instead.Best for: Content teams — a clustered, prioritized plan turns "we should blog more" into a concrete quarter of work.
33. Multi-channel campaign build
Build a launch campaign for [product/offer] targeting [audience]. Goal: [e.g. drive signups over 4 weeks]. Channels: email (3-email sequence), LinkedIn (5 posts), and a landing-page headline set (3 options). Deliverable: a document organized by channel with every asset written out, plus a simple 4-week calendar (Week, Channel, Asset, Status). Rules: keep one consistent core message across channels; match our tone [paste 2-3 lines of brand voice or point to Knowledge]; mark any claim needing a real stat as [FILL]; no hype words.Why it works: Asking for every asset written out plus a calendar means you can start executing immediately instead of briefing each piece separately.
34. Competitor content audit
Audit the content marketing of these [3] competitors: [list]. For each, review their blog, key landing pages, and any resources, and identify what topics they cover, their formats, their apparent keywords, and content gaps we could own. Deliverable: a report with a per-competitor summary, a combined "topics they cover vs we cover" table, and a ranked list of 10 content opportunities for us. Rules: cite the specific pages you reviewed; base "gaps" on what you actually observed, not assumptions; tag each opportunity with effort (Low/Med/High).Best for: Finding your content angle — the observed-not-assumed rule keeps the gap list grounded in real pages.
35. Newsletter and social pack
From the attached article/announcement [attach or paste], produce a repurposing pack. Deliverable: one newsletter issue (subject line + 200-word body + CTA), 3 LinkedIn posts (different angles), 5 short X/social posts, and 3 subject-line variants for A/B testing. Rules: keep the core message consistent; match our voice [paste or reference Knowledge]; don't add facts not in the source; keep each social post standalone and under [280] characters where the platform requires it; no emojis unless I ask.Why it works: One source in, a full multi-format pack out — the standalone-post rule means each asset actually works on its own channel.
36. Ad copy variant set
Write [10] ad copy variants for [product] on [platform, e.g. Google Search or Meta]. Angles to cover: [problem-led], [benefit-led], [social-proof], [urgency]. Deliverable: a spreadsheet with columns — Variant #, Angle, Headline, Primary Text, CTA, Character Count — respecting [platform]'s length limits. Rules: stay within the character limits and flag any that exceed; use only claims I can substantiate — mark unverifiable stats as [FILL]; keep at least one plain, no-hype control variant for benchmarking.Best for: Paid teams — organized-by-angle variants with character counts drop straight into an ad platform for testing.
Personal Productivity & Scheduled Tasks
Manus handles planning-heavy chores end to end, and Scheduled Tasks turn recurring work — briefs, monitors, digests — into automations that run daily, weekly, or monthly without you re-launching them.
37. End-to-end trip plan
Plan a [5]-day trip to [destination] for [number] people, [dates], budget [amount] total. Preferences: [pace, interests, dietary, mobility]. Deliverable: a day-by-day itinerary document with morning/afternoon/evening blocks, specific place names with why-recommended, rough costs, a booking checklist, and a map-link column. Rules: keep the total within budget and show a running cost estimate; cite hours/prices with links and note they can change; leave a booking blank rather than guessing availability; flag anything time-sensitive I should book now.Why it works: A running cost estimate and a booking checklist turn a wall of suggestions into a plan you can actually act on within budget.
38. Event and offsite plan
Plan a [team offsite] for [N] people in [city], [dates], budget [amount]. Cover: venue options (3, with pros/cons and cost), a sample agenda, catering options, one team activity, and a logistics checklist. Deliverable: a planning document with a comparison table for venues (Name, Capacity, Day Rate, Distance, Link, Notes) and a timeline of what to book when. Rules: cite venue prices and capacities with links; keep the plan within budget with a cost breakdown; mark availability as "to confirm" rather than assuming; note deposit deadlines.Best for: Ops and EA work — the venue comparison table and booking timeline compress hours of tab-juggling into one document.
39. Daily inbox and news brief
Set up a Scheduled Task to run every weekday at [8am my time]. Each run: check these sources [list newsletters/sites/feeds] for anything new in the last 24 hours relevant to [my role/topics], and produce a short brief. Deliverable each day: a one-page digest with sections — Top 3 Things To Know, Worth A Skim (with links), and Nothing-Burger (ignore). Rules: link every item to its source; deduplicate stories covered by multiple outlets; if nothing meaningful happened, say so in one line rather than padding.Why it works: Scheduled Tasks makes this run itself every morning; the "say so if nothing happened" rule stops it from manufacturing news on slow days.
40. Weekly competitor monitor
Set up a Scheduled Task to run every [Monday at 9am]. Each week, use the Browser Agent to check these competitors [list sites] for changes since last week: pricing, new features/pages, blog posts, and job postings. Deliverable each week: a spreadsheet appended with a dated section per competitor — What Changed, Evidence URL, Why It Matters — plus a 3-bullet "This Week's Signals" summary at top. Rules: only report actual changes vs the prior run; link every change; leave a competitor's row empty and say "no change detected" rather than inventing activity.Best for: Competitive intelligence on autopilot — a weekly Scheduled Task builds a change log over time so you spot rivals' moves without manual checking.
Frequently Asked Questions
What is Manus?
Manus is an autonomous general AI agent that runs in the cloud. You give it a goal in plain language and it plans the steps, does the work across many steps, and hands back a finished deliverable — a research report, a spreadsheet, a slide deck, a website, or a video. It is not a chatbot: you delegate a task and come back to a finished result, because it keeps working even after you close the tab.
Do Manus prompts differ from ChatGPT prompts?
Yes. A Manus prompt is a delegation brief, not a message. Because Manus works autonomously for many minutes, you write it like a task you hand to a contractor: one clear goal, hard constraints (scope, timeframe, budget, sources), the exact deliverable format (spreadsheet columns, slide count, report sections), and audit rules (cite every claim with a URL, leave fields blank rather than guess, tag uncertain claims with a confidence level). Ambiguity early compounds into wasted autonomous work, so you pin it down up front.
What is Wide Research?
Wide Research is Manus's feature for large lists. Instead of one agent working through items one at a time, it launches many sub-agents in parallel — asking it to research 100 companies runs as roughly 100 simultaneous jobs. Use it whenever your task is a list of dozens to hundreds of items: companies, products, papers, keywords, or prospects. Name the columns you want back and it fills the same schema for every item.
How long do Manus tasks take?
It depends on the task. A quick lookup in Chat Mode returns in seconds, but a real delegated task — deep research, a lead list, a data dashboard, a deck — runs asynchronously in the cloud for many minutes. Manus keeps working after you close the tab, so you start the task, walk away, and return to a finished deliverable. Bigger scope and 1.6 Max reasoning take longer than a Lite run.
Can I trust Manus output?
Trust it, but verify — and write your prompt so verification is easy. Always tell Manus to cite every claim with a source URL, leave a field blank rather than guess, tag uncertain claims with a High/Med/Low confidence level, and add a sources appendix. With those audit rules in the brief, you get output you can spot-check against real links instead of taking it at face value.
What is the difference between Manus 1.6 Lite and 1.6 Max?
Manus 1.6 comes in Lite, standard, and Max tiers. 1.6 Lite is fast and cheap — good for simple lookups, small lists, and drafts. 1.6 Max is the deepest-reasoning tier — use it for complex multi-step research, nuanced analysis, and high-stakes deliverables where accuracy matters more than speed. Standard 1.6 sits in between for everyday tasks.
How do Scheduled Tasks work?
Scheduled Tasks let you set a Manus task to run automatically on a daily, weekly, or monthly cadence. You write the brief once — for example, every weekday at 9am check five sources and append new leads to a sheet — and Manus runs it on that schedule and updates the same deliverable each time. It is built for monitoring, recurring lead gen, and competitive tracking without you re-launching the task.