Support recurring maintenance relationships and predictable follow-up.
Plumbing operators who want repeat-service revenue without letting renewals, scheduled maintenance, and customer promises drift into manual chaos.
Service Agreement is strategically strong for recurring revenue, but it is still beta until agreement events, renewals, and notifications are persisted.
Turns one-off service work into a retention loop, which is why it matters to the macro Plumbing platform.
Apex now has a signed-in Plumbing workspace shell so this wedge is no longer catalog-only.
Public beta page and workspace shell exist, but recurring agreement events and renewal notifications are not yet certified.
Apex should market this as a serious beta wedge, not as a fully certified plumbing operating system. The right claim is: public explanation, signed-in workspace shell, and a clear certification lane.
What still needs proof is the service-data contract itself: real job intake, dispatch writes, estimate persistence, and recurring-service state.
Use Service Agreement as a beta wedge, not a fake self-serve promise. Join the Plumbing beta if this workflow pain is real for you, or go back to the family map if you need the broader rollout context.
Pricing is the direct path. The product map is the context layer.
We use cookies to make APEX better. That's it. No tracking, no selling your data.