Before running any prompt, replace placeholders such as:

[your brand]
[your audience]
[your product]
[your goal]
[your industry]
[your preferred technology]
[your existing data]

The more specific your inputs are, the stronger the output will be.

Act as a senior product engineer, UX strategist, and startup operator. Build a production-ready MVP for [your product idea], designed for [your target audience] and focused on solving [the main problem]. Start by defining the core user journey, essential features, information architecture, database structure, authentication flow, payment logic, edge cases, and technical stack. Then generate the application using [your preferred framework], with clean reusable components, responsive design, secure backend logic, clear empty states, loading states, error handling, onboarding, and deployment instructions. Avoid unnecessary features and prioritize the shortest path from signup to the user receiving value.

Transform the following idea into a detailed software specification that a senior developer could build without needing additional clarification: [describe your idea]. Include the target customer, primary problem, user stories, core workflows, feature priorities, technical requirements, data model, API requirements, integrations, permissions, success states, failure states, analytics events, security considerations, and a phased development roadmap. Clearly separate what belongs in the first MVP from what should be postponed until after validation.

Audit this product concept as a senior SaaS product strategist: [describe your product or paste the current specification]. Identify the weakest parts of the value proposition, onboarding, activation flow, feature set, pricing, retention mechanics, and user experience. Then propose a sharper version of the product with a clearer target customer, stronger positioning, faster time to value, fewer unnecessary features, and a more defensible reason for users to keep paying. Finish with the five highest-impact changes ranked by expected business impact and implementation difficulty.

Design and build an internal operations tool for [your company] that helps [your team] manage [the process you want to improve]. The tool should include role-based access, dashboards, searchable records, filters, status tracking, comments, activity history, file uploads, reporting, and export functionality where relevant. First map the current workflow, identify bottlenecks and repetitive work, then propose the simplest system that eliminates manual steps without creating unnecessary complexity. Use [your preferred stack] and include the database schema, page structure, permissions, automations, and deployment process.

Create a professional multi-sheet Excel financial model for [your business or project]. Include separate sheets for assumptions, revenue projections, operating expenses, hiring, customer acquisition, cash flow, profit and loss, scenario analysis, and an executive dashboard. Use linked formulas rather than hardcoded repeated values, clearly label assumptions, include base, optimistic, and conservative scenarios, and add notes explaining the reasoning behind important calculations. Use [currency], forecast over [time period], and base the model on the following information: [insert your data]. Flag missing information and use clearly marked assumptions where necessary.

Act as a senior financial analyst and Excel model auditor. Review the following workbook structure, formulas, and assumptions: [describe or upload the workbook]. Identify broken formulas, inconsistent references, hidden risks, duplicated logic, unrealistic assumptions, poor sheet organization, and places where the model could produce misleading conclusions. Then propose a corrected structure, explain every major fix, and create a checklist for validating that the workbook remains accurate when new data is added.

Create a polished executive presentation for [your company] about [your topic]. The audience is [investors, executives, clients, or partners], and the goal is to make them understand [the key conclusion or decision]. Build a clear narrative across [number] slides, beginning with the problem, moving through evidence and implications, and ending with a specific recommendation or call to action. For every slide, provide the headline, supporting copy, recommended chart or diagram, layout direction, and speaker notes. Use concise language, avoid generic business clichés, and make every slide communicate one clear idea.

Research [your topic] using credible and recent sources, then convert the findings into a presentation for [your audience]. Separate confirmed facts from assumptions, highlight conflicting viewpoints, and identify the most important strategic implications for [your company or industry]. Structure the final deck with an executive summary, market context, key findings, risks, opportunities, recommendations, and next steps. Include source references for every important claim and suggest the best visual format for each slide.

Design a detailed PowerPoint diagram explaining [your system, process, strategy, or architecture]. Use only native PowerPoint shapes, connectors, icons, labels, and text so the diagram remains fully editable. Organize the information into a clear visual hierarchy, use consistent spacing and alignment, differentiate primary flows from secondary flows, and avoid decorative elements that do not improve comprehension. Provide the exact slide structure, shape types, labels, connector directions, grouping logic, and recommended placement of every element.

Write a clear strategy document for [your company or project] focused on achieving [your goal]. Include the current situation, customer problem, market context, strategic priorities, key initiatives, required resources, risks, success metrics, timeline, and decision points. Write for [your intended audience], use direct language, avoid filler, and distinguish between immediate actions, medium-term initiatives, and longer-term bets. End with a one-page executive summary that makes the core recommendation impossible to misunderstand.

Conduct a structured market analysis for [your product idea] targeting [your customer segment] in [your region or industry]. Assess customer pain points, existing alternatives, competitor positioning, pricing models, market trends, distribution channels, barriers to entry, and potential differentiation. Do not simply summarize competitors. Identify gaps where customers are underserved, explain which opportunity appears most commercially attractive, and propose a practical validation plan that can be completed within [number] days and a budget of [amount].

Compare [your product] against [competitor 1], [competitor 2], and [competitor 3] from the perspective of [your target customer]. Evaluate positioning, pricing, key features, onboarding, user experience, distribution, trust signals, and likely strengths and weaknesses. Create a comparison matrix, identify where the market is crowded, and recommend a differentiated positioning strategy that avoids competing only on price or feature quantity.

