Tips & Tricks

Thirteen habits that separate a quick, on-brand result from a generic one, plus two gotchas worth knowing before they bite you.

1. Ask Ploy's Agent first, docs second

Ploy's Agent has live context on your workspace, sites, and deploys, and it can act, not just answer. Ask it first. This help site covers the things it can't fix from inside the app.

Learn more: Ploy's Agent — capabilities and tips

2. Be specific and scoped, not evaluative

"Make the site better" gets generic output. "Add a testimonials section below the hero with 3 customer quotes on a light gray background" gets what you actually wanted.

• Lead with business context — "we're B2B SaaS targeting engineering leaders."
• Reference real examples — "like the hero on stripe.com."

Provide one complete brief up front: your product, audience, offer, the sections you need, proof points, and the main call to action. A clear brief means fewer correction rounds.

One of the best ways to get there is to show what you want. Share a demo from another website or attach a screenshot of the result you want. A concrete target helps Ploy's Agent reach the result faster.

Learn more: Ploy's Agent — how to prompt effectively

3. Iterate in layers, one goal per chat

Build → refine the hero → change the CTA → add social proof, as separate turns. Each chat is a scoped workflow; stuffing four goals into one prompt is where quality drops. And ask for options ("give me 2 headline variants") instead of re-rolling the whole thing.

Start a new chat for each distinct change, for example one chat for the hero and another for pricing. Ask for one or two changes per message, and review them in the preview before you request more polish.

Learn more: Ploy's Agent, working in focused chats

4. Start from your current site

Give Ploy's Agent your public website URL. On a new Ploy site, it builds a design system from that site, then rebuilds your pages on it. For inspiration from another site, name the page and the parts you like, such as layout or motion, and Ploy's Agent adapts them with your own brand. Review every page before you publish.

Learn more: Site Builder, design system from your website

5. Change the design system, not individual pages

Say "change our primary color to navy" once and the tokens propagate everywhere. Don't hand-specify fonts, spacing, or hex codes per section — that fights the system and is a top cause of off-brand output.

Learn more: Site Builder — the design system

6. Make “done” mean tested

Before you launch, ask Ploy's Agent to verify the published experience. A quick check of your key pages, buttons, forms, and sign-in flows helps catch small issues before visitors do — so you can ship with confidence.

7. If it goes quiet, nudge it

"Agent silently stops mid-task" came up many times in the past. We've shipped fixes for it, but it can still happen in the odd edge case. If it does, a short "continue" usually resumes the work — and please also drop a note to support@ploy.ai so we know it happened. That's what helps us close out the remaining edge cases.

Separately, a "Failed JSON" error usually just means your session expired — refresh the page.

8. Publish often, roll back freely

Deploys take seconds and every publish is an immutable snapshot. To go back, select Versions next to Publish in the preview and restore an earlier version. Then publish to make it live. Run the go-live checklist first: mobile preview, links, meta/OG tags, Lighthouse, analytics, and domain SSL.

Note: your work auto-saves as a snapshot every 3 seconds, so you don't need to publish just to save — publishing is only for pushing changes live.

Learn more: Publishing & Deploys, restore an earlier version

Learn more: Launch Checklist — the full go-live list

9. Connect integrations early

Integrations expand what Ploy's Agent can do — GA4, Search Console, GitHub, Notion, Slack, HubSpot. Then query conversationally:

• "Check the acme/api GitHub repo against our current docs — do we have gaps in the billing-system documentation?"
• "Look through Slack and Notion for the new features we shipped this week, then draft me a blog post about them."
• "What keywords are we ranking for, and which pages are slipping?"
• "Who visited our site this week, and which companies look like a fit?"

The real power shows up when Ploy's Agent combines integrations — pulling from your repo, docs, Slack, and analytics in a single request.

Visitor ID is on by default.

Learn more: Integrations — connect GitHub, Notion, Slack, and more

Learn more: Visitor Identification

10. Automate recurring work with scheduled Ploybooks

You don't need to build Ploybooks or schedules by hand. Just open a chat and ask — for example, "Every morning, get yesterday's visitors and send a summary to my Slack #channel." Ploy's Agent creates the Ploybook and sets up the schedule for you. Review and adjust it anytime in the Ploybooks section in the left sidebar.

Each scheduled run uses credits, so run the Ploybook manually first to make sure the output is right. Start with a daily schedule instead of a high-frequency schedule such as every 15 minutes, then increase the frequency only when the workflow truly needs it. Ploy uses this same approach to automate work on its own marketing site.

(First connect Slack from Integrations in your workspace sidebar so Ploy's Agent can post to your channels.)

Security tip: use a dedicated Slack login so the integration only sees the channels you invite it to.

Learn more: Ploybooks — saving and scheduling workflows

11. Pick the right agent for the change

When you write a prompt, open the agent picker in the message box and choose a profile.

• Ploy Ultra uses a better model for your change. It costs more credits, but it often reaches the result in fewer rounds, so it can save credits overall.
• Ploy Lite suits small edits, such as a wording change or a spacing fix.

You can switch profiles at any point in a chat. Your next message runs on the new profile.

Learn more: Ploy's Agent, choose an agent profile

Learn more: Ploy Lite

12. Check your credits before a full build

Before a full site build, open Settings, then Organization, then Usage. Make sure you have enough credits so a large run doesn't stop halfway.

Learn more: Credits, tracking your balance

13. Put the most important part in capital letters

In a bigger prompt, write the most important part in capital letters. Ploy's Agent treats it as more important. For example: "Rebuild the pricing page in our new layout. KEEP THE EXISTING PLAN NAMES AND PRICES."

Two gotchas worth knowing