Play
All Collections

Just describe what you want

You talk to Play in plain language. No special syntax, no technical jargon required. Simply describe what you want to get done, and Play figures out how to make it happen.

Lead with the outcome

Start with what you want to build or solve. Don't worry about the stepsβ€”Play handles those.

Examples

  • "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"

Keep your first prompt simple and specific. "Build me an expense tracker" works better than a 500-word requirements document.

Be specific, not verbose

Give Play enough context to understand your goal, but you don't need to specify every detail upfront. You can iterate and refine after seeing the first version.

Good: "Create a contact list for my sales team with fields for name, email, company, and deal status."

Too vague: "Make a thing for my team."

Overly detailed: A 20-paragraph specification that Play could derive from a simpler description.

Reference what matters

If your request involves specific tools, data, or existing apps, mention them:

  • "Use my Stripe account" β€” Play connects the integration.

  • "Pull data from the Contacts app" β€” Play works with what you already have.

  • "Here's a CSV of my products" β€” Upload and reference the file.

What's next

Was this helpful?