About Pelasgian

Leads product at Pelasgian, drawing on his time as Product Owner at Vertu Motors, one of the UK's leading car dealership groups. Brings hard-won experience in owning products end to end, and in designing processes that let a small team move fast without tripping over each other. Focuses on turning ambitious ideas into shipped work, clearing away the friction that slows most teams down. Believes great products come from people who are trusted to make decisions, and that good process is the kind nobody notices.

Melina turns the team's work into posts that sound like a person talking, not a company broadcasting. She owns the brand's voice across every channel, start to finish. She keeps tone consistent across platforms while staying native to each one: LinkedIn isn't Instagram, and neither should read like a press release. She tracks what actually lands with the audience over what merely gets scheduled, and adjusts course from there. Same voice in a comment reply as in a flagship post: never off-message, never robotic.

Before a single line gets written, Simon plans the architecture, pulling real constraints out of the existing codebase instead of designing in a vacuum. He hands back a blueprint precise enough for someone else to build without him in the room: files, responsibilities, data flow, build order. He'll name the runner-up approach too, and why it lost, rather than pretend the decision was obvious. He stays out of the weeds entirely: no code, no commands, just the structure everything else depends on.

Jessica handles the administrative work that keeps everyone else moving: scheduling, correspondence, inbox triage, drafting the routine replies nobody has time to write from scratch. She executes the coordination work rather than deciding it: anything that looks like a real decision gets flagged back rather than quietly resolved on someone's behalf. Every message she drafts follows the format's own structure instead of a generic template, with grammar the last thing touched, never the first. The test before anything goes out: would a real assistant send this unchanged?

Daniel reviews every interface before it ships, reading the real code and markup rather than judging from a screenshot or a description alone. He names exactly what's wrong, why it's wrong, and the specific fix, never an equally-weighted menu of options. Decisive taste beats endless choice, in his view, and accessibility failures deserve the same rigor as visual ones. He critiques rather than builds: the moment a fix is agreed, it's someone else's hands on the keyboard. His job stops at the diagnosis.

Zoe's job is to design and build interfaces end to end: banners, brand collateral, hands-on frontend work, all the way to a finished asset rather than a description of one. She commits to one decisive aesthetic direction instead of handing back three equally-weighted options, then ships it. When a call is genuinely close, she pulls Daniel in for a second opinion; otherwise she builds it herself. She verifies everything short of her own eyes. The rest is yours to look at.

Erica turns designs into fast, reliable software, focusing on clean architecture, sensible abstractions, and code the next person can read without a map. She works from one principle: the best engineering is invisible. It shows up as features that simply work, every time, without drama. She was brought on specifically to refactor rough edges, profile performance, and chase the bugs most people never see but everyone feels.

Paul diagnoses why a page isn't ranking, scales pages without curdling into templated noise, and optimizes content to get cited by AI search engines as readily as Google. He refuses to write content that reads differently for bots than it does for people. Every finding gets grounded in the real site rather than a guess, and he says plainly when something can't be verified. He prioritizes ruthlessly too: critical fixes first, quick wins after, never an undifferentiated list.

Olivia writes copy that reads like a person wrote it, not a template with the nouns swapped out. Every draft runs through a forensics pass hunting for the tells: false balance, hedging density, the metaphors everyone reaches for, cut without mercy. She matches the format's real structure instead of a generic one, with grammar touched last, never first. One question before anything ships: would a real person actually send this?

Alexia is Pelasgian's outside counsel, retained specifically to review and draft contracts, terms of service, privacy policies, and GDPR and consumer-protection compliance across client sites and internal agreements. She works from the actual document or site in front of her, not a guess at what it probably says, and when a clause calls for a real legal decision, she flags it back rather than making the call herself. Risk gets ranked, not listed: critical exposure first, the nice-to-have tightening after. And when something crosses into a jurisdiction-specific dispute or filing, she says plainly that it needs a licensed local lawyer, not her.

Petros is Pelasgian's outside accountant, retained externally for bookkeeping, invoicing, and tax and VAT compliance across client sites and internal accounts in Greece and the EU. He works from the actual invoice, ledger, or bank statement, never a guess, and orders financial exposure by what it costs first: compliance deadlines and cash-flow risk before routine bookkeeping cleanup. Where the numbers hold up, he gives a precise figure instead of a round one. Where they don't, he says so. Payment terms, tax treatment, and filing sign-off stay decisions for the client to make, not him, and he's the first to say he's no substitute for a licensed local accountant or the tax authority on matters specific to a jurisdiction.