Do I really own it?
Yes, in the plainest sense. The code sits in a private repository in your GitHub account. The server runs in your cloud account on your card. The database is yours. We keep access so we can support and update it for as long as you are a member, and because it is your account, you could revoke that access any day you like. There is no license to revoke on our side, because it is not licensed. It is yours. If you ever stop your membership, the system stays yours and keeps running; we simply step back, and any changes after that become paid work instead of part of your monthly.
What happens if PoolFoundry disappears?
Your system keeps running without us. We build on standard, boring, widely known technology on purpose, so any competent developer can pick it up cold. Compare that with a platform shutting down or getting acquired, where your whole operation has 90 days to find a new home. But the good news is, this is the one software headache you do not have to lie awake over: it is already yours, already running, already on your server. Us disappearing would be our problem, not yours.
It is billing day and something breaks. What happens?
You reach our team directly, the people who actually built your system, not a ticket queue in another time zone. The money-critical things, your invoicing, payments, and payroll, get treated as same-day, because a billing day does not wait. The exact response promise is written into your agreement, in plain numbers, before you ever go live.
It is a small team behind this. What if someone is not available?
Fair, and it is the fear we take most seriously. PoolFoundry is run by a small, tight team, not one person, and your system runs on standard, boring, widely known technology with a written runbook for every build, so it is never locked inside one head. The continuity plan, who steps in and how, is spelled out in your agreement in writing. Staying lean is also how we keep your price down: because the software is built to be simple and standard, we do not need a big, expensive coding team, and that saving lands in your monthly instead of someone's venture-backed payroll. You are betting your billing on software you own and can hand to any competent developer, not on one person's good week.
What about my current pool routing software?
Migration is part of the build: clients, locations, visit history, gate codes, equipment photos, the works. We run your old platform and your new system side by side until you say switch, and the cutover happens on a quiet day of your choosing.
How long does the build take?
A working version lands on your phone within days of the walkthrough. Most companies are fully cut over in three to four weeks, and the pace is set by your schedule, not ours. The good news: the heavy lifting of moving your data over and mapping it in is handled for you, not dumped on you to upload and match up yourself the way other platforms make you.
What does the monthly actually cover?
Two things, and the second is the one that pays you back. First, the upkeep: managed hosting, monitoring, nightly backups, security patches, and real support from people who know your exact build, not a call center reading a script. That alone is what keeps the software your whole company runs on from going dark on a billing day.
Second, the part rented software can never give you: your system keeps getting better, and you choose how much of it to take. Every bug another operator turns up gets fixed for you. Every sharp idea anyone in the Foundry brings gets forged into the shared core, and you get the option to add it to your own build at no extra charge. No new feature lands in your system unless you want it, so you pick the improvements that fit how you run and leave the rest. Either way, you are paying into software that is worth more this year than it was last year, built and proven by a whole community of people who run pools for a living.
It also keeps you tied to the team that built it: a direct line instead of a ticket queue, and your problems near the front of the line. Ask an old-school software company for a change and you know exactly how it goes: maybe it ships next year, maybe in two, maybe never, while you wait behind ten thousand other companies. Here, if it can be built, it gets built. And when you commission something custom, it is shaped by people who already know your system cold, so an hour of their time goes further than a week of onboarding anywhere else.
And yes, you own it, so you can walk any time. Stop your membership and you keep a working system on your own server; nothing gets switched off. But the day you leave is the day the improvements stop and the upkeep becomes yours alone. Staying is simply the cheapest way to own something that keeps getting smarter while you sleep. Most owners run that math once and never think about leaving again.
Can it cut my card-processing fees?
Yes, by design. Your invoices encourage Zelle and ACH first (free or near-free, bank to bank) and take cards only as the fallback. Move even part of your client base off cards and the processor's cut stops eating your margin. Your invoicing, your payment rules.
iPhone and Android?
Both. Your techs get a real native app built for one-handed use at the side of a pool with wet hands and a hose in the other. Fast camera, offline-friendly, no website pretending to be an app.
My company does things differently. Like, really differently.
Good. That is exactly why we started this. We wanted software that ran the way our business actually runs, not our business bent to fit something generic that was built for ten thousand companies at once. So we built it around our own goals first, and now we do the same for you. Your chemistry philosophy, your service tiers, your billing quirks, the weird thing you do that your clients love: that all goes in. The walkthrough exists to find exactly those things.