Just describe what you want
Start with what you want to build or solve, who it is for, and any constraints that matter. You do not need to specify the technical steps.
Lead with the goal
Keep the first request focused on a useful result:
Build me a CRM for tracking consulting clients.
Create a dashboard showing weekly sales from Stripe.
Set up an automation that emails me every Monday with last week’s activity.
Make a project tracker for my design team.
Name the audience and the information you need. Compare these requests:
| Request | Why it helps or falls short |
|---|---|
| “Create a contact list for my sales team with fields for name, email, company, and deal status.” | Names the audience and fields |
| “Make a thing for my team.” | Does not say what the result should do |
| A long specification of every implementation detail | Can obscure the first outcome you need to review |
Add important requirements upfront, then use follow-up messages to refine the first version. A short prompt is not a reason to leave out a required approval step, data restriction, or business rule.
Mention relevant context
Name the app, collection, file, or connected service you want to use:
Use my Stripe account.
Pull data from the Contacts app.
Here’s a CSV of my products.
Identify the intended account and provide any required connection or access. See Connect your data sources.
Tip: If you are unsure what to build, ask Play to suggest options before making changes. Brainstorming gives you a way to compare approaches first.
Still stuck? Email support@play.fast