Data, Automation & Technical Product.
I turn operational problems into reliable data, automation, and AI workflows.
I connect business needs with data pipelines, SQL and Python workflows, dashboards, automation, product definition and delivery — from reporting and validation through to shipped applications.
Open to Business Intelligence, Data Analytics, Product Operations, Technical Product and AI/Data roles.
From problem to working systems.
I identify the operational problem, define the business outcome, design the data or automation workflow, work through implementation and validate whether the result solves the original need.
Professional evidence of data & automation delivery.
Work at the intersection of business intelligence, operational data, workflow automation and cross-functional delivery with Product, Data Science and Engineering.
Operational data for better sales, inventory and distribution decisions.
Standardised customer data, improved recurring reporting and helped turn operational questions into clearer KPIs and replenishment decisions.
Selected data, automation & product work.
Projects across business intelligence, data systems, workflow automation, AI products and technical delivery — from SQL pipelines and dashboards through to shipped applications.
MeetBook → Nimo
Nimo is a private event contact book that helps people capture who they meet, remember the context behind each connection and follow up after the event.
Originally developed as MeetBook, the product is now evolving into Nimo ahead of its October 2026 launch.
Bidly
A local-services marketplace where customers post a job, nearby providers bid, and the customer chooses using price, ratings, reviews and availability.
ContractGuard AI
A working prototype for teams that need to turn uploaded contracts into structured deadlines, risk signals and reviewable information.

ORB Market Research Pipeline
A reproducible Python research system for five-minute QQQ market data — covering ingestion, rule-based strategy logic, validation, signal exploration, risk-aware analysis and backtesting foundations.

ACPT
An assurance product for enterprise teams that need workflow monitoring, investigation and audit evidence around AI-agent outcomes.

- Python
- SQL
- Power BI
- TypeScript
- React
- React Native
- Expo
- Supabase
- PostgreSQL
- REST APIs
- n8n
- OpenAI
- Claude
- Codex
- Cursor
- GitHub
- Jupyter
- Data Validation
- Workflow Automation
How I work with AI.
I use AI coding tools for speed, but the system around them matters more: context before execution, bounded tasks, acceptance criteria, testing, guardrails and human judgement over architecture and product decisions.
From discovery through delivery.
Capabilities demonstrated through BI workflow improvement, data pipelines, automation, founder-led product work, client delivery and technical prototypes.
Turn data into decisions
SQL, reporting, Power BI dashboards, KPI definition and operational analytics.
Understand the problem
Data analysis, validation, exploratory research, workflow mapping and requirement clarification.
Remove manual work
Python pipelines, API ingestion, workflow automation, data-quality checks and monitoring.
Shape the right scope
Product requirements, prioritisation, cross-functional coordination, testing and iteration.
Design informed workflows
AI workflow design, data models, integrations and outcome validation.
Move work to completion
Implementation coordination, documentation, launch validation and continuous improvement.
Posts, lessons & experiments.
Public thinking from LinkedIn — read it here, then open the thread if you want the rest.
LinkedIn profile ↗Validate before you finish building.
I went into the hackathon thinking the hard part was building fast. I left realizing that when software can be built in days, you can also build the wrong thing in days.
Open on LinkedIn ↗I went into SummerUP thinking the hard part was building fast. I left realizing that building fast might actually be the dangerous part. Because when software can be built in days, you can also build the wrong thing in days.
One lesson stuck: validate before you finish building. Talk to potential customers before the product is done. Ask questions. Get on calls. Understand how they deal with the problem today and whether what you’re building actually matters to them.
The idea I was working on was ACPT — governance and control for AI agents. Being surrounded by people from different industries changed the question from “Can I build this?” to “Should I build this?”
Two days ago I attended the Engineering AI Together Unconference at the Merantix AI Campus in Berlin — speaking with AI engineers, sharing VoiceOps, and getting honest feedback.
The conversations moved from benchmarking, multi-agent workflows and security into product decisions. One person asked why VoiceOps should be desktop-first when most people already use voice assistants on their phones. A fair question — and it made me think more carefully about the environment the product is actually meant to be used in.
Last Friday I joined Build Fridays in Berlin, hosted by AI BEAVERS, to advance the product direction and technical foundation for VoiceOps.
I used the session for focused product discovery with engineers — workflows, pain points, workarounds, privacy concerns, desktop vs mobile. The result was not a feature list. It was a clearer product direction, a validated MVP focus, and an architecture aligned with the highest-value user needs.
Let’s work on
something difficult.
If you’re hiring for business intelligence, data analytics, automation, technical product or AI/data roles, I’d be happy to talk.
