Skip to content
YAPS

About

Built by a pool guy, for pool guys.

I run Delaware Pool Service. I built YAPS because the tools I tried were either built for landscapers, priced for franchises, or designed by people who'd never opened a pool.

Who I am. Mike Magyar — owner of Delaware Pool Service in Wilmington, DE. I'm a pool service operator first. I write the software because nobody else built the one I needed.

Why YAPS. The shop was a stack of clipboards and a spreadsheet only I could read. So I tried the obvious tools. ServiceTitan was priced and built for shops with an office manager and an IT person. Jobber missed half of what a pool route actually does. Skimmer covered the chem log but left the office work — calls, invoicing, comms — sitting on me. None of them solved the real problem: a one-person shop can't afford to hire an office coordinator, so the software has to be the coordinator.

So I built it. Early 2026 I started writing YAPS. v1.0.0 went into production at DPS in Q1 — scheduling, routing, invoicing, customer SMS, field ops, chem logs, the whole back office, deterministic and auditable. Every feature traces back to a specific job where an existing tool didn't fit.

Where it is now. DPS runs the full season on YAPS. A second shop (MBC) came online in May 2026. v2.0.0 — the multi-tenant SaaS version — is in scoping now, and the waitlist is open for the first cohort of outside operators.

The thesis. YAPS isn't another FSM app. YAPS replaces a headcount — the office coordinator a solo operator or 2-truck shop can't afford to hire. That's not a features conversation. It's a CFO conversation, and it's the reason this exists.

Want to talk?

Drop a note and we'll figure out whether YAPS is the right fit for your shop.