Sound familiar?
What funeral homes tell us before a project starts.
- Families are asked for the same details on the phone, in person and on three forms.
- Arrangement paperwork is retyped from one document into another.
- Services, clergy, florists and cemetery bookings are chased by phone and email.
- Obituary text and service notices go to several places by hand.
- Invoices and payments for services wait until things quiet down.
What we build
Each one is a working piece you can open and check when it's done.
Family intake form
One gentle, well-worded form for the details you need, saved to one record so staff do not ask twice.
Web apps and MVPs n8n, Make and Zapier automationPaperwork from the record
Contracts, statements and permits filled from the case record into your templates, ready for a person to review and sign.
Python scripts and utilities Google Sheets and Apps Script automationService calendar and vendors
Each service on a calendar with the vendors it needs, and a note sent to clergy, florists and the cemetery when something is set or changes.
Booking and scheduling systems n8n, Make and Zapier automationNotices and obituaries
Approved text sent to your website, the newspaper contact and a family email in one step, not four.
API integrations and data sync n8n, Make and Zapier automationStatements and payments
Statements made from the arrangement, payment links where a family wants them, and entries made in the accounting tool.
Stripe integration and billing QuickBooks, Xero and HubSpot integrationsAftercare follow-up
Thoughtful check-in notes scheduled for staff to send, such as an anniversary card list, so no family is forgotten.
n8n, Make and Zapier automationFuneral homes software we work with: Square.
And the general tools around it: QuickBooks, Google Sheets, Google Calendar, Gmail, Microsoft Outlook, DocuSign, Zapier.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Intake that fills the contract
Example: a family-owned home has the family complete one intake form, and the details are filled into the arrangement contract and statement for a director to check.
Form, document templates, PDFExample project
One note to every vendor
Example: when a service time is set, the florist, cemetery and clergy contacts each get a short message with the details, and a change notice if the time moves.
Calendar, email, Google SheetsExample project
Aftercare list
Example: a home wants a list each month of families due for a card or call, with the staff member to reach out.
Case sheet, calendar remindersQuestions people ask first
How do you handle sensitive family information?
Records stay in the accounts you own, with access limited to the people you name. We ask what you already use and keep to that, and we don't put anything somewhere you haven't approved.
Who owns what you build?
You do. It is built in your own accounts, and you get notes on how it works so your team can change it without us.
Will it feel cold to families?
No. We keep the wording yours, and automation stays behind the scenes: paperwork, reminders and vendor notes, never the conversation with the family.
How do we start?
Tell us which tools you use and the one thing that wastes the most time each week. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com