Dispatch, scheduling, inventory, quoting, invoicing, and billing in one CRM workflow.
The CRM side of X-Ploy is built for service businesses that need operational control, tighter handoffs, and cleaner revenue flow from request through payment.
“Keeping two codebases separate while selling one brand is the right launch move when you care more about shipping than forcing an artificial merge.”
Implementation principle
Platform strategy · X-Ploy
“The value pitch lands when buyers can see dispatch, quoting, invoicing, and inventory as one operational loop instead of a list of disconnected modules.”
Launch narrative
Operations positioning · X-Ploy CRM
FAQ
CRM questions
Can customers sign themselves up immediately at launch?
Not in the first launch phase. The public site captures qualified requests, then your team handles account setup, hosted checkout links, and provisioning using the existing platform admin surfaces.
Will the CRM stay on the existing infrastructure?
Yes. The current plan keeps the CRM on apps.x-ploy.com with the existing FastAPI backend and Cloudflare deployment model, while the public site becomes a separate marketing surface.
Why not use WordPress for this site right now?
A WordPress launch would add PHP, MySQL, plugin maintenance, and a second hosting model that does not align with the current Cloudflare Pages setup. The Astro plus Git-backed CMS path ships faster and keeps operations lighter.
Is X-Ploy launching its own internal email hosting with the site?
No. The launch keeps mailbox hosting out of scope and uses Postmark for transactional platform email. Forwarding aliases can be added separately without running a full mail server.
Are forums or customer websites part of this launch?
No. Forums, community features, and hosted customer websites are phase-two items so the initial launch stays focused on the marketing site and the two product surfaces.