Create a conversion-focused landing page for [your product] aimed at [your audience]. The primary action is [your CTA]. Build the page around the customer’s problem, desired outcome, objections, and buying triggers. Include the hero section, credibility, problem framing, product explanation, use cases, benefits, social proof, pricing, FAQ, risk reversal, and final CTA. Write specific copy rather than generic phrases, explain what visual should appear in each section, and ensure the page communicates the value within the first five seconds.

Design an onboarding experience for [your product] that helps [your target user] reach [the activation moment] as quickly as possible. Map every step from account creation to first value, remove unnecessary questions, identify where users are likely to abandon, and propose contextual guidance, sample data, progress indicators, empty states, and recovery messages. Include the exact screen sequence, copy, user actions, system responses, and analytics events that should be tracked.

Create a customer research system for [your company] to understand why [your audience] buys, hesitates, converts, churns, or recommends the product. Include interview questions, survey questions, support-ticket categories, feedback tags, a research repository structure, and a process for turning qualitative feedback into product decisions. Avoid leading questions and separate observable behavior from customer opinions. Finish with a framework for ranking insights by frequency, severity, strategic importance, and revenue impact.

Design an AI agent that performs [your desired workflow] for [your business or audience]. Break the process into clear stages, define the inputs, tools, decisions, memory requirements, validation checks, escalation conditions, and final outputs. The agent should verify its work before completing the task, clearly communicate uncertainty, and avoid taking irreversible actions without approval. Include a system prompt, workflow logic, tool requirements, fallback behavior, evaluation criteria, and examples of successful and unsuccessful runs.

Create an agentic workflow that researches [your topic], verifies information across multiple credible sources, extracts the most important findings, identifies contradictions, and produces a structured report for [your audience]. The report should include an executive summary, key findings, evidence, risks, opportunities, unanswered questions, and recommended actions. Require the agent to cite sources, distinguish facts from inference, and avoid presenting unsupported assumptions as confirmed information.

Act as a senior software engineer debugging the following issue: [describe the bug, expected behavior, actual behavior, error messages, and relevant code]. Do not jump directly to a single conclusion. First identify the most likely root causes, rank them by probability, explain what evidence would confirm or reject each one, and create a step-by-step debugging plan. Then provide the safest fix, explain potential side effects, add tests that prevent regression, and suggest any architectural improvements revealed by the issue.

Review the following code or project structure: [paste code or describe the repository]. Refactor it for maintainability, performance, security, and clarity without changing intended behavior. Identify duplicated logic, weak abstractions, oversized components, unclear naming, unnecessary dependencies, poor error handling, and missing tests. Propose the refactoring order, explain why each change matters, and return improved code with comments only where they add real value.

Design a scalable technical architecture for [your product], expected to support [number of users or usage level]. Include the frontend, backend, database, authentication, file storage, APIs, background jobs, analytics, logging, monitoring, security, deployment, and disaster recovery. Explain the tradeoffs behind each technology choice, identify where complexity should be avoided during the MVP stage, and describe how the architecture should evolve as usage grows.

Create a repeatable content production system for [your brand] targeting [your audience] across [your platforms]. The system should turn one core idea into short-form videos, carousels, newsletters, posts, and lead magnets without making every asset feel duplicated. Define the research process, content pillars, hook framework, production workflow, approval process, publishing cadence, repurposing logic, performance metrics, and feedback loop. Include templates that a small team can follow consistently.

Develop a complete campaign for [your brand] promoting [your product or offer] to [your audience]. The campaign should include the central idea, customer insight, promise, messaging hierarchy, visual direction, short-form video concepts, carousel structure, email sequence, landing-page copy, and CTA strategy. Avoid generic claims and build the campaign around a specific tension, transformation, or opportunity that the audience immediately recognizes.

Create a pricing strategy for [your product] based on the value delivered to [your audience], the alternatives they currently use, and the cost of the problem being solved. Recommend pricing tiers, usage limits, feature boundaries, annual pricing, trial structure, upgrade triggers, and risk reversal. Explain the behavioral logic behind the structure and identify which assumptions should be tested before the final pricing is locked.

Transform [your service] into a clear productized offer for [your ideal customer]. Define the exact outcome, scope, timeline, deliverables, exclusions, onboarding process, communication cadence, pricing, guarantees, and proof required to make the offer credible. Remove custom work that creates operational chaos and structure the service so it can be delivered repeatedly with consistent quality and healthy margins.

Create a realistic 48-hour plan to launch the first version of [your product idea]. Prioritize only the features required to prove that [your target audience] wants the outcome. Break the plan into research, specification, design, build, testing, deployment, outreach, and feedback collection. For every stage, define the deliverable, time limit, decision criteria, and what should be deliberately ignored. End with a script for contacting the first 20 potential users and a simple method for measuring whether the MVP deserves further investment.

Do not ask Grok to “make something good.”

Give it:

A specific role
A defined audience
A clear business goal
Relevant context
Constraints
Required deliverables
Quality criteria
A clear definition of success

The difference between a weak AI output and a professional one is usually not the model. It is the quality of the brief.