You're hiring
the person who builds it
Most consultancies work like this: you talk to a salesperson, they scope the project, then hand it off to whoever's available. You might never meet the person writing your code.
I work differently. When you hire Polyxmedia, you're working directly with me. I'm the one designing the architecture, writing the code, making the technical calls. There's no layer of account managers between us, no handoff to a junior team.
What 20 years actually looks like
I started professionally in 2003. PHP 4, FTP uploads to production, no version control. You learn a lot about resilience building things that way, mostly that you never want to do it again.
Since then I've built systems for ASDA, Loblaws, Tesco, South Eastern Grocers, Pizza Express, Harvester, T.I.'s Trap Music Museum, and a bunch of startups in between. The systems I've architected process billions of events per year. That's not a marketing number, that's the actual Datadog dashboard.
I've done the full-stack thing across Go, Python, PHP, TypeScript, Vue, React. I've shipped Kubernetes clusters, set up CI/CD pipelines, integrated payment systems, built AI features with LLMs and RAG before most people knew what embeddings were. The range matters because real projects don't stay neatly inside one technology.
What working together actually looks like
Direct communication
You message me, I reply. No ticket system, no "I'll escalate this to the team." When something needs a technical decision, you're talking to the person who actually understands the tradeoffs.
Architecture that fits
I'm not going to recommend microservices if a monolith does the job. I'm not going to add AI to something that doesn't need it. You get the right solution for your problem, not whatever I'm most excited about this week.
Real production experience
I've been on the other end of the pager at 3am. I know what it feels like when systems go down and people are waiting. That experience shapes how I build things, you end up with systems that are boring in the best way.
No surprise invoices
I scope work honestly. If something is going to take longer than expected, I tell you before it becomes a problem. I'd rather have an awkward conversation early than a bad surprise later.
Speed without shortcuts
One experienced engineer with context moves faster than a team that needs to sync up every morning. I can hold the full system in my head, which means less overhead and fewer "wait, who changed this?" moments.
I stick around
I don't disappear after handoff. If something breaks six months later, you can reach out. I built it, I understand it, and I'll help fix it. That's just how I think about this stuff.
When I'm probably not the right fit
If you need a team of 15 engineers tomorrow, I can't do that. If you need someone on-site five days a week, that's not how I work. If your project requires deep domain expertise in biotech or fintech compliance specifically, I'll tell you upfront if I'm the wrong person.
I keep my client roster small on purpose. It means I can give proper attention to the projects I take on, but it also means I sometimes have to say no. I'd rather be honest about that than overcommit and deliver something mediocre.
The numbers, if you want them
I generally prefer to let the work speak for itself, but sometimes you need concrete figures before making a decision. Fair enough.
"I started Polyxmedia because I wanted to build things properly, work with people directly, and skip all the layers of nonsense that slow everything down."
André Figueira, Founder