Skip to content

Selected work

Projects Judged by What Changed for the Business

Every case study starts with the problem and ends with a measured result: hours saved, response time cut, pages that load faster, orders that arrive. Where a project fell short of its goal, I say that too.

Client names appear only where the client has agreed to it.

MEASURED BEFORE / AFTER[Metric 1][X] → [Y][Metric 2][X] → [Y][Metric 3][X] → [Y]grey = before · orange = after
IllustrationHow results are reported
8+Years
200+Projects delivered
15+Industries
[N]Case studies with measured results

Case studies

Problem, Build, Measured Result

[Intro line — add once the four case studies and their numbers are confirmed. Remove any card below that has no real result yet.]

Placeholder · featured case studyAI & Automation

[Case study title: outcome first, e.g. what stopped being manual]

[RESULT: X, unit, timeframe]

[X%][Metric, before to after]
[X hrs][Time saved per week]
[X wks][Time to launch]
Client
[Industry] business, [size]
Problem
[The situation before: manual work, slow site, missing platform]
Built
[What was delivered, in one line]
Stack
[Technologies used]
Read the Case Study →
Placeholder · case studyDigital Transformation

[Case study title: systems connected, process replaced]

[RESULT: X, unit, timeframe]

Client
[Industry] business, [size]
Problem
[The situation before: manual work, slow site, missing platform]
Stack
[Technologies used]
Read the Case Study →
Placeholder · case studyFull Stack Engineering

[Case study title: product or platform built]

[RESULT: X, unit, timeframe]

Client
[Industry] business, [size]
Problem
[The situation before: manual work, slow site, missing platform]
Stack
[Technologies used]
Read the Case Study →
Placeholder · case studyWeb & Ecommerce

[Case study title: store or site outcome]

[RESULT: X, unit, timeframe]

Client
[Industry] business, [size]
Problem
[The situation before: manual work, slow site, missing platform]
Stack
[Technologies used]
Read the Case Study →
Placeholder · case studyWordPress

[Case study title: site rescued or rebuilt]

[RESULT: X, unit, timeframe]

Client
[Industry] business, [size]
Problem
[The situation before: manual work, slow site, missing platform]
Stack
[Technologies used]
Read the Case Study →

How to read them

Every Case Study Follows the Same Four Parts

So you can compare projects like for like, and see the parts that didn't go smoothly as well as the ones that did.

The problem

What the business was dealing with, in its own terms: the hours, the errors, the lost sales. Measured before I start.

What I built

The system or site delivered, the tools chosen and why. Named technologies, not buzzwords.

The result, in numbers

The same measure as the baseline, after launch, with the timeframe. Never an estimate presented as a result.

What didn't go to plan

The delay, the wrong assumption, the feature we dropped. Honest about tradeoffs is part of the brand.

Beyond the case studies

More From 200+ Projects

A wider sample across industries. Full references and demos on request, on a call.

IndustryWhat was builtServiceResult
[Industry][One-line description of the project]AI & Automation[RESULT]
[Industry][One-line description of the project]Digital Transformation[RESULT]
[Industry][One-line description of the project]Full Stack Engineering[RESULT]
[Industry][One-line description of the project]Web & Ecommerce[RESULT]
[Industry][One-line description of the project]WordPress[RESULT]
[Industry][One-line description of the project]AI & Automation[RESULT]
[Industry][One-line description of the project]Digital Transformation[RESULT]
[Industry][One-line description of the project]Full Stack Engineering[RESULT]

Placeholder  [Replace with 6–8 real rows. Client names optional.]

Clients

What Clients Say

[Add 5–8 real testimonials with name, role and company. Show three here.]

Placeholder · client testimonial
"[Quote 1 — specific about the result, the process or working together]"
[Full Name] — [Role], [Company]
Placeholder · client testimonial
"[Quote 2 — specific about the result, the process or working together]"
[Full Name] — [Role], [Company]
Placeholder · client testimonial
"[Quote 3 — specific about the result, the process or working together]"
[Full Name] — [Role], [Company]

Stack

Technologies Used Across These Projects

I choose the tool that fits the problem. Each case study names what was used on that project.

AreaTools
AI modelsOpenAI (GPT), Anthropic (Claude), open-source models where data must stay in-house
AutomationCustom API integrations, n8n, Make, Zapier where appropriate
FrontendReact, Next.js, TypeScript, Tailwind
BackendLaravel, Node.js, Python, PHP
DatabasesPostgreSQL, MySQL, Redis
Web & EcommerceWordPress, WooCommerce, Shopify

FAQ

Questions About the Work

Can I see live examples of your work?

Yes, wherever the client allows it. Each case study links to the live site or product. Where a system sits behind a login or under confidentiality, I describe the problem, the build and the measured result instead, and can walk you through a demo on a call.

Why are some client names left out?

Some clients need confidentiality, especially where the work touches internal operations or customer data. In those cases the case study names the industry and company size, reports real results and leaves the name out. Where a client has agreed to be a reference, I'll arrange a conversation.

How do you measure results?

Every project starts with a baseline: hours spent, response time, page speed, conversion rate or error count, whichever fits the problem. The case study reports the same measure before and after, with the timeframe. If a result can't be measured honestly, I say so instead of estimating.

Can you guarantee the same results for me?

No. Results depend on your starting point, your data and how your team adopts the change, so I don't promise numbers up front. I can show what happened in similar situations, agree a measurable target for your project, and tell you early if the target looks unrealistic.

Do you have experience in my industry?

I've delivered 200+ projects across 15+ industries over 8+ years. The process problem underneath usually matters more than the sector, and most problems repeat across industries. Tell me yours on a call and I'll point to the closest projects.

Have a problem like one of these? Tell me about it and I'll reply within 24 hours.

Send a Message →