Manus is an autonomous agent that builds finished deliverables, not chat replies — so a good deck or website prompt is a delegation brief: a clear goal, hard constraints, the exact format you want back, and quality rules. Give it those four things and it plans the work, drafts the copy, designs the layout, and hands back a real deck, document, or deployable site.
Two tools do the heavy lifting here. Manus Slides generates full slide decks you can edit in the workspace or export to PDF and PowerPoint. And because Manus writes and runs code, it ships working websites and web apps — real HTML/CSS/JS with a live preview URL and the source files handed back to you, not a mockup.
Every prompt below pins down the audience, brand voice and colors, slide count or page sections, and length, then names the exact deliverable and the quality rules. Fill the [bracketed placeholders] and paste. New to Manus? Start with the best Manus prompts roundup, and for chart-heavy decks pair these with the data analysis prompts.
Slide Decks with Manus Slides
For every deck, state the exact slide count and a per-slide outline so Manus does not pad or drop sections. Give it your brand colors and voice, point it at your source material, and add an audit rule for any stat slides.
1. 12-slide startup pitch deck
Build a 12-slide investor pitch deck using Manus Slides for [company], a [one-line description] raising a [round, e.g. seed] round. Audience: early-stage VCs. Brand: colors [#hex, #hex], font [font], logo attached; voice = confident, concrete, no hype. Use this exact slide outline, one idea per slide: 1) title + tagline, 2) problem, 3) solution, 4) product/how it works, 5) market size, 6) business model, 7) traction with real metrics, 8) go-to-market, 9) competition matrix, 10) team, 11) financials/projections, 12) the ask + use of funds. Pull all facts from [attached data / this deck / these notes]. Deliverable: a finished 12-slide deck, editable in Manus Slides and exported to PDF and PPTX. Quality rules: cite the source of every stat on the slide or in a sources appendix, leave a number blank rather than guess, no placeholder or lorem text, consistent typography, and readable contrast on every slide.Why it works: The fixed 12-slide outline and per-slide topics give Manus a skeleton to fill, while the audit rule keeps the traction and market numbers honest and cited.
2. 10-slide sales deck
Create a 10-slide sales deck in Manus Slides to pitch [product] to [buyer persona, e.g. VP of Ops at mid-market logistics firms]. Brand colors [#hex, #hex], font [font], voice = clear and outcome-focused. Slide outline: 1) cover, 2) the buyer's problem in their words, 3) cost of doing nothing, 4) our solution, 5) how it works in 3 steps, 6) proof (2 customer results with numbers), 7) ROI/pricing, 8) integrations and security, 9) implementation timeline, 10) next steps + CTA. Base every claim on [attached case studies / product docs]. Deliverable: a polished 10-slide deck, exported to PDF and PPTX and editable in the workspace. Quality rules: cite the source of each customer result, no invented logos or quotes, placeholder-free copy, and a consistent visual system across all slides.Best for: Account execs who need an on-brand deck fast — the persona and step-by-step outline keep it tight and buyer-centric.
3. 8-slide quarterly business review
Build an 8-slide QBR deck in Manus Slides for [account/client] covering [Q_ 2026]. Audience: the client's executive sponsor. Brand: our colors [#hex, #hex] plus the client logo. Slide outline: 1) cover + period, 2) goals set last quarter, 3) results vs. those goals with a scorecard, 4) key wins, 5) issues and how they were resolved, 6) usage/adoption trends, 7) roadmap and plan for next quarter, 8) asks and success plan. Use the metrics in [attached spreadsheet / dashboard export]. Deliverable: an 8-slide deck exported to PDF and PPTX. Quality rules: every metric must trace to the source file, mark any estimate as an estimate, leave gaps blank rather than guess, and keep charts clean and labeled.Why it works: Goals-versus-results framing plus a source-traced scorecard makes the QBR credible and stops Manus from smoothing over misses.
4. 6-slide investor update
Create a 6-slide monthly investor update deck in Manus Slides for [company], [month 2026]. Audience: existing investors. Brand colors [#hex, #hex], voice = candid and metrics-first. Slide outline: 1) TL;DR + headline metrics (MRR, growth, runway), 2) KPIs vs. last month, 3) wins, 4) lowlights and risks, 5) asks (intros, hiring, advice), 6) what's next. Pull numbers from [attached metrics sheet]. Deliverable: a 6-slide deck exported to PDF. Quality rules: cite the source for each metric, be honest about lowlights, tag any projected figure as a projection, no placeholder text, and one clear takeaway per slide.Best for: Founders sending monthly updates — the short, candid format is what investors actually read, and Manus can run it as a Scheduled Task each month.
5. 10-slide training deck
Build a 10-slide training deck in Manus Slides to onboard new [role, e.g. support agents] on [topic/process]. Audience: new hires with no prior context. Brand colors [#hex, #hex], voice = plain and step-by-step. Slide outline: 1) title + what you'll learn, 2) why this matters, 3-7) the process broken into 5 clear steps with one example each, 8) common mistakes, 9) a short knowledge check with 3 questions, 10) where to get help + resources. Base it on [attached SOP / recorded process]. Deliverable: a 10-slide deck exported to PDF and PPTX and editable in Manus Slides. Quality rules: accurate to the source process, no invented steps, placeholder-free, plain language, and accessible contrast and font sizes.Why it works: Chunking the process into five named steps with examples turns a raw SOP into a teachable deck without Manus improvising the procedure.
6. 12-slide webinar deck
Create a 12-slide webinar presentation in Manus Slides on [topic] for [audience, e.g. marketing leaders]. Brand colors [#hex, #hex], font [font], voice = expert but approachable. Slide outline: 1) title + presenter, 2) agenda, 3) the problem/context, 4-9) six teaching sections, each one takeaway with a supporting stat or example, 10) case study, 11) recap of key points, 12) CTA + Q&A prompt. Source the content from [attached research / blog posts / notes]. Deliverable: a 12-slide deck exported to PDF and PPTX, plus a short speaker note under each slide. Quality rules: cite every stat with its source, no fabricated data, placeholder-free copy, and a consistent, uncluttered layout with big readable type for screen-share.Best for: Webinars and conference talks — the speaker-notes ask means you get a deck and a talk track in one run.
Documents & One-Pagers
Manus writes finished documents from your sources. Name the audience, the sections, and the length, then tell it to work only from the material you attach so nothing is invented.
7. One-page product one-pager
Write a one-page product one-pager for [product] aimed at [audience, e.g. procurement teams]. Brand voice = concise and benefit-led; colors [#hex, #hex] if formatting as a designed PDF. Sections, in order: headline + one-line value prop, the problem, what it does, 3 key benefits with a proof point each, how it fits existing tools, pricing tiers, and a clear CTA with contact details. Keep it to a single page, roughly 350-450 words. Base everything on [attached product docs / spec]. Deliverable: a formatted one-page document exported to PDF. Quality rules: every proof point cited or attributed, no placeholder text, no invented pricing, and scannable formatting with short bullets.Why it works: The one-page limit and fixed section list force Manus to prioritize, so you get a genuinely tight leave-behind rather than a wall of text.
8. Executive briefing document
Write a 2-page executive briefing on [topic/decision] for [audience, e.g. our leadership team]. Voice = neutral and decision-oriented. Sections: 1) bottom line up front (the recommendation in 2-3 sentences), 2) background and context, 3) the options with pros/cons, 4) key data and what it shows, 5) risks and mitigations, 6) recommended next steps with owners. Length: about 800-1000 words. Work only from [attached reports / data]. Deliverable: a 2-page briefing document exported to PDF. Quality rules: cite every claim with its source, leave a fact blank rather than guess, tag uncertain points with a confidence level, and lead with the recommendation.Best for: Decision memos — the BLUF-first structure and confidence tags give executives a document they can act on quickly.
9. Client proposal document
Draft a client proposal for [our company] to deliver [service/project] to [client]. Audience: the client's decision-maker. Brand colors [#hex, #hex], logo attached, voice = professional and reassuring. Sections: cover, executive summary, understanding of the client's needs, proposed approach/scope, deliverables and timeline, pricing/investment, team and credentials, terms, and next steps to sign. Length: 4-6 pages. Base scope and pricing on [attached brief / SOW notes]. Deliverable: a formatted proposal exported to PDF. Quality rules: no invented client facts, use only pricing I provide, placeholder-free copy, consistent branded formatting, and a clear signature/next-step section.Why it works: A full proposal skeleton plus a "use only pricing I provide" rule means Manus assembles a client-ready document without guessing numbers.
10. Standard operating procedure
Write a standard operating procedure (SOP) for [process, e.g. onboarding a new client]. Audience: the team member performing it. Voice = clear, imperative, step-by-step. Sections: purpose, scope, roles and responsibilities, prerequisites/tools, the numbered step-by-step procedure, a checklist version at the end, and escalation/edge cases. Base every step on [attached recording / rough notes / existing doc]. Deliverable: a formatted SOP document exported to PDF, with a copy-ready checklist. Quality rules: accurate to the source process, no invented steps, flag any gaps in the source as "TO CONFIRM" rather than guessing, and use numbered, testable steps.Best for: Documenting a repeatable process — the "TO CONFIRM" rule surfaces gaps instead of papering over them.
11. FAQ page from source docs
Build an FAQ page for [product/service] by extracting the most common questions from [attached support tickets / help docs / sales call notes]. Audience: prospects and new customers. Voice = friendly and direct. Produce 12-15 question-and-answer pairs grouped into logical sections (e.g. getting started, pricing, security, support). Each answer 2-4 sentences. Deliverable: both a formatted document AND a ready-to-publish HTML block with FAQPage schema markup, mobile-responsive and accessible. Quality rules: every answer grounded in the source material, no invented policies or prices, mark anything unclear as "needs review", and keep answers scannable.Why it works: Manus mines your real tickets for the actual questions and returns publish-ready HTML with schema — a document and a web asset in one go.
Websites & Landing Pages
Manus builds real, deployable sites — it writes the code, runs the build, and gives you a live preview URL plus the source files. Name the sections, the style, and ask it to deploy and hand back the source.
12. Product landing page
Build a responsive marketing landing page for [product], a [one-line description], targeting [audience]. Brand: colors [#hex, #hex], font [font], logo attached; style = clean and modern. Named sections, in order: sticky nav, hero with headline + subhead + primary CTA, social proof strip, 3-feature benefits grid, how-it-works in 3 steps, testimonials, pricing, FAQ, and a footer with links. Write real, benefit-led copy from [attached product notes] — no lorem ipsum. Deliverable: a working, deployable landing page (HTML/CSS/JS) — build it, give me a live preview URL, and return the source files. Quality rules: fully mobile-responsive, accessible (alt text, semantic headings, keyboard-navigable, good contrast), fast-loading, and every CTA wired to [link/#].Why it works: Naming the sections and demanding real copy plus a live URL and source files gets you a launch-ready page, not a wireframe.
13. Personal portfolio site
Build a responsive personal portfolio website for [name], a [role, e.g. product designer]. Style = minimal and elegant; colors [#hex, #hex], font [font]. Named sections: hero with name + tagline + photo, about, selected work (grid of [N] projects, each with image, title, role, and a short case-study link), skills, testimonials, and a contact section with a working form and social links. Use the details in [attached resume / project list]. Deliverable: a working, deployable multi-section site (HTML/CSS/JS) — build it, give me a live preview URL, and return the source files so I can host it. Quality rules: mobile-responsive, accessible, no placeholder images (use tasteful placeholders only where I haven't supplied assets and flag them), and clean semantic markup.Best for: Freelancers and job-seekers — Manus turns a resume into a live portfolio you can deploy the same afternoon.
14. Event microsite
Build a responsive one-page event microsite for [event name], on [date] at [location/online]. Brand colors [#hex, #hex], font [font], style = bold and energetic. Named sections: hero with event name, date, and a register CTA; about the event; agenda/schedule; speakers grid; venue/how-to-join; pricing/tickets; sponsors; and an FAQ. Populate from [attached event brief]. Deliverable: a working, deployable microsite (HTML/CSS/JS) with the register button wired to [registration link] — build it, give me a live preview URL, and return the source. Quality rules: mobile-responsive, accessible, real copy from the brief (no lorem ipsum), fast-loading, and a countdown or prominent date so the deadline is obvious.Why it works: A single-page section list plus a wired register CTA gives you a complete, conversion-ready event page in one build.
15. Product docs site
Build a responsive documentation site for [product] from [attached docs / README / help articles]. Style = clean and readable; brand colors [#hex, #hex]. Structure: a left-hand nav with sections (Getting Started, Guides, API Reference, FAQ, Changelog), a searchable content area, syntax-highlighted code blocks, and anchor links for every heading. Organize my source material into logical pages. Deliverable: a working, deployable docs site (HTML/CSS/JS) — build it, give me a live preview URL, and return the source files. Quality rules: mobile-responsive, accessible, working in-page search and nav, no invented API details (use only what's in my source), and a consistent, scannable layout.Best for: Teams shipping a product — Manus turns a messy pile of docs into a navigable, searchable site.
16. Waitlist launch page
Build a responsive waitlist / coming-soon page for [product], launching [timeframe]. Style = sleek and minimal; colors [#hex, #hex], font [font]. Named sections: hero with a compelling headline, a one-line value prop, an email capture form with a "Join the waitlist" button, 3 quick benefit bullets, a social-proof line ("[N] people already joined"), and a footer. Write persuasive real copy from [attached product notes]. Deliverable: a working, deployable page (HTML/CSS/JS) with the email form wired to [Mailchimp/form endpoint] and a thank-you state — build it, give me a live preview URL, and return the source. Quality rules: mobile-responsive, accessible, fast-loading, form validation on the email field, and no placeholder copy.Why it works: The wired email form plus thank-you state makes this a functioning capture page, not just a pretty splash screen.
17. Multi-page small-business site
Build a responsive multi-page website for [business], a [type, e.g. local bakery] in [location]. Brand colors [#hex, #hex], font [font], style = warm and inviting. Pages: Home (hero, services/menu highlights, CTA), About, Services/Menu, Gallery, Testimonials, and Contact with a working form, map embed, hours, and address. Use the details in [attached business info]. Deliverable: a working, deployable multi-page site (HTML/CSS/JS) with shared nav and footer — build it, give me a live preview URL, and return the source files so I can host it. Quality rules: mobile-responsive, accessible, real copy (no lorem ipsum), consistent branding across pages, and every link and the contact form functional.Best for: Small businesses that need a real site without a developer — Manus delivers a hostable multi-page build from a simple brief.
Prototypes & Web Apps
Because Manus writes and runs code, it ships working tools with real logic. Describe the inputs, the calculation or data, and the output, then ask for a deployable app with source files returned.
18. ROI calculator tool
Build a working ROI calculator web app for [product/service]. Inputs the user enters: [e.g. team size, hours spent per week on X, hourly cost, our monthly price]. Logic: compute time saved, cost saved, net ROI, and payback period using [describe the formula]. Output: show the results clearly with a summary line and a simple chart, and a "download/share results" option. Style: clean, brand colors [#hex, #hex]. Deliverable: a working, deployable single-page web app (HTML/CSS/JS) — build it, give me a live preview URL, and return the source. Quality rules: correct math (show your formula), input validation, mobile-responsive, accessible, and no placeholder logic — the calculator must actually compute.Why it works: Spelling out the inputs, formula, and outputs lets Manus build a calculator that genuinely computes and doubles as a lead magnet.
19. KPI dashboard app
Build a working KPI dashboard web app that visualizes the data in [attached CSV / spreadsheet]. Show these metrics: [list the KPIs, e.g. revenue, active users, churn, MRR growth]. Layout: a top row of summary cards with the current value and change vs. prior period, then charts (trend line, bar, and a breakdown) with a date-range filter. Style: clean and modern, colors [#hex, #hex]. Deliverable: a working, deployable dashboard (HTML/CSS/JS) that loads my data — build it, give me a live preview URL, and return the source files. Quality rules: numbers must match the source data exactly, label every axis and chart, mobile-responsive, accessible, and no fabricated data points.Best for: Turning a spreadsheet into a shareable dashboard — pair this with the data analysis prompts for deeper cuts of the same data.
20. Internal admin tool
Build a working internal tool for [team] to [task, e.g. track and update the status of incoming requests]. Features: a table view of records loaded from [attached CSV / sample data] with columns [list], the ability to add, edit, filter, and search records, status labels, and an export-to-CSV button. Style: functional and clean, brand colors [#hex, #hex]. Deliverable: a working, deployable web app (HTML/CSS/JS, with local storage or a simple data layer) — build it, give me a live preview URL, and return the source. Quality rules: all CRUD actions actually work, input validation, mobile-responsive, accessible, and clear empty/loading states — no placeholder buttons.Why it works: Listing the exact features and demanding working CRUD gives you a usable internal tool rather than a static table mock-up.
21. MVP prototype app
Build a clickable MVP prototype for [app idea] that [core value, e.g. helps users plan weekly meals]. Core flow to make functional: [describe the main user journey, e.g. pick preferences -> generate a plan -> save it]. Include the 3-4 key screens for that flow with working navigation and the core interaction actually functioning. Style: modern app UI, colors [#hex, #hex]. Deliverable: a working, deployable web app prototype (HTML/CSS/JS) — build it, give me a live preview URL, and return the source files so I can extend it. Quality rules: the primary flow must work end to end (not just static screens), mobile-responsive, accessible, and label any not-yet-built feature clearly rather than faking it.Best for: Founders validating an idea — a working primary flow is enough to test with users before writing a line of production code.
22. Quiz / lead-capture app
Build a working interactive quiz web app titled "[quiz name, e.g. Which plan is right for you?]" for [audience]. Flow: [N] multiple-choice questions, scored logic that maps answers to one of [list outcomes/recommendations], a results screen with a tailored recommendation and CTA, and an email capture before showing results. Questions and outcomes are in [attached notes]. Style: friendly and on-brand, colors [#hex, #hex]. Deliverable: a working, deployable single-page app (HTML/CSS/JS) with the email form wired to [endpoint] — build it, give me a live preview URL, and return the source. Quality rules: scoring logic works correctly, progress indicator, mobile-responsive, accessible, and no placeholder questions or dead buttons.Why it works: Real scoring logic plus email capture turns a simple quiz into a working lead-gen tool you can embed and deploy.
Frequently Asked Questions
Can Manus actually build and deploy a working website?
Yes. Manus writes the real HTML, CSS, and JavaScript, builds the site in its cloud environment, and gives you a live preview URL you can open and share. Ask it to deploy the site and hand back the live link plus the source files so you can host it yourself. Because it is an autonomous agent, it runs the build end to end and returns a working, mobile-responsive site rather than a mockup.
Can I edit the deck or site after Manus makes it?
Yes. For decks built with Manus Slides you can edit slides directly in the workspace or export to PDF and PowerPoint for further edits. For sites and apps, Manus returns the source files, so you can download the code, tweak it, or ask Manus to make specific changes in a follow-up message. Ask for exports and source in your prompt so everything is handed back editable.
How do I stop Manus from inventing statistics on data slides?
Give Manus the source material — your files, a link, or pasted data — and add an audit rule: cite every stat with its source on the slide or in a sources appendix, and leave a figure blank rather than guess. Tell it to tag any estimated number as an estimate. That keeps the deck verifiable and stops fabricated figures.
How many slides should I ask for?
State the exact slide count and a per-slide outline in the prompt. A pitch deck is usually 10 to 12 slides, a sales deck 8 to 12, a QBR 6 to 10, and an investor update 5 to 8. Naming the count and the section for each slide stops Manus from padding or dropping key points and keeps the deck tight.
Should I give Manus my brand colors and voice?
Yes, always. Put your brand colors as hex codes, your font, your logo, and a one-line voice description right in the prompt, or save them as Manus Knowledge so every future deck and site uses them automatically. Brand constraints up front save a full round of revisions and keep decks and sites on-brand.
Can Manus build a working web app, not just a static page?
Yes. Manus writes and runs code, so it can build interactive tools — calculators, dashboards, internal tools, and MVP prototypes with real logic and a usable interface. Describe the inputs, the calculation or data, and the output, and ask for a working, deployable app with the source files returned so you can host and extend it. For agentic, multi-step builds see how to prompt Manus for agentic tasks.