Team - Rubber Duck Technology

Why Rubber Duck

Built like rubber duck debugging

Rubber duck debugging is an old coder’s trick: explain your code to a rubber duck, line by line, until the flaw reveals itself. That is exactly how we operate — understand a client’s entire environment, A to Z, then solve for the inefficiencies hiding inside it. Rubber Duck Technology was built so businesses can learn what’s actually out there, and choose with confidence — no sales team pushing you one way or another.

The whole environment, A to Z

Solve for the inefficiencies

Learn without sales pressure

Rubber Ducks

William Burnett

Owner | Information Technology Engineer

An IT engineer by trade, William runs every engagement the way rubber duck debugging works: walk the client’s entire environment A to Z, explain it back in plain language, and let the inefficiencies surface. He built Rubber Duck — and personally vetted the 475+ supplier network behind it — so businesses can see every serious option side by side, with an advisor on their side of the table instead of a quota.

Mason Herbel

Co-Founder | Lead Engineer

Mason is the engineer’s engineer. His background is in infrastructure operations and system deployments — most recently at StudyFetch, an AI education platform serving millions of students — where he has led the upkeep of the systems the business runs on. Clients get that same proactive approach: deep technical expertise, a bias for continuous improvement, and innovative answers to problems others have written off.