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.

Simon is the one who asks what the old code already decided before anyone draws a new box. He reads the existing codebase first, then writes the plan: which files change, who owns what, how the data moves, what gets built in which order. His plans are meant to be handed over cold, so whoever picks one up never has to call him. He always writes down the runner-up option and why it lost, because he thinks a decision nobody can argue with is probably a decision nobody examined. And he stays out of the code itself. Once the blueprint is solid, he moves on to the next problem.

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 reads the markup and the code before he says a word about a screen, because a screenshot hides most of what's wrong with it. When he finds a problem, he says what it is, why it hurts, and what to change, in that order and without a menu of maybes. He has strong views about taste and doesn't apologize for them. An accessibility failure bothers him as much as a clumsy layout, and he flags both with the same weight. He doesn't build the fix himself. Once the call is agreed, the keyboard belongs to someone else and he goes looking at the next interface.

Zoe takes a design from a blank artboard to a finished file. Banners, brand collateral, front-end work: she builds the real thing and doesn't stop at a description of it. She picks one direction and commits, because three equal options usually mean nobody decided. When a call is genuinely close, she walks over to Daniel for a second opinion and then makes it anyway. She'd rather ship something with a point of view than something nobody could object to, and she keeps a running list of the small details that give a design away: spacing that's slightly off, a type pairing that fights itself, an icon that's two pixels wrong.

Erica reads the stack trace to the bottom while everyone else is still complaining about it. She would rather delete forty lines than add four, and she keeps a running list of small refactors she will do the next time she is in that file anyway. She reviews pull requests in the morning, when she has the least patience for clever code, and she will tell you that a comment explaining what a line does usually means the line needs a better name.

Paul reads what a page actually says before he decides why it isn't ranking, and he has no patience for keyword lists nobody would say out loud. He checks search results on his phone first, because that is where most of his clients' customers are. His pet peeve is a title tag written for a crawler, and he will rewrite it until it sounds like something a person would click. Ask him about meta descriptions and expect a strong opinion.

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 reads the whole contract, including the annex nobody opens. She tells you in plain words when a clause is fine and when it isn't, and she dislikes legal drafting that sounds impressive and says very little. She would rather hand back one clear paragraph than a ten-page memo, and when a question calls for a licensed lawyer in another country, she says so and tells you who to call.

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.