Software for private cemeteries and memorial parks: billing, CRM and a customer portal
Most cemetery management software was designed for city government: the focus is burials and public records. A private memorial park lives on contracts, installments and the relationship with the plot owner. We built a cemetery ERP with contracts, installments and billing for a memorial park, and we run its online payment portal.
What goes into cemetery software built for the private sector
Every module exists because it came up in the real operation of a memorial park. No screens nobody opens.
Contracts and installments
Contract records by owner, plan, plot and payment schedule. The installment comes from the contract, with its due date, adjustments and change history. This is the heart of management software for a private cemetery: if the contract is right, billing runs on its own.
Billing integrated with Mercado Pago
Pix (Brazil’s instant payment system) and boleto (a Brazilian bank payment slip) are generated from the installment, and payments are cleared automatically when the payment provider reports back. We are a Top 5 Mercado Pago · Platinum Partner, and that is the channel we use to reconcile. Fees are the platform’s own — check the costs on the official Mercado Pago page.
Owner portal
An area where the plot owner logs in, sees the contract and the open installments, and pays right there. At a memorial park we serve, the payment portal is built and run by us, with Pix and boleto reconciled.
CRM and service history
Who the owner is, who has spoken with them, what was agreed. A memorial park system without a relationship history asks the customer the same question three times. The CRM keeps all of it in one place, tied to the contract.
Outbound collections over WhatsApp
Broadcasts to the customer base using a Meta-approved template, a chatbot flow and an on-duty schedule for the agents, as SZ Chat (Fortics) partners. In one WhatsApp campaign to a memorial park’s customer base, payments per day went up 235%.
Migration from the old system
Spreadsheet, Access, legacy system: we read it, map it and load it. We have already migrated more than 500,000 records from an old system without losing a single one. The check is done by someone who did not run the load.
Website, payment page and measurement
The system does not live alone. At the memorial park where it was built, it runs alongside a company website and a WooCommerce payment page, with GTM, GA4 and Consent Mode v2 configured.
AI in your own environment
Models running on our server with Ollama: no cost per query and no data leaving the environment. That is how 82,000 service conversations from 15 years of history feed a client’s chatbot.
Results
No big bang: diagnosis, implementation, optimization
1. Diagnosis with data
We look at what exists today: spreadsheet, legacy system, billing method, overdue accounts, contract volume. That reading shapes what goes in first — and what can wait.
2. Implementation in weekly sprints
One-week deliveries, starting with the module that unlocks money: usually contracts and billing. Migration only after the destination has been checked. House rule: whoever built it does not verify it, whoever verified it does not approve it.
3. Weekly optimization
With the system live, the conversation turns to numbers: installments paid, installments overdue, cost per conversation in customer service. A monthly report cross-referencing paid traffic and customer service, and adjustments the following week.
Questions from people who run a memorial park
What is the difference between software for a municipal cemetery and software for a private memorial park?
The municipal one comes from a public duty: burial records, area control, serving citizens. The private one comes from revenue: contracts, installments, billing, overdue accounts and the relationship with the plot owner. That is why cemetery management software built for city government usually has no recurring billing and no customer portal — and that is exactly what a memorial park misses.
Does the system issue recurring charges and integrate with Mercado Pago?
Yes. The installment generated in the contract becomes a Pix or a boleto, and the payment confirmation clears it in the system. We use the Mercado Pago integration, where we are a Top 5 · Platinum Partner. On the cost of each payment method, the reference is the official Mercado Pago cost page — we do not pass on a price list of our own.
Does the plot owner get a portal to see the contract and the boleto?
Yes. The owner logs in, sees the contract and the open installments, and pays there. At a memorial park we serve, that portal is already live, with Pix and boleto reconciled. It also cuts down calls to the office asking for a second copy of a bill.
Can we migrate data from a spreadsheet or another system?
Yes, and it is part of the job. We have already migrated more than 500,000 records from an old system without losing a single one. The path is always the same: extract, map field by field, load into a test environment, check against the source and only then go live. The check is done by someone who did not run the load.
Does the system run in the cloud? What about LGPD (Brazil’s data protection law) for the owners’ data?
It runs on a cloud server, in an environment isolated from other clients — that is how the ERP we built for a memorial park is configured. On the websites and payment pages we use Consent Mode v2 and a setup aimed at LGPD. And when AI comes in, the models run on our own server with Ollama: the data does not leave the environment and does not become a paid query to a third party.
Tell the urutau about your challenge
It answers right away and, if needed, brings in one of us. No strings attached.