Tried and tested.
Now automated.

Bespoke senior AI consulting for teams who know they need to do something with AI, but aren’t yet sure what. Maybe you’ve run a few pilots that quietly went nowhere, or you’re staring at the budget line and don’t yet know where it should go. The field is still young, every business I’ve worked with has needed something a bit different, and most of the value is in the figuring-out part. So we work that out together, and then we build.

I spent 20 years in search and digital strategy (I founded Builtvisible, later acquired), and for the past few years I’ve been building AI infrastructure full-time. I’ve published 16 open-source MCP servers on npm, I run two paying SaaS products entirely on the architecture I’d build for you, and I use every tool I recommend to clients on my own projects before I suggest it to anyone. If it doesn’t work in practice, I don’t sell it.

Book a conversation
20 years in search & digital
16 open-source MCP servers published
2 running SaaS products I ship & maintain
36+ published technical guides

The 95% problem

MIT’s August 2025 study of enterprise AI found that 95% of GenAI pilots fail to deliver measurable financial impact. Only 5% cross what the researchers call the “GenAI Divide” into real production.

McKinsey’s 2025 State of AI reaches the same conclusion from a different angle. About 65% of organisations use generative AI regularly, but only a third have scaled it. The ones that succeed share one thing: they redesigned the workflow first, then applied the AI. The ones that fail bolt a model onto a process that wasn’t ready for it.

That redesign work is the harder, less glamorous part, and it’s where most engagements either stall or skip the step entirely. A strategy deck, a workshop, or a platform subscription can each be useful in the right place. None of them, on their own, do the specific reverse-engineering that moves the number for your business. That’s the work I like to focus on.

How I think about a business

Every engagement starts with me spending real time inside your operation. Not a kickoff call and a discovery survey. I watch how your team really spends their days, the spreadsheets they keep open, the systems they copy data between, the Friday morning report someone builds by hand because the tooling never quite worked, the Slack channels where decisions get made before they hit the meeting.

The procedures that are tried-and-tested at the human level are the ones that automate reliably. If your marketing team has been producing briefs the same way for two years and it works, that’s a procedure I can replicate with AI in the loop, faster, more consistent, and off your team’s plate. If something is still being figured out, no amount of AI will make it work until the humans figure it out first.

Once I understand the shape of the business, I build the systems. Document processing pipelines, research and monitoring workflows, content production systems, custom MCP servers that connect AI to your internal data, reporting automations that replace the Friday morning spreadsheet. I build with tools I use every day.

The goal is that six months after I leave, your team is running AI-enabled procedures that feel like a natural extension of how you’ve always worked, just faster, more consistent, and without the manual grunt that used to eat half a person’s week.

Think of it as AI R&D

Every business is different under the hood. The way your sales team triages leads, the spreadsheet your ops manager has been quietly maintaining for three years, the report someone rebuilds every Monday because the system never quite did it properly. None of that is in a textbook, and none of it is going to be solved by buying a SaaS subscription and hoping for the best.

So a lot of what I do is research and development, in the proper sense. We try things, we measure what happened, we throw out what didn’t work, and we keep what did. The bits that survive get built into something your team can run without me. That’s the bit nobody else seems to want to do, and it’s the bit that moves the number.

If you’ve ever felt like the AI conversation in your business has been all talk and not much shipped, this is probably why. The talking is easy. The R&D is what gets you to the 5%.

The facets of the work

Not sure which of these you need? Most engagements start with a workflow audit, because it’s the fastest way for both of us to figure out what’s worth building. If you’d rather just have a chat first, that works too. Book 45 minutes and we’ll talk it through.

Workflow Audit

Two weeks inside your operation, mapping what your team does day to day (which is often a bit different from what they think they do), scoring each task for automation potential, and handing over a ranked list of what to build first, what to skip for now, and what’s probably not worth the effort yet.

Discovery

AI Automation Build

Multi-step workflows that connect your tools, process your real data, and keep running after I’ve gone. Document processing, research pipelines, content production, data transformation, reporting. Deployed on your infrastructure with full documentation so your team maintains it without me.

Implementation

Custom MCP Servers

Your CRM, your ERP, your internal databases, the weird legacy system nobody wants to touch but everyone depends on. Secure structured AI access to each of them, without your data leaving your infrastructure. 16 production MCP servers already published on npm under @houtini, and I build yours the same way.

System Design

Team Training

Hands-on workshops where your team builds real workflows on their own laptops using your actual data. By the end everyone has Claude Desktop configured, MCP servers installed, and at least one working automation they built themselves. Minimal slides. People remember what they’ve built, not what they’ve been shown.

Training

Fractional AI Lead

Ongoing strategic oversight where I attend your planning meetings, guide tool selection, oversee implementation, and gradually upskill your team so they don’t need me anymore. Usually offered post-engagement, or as a lighter-weight alternative when you need expertise but not yet a full build.

Advisory

AI Content & AEO Strategy

