Working technology
The stack behind the work
Tools I implement and operate for clients, not logos collected for a wall. Curated deliberately: fewer tools, mastered properly, connected well.
AI systems and MCP
- Claude
- Anthropic API
- OpenAI API
- Model Context Protocol
- Custom AI applications
CRM
- HubSpot
- Salesforce
- Brevo
- Zoho
Automation
- n8n
- Zapier
- Make
- Airtable
Analytics
- GA4
- Google Tag Manager
- Looker Studio
- Microsoft Clarity
- Hotjar
Web development
- Astro
- React
- TypeScript
- Tailwind CSS
- WordPress
- Drupal
- Webflow
- Prestashop
Advertising
- Google Ads
- LinkedIn Ads
- Meta Ads
- TikTok Ads
Content and SEO
- Semrush
- Google Search Console
- Screaming Frog
Data and reporting
- Google Sheets
- Looker Studio
- BigQuery basics
Positions, not just tools
What I believe about the stack, so you know what you are hiring.
Static-first web architecture
Marketing sites should ship as fast static HTML with JavaScript only where interaction demands it. This site is the reference implementation: Astro, content collections, React islands, deployed as pure static files.
n8n as the automation backbone
Excellent for complex branching, reusable workflows and code steps. I use managed hosting when shared cPanel cannot operate a persistent application, and choose Zapier or Make when their managed experience is the better organisational fit.
HubSpot as the default CRM, not the only one
Best marketing-sales integration and adoption curve for most mid-sized teams. Salesforce for enterprise structures, Brevo and Zoho where budget leads the decision.
AI inside workflows, not instead of judgement
Claude and other models interpret, draft, classify and orchestrate approved MCP tools inside governed systems. Validation, permissions, logs and human approval remain where impact demands them.
Next move
Want this stack working for you?
Describe your current tools in the project brief and I will tell you what to keep, connect or replace.

