Complete website copy for Playmoove's enterprise platform relaunch — 56 numbered pieces across eight solution pages, four industry pages, platform documentation, company narrative, and all supporting microcopy. Functional enterprise writing throughout. The interesting writing is the company origin story and brand guidelines, excerpted below.
Homepage Hero
Not a turnkey app. An operating system.
Enterprise mobility infrastructure. Your vision. One platform for all your operations. Built for you.
Platform page positioning statement:
Playmoove is not a turnkey app. It's a configurable operating system managing the complete lifecycle of shared mobility operations: vehicle control, driver verification, zone enforcement, billing automation, and regulatory compliance. Built for institutions that need governance infrastructure, not growth-stage experiments.
"Not a turnkey app" and "not growth-stage experiments" are both explicit competitive rejections — written to disqualify consumer-grade platforms without naming them. The institutional buyer reads this and recognizes it immediately.
Built from Real Operations
Company Page / Origin narrative
In 2016, Playcar was operating car-sharing in Cagliari when our software vendor went under. We faced a choice: cobble together multiple systems that didn't talk to each other, or force our business into software built for someone else's operational model.
We chose neither.
Three developers. One year. One requirement: build a platform that works the way operators actually work — not the way software vendors think they should work. Playmoove 1.0 went live in May 2017, the same month our old vendor turned out the lights.
We know code, and we know the road. When we say "zone enforcement" we mean the version that actually works in a city with 47 restricted parking areas and a compliance officer who audits every violation. When we say "multi-wallet billing" we mean the version that survives corporate procurement review and integrates with SAP.
"We chose neither" is doing the same work as "We don't just know retail. We live it." — a short kicker that earns its isolation. The 47 restricted parking areas and the compliance officer are invented specifics; their function is to make the abstract ("zone enforcement") feel earned by someone who has actually been in the room.
Brand Guidelines v2.0 — Written and Designed
30 pages. Strategy, copy & design.
The Playmoove Brand Guidelines — Version 2.0 — are a complete brand strategy document: voice and tone, messaging hierarchy, visual design system, typography rules, photography direction, animation principles, content dos and don'ts, and legal copy. Written and laid out in full. The cover art is original.
The document includes the brand story in narrative form, a competitive differentiation framework, a quick-reference publishing checklist, and specific do/don't pairs for every major brand decision — from how to reference Italian heritage ("supporting detail, not primary message") to how long animations are allowed to run (600ms maximum).
Selected voice & tone pairs — as written:
- "Works with any IoT provider" — not "We support most major hardware vendors"
- "No hidden fees. Ever." — not "We strive to maintain transparent pricing structures"
- "Real engineers answer your calls" — not "We provide comprehensive technical support services"
- "Switch hardware anytime. Zero penalty." — not "We offer flexible partnership arrangements"
- "Monthly releases. No waiting." — not "We continuously enhance our platform capabilities"
The do/don't pairs are the most useful thing in the document for a future writer picking up the voice. They're not style rules — they're a demonstration of how the brand thinks. Each wrong version is a real failure mode someone would actually reach for.