Iurii Uses: #Architecture

We publish 20-30 news articles per day and indexing latency was killing us — by the time Google crawled a story, the news cycle had moved on. Iurii's audit covered IndexNow setup, a sitemap that was hitting size limits and dropping URLs silently, and canonical tags that were inconsistent between AMP and non-AMP versions. The IndexNow integration alone moved median time-to-index for Bing from days to under an hour. Report was direct, no fluff, exactly what we needed.

As COO, I worked closely with Iurii, who led our IT department with rare clarity and ownership. He consistently turned business needs into reliable technical solutions, improved our infrastructure, and kept delivery predictable even under pressure. Communication was straightforward, priorities were transparent, and results were measurable. I'd gladly work with him again and strongly recommend him.

As Head of Production I had the opportunity to work closely with Iurii during his time with our company. Although I do not have a technical background, it was clear to me that he is a highly competent and professional IT specialist. He approaches his work in a structured and well-documented manner, ensuring long-term stability rather than quick fixes. I particularly value his ability to fully understand business needs before implementing solutions, as well as his responsiveness in urgent situations. His contribution extended beyond his formal responsibilities, often bringing valuable insights to the team. I confidently recommend Iurii for any technical role.

I'd read about llms.txt and AI discoverability but had no idea whether any of it actually mattered for our SaaS docs site. Iurii's audit gave me the honest answer: most of it is speculative right now, but a few things genuinely move the needle today — clean semantic HTML, robots.txt directives for AI crawlers, and structured data that retrieval systems can use. He also flagged that we were blocking GPTBot by accident in a leftover robots rule from 2023. The report saved me from chasing trendy fixes and pointed at the boring ones that actually work.

Before we closed on a seed-stage SaaS we asked Iurii to look under the hood. He gave us a written report in five days: what was solid, what was held together with tape, and roughly what it would cost to fix the worst of it. He flagged a scaling bottleneck in their database layer that the founders hadn't mentioned, and rated the rest realistically instead of either rubber-stamping it or scaring us off. That report changed how we structured the deal.

We had three CRM options on the table and kept going in circles for weeks. Sent Iurii our list of needs, he came back the next day with a clear pick and a short explanation why the other two wouldn't work for us. Done.

We had a small in-house dev team and no one senior enough to make the hard architectural calls. Hiring a full-time CTO didn't make sense at our stage, so we brought Iurii in two days a week. Within a month he'd untangled the deployment process, sat in on hiring interviews, and helped the team push back on a feature request from sales that would have cost us six weeks. He treats the role like a partner, not a consultant billing hours.

We'd just raised and needed to double the engineering team fast, but nobody internally had hired at that scale or owned the architecture decisions that came with it. A full-time CTO was a six-month search we didn't have time for. Iurii held the role two days a week in the meantime — he set up the interview loop, sat in on the senior candidates, killed a rewrite the team was quietly drifting toward, and made the infrastructure call before it turned into a fire. When we finally hired someone permanent the handover took a week because everything was already documented. He ran it like an owner, not a consultant billing hours.

I was starting a new project and spent two weeks reading comparisons online and getting nowhere. One hour with Iurii and I had a clear answer. He asked the right questions, cut through the noise, and gave me a real recommendation — not 'it depends'.

We migrated our content platform last autumn and assumed everything was fine because the tests passed. Iurii's audit found 140+ broken internal links — old slugs that survived the migration, redirects that pointed to redirects, and a few documentation pages quietly returning 410. Linkinator in CI now catches them before they ship. What surprised me most was the report explained why each broken link mattered for crawl budget, not just that it existed. That made the case for fixing them easy to sell internally.

We took over a Next.js project from another agency and inherited a mess — failing builds, no tests, deployments that worked locally and broke in production. Iurii spent two weeks getting it stable before touching any new features. He documented what was broken, fixed the critical issues, and left us a short list of the smaller things we could handle ourselves. By the end the project was actually maintainable, which had felt impossible at the start.

Had a client project coming up and wasn't sure which CMS to go with. Iurii asked a few questions about what the client actually needed, then gave me one answer — not a list of options. That's what I wanted. Went with it, no regrets.

We were about to hand a project off to a new development team and I wanted someone to look at the code first. Iurii reviewed it and found a few things that would have caused real problems down the line. The new team thanked us for the cleanup.

I'd built most of our MVP with Cursor and it looked finished — it compiled, the tests were green, the demo worked. It just wouldn't survive real users. Iurii took it over and found what I couldn't see: authentication handled four different ways, tests that only asserted what the code already did, and a dependency list half of which was unused. He didn't rewrite it from scratch — he told me honestly what was salvageable, ripped out the dead code, and got it to something a real team could build on. Two weeks and it went from 'looks done' to actually shippable.

We were about to pay for a hosting plan that was way more than we needed. Iurii looked at what we actually have — traffic, data, usage patterns — and suggested something much simpler. We switched, saved money, and nothing broke.

We had an acquisition offer on the table and I needed to know whether our own codebase would survive the buyer's technical review before I walked into that room. Iurii did a five-day independent audit and gave me a written report I could actually act on — what was solid, the two things that would raise flags in a data room, and what it would take to fix them first. He caught an undocumented dependency on one ex-contractor's private package that would have been a red flag the moment their team looked. We cleaned it up before diligence started, and the deal closed without a single technical concession. Best money I spent on the whole process.