AI Engine Ecosystem
The LinkedIn Content Engine, Person Research Engine, Company Research Engine, Post-Call Follow-Up Engine, Social Omni-Post Engine and AI Readiness Review Engine.
From fixing the website to fixing what it was connected to.
I joined through web development and kept finding deeper problems. Pages needed analytics. Analytics exposed manual work. Manual work became automations. Eventually the job changed from making the website better to making the operation itself behave better.
The internship became a full-time role in August 2025. I was still learning most of it on the job, including how a workflow can fail silently in production. More on that further down.
I build and maintain the automation layer behind Saizen's internal work and client systems: data engineering, AI orchestration, analytics and workflow architecture. The other half of the job is research, and enough business context to notice when a technically elegant answer is solving the wrong problem.
The result was not speed alone. Work became repeatable, visible, easier to scale, and able to keep producing after deployment.
Design and maintain connected systems across research, content, communication, lead generation, analytics and client delivery.
Build AI agents and multi-stage workflows that collect information, reason across it, produce structured outputs and trigger what happens next.
Find out what a problem really is, then test the answer honestly. For Bump4Life AI, that meant a 200-question benchmark against ChatGPT and Gemini, every answer graded by hand.
Connect campaign data, UTM structures, GA4, CRM records and conversion events into reporting people can actually use.
Credential protection, role-based access, audit logs, error notifications, retries and recovery, because production has opinions.
Work directly with leadership so the technical systems serve growth, marketing, operations and client outcomes, not just each other.
The LinkedIn Content Engine, Person Research Engine, Company Research Engine, Post-Call Follow-Up Engine, Social Omni-Post Engine and AI Readiness Review Engine.
Standard workflow templates that cut the time to deploy a new client engine from hours to minutes.
Automated PDF and HTML exports for AI-generated reports, KPI summaries, recommendations and client action plans.
Link hygiene standards, UTM governance and campaign tracking, so attribution stays accurate across platforms.
Content publishing, CRM enrichment, research, data processing and delivery, joined up with Python, JavaScript, APIs, GA4 and workflow orchestration.
The AI behind Bump4Life answers specific questions about years of maternal and child health data, by retrieving the right records and calculating against them instead of feeding a model the lot.
A fragmented property inventory turned into one structured dataset, ready for the website, Property Hive and Rightmove feed testing, without the data becoming the weak link.
Two browser demos that draw structured hardware-design data as schematics and boards you can inspect and edit, and flag any change that still needs a backend electrical check.
The company's second-generation platform, rebuilt as a Python and Flask application rather than another set of WordPress pages, with one application serving everything from structured content.
A senior engineer asked me that after one of my workflows failed silently in production. The logic was clean. The world was not. Pick something that goes wrong, then run it through the kind of demo that fools you and the version that belongs in production.
What the customer receives
Validation before confidence. Fallbacks before elegance. Human review before anything irreversible.
A simplified model with an invented customer, not a live system.
My first job was rebuilding the digital layer: development, design, SEO, analytics, security, and the automations around the website. What started as improving pages became the technical base for later engines, measurement systems and client-facing services. The site stopped being a static presence and became infrastructure.
Heatmaps and GA4 replaced arguments about design with evidence. We could see where attention died, where people stopped, and what actually changed after a rebuild.
Built and refined WordPress and Elementor pages from the ground up, with custom CSS and JavaScript wherever the native tools fell short of the standard.
Structured pages around clear journeys, deliberate spacing, stronger calls to action and mobile-first usability.
Metadata, schema, internal linking, image optimisation, semantic hierarchy and on-page SEO through RankMath.
GA4, heatmaps, scroll tracking, click tracking and event measurement, to replace design assumptions with evidence.
SSL, access control, firewall configuration, plugin governance, backups and overall platform resilience.
Reprogrammed the main website with a unified dark visual system, stronger responsiveness and a more deliberate brand experience.
Reusable frameworks for services, AI Readiness Reviews, strategic offers and future campaigns.
A structured news module that publishes live updates without compromising performance.
Forms connected to Slack and Google Sheets through n8n, so nobody had to carry a lead across by hand.
A site prepared for the dashboards, automation engines, attribution systems and campaigns that came after it.
The internship lasted two months. The web work did not stop with it.
A cleaner, more operational property platform across frontend, listings, enquiries, migration and launch, because a property website stops being “just design” very quickly.
The company site rebuilt and relaunched with analytics, authority pages, lead routing and performance work, then measured properly afterwards.
The complete client-side build for a technical recruitment brand, through repeated changes to positioning, hiring content, navigation and layouts.
Design affects data, data affects strategy, automation changes operations, and pretending those are separate disciplines usually creates worse systems.