What it really costs to run a custom CRM on Cloudflare
The custom CRM cost to run each month comes down to three lines: Cloudflare usage billed to your own account, a care plan for updates and backups, and the staff time it takes to keep the data clean. For Papaya Admin, the care plan is Admin Care from $149/month plus HST, and Cloudflare bills you directly at its own published rates, so nobody is marking up your hosting.
The build is a separate, one-time number (from $4,000). This post covers what happens after launch.
What are you actually paying for each month?
A custom admin system is not free to run just because nobody charges you per seat. Here is how the running cost breaks down for Papaya Admin:
- Cloudflare usage. The app, database and file storage run on a Cloudflare account in your business's name. Cloudflare invoices you directly, so the real amount shows up on your own statement.
- Admin Care, from $149/month. Security updates, backup checks, small fixes and keeping the system working as Cloudflare and Gmail change around it.
- Things you already pay for. Your domain and your Gmail or Google Workspace account. The CRM plugs into them; it does not replace them.
- New features. Anything beyond small fixes, such as a new report, a new workflow stage or a new integration, is scoped and quoted separately.
Why run it on Cloudflare at all?
Because it keeps ownership simple. The system sits on your account, so the data, the database and the code live with you rather than on a vendor's server.
That matters when you change providers, sell the business or just want a copy of everything. We covered that trade-off in own vs rent business software.
It also means no platform subscription stacked on top: one Cloudflare invoice, one care invoice.
What does Admin Care cover?
Software nobody maintains slowly breaks: browsers change, Gmail connections change, security fixes need applying.
Care covers the routine work:
- Applying updates and security fixes
- Checking that nightly backups are running and can be restored
- Keeping an eye on the login lockout and audit log
- Small edits, like a new field on a form or a renamed workflow stage
- Keeping enquiry capture from the website form, Gmail and text/Telegram working
New modules get a written quote first, so the monthly number stays predictable.
How does that compare with per-seat software?
It depends on headcount, and anyone who answers without asking how many people log in is guessing. Per-seat tools cost more as you hire; a custom system's running cost mostly does not move with headcount.
Here is a worked example with illustrative numbers. Say a per-seat CRM costs $60 per user per month and five people log in.
| Over 36 months, before HST | Per-seat tool (hypothetical, $60 x 5 users) | Papaya Admin (starting prices) |
|---|---|---|
| Setup | $0 | from $4,000 |
| Monthly | $300 x 36 = $10,800 | $149 x 36 = $5,364 |
| Total | $10,800 | from $9,364 plus Cloudflare usage |
With two users instead of five, the per-seat tool comes to $4,320 over the same period and wins on cost. With ten users it reaches $21,600. The crossover point for your own team is the number worth finding, not the headline price.
Off-the-shelf tools also include things a custom build may not, like phone apps and large integration libraries. If you need those, pay for them; we compared the options in HubSpot vs Jobber vs a custom CRM.
What does it cost in time?
Every CRM, custom or not, costs somebody a few minutes a day to keep accurate.
Papaya Admin cuts some of that by auto-creating enquiries from the website form, Gmail and texts, then flagging them for review instead of making staff retype them. Someone still has to review the flags, move work along the board from Lead to Completed, and close out invoices.
Anyone who has reconciled job costs after the fact knows the pattern: the system was fine, the data going in was late. Budget the time, not just the subscription.
How do you keep the running cost predictable?
A few habits keep the monthly number boring, which is what you want:
- Keep the Cloudflare account in the business's name, with billing emails going to someone who reads them
- Agree in writing what Care includes and what counts as a new feature
- Batch change requests into a short monthly list instead of one-offs every day
- Review the Cloudflare invoice quarterly so a jump in usage gets noticed early
- Export your data now and then, even though nightly backups exist
It is the same discipline as reviewing a WIP schedule: look at the numbers on a schedule and very little surprises you.
Where Papaya fits
Papaya Admin is a CRM and admin system that runs on your own Cloudflare account, from $4,000 one-time plus Admin Care from $149/month. If you want to check whether the numbers work for your team size, the CRM page lays out what is included, and the contact form gets you a fixed written quote.
Common questions
What does a custom CRM cost to run each month?
For Papaya Admin, the running cost is Admin Care from $149/month plus HST, plus whatever Cloudflare bills your own account for usage. New features are quoted separately.
Is Papaya Admin priced per user?
No. Staff logins are part of the system rather than a per-seat fee, though a larger scope can change the one-time quote.
Who owns the data in a custom CRM on Cloudflare?
With Papaya Admin, the system runs on a Cloudflare account in your business's name, so the data stays with you. Nightly backups are part of the setup.
CRM & Admin Systems
Your own CRM, quotes, invoices with HST and job costing in one branded system. From $4,000.