20 years of search expertise applied to AI-native content operations. AEO (answer-engine optimisation), AI-enhanced content pipelines, voice analysis, brand consistency at scale. I built the pipeline that produces houtini.com itself. If you need the content side done properly, this is where the search history is most directly useful.

Strategy

These are facets of an engagement, not a product menu. Every piece of work is scoped to your business, your team, your systems. A 50-person marketing agency is a different engagement from a 20-person e-commerce operation.

How we’d work together

AI in business is still embryonic. Most of the agencies and teams I talk to don’t need a product bolted on. They need someone sitting with them, watching how the work really flows, and teaching the fundamentals so the team can keep going after I’ve left.

Think of it as a forward deployed engineer rather than a consultant with a deck. I spend time inside your business, learn the specific shape of it, and we build what fits. No two engagements have looked the same, and I’d be suspicious of anyone telling you otherwise. Past work has included full content production pipelines, bespoke document processing systems, custom AI access to internal databases via MCP servers, AI-driven competitive monitoring, private on-premises AI for regulated data, and senior AI advisory for leadership teams figuring out the strategy layer.

Engagements usually run a few months rather than a few weeks. Long enough to move something real, short enough that you’re not locked in. If what you need is off-the-shelf or urgent-next-week, I’ll happily point you somewhere better. I’d rather have a friendly conversation and send you elsewhere than take work that isn’t a fit.

Pricing is scoped to the work once we both understand it. Talk to me first. Numbers without context aren’t useful to either of us.

Questions I get asked

Why bespoke engagements instead of fixed-price packages?

Because your business isn’t a fixed-price package. A 50-person marketing agency is a completely different piece of work from a 20-person e-commerce operation or a 200-person professional services firm. Bespoke engagement pricing means I build what helps you, after spending time with you to understand how your business works. We discuss, plan, evaluate, scope, cost, execute, support, develop and train.

Do we need technical people on our team?

No. The whole point of what I build is that non-technical people can run it. I design the systems, I train your team on how to operate them, and I make sure the documentation is good enough that someone who wasn’t in the training session can still figure it out. If something goes wrong after the engagement, you call me.

Can you work with our existing tools?

Most of the time, yes. The honest answer is it comes down to three things: does the platform have an API, is there a test environment I can build against safely, and are the docs good enough that I’m not reverse-engineering from HTTP traces. Platforms I’ve built production integrations with include Brevo, WordPress, Shopify, Jira, Firecrawl, Supadata, Amazon product feeds, Google Search Console, Google Knowledge Graph, yubhub, and various recruitment platform APIs. I’ve also connected to spreadsheets that probably should have been databases years ago, which is more common than anyone likes to admit.

What about data privacy and security?

This is something I care about independently of client work. I run local LLMs on my own multi-GPU Threadripper workstation with six NVIDIA cards, precisely because some data shouldn’t leave the building. If your work involves sensitive information, I can build with local models like Ollama and LM Studio that keep everything on your infrastructure, with nothing going to a cloud API at all. I wrote a complete guide to setting up LM Studio that explains how this works in practice.

How is this different from just buying Copilot or ChatGPT Enterprise?

Those are general-purpose tools, useful for general-purpose things like drafting emails and summarising documents. But they don’t know your processes, your data structures, or your terminology, and they can’t connect to your internal systems without custom integration work. What I build is specific to how your team works in practice. The difference is a bit like buying Microsoft Excel versus hiring someone to build you a financial model that fits your business.

What are you working on?

Plenty. The tools page is the clearest picture of what’s live right now. yubhub.co is my AI-agent-ready jobs board, currently tracking 13,700+ live jobs across categories and employers, with MCP, WebMCP, and free XML feeds available with attribution. Content Marketing Ideas is a working SaaS I ship and maintain on the same architecture I’d build for you. I’ve also published 16 open-source MCP servers on npm as @houtini that other developers install in production, and I publish 36+ technical guides on houtini.com explaining how each system works. If you want to verify anything I claim, you can, because I’ve shown the working.

Do you do one-off projects?

Occasionally. If what you need really is a one-off, a specific workflow, a specific MCP server, a specific automation, we can talk about it. But the work is usually more valuable as part of a broader engagement, because the hardest part of AI implementation isn’t any one system, it’s understanding how the systems fit together with how the business really runs.

What’s your tech stack?

TypeScript and Python for most things, n8n for workflow orchestration, Cloudflare Workers and D1 for edge deployment, SQLite for local data, Crawlee for web scraping, Claude and Gemini APIs for reasoning tasks, and local LLMs via LM Studio and Ollama for privacy-sensitive work. The honest answer is that the stack depends on what the engagement needs. I pick tools based on what I’ve already proven works in production, not whatever’s trending on Hacker News this week.

Let’s have a conversation

45 minutes. Tell me what’s slow, what’s frustrating, or what you’re trying to figure out. I’ll be honest about whether I’m the right person to help or whether you’d be better served somewhere else. No pitch deck, no follow-up sequence.

Book a conversation

Receive the latest articles in your inbox

Join the Houtini Newsletter

Practical AI tools, local LLM updates, and MCP workflows straight to your inbox.