Work with me
Everything below is organised around business outcomes, not a technology menu. No business needs all of it, and part of the job is telling you which parts you don't need. The right answer is the smallest system that solves the problem.
I take responsibility for the whole lifecycle: architecture, implementation, and ongoing operation. One engineer, accountable end to end, delivering through my consultancy, Pragmatik.
Data platforms and analytics
For businesses whose numbers are scattered across systems and spreadsheets, and nobody fully trusts any of them. The outcome is one reliable picture of the business, built on data you collect and control.
- Behavioural tracking and data collection
- Data warehouses and pipelines
- Business intelligence and reporting
- Customer and revenue analytics
- Marketing attribution and measurement
Private AI and business automation
For businesses that want AI working on their own knowledge and data, with a clear-eyed decision about what runs privately and what goes to an external API. The outcome is AI that answers from your business, not the internet.
- Private AI assistants
- Internal knowledge search and RAG systems
- LLM integrations
- AI-enabled business workflows
- Secure access to business data through AI interfaces
Infrastructure and technology ownership
For businesses that want to know where their systems run, who holds the credentials, and what it would take to move. The outcome is infrastructure you understand and control, with the boring parts (monitoring, backups, access) handled properly.
- Open-source infrastructure
- Self-hosted business applications
- Private cloud environments
- Identity, access and security
- Monitoring, backups and ongoing operations
Machine learning and predictive systems
For businesses sitting on history they are not using: who bought, who left, what sold. The outcome is predictions wired into daily operations, not a model in a notebook.
- Customer propensity and lead scoring
- Revenue and lifetime value prediction
- Forecasting
- Customer segmentation
- Predictive models integrated into operational systems
How an engagement starts
The intro call
Thirty minutes about your business and where its data and systems actually stand. No deck, no obligation. You leave with at least one thing worth acting on, whether we work together or not.
The map
I trace what you have: the systems, the data, the dependencies, and what each one costs you in money and control. You get a plain-English picture of what is solid, what is risky, and what to do first.
The build
I design the architecture, build the system, and run it in production. Your team is trained along the way, the documentation is in plain English, and ongoing operation is mine for as long as you want it to be.
Not sure which of these you need?
That's normal, and it's what the intro call is for. Bring the problem; we'll work out the smallest system that solves it.