About
I built Implai because I was tired of guessing which AI tools actually work.
Eight years running SEO and content operations at scale. Five years using AI inside that work, not around it. Implai is where we test everything before you have to.
The story
I started in SEO in 2017, freelancing solo for the better part of a year before taking my first in-house role in 2018 — optimizing five English-language sites by hand — on-page, off-page, link outreach, the whole slow manual grind. By 2021 I was running SEO and content operations for international projects across Australia, Canada, and India, leading a team of ten-plus specialists, and managing technical health across a network that peaked at 2,000+ web properties in the iGaming and affiliate space.
That scale is what forced the shift to AI. You cannot manually QA a thousand sites. You cannot brief a content team by hand when you’re publishing at that volume. Starting in 2021, I began integrating AI into every stage of that pipeline — content production, technical monitoring, reporting — and it cut content costs by 60% while the team kept output quality up, not down.
That was the first version of what Implai is now. Since then I’ve kept pushing the same question further: which parts of running a digital project can AI actually own, and which still need a human checking its work?
Today, that question runs through everything from research and competitive analysis to design and site-build, content production, promotion — organic, AI-driven, social — and reporting and forecasting. We run 10+ AI tools across those stages on live projects, not as an experiment but as the default way work gets done. Over the last five years, my team and I have tested 50+ AI tools in production — not in a sandbox, on real budgets with real deadlines. Most didn’t earn a permanent place in the stack. The ones that did are the reason Implai exists: somebody has to do that filtering, and most “AI tool” content online is written by people who never shipped anything with the tool they’re reviewing.
Over the past year, we’ve also run AEO optimization on live projects — structuring content so it gets cited directly in AI answers, not just ranked in search. It worked well enough that we now apply the same methods by default on every new project: 30–40% of visitors and leads on those projects now arrive through AI-driven channels, a share that keeps growing.
That combination — testing tools obsessively, and watching how other people use them — led to the real insight behind Implai: most people don’t know how to use AI well, and it’s costing them. Not because the tools are bad, but because almost nobody has the time to learn which tool fits which job, or how to prompt it properly once they’ve picked one. So we did that work first. Implai exists so you don’t have to: we’ve already tested it — come see what fits what you’re trying to do.
Implai is that filter, made public. Every review, every workflow guide, every recommendation on this site comes from work we’ve actually done — not a lab benchmark, not an affiliate-driven top-10 list.
By the numbers
What we’re building next
Testing and reviewing tools is the first layer. The deeper pattern I keep running into: most of what a solo founder or a small team needs isn’t one more tool to log into — it’s the workflow already assembled and running. That’s the direction we’re building toward: AI-driven tooling that removes the manual assembly work entirely, so a one-person team can operate like a ten-person one.
Implai will always publish what we test before we build it. If we launch something ourselves, you’ll know exactly how it compares to the alternatives — because we’ll have reviewed those too.
How we test
Every review on this site follows the same standard: minimum 20 hours of hands-on use, real project context, transparent scoring. No AggregateRating theater, no pay-for-placement rankings.