EvaCodes

I am the CEO of kz.design

ux ui design

At K&Z, we design complex SaaS interfaces — the kind where every component has logic behind it, every state matters, and a developer who doesn't read the design carefully will break things in ways that are painful to fix later. We needed a dev partner who could take our structured Figma deliverables and implement them with precision. Not interpret them. Not simplify them. Implement them. That's a higher bar than it sounds, and it's why finding EvaCodes took a while.

Referral

2-5 Employees

We brought EvaCodes in as the development side of a SaaS dashboard project — a complex B2B platform with multiple user roles, dense data views, and a design system we'd built from scratch. Their job was to take our Figma files — component library, interaction specs, responsive behaviour, edge cases — and turn them into working frontend code. They also handled backend integration for the data layer and built out the authentication and permissions logic. Key deliverables: pixel-accurate frontend implementation, integrated design system in code, role-based access logic, and a staging environment with full QA sign-off against our design specs.

Two things I track on every project: how close the build is to the design, and how many rounds of revision it takes to get there. With EvaCodes, both were better than average. The first review pass had a shorter correction list than I'm used to — specific things, not fundamental misunderstandings of the design. The client's internal dev team, who took over after handoff, came back to say the code was clean and the component structure made sense to them. That last part matters more than people think: a good handoff saves everyone downstream.

We run on two-week sprints and have no patience for vague updates. EvaCodes matched that rhythm without friction. They documented what was done, what was next, and what needed a decision from us — and they kept those updates short and useful. When I flagged a design inconsistency mid-build, they fixed it the same day instead of putting it in a backlog somewhere. That responsiveness to design feedback specifically is something I don't take for granted, because not every dev team treats design notes as real blockers.

They read the design system. Properly. Not just the screens — the components, the variants, the naming conventions. By the third sprint, they were using our design language in their own comments and tickets, which made communication significantly faster. When a developer understands why a component is built the way it is — not just what it looks like — the implementation quality goes up. That understanding showed up in the output.

The one thing I'd mention is that early on, a couple of interaction behaviours were implemented slightly off-spec — not the visuals, but how certain states behaved. Small things, caught quickly, fixed without drama. If I were doing it again, I'd just add an explicit interaction QA checkpoint from day one on top of the visual review. More of a process suggestion than a complaint.

I am the PR manager of Stripo

Stripo is an email builder for teams and individuals who need to produce high-quality emails fast.

Referral

2-5 Employees

EvaCodes worked across two main areas. First, they developed new interactive content modules for the platform — gamification elements, survey embeds, and countdown timer functionality compatible with major email clients. Second, they redesigned the team management interface: the roles and permissions UI that our enterprise users use daily to coordinate across larger production teams. On top of that, they handled integration testing to make sure everything worked cleanly within our existing system. Key deliverables: three new interactive modules, a redesigned team management UI, and integration QA documentation.

The interactive modules got adopted faster than we expected. The gamification element in particular became a talking point — it fed into content we published and got picked up by our audience in a way that felt organic, not forced. The team management UI update reduced friction during enterprise onboarding, which our customer success colleagues noticed and mentioned unprompted. From a communications standpoint, having tangible new features to announce on a predictable schedule made a real difference to how we plan campaigns and partner updates.

Structured and reliable. They ran sprints with clear scope, gave updates without needing to be chased, and flagged potential blockers early enough that nothing became a crisis. When I needed something for an announcement — a demo environment, a feature summary, specific details for a partner brief — they turned it around quickly. I'm not always close to the technical day-to-day, but I could tell things were running smoothly because the information I needed kept arriving when I needed it.

They cared about how the work would land, not just whether it was technically complete. A few times they asked questions I wouldn't have expected from a dev team — about how a feature would be explained to users, what the use case looked like from a non-technical perspective, whether the naming made sense. That kind of curiosity makes the output better. It also made collaboration easier, because we were clearly working toward the same thing.

nothing major, we worked in synergy

I am the Founder & CEO of O-CMO

O-CMO is a platform matching tech service companies with marketing executives and senior experts.

When I started O-CMO, the platform lived mostly in my head and in a few Notion docs. I had the matching model figured out, the CMO network was growing, and clients were coming in — but everything ran manually. I needed to turn that into an actual product: CMO profiles, a client-facing portal, an onboarding flow, and the internal tooling to manage engagements without me being the glue holding it all together. Finding a dev team that could build something like that without six discovery workshops and a €50K proposal was the challenge.

Recommendation

2-5 Employees

