Ploy demo: what a walkthrough should show and what to ask before you commit

By Ranjit Bhinge, founder of Blur Studio · Updated · 8 min read

Short answer: Ploy is an AI platform that builds and hosts business websites and tracks who visits them. Its demo page asks for your work email and says it uses it to tailor your demo, with a walkthrough from Ploy's team or your own workspace as the two paths. Ploy does not publish how long the call is or what it covers, so go in with a test project, a question list and pass or fail marks.

Ranjit Bhinge

You are about to book a Ploy demo, or you are deciding whether to, and you want to know what to look for and what to ask.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

A demo is a sales call that is set up to show a product at its best. That is fine, as long as you bring your own test. Ploy's public pages do not describe the demo agenda, its length or who runs it, so treat any agenda you read elsewhere as unconfirmed. What they do give you is a long list of features and limits. This page turns that into a plan: what to have ready, what to ask Ploy to show live, 25 questions, and a pass or fail sheet. Details are as of November 2026, so check Ploy's pages before you book.

One more option: you can often learn more from a hands-on test than a call. Ploy's Free plan needs no credit card, so you can try the builder on a copy of your site before or after the call.

This page may contain affiliate links from which Blur Studio earns commissions.

What Ploy's demo page says

The demo page is titled "See Ploy in action". Its description says you answer a few quick questions and Ploy points you to the fastest path: a tailored walkthrough with the team, or your own workspace to start building right away. On the page itself you drop your work email, and Ploy says it "reads your company and site automatically" so it only asks for what it cannot find. It is a two-step flow, and Ploy states "work email only", because that is how it tailors your demo.

Two practical points follow:

  • Use the email you are happy to be contacted on. Ploy says it uses your email to look up your company and site.
  • Ploy does not say how long the walkthrough is, who runs it, whether it is recorded or what it shows. Ask when you book, and ask for the agenda in writing.

Ploy's enterprise page adds that if you ask for a demo it will "plan a phased rollout with your team", which suggests demos are aimed at teams, but it does not say a small business cannot book one. If you want to book directly, you can book a demo here.

What a good demo should show, live

Ploy lists a lot on its pages. In a walkthrough, ask to see these on your own site or a close copy, not on a prepared sample. Screens built for the call hide the awkward parts.

  1. A rebuild from a public URL. Ploy's docs say it rebuilds a site from a public address and that this is "a rebuild, not an identical copy". Ask to see yours, including a page with a form and a page with something unusual such as a calculator or embed. Ploy's docs say forms, plugins, embeds and custom code may need separate work. See Ploy site migration.
  2. The design system. This is the shared set of colors, fonts and components the pages are built from. Ask what happens when you change one token and how a new page stays on brand.
  3. A text edit and a new page. Ask for both, with the credit count before and after. Ploy says direct text edits usually cost nothing, and chats and generation cost credits.
  4. Preview, publish and rollback. Every publish is a saved snapshot, and you can restore an earlier one. Ask them to roll one back.
  5. Forms and where submissions go. Built-in forms store text fields in the dashboard, with a 128 KB limit per submission. Ask to see an entry arrive and a copy reach your CRM (the system that holds your customer records) or inbox.
  6. Analytics. Ask what a real week of data looks like, how AI assistant visits and crawlers are separated from people, and how refused cookies are counted.
  7. Visitor identification. Ask for the real rules: US only for new visitors, cookie-consent only, one enrichment credit per match, no published match rate. Read Ploy visitor identification and outreach first.
  8. AI visibility tracking. Ask what it shows for your category, how many credits a daily check uses, and how it handles the fact that answers change.
  9. Experiments. A/B testing is on request per workspace. Ask if it is enabled in the demo account, how many tests run on your plan and how it decides a winner.
  10. Domains and routing. Ask to see a path routed to Ploy while the rest stays on your old host, and the redirect (301) setup for changed URLs.
  11. Roles and access. Ask what an Owner, Admin and Member can each do.
  12. Credit and usage screens. Ask to see the usage page. It is where your real cost shows up.

25 questions to ask

Product fit

  1. Which of my pages will not move cleanly, and what do you suggest for each?
  2. What happens to my forms, plugins, tracking tags and embeds?
  3. Which features in the demo are live for my plan, and which are on request or on a waitlist? (PloyAds and PloyGrow are "coming soon" pages as of November 2026.)
  4. Which of my must-have integrations need Pro or Enterprise?
  5. What can I not do on Ploy that I do today?

Cost

  1. How many credits does my first build need, and how do you estimate it?
  2. What happens when credits run out mid-month, and what does auto-reload cost?
  3. Which plan do you expect me to need in 6 months?
  4. Is there a discount for startups or a program I should apply to first? See Ploy for startups.
  5. What are the renewal and cancellation terms on my plan?

