Fixing the Web: A Former Smartphone Repairman's Approach

Before I wrote code, I fixed phones.

Cracked screens. Water damage. Failed batteries. Broken buttons.

People would bring in their devices, panicking: "I can't live without my phone."

And I'd fix them. One screw at a time. One component at a time.

That experience shaped how I build software today.

The Repair Shop Philosophy

1. Find the Root Cause

When someone brings in a phone that won't charge, you could:

• Replace the battery (expensive, might not work)
• Clean the port (cheap, often works)
• Replace the port (moderate, if cleaning doesn't work)

You start with the simplest explanation.

In web development, I see agencies throwing complex solutions at simple problems:

• "Email notifications are slow" → Set up a Zapier workflow → Configure SMTP → Add monitoring → Pay $50/month

Or you could ask: why are we using email at all?

2. Make It Actually Work

A phone isn't fixed when it turns on. It's fixed when:

• It charges reliably
• It holds charge for a normal day
• The customer can use it without thinking about it

Software is the same. "It works" isn't enough. It has to work every time, without the user needing to babysit it.

ZeroContact delivers in 2 seconds, every time. Not sometimes. Not usually. Every single submission.

3. Don't Charge for the Fix They Don't Need

I've seen shops charge $100 to "replace a battery" when the problem was a $5 charging cable.

In software:

• Don't pay for enterprise features you'll never use
• Don't pay for "tasks" when you need unlimited notifications
• Don't set up infrastructure when someone else maintains it

ZeroContact is $15/month base. Not $69/month for "team features" you don't need.

From Phones to Forms

I started a web agency after the repair shop. Built WordPress sites. Added contact forms.

And I kept seeing the same problem: clients weren't getting their leads on time.

Email delays. Spam filters. SMTP configuration nightmares.

It reminded me of a cracked screen: the underlying system is broken, and everyone is just living with it.

The Repairman's Question

When a phone came in broken, I'd ask: "What's the simplest thing that could fix this?"

For form notifications, I asked the same question:

What's the simplest path from "form submitted" to "phone buzzes"?

The answer:

Form → Webhook → Push notification

No email server. No SMTP. No spam filter. Just a direct connection.

Why wasn't anyone doing this?

The Missing Tool

I looked for existing solutions:

• Zapier: 15-minute polling delay, task-based pricing
• Make.com: Same polling problem
• Pushover: Technical setup, no agency workflow
• PagerDuty: Enterprise pricing, incident-focused

Nothing was built for the simple use case: agency needs client to get form notifications instantly.

So I built it.

How the Repair Mindset Shaped ZeroContact

Simple Setup

Remember: find the simplest fix.

ZeroContact setup:

• Create form in dashboard
• Get webhook URL
• Paste in form builder
• Done

No Zapier flows. No SMTP configuration. No training needed.

It Just Works

"Fixed" means fixed forever.

ZeroContact delivery:

• 2-second notification, every time
• 5 channels simultaneously
• Automatic retry on failure
• No maintenance needed

Right-Sized Pricing

Don't charge for what they don't need.

ZeroContact pricing:

• $15/month base (1 form included)
• $5/additional form
• Unlimited notifications
• No task counting, no overage fees

The Unbroken Promise

When someone left my repair shop, their phone worked. Not "mostly worked" or "worked until the next problem." Worked.

When someone sets up ZeroContact, their notifications work. Not "get delivered eventually" or "unless it goes to spam." Instantly. Reliably. Forever.

That's the standard from the repair shop, applied to software.

What's Still Broken

The web is full of things that don't work as well as they should:

• Email notifications: slow and unreliable
• Form builders: complex setup for simple needs
• Analytics: data without insights
• Website performance: fast on localhost, slow in production

I can't fix all of it. But I can fix the parts I understand.

Form notifications are where I started. There's more to come.

The Repairman's Promise

If you've ever had something fixed by someone who actually cared about fixing it—not just charging you—you know the difference.

That's how I build. Not feature-complete. Not enterprise-grade. Just working.

Your forms should send notifications instantly. If they don't, that's a bug. And bugs should be fixed.

---

Ready for notifications that just work? Get started with ZeroContact →