John G.
Email Deliverability Consultant | Critical Email & Revenue Assurance
Important emails going to spam, arriving late, or disappearing? I find where the flow is failing, help you establish what it’s costing the business, and fix and re-test the affected flow, not just the settings. A customer pays but never receives access. An attendee registers but misses the joining instructions. An appointment exists in your system, but the customer never gets the confirmation. These failures can lead to refunds, missed appointments, extra support work, and lost revenue. If your platform says “Delivered” but customers say otherwise, I investigate the gap. Passing SPF, DKIM, and DMARC is important, but it doesn’t answer every question. I trace the affected flow through the application and sending infrastructure, using controlled receiving tests where appropriate to establish what’s happening, including cases where Gmail and Outlook behave differently. My work has included detecting, fixing, and monitoring email failures across KumoMTA and Postfix sending infrastructure, Mumara campaigns, and the email workflows behind CRM, virtual-event, and appointment-scheduling applications. That experience covers both the software that should trigger a message and the infrastructure responsible for sending it. We start with the email that matters, what happens when it fails, and the evidence you already have. Before I begin, we agree what I’m investigating and what you’ll get back. If the investigation needs to go further, we discuss that first. You’ll get a plain-language explanation of what I tested, what the evidence shows, what’s still uncertain, and what I recommend next. I handle the agreed fixes, then re-test the affected flow and show you what happened in the receiving environments we tested. When your platform provider needs to make a change, I document the findings and the next step so the investigation doesn’t have to start over. Once the flow is healthy, I can establish a known-good baseline and set up recurring checks with alerts when those checks detect meaningful changes. Where another failure would have a real business cost, customer complaints don’t have to be your only warning system. Send me a short description of which email is failing, what happens when someone doesn’t receive it, and the platform involved. Include any sending status or error you already have. You don’t need to diagnose the cause or gather technical logs before getting in touch.
Earnings and projects
Last 6 months ÷ 6
Last 6 months: $2.8k
Billed in all: $252,534$253k
$2.8k in the last 6 months
Across 12 contracts
Earnings, last 30 days
Read once a week before Oct 9, 2026, daily since. Dotted: longer than usual between two readings. Hatched: over two weeks without one.
Skill rankings: Top 17% in Django
Ranked by MRR among everyone on Upwork with the skill.
- #36Business Applications Development131 freelancers · 🇰🇪 #1Top 27%🇰🇪#1 of 2
- #69OpenAPI272 freelancers · 🇰🇪 #1Top 25%🇰🇪#1 of 2
- #173Zoom Video Conferencing725 freelancers · 🇰🇪 #1Top 24%🇰🇪#1 of 9
- #185Twilio API710 freelancers · 🇰🇪 #1Top 26%🇰🇪#1 of 6
- #753CRM Development2,819 freelancers · 🇰🇪 #6Top 27%🇰🇪#6 of 20
- #815Process Improvement2,840 freelancers · 🇰🇪 #16Top 29%🇰🇪#16 of 41
- #967Business Process Automation3,508 freelancers · 🇰🇪 #7Top 28%🇰🇪#7 of 24
- #984Django5,931 freelancers · 🇰🇪 #8Top 17%🇰🇪#8 of 87