Data and security

  1. Who owns my content and run data, and is any of it used to train AI models?
  2. Do you hold a SOC 2 report today, what type and for which dates? (Ploy's pages describe SOC 2 in different ways.)
  3. Can I see the DPA and the subprocessor list?
  4. How do I export my site and data, and how long is it kept after I cancel? Ploy's terms say 30 days to export and its privacy policy says 60 days of retention.
  5. What does your status page history show, and is there an uptime commitment?

Working with it

  1. Who reviews AI-written pages before they go live, and what stops one from publishing on its own?
  2. How does the agent show a plan before it spends many credits?
  3. How do I restore a page after a bad edit?
  4. What support do I get, how fast and where? (Ploy lists support email, a community Slack and a status page, and no response time.)
  5. How do you handle a site with thousands of pages?

Exit and risk

  1. If I leave, what do I take with me: source, database tables, forms, analytics?
  2. Does the source run elsewhere without Ploy, and have you seen a customer do that?
  3. What happens to rankings during a path-by-path move?
  4. Can you share a reference from a customer my size, not a logo bar?
  5. What is on your roadmap that I should not plan around yet?

Bring a test project, with pass and fail marks

Pick one real task and score the demo against it. Here is a template. The scoring is mine, not Ploy's, so adjust it to your needs.

TestPassFail
Rebuild 3 of your pages from the live URLLayout, copy and links are right after at most two rounds of editsNeeds rewriting from scratch, or links and forms break
Submit your contact formEntry arrives where you need it within a minuteEntry is lost or needs a developer
Make a text edit and a new pageDone, previewed on phone and desktop, credits shownCredit use is unclear or the page needs manual cleanup
Restore an earlier versionDone in a few clicksNot possible or unclear
Route one path while the rest stays elsewhereWorks with redirects for changed URLsNeeds a full cutover
Show the real monthly costYou get a number for your plan and credit tier in writingAnswer is "it depends"
Export the sourceYou get a working copyIt cannot be opened or run

Scoring: 7 passes, go ahead. 5 or 6, run a one-week trial on the Free plan before you pay. 4 or fewer, skip it for now.

An example of how to use it, with made-up results. Say you score a Ploy demo like this: rebuild passes, form passes, text edit and new page passes, restore passes, routing fails because your old host will not allow a proxy, cost passes with a written quote, export passes. That is six passes and one fail. Your rule says run a week-long Free plan trial. The trial should focus on the one failed test, so you learn whether a full cutover of the whole site is acceptable before you pay for anything.

Red flags in any software demo

  • The sample site is never yours.
  • Answers to cost questions come as "most customers use" instead of your number.
  • Outcome numbers such as traffic or lead gains are shown with no source. Ploy's own case studies (such as moving 600 pages in one night) are self-reported, and Ploy's pages do not say they are typical.
  • You are pushed to a plan before you have tested the Free one.
  • Limits (US-only visitor ID, request-only experiments) are missing from the call until you ask.
  • They will not put answers in writing.

Who can skip the demo

If your site is small and standard, a self-serve test costs you a few hours and no call. A self-serve test on Ploy lets you build a test site and read your credit use. See what the Free plan allows and how to use Ploy.ai. A demo is worth the time if you have a big or messy site, need SSO or a security review, or want a plan scoped. Skip Ploy altogether if you need a store, built-in booking or payments, or a fully white-labeled agency tool. See Ploy alternatives.

Checklist before you commit

  1. Free plan test done on your own content.
  2. Credit use from that test written down.
  3. Plan and tier chosen, with monthly and yearly prices as of November 2026 checked on Ploy's pricing page.
  4. Pass or fail sheet scored.
  5. Written answers saved for SOC 2, DPA, export and support.
  6. A fallback: your old site stays live and you have a backup.
  7. One named person who approves pages before they go live.
  8. A date to review the decision after 30 days.

How I'd approach this

Do a Free plan test before the call, so the demo is a conversation about your real problems and not a tour. Write your three biggest worries and make sure each gets an answer in writing. After the call, run the pass or fail sheet yourself without the salesperson.

First-week plan: day 1, list your must-haves and your three riskiest pages. Day 2, build those pages on the Free plan and note credit use. Day 3, book the demo and send your question list and test pages ahead. Day 4, attend the demo and ask for the usage page and the export live. Day 5, score the sheet and decide: buy, trial longer or skip. If what you need is beyond a template platform, such as your own CRM and calendar connections with AI agents that use your business knowledge, Blur Studio builds custom versions, and you can see what that includes.

Questions people ask

How do I book a Ploy demo?

Ploy has a demo page where you enter your work email, and Ploy says it reads your company and site to tailor the demo. Ploy does not publish how long it is or what it covers, so ask for the agenda when you book. You can also start on Ploy's Free plan with no credit card.

Is there a free trial of Ploy?

There is a Free plan with no credit card: 500 credits a day up to 2,000, a ploy.build address and no custom domain. A paid trial is not described on Ploy's pricing page. See what the Free plan allows.

How long is a Ploy demo?

Ploy does not say on its public pages. Ask when you book and get it in writing, along with who will run it and what it will cover.

What should I prepare for a Ploy demo?

Your live site address, three pages that worry you most, your must-have integrations, your security requirements and your budget. Use the test table in this article to score what you see. See the quality control checklist for AI-built websites.

Does the demo cost anything?

Ploy's demo page does not mention a fee. It asks only for a work email. Check what the booking confirmation says, and do not enter payment details for a demo.

What should I not trust in a demo?

Sample sites, traffic and lead numbers without a source, and "most customers" answers on cost. Ploy's case studies are the company's own claims. Ask to see your own site rebuilt and your own credit usage.

Can I try Ploy without talking to sales?

Yes. The Free plan needs no card and you can build a test site on a ploy.build address. SSO, the audit log and a SOC 2 report are Enterprise features, which go through sales. See Ploy for enterprise.

What if the demo goes well but I still have doubts?

Run a one-week trial on the Free plan with your real pages, score the pass or fail table and compare at least one alternative. See Ploy alternatives and the Ploy.ai review.

More in this topic: Ploy.ai: login, startups, enterprise and integrations (8 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…