EvaCodes built the core of the O-CMO platform. On the client side: a matching intake flow, a CMO catalog with filters by vertical and seniority, and a client dashboard to track engagement status. On the specialist side: CMO application and profile management, verification status, and a basic pipeline view. They also built the CMS layer so I could update content, add new CMO profiles, and publish case studies without touching a developer. Key deliverables: platform frontend and backend, CMO and client portals, CMS integration, and infrastructure setup.

Before the platform, onboarding a new client took me personally involved at every step. After launch, a significant chunk of that became self-serve. Time-to-first-match dropped noticeably, and we were able to handle more concurrent engagements without adding headcount. The CMO application flow alone brought in more inbound specialist applications than I expected — the product itself started doing acquisition work I was doing manually before.

I'll be honest — I'm a difficult client. I know what I want, I change my mind when I see something, and I have opinions about copy and UX that most devs find annoying. EvaCodes handled it well. They pushed back when my changes would've broken the sprint, explained the tradeoffs clearly, and found ways to accommodate most of what I needed without derailing the timeline. Everything shipped on schedule. That's not something I take for granted.

They understood that I wasn't just building a website — I was building a business tool I'd use every day. That shifted how they approached decisions. They'd ask "how does this work in practice?" before implementing something, which meant we caught a bunch of UX problems before they became support issues. For a founder who's also the main user of the product, that kind of thinking from the dev side is genuinely valuable.

I would've liked more proactive input on the product architecture earlier in the project. There were a couple of structural decisions we made in sprint one that we partially revisited later — not because of mistakes, but because nobody stopped to ask "where is this going in six months?" That's partly on me, but a more experienced team might've pushed for that conversation upfront.

I am the Co-founder of Paintit.ai

Vertical AI SaaS workspace for interiors and exteriors.

Referral

2-5 Employees

The scope was substantial. EvaCodes built the frontend application — the editor, the style selection flow, room upload logic, and the generate/repaint/stage interactions. On the backend, they integrated the AI image generation models, built the API layer, and set up the furniture recommendation engine that pulls real products from retail partners. They also handled cloud infrastructure, image storage, and performance optimization for generation speed. Key deliverables: production-ready web app, AI pipeline integration, furniture matching API, and the partner-facing e-commerce module.

We launched on schedule and hit our first user milestones faster than expected. The generation speed was a specific concern for me — nobody waits for slow AI tools — and the team optimized it to a point where I was genuinely impressed. Post-launch, user retention was solid, and the furniture click-through feature became one of our top engagement drivers. That module alone justified the entire partnership.

I've worked with agencies before, and the usual story is: things slip, scope creeps, communication gets vague. With EvaCodes it was different. They ran structured sprints, flagged blockers early — not after a deadline missed — and were genuinely flexible when I came in with a design change or a new product direction mid-sprint. As a creative director, I change my mind a lot when I see something rendered. They handled that without making me feel like I was breaking the project.

They understood the product. Not just the technical spec — the actual product. They're building for a creative audience, they got what mattered about UX, and they cared about how things looked and felt, not just whether they worked. That's rare from a dev team. I didn't have to argue for quality or push to get the UI right. They brought that themselves.

I have nothing to add.

I am the CMO of Pluspoint.io

One-click AI ad copy and marketing strategy generator

Referral

2-5 Employees

EvaCodes handled the full development cycle for the micro-sites feature: frontend templating (responsive, white-label, SEO-optimized), backend API to serve dynamic location content, and integration with our existing review and campaign data. They also set up the CMS logic so our clients could manage their pages without touching code. Deliverables: production-ready templates, content API, integration docs, and support through QA and launch.

The module shipped on time, which honestly was the most important thing for us. Post-launch, location page conversion improved noticeably, and the time our team spent on manual content updates dropped significantly. The API held up fine under real traffic. No scramble after go-live, which is rarer than it should be.

Clean. We ran it in sprints, they gave updates without me having to ask, and when I changed priorities halfway through (which I did, because that's marketing), they regrouped without making it a whole thing. I had a direct line to the dev and the PM, no "we'll check with the team and get back to you" delays. That matters a lot when you're moving fast.

They actually read the product. Not just the task, the product. They'd come to calls having looked at what we built, understood the context, and sometimes pushed back with "have you considered doing it this way instead?" I didn't expect that from a dev partner. It saved us from at least one bad architectural decision.

In the very beginning, evening response times were a bit slow — we're partly async across time zones, so that created a couple of small delays. Once we synced on working hours, it was fine. Minor thing, but worth mentioning if someone's working with a tight deadline from day one.