Monument Design Software
Monument design software for proofs families actually sign off.
The design proof sits in an email chain, the order in a spreadsheet, the deposit in a notebook, and the setting date on a paper calendar. We turn that into one system built around your monument orders, so a family's approved proof is the same record the shop cuts from and the crew sets from.
Bring one stuck workflow. Leave with a build, buy, repair, or wait recommendation.
Trusted by
The brief
Start with what is not working.
Good software decisions begin with the constraint, not a list of features or a preferred technology.
A family approves a design by text message, and that approval never reaches the shop floor.
The same order is tracked in a spreadsheet, an email chain, and someone's memory, and the copies drift.
A deposit is taken, a balance is owed, and nobody can say which orders are paid up without digging.
Plain answer
Monument design software built around your company gives families one secure place to review a design proof, request changes, and sign approval before any stone is cut. RaftLabs builds that system for monument companies whose proofs, orders, deposits, and installation dates live in separate tools. Scope and price are agreed in writing first.
What to remember
- Use this when a proof, an order, and a payment for the same family live in three places and stop matching.
- The first release should take one order from first quote to final setting, not collect disconnected features.
- No stone should be cut from anything other than the proof the family signed, with the date attached.
- Quote your own team's screens as their own scope: order tracking, proof approvals, and production boards are a second product, not a single admin-panel line.
- Hire freelancers for one small, well-defined task; use one accountable party when the work needs coordination across screens, rules, data, and system connections.
Fit
Custom software should earn its place in a business built on trust.
A feature request is not enough. The case is real when the same problem shows up in lost proofs, wrong inscriptions, unrecorded deposits, or setting dates nobody can confirm.
Proofs, orders, and payments for the same family live in email, spreadsheets, and paper, and the copies stop matching.
Your proofing, production, and cemetery steps are settled enough to write down, and they are how your company protects its name.
The company can name one person who owns the workflow and what 'done' looks like for the first release.
A maintained tool fits once someone sets it up properly and the whole office actually uses it.
The team wants software to settle pricing or production rules that are still changing every week.
The brief is a feature list with no single order path, user, or business result attached.
Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.
Start with the order, not the software.
A monument order looks simple from the counter. A family picks a stone, agrees a design, pays a deposit. Underneath, that one order is months of handoffs. The design goes back and forth until the family signs it. The granite has to be ordered and tracked. The inscription has to be letter-perfect. A foundation has to go in, the cemetery has its own rules and paperwork, and the setting crew needs a date everyone trusts.
Most monument companies run those handoffs in separate places. The proof lives in an email chain. The order status lives in a spreadsheet that drifts out of date. The deposit lives in a book by the till. The setting route gets planned on paper the night before. Nothing is wrong with any single step. The cost sits in the joins, where an approval given by text never reaches the shop floor, or the shop cuts from a proof version the family already changed.
A second product hides inside the first. Families see designs, proofs, and gentle progress updates. Your team lives in the other half: deposits and balances, granite and vendor tracking, cemetery lot and section details, production stages, and a record of who approved what and when. Quotes that squeeze all of that into an "admin panel" line item are where budgets break, so we quote your team's screens as their own job from the start.
Custom software for a monument company makes sense when one owned system can hold the whole order better than the patchwork does. The first release should take one order from first quote to final setting. It should not try to replace every tool you own at once.
We start where the order leaks trust.
The screen is only one part of the job. The real scope includes your proofing and approval rules, your production stages, each cemetery's requirements, the connections to your other systems, who can see and change what, and who runs it after release.
A proof portal families can actually use
Each family gets one secure link to their design proof. They view it at full size, ask for revisions in the same place, and sign their approval there. Every step is recorded with a date on the order, so the approved version is never a matter of opinion.
Inscriptions locked to the signed proof
Names, dates, and epitaph text are entered once, checked by the family on the proof, and locked at signing. The shop cuts from that locked version only. A change after signing starts a new proof version and a new approval, never a quiet edit to a file.
One order record from quote to setting
The quote converts to an order in one step, and the order carries its status, deposit and balance, granite and vendor details, and cemetery lot and section from that point on. Anyone can find any order and say where it stands without asking around.
A production board the shop can see
Orders move across a simple board: stone ordered, stone in, engraving, polishing, foundation, ready to set. A job stuck at one stage is visible the day it sticks, not the week the family calls to ask where their memorial is.
Deposits and balances on the order
The deposit is recorded when it is taken and every later payment lands on the same record, so the balance owed is never a separate calculation in a separate book. The family's paperwork and the office view always show the same number.
Which one is yours?
Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.
The long middle
Built for orders that take months, not days.
A monument order can sit open for months between deposit and setting. Granite ships late, cemeteries close sections in winter, families take time over wording. The system has to hold an order steady for exactly that long middle stretch.
Full history on every order
Quote changes, proof versions, payments, vendor notes, and phone call summaries all sit on the order in date order. When a family member who was not part of the first meeting asks what was agreed, the answer is in the record, not in one employee's memory.
Setting days planned with the cemetery in view
Foundation and setting work is scheduled against each cemetery's rules, paperwork, and the lot and section on the order. Crews see a route built from jobs that are genuinely ready to set, not a paper list rebuilt the night before.
Photo records from shop to cemetery
Photos of the finished stone and the completed setting attach to the order, next to the signed proof they were checked against. The family gets proof of the finished work, and the office gets a record that closes the order cleanly.
Proof
The fifth attempt became a product customers could keep using.
UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.
The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.
Read the UrShipper case studyWhich part of the order is costing you the most right now?
Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.
How it works
Close one expensive risk before opening the next.
Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.
- 01Understand
Trace one real monument order
Where do proofs, payments, and handoffs actually break?
Follow one order from the family's first visit to the setting. Include the proof that went back and forth by email, the deposit recorded in a book, the granite order chased by phone, and the approval that never reached the person cutting the stone.
Decision produced
A map of one order from first meeting to final setting, with the lost approvals, retyped details, and waiting points named, and the cost of each worth changing.Risk closed
Paying to automate the visible symptom while the expensive join between office, shop floor, and cemetery stays broken. - 02Shape
Choose the first useful release
What needs to exist together for one order to run end to end?
Choose the path from the way your orders run, not from a feature catalogue. Name the proof and approval steps, the production stages, who records payments, the cemetery details each order needs, and the result the first release must complete.
Decision produced
The first-release boundary: one complete path, the users it serves, the rules it encodes, and a clear definition of done.Risk closed
A small-looking feature list that quietly depends on proofing habits, cemetery rules, and three people's memory. - 03Prove
Review working software
Will it carry a real family's order without a gap?
Review the product against your own orders, not a tour of finished screens. Run one order through from quote to a signed proof to a setting date and check every step against how it should have gone. Record changed assumptions while there is still time to act on them.
Decision produced
Working checkpoints tested with your real order types, your stone and vendor range, your cemeteries, and the people who will use the system every day.Risk closed
Discovering the gaps after the shop depends on the board or a family has signed a proof the system recorded wrong. - 04Transfer
Release, measure, and hand over
Did the new system improve the original problem, and can another capable team operate it?
Move one order type or one location onto the system first. Compare lost proofs, payment questions, and handoff errors with the old way before adding the next workflow.
Decision produced
A controlled release, comparison with the starting point, operating notes, an account ownership map, and a recommendation for what should happen next.Risk closed
Measuring activity instead of results, or depending on the original vendor to keep the system running.
What it costs
Every project starts at $10K.
The first phase turns the costliest patched workflow into a scoped build with written acceptance criteria.
Starting investment
Starts at $10K
Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.
Not ready to talk? Start here.
Useful next paths: run the build-or-buy numbers, read what moves software cost, see the wider custom software picture, or inspect a comparable recovery.
Run the build-vs-buy calculator
Compare the cost and operating trade-offs before turning a workflow into a development brief.
Read the cost guide
See the scope factors that move price, timing, team shape, and long-term maintenance.
See custom software development
How we scope, price, and hand over owned software when standard tools stop fitting a business.
Inspect a product recovery
See what changed when UrShipper moved from four failed vendor attempts to a controlled migration.
Work with us
Bring one stuck workflow. Leave with a decision.
In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.
- One named workflow owner and one complete path for the first phase.
- Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
- Code, cloud, data, and provider access remain under your control.
- Post-launch warranty cover for defects in the agreed scope.
Frequently asked questions
Straight answers to what buyers ask before they scope. Still stuck? .
One record per order that every step reads from: the family's details and the cemetery lot and section, the quote, the design proof and its signed approval, the deposit and balance, the granite order and vendor, and the production and setting dates. When the family changes a date or a line of the inscription, the proof, the shop instructions, and the balance should move together instead of being retyped in three places.
The family gets one secure link to their proof. They view the design at full size, request revisions in the same place, and sign their approval there when it is right. Every view, revision request, and signature is recorded with a date on the order itself. That ends the pattern where a proof is approved in a text message or a buried email thread and the shop floor never sees it, or cuts from an earlier version.
The stone is cut from the signed proof, and only from the signed proof. Names, dates, and epitaph text are entered once on the order, checked by the family on the proof they approve, and locked when they sign. Any change after signing creates a new proof version that needs a fresh approval, so an old draft sitting in someone's inbox can never become the cutting file by accident.
Each order carries one status that moves with the work: quote sent, deposit received, proof approved, stone ordered, engraving done, foundation ready, set in the cemetery, balance paid. Anyone in the office can open the order and see where it stands, what is owed, and what happens next, instead of asking the one person who keeps the spreadsheet or remembers the conversation.
Payments sit on the order they belong to, not in a separate book. The deposit is recorded when it is taken, progress payments are added as they arrive, and the remaining balance is always visible on the order record and on the family's paperwork. When a family calls to ask what they still owe, the answer comes from the same record the shop and the setting crew are working from.
The order record carries the cemetery, the lot and section, and that cemetery's requirements and paperwork, so foundation and setting dates are planned against the rules that apply to that ground. The crew schedule shows which jobs are ready to set, which are waiting on a foundation or a cemetery approval, and which are blocked because the stone or the proof is not finished yet.
The first paid phase may cover a bounded audit, a proof of concept, or a small first release that takes one order from quote to setting. The final price depends on how deep the workflow goes, how many kinds of users it serves, what it needs to connect to, whether your order history needs moving over, and whether the shop floor and setting crews need phones or tablets. The agreed phase is priced in writing before it starts.
Timing depends on scope. A first release that covers one complete path, such as quote to proof approval to production to setting, is a smaller engagement than one that also adds online payments, photo tools for engraving, and connections to your accounting system. The schedule is set once that first path and what 'done' looks like are clear.
You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start: send a proof to a test family, sign it, and follow that order through to a setting date. Progress is reported in plain language: what changed, what is next, and what it costs. Our job is to make the work checkable; your job is to check it against your business.
You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.
![Monument design software for [proofs families actually sign off.]](/_next/image?url=https%3A%2F%2Fassets.raftlabs.com%2Fservice-assets%2Fmonument-company-management%2Ffeatured.png&w=3840&q=75)