Ployin
Around.
An honest teardown of Ploy — researched, written, and shipped on Ploy itself. I used it to build real websites, watched the agents work, and wrote down everything that wowed me and everything I'd fix.
I ran Ploy on my own websites, let the agents ship real pages, then turned my customer experience into this site.
Hit spin. See what I've built.
0 pulls
Press the button →
Where Ploy genuinely wowed me.
It understood the offer deeply
It grasped what I was selling and why it mattered, then built a page that explained my competitive advantage more clearly than my own copy did.
It found trends I'd actually used
From nothing but my site's context, Ploy surfaced marketing angles that aligned with my product — some I'd already tried myself. That it inferred them cold was genuinely surprising.
Shipping was painless — and it flagged what I'd miss
One click to ship, and along the way it surfaced the important stuff I would have forgotten — like adding an OG image so the site previews cleanly when shared. Proactive, not just reactive.
It coached me on SEO
Indexable URLs, concrete on-page suggestions, and a clean export I could feed straight into Codex. Ploy acted like a seasoned SEO expert — specific, actionable guidance instead of vague advice.
The rough edges I hit.
The new-user invite flow breaks and drops you outside the workspace
When a brand-new user accepts an invite and clicks into their personal organization, the flow breaks — they get kicked out of the workspace entirely, because the invite skipped the setup phase. You end up dropped outside the workspace you were just invited to.
Multi-site workspaces glitched into a site switcher
The docs say one workspace can hold multiple sites, but I hit glitches where Ploy told me it couldn't work on a certain site — and that I'd have to use a site switcher to get to it.
It couldn't load big dynamic sites
Importing large, dynamic websites failed outright — seemingly because of Cloudflare restrictions. Ploy hit a limit and couldn't bring the site in at all.
It couldn't see the embedded YouTube demo
On hephasbot.com, Ploy missed the embedded YouTube clip entirely and suggested I add a video instead of recognizing the one already there.
It couldn't “enter” my portfolio site
Ploy couldn't get past the entry interaction on adityainduri.com, so it never analyzed the data living behind it.
Small fixes worth shipping.
Share integrations across an org's workspaces
Have integrations carry across the workspaces in an organization so I don't reconnect everything per workspace. Even a simple “reuse these connections?” prompt would do it.
Differentiate workspaces vs. organizations
Workspaces and organizations look like the same thing. It's a small nitpick, but a little visual and conceptual separation would go a long way.
Selective Google account connect
Let me connect all my Google accounts and then choose which ones to use — rather than individually connecting Google Slides, Docs, and the rest one by one.
Autofill the email on invite signup
When you accept an email invite and go to sign up, it asks for your email again — it already knows the address it invited, so just autofill it.
Buy domains through Ploy with Entri
Add a way to buy domain names directly inside Ploy using Entri domains — you can use the Entri API to do exactly that.
Manage members per workspace, not just per org
Both invite surfaces say you're inviting people to the workspace, but you can only add or remove members at the organization level. A per-workspace membership control would close that gap.
Confirm a connection worked in chat
After connecting Ploy to a service from chat, have it confirm right there that the connection worked — the UI didn't make the new connection obvious.
Three real sites, not a sandbox.
Hephasbot
Browser-native robotics · live on Ploy
Ploy understood my product cold — LeRobot is the powerful open-source stack, Hephasbot is the no-driver browser shortcut to SO-100/SO-101 hardware — and rebuilt my homepage as the “Hugging Face LeRobot, without the terminal” keyword landing page.
1-click publish · fully responsive
Pocodex
Open-source Pokémon sprite gallery · 17,190 pets
I cloned the entire production site into Ploy 1:1, then used it to ship serious SEO/AEO: a server-rendered homepage band, a crawlable /pokemon catalog linking thousands of individual pet pages, real Pokédex flavor text per species, an on-brand OG card, and an llms.txt so AI engines can cite it. This is the depth Ploy unlocks once your site is in.
51,570+ sprites · per-pet pages · AEO schema
ployin around
This very site · the teardown you're reading
Meta proof: the page you're on right now was built entirely on Ploy. Loud Archivo display type, a white→black→lime color-band rhythm, the interactive Ploy-o-matic generator, click-to-expand evidence galleries, and a fused “ployinaround” wordmark — all designed, written, and shipped with the agents, then taken live on its own domain.
Custom domain · interactive · live on Ploy
I didn't just use Ploy. I stress-tested it.
I'm Aditya — a builder and operator who's driven real growth and shipped product. I don't wait for perfect instructions: I built sites on Ploy, broke it on purpose, and turned the mess into structured feedback a team can act on. That same high-agency, research-to-action mode is what I'd bring to the growth, GTM, and customer work this role is built around as a Summer Intern at Ploy.
