Template, fitted or custom: which one you actually need.
The same code ships in all three cases and you own it in all three cases. What changes is how much work happens between the catalogue and your team, and most firms need less of it than they assume.
The three, briefly
| From | What happens first | |
|---|---|---|
| Template | $479 | Nothing. The app as it stands, source included. |
| Fitted | $2,400 | We shape it to how your team already works. |
| Custom build | Quoted | We build what the catalogue does not cover. |
How to tell which
Open the application and use it properly for twenty minutes, with your own situation in mind. Not a tour, actual use: enter a real record, run the process you run on a Tuesday, look for the field you would need. Every app in the catalogue is live with sample data for exactly this.
If nothing stops you, take the template. If you keep hitting the same two or three gaps, that is a fitted build and the gaps are the scope. If the process you are trying to run does not appear anywhere on the screen, it is a custom build and you will know within ten minutes.
The mistake in both directions
Overbuying is the common one. Firms describe themselves as unusual and commission shaping they turn out not to need, because most of what felt distinctive was a habit inherited from the last system. Twenty minutes in the real application settles that faster than any discovery workshop.
Underbuying happens too, and it is worse. Taking a template when you knew about three gaps means someone spends the next six months working around them in a spreadsheet, which is where the last system went wrong. If you found the gaps, pay to close them.
What does not change
The repository moves to your organisation in all three cases. Twelve months of updates are included in all three. There is no licence server, no seat count and no renewal in any of them. The differences are entirely about the work done before delivery, never about what you end up owning. That is spelled out in what you own.
If you are unsure, send us what you are replacing and the quote you were given for it. We will tell you which of the three fits, including when the answer is the cheapest one. Use request a quote.
Read something similar
OwnershipWhere self-hosting costs you, and where it does not.
Owning the code moves some costs onto you. Here is an honest account of which ones, what they come to, and when renting really is the better answer.
GuideMoving off a subscription without losing your history.
Export, mapping, parallel running and cutover: how a migration away from per-seat software actually runs, and which parts go wrong most often.
GuideWhat to check before you buy software you mean to own.
Seven questions that separate owning software from having a long licence to it, and the answers you should expect to get in writing before you pay.
Start here
Run the numbers on your own team.
Send the renewal quote you are looking at and we will price the owned version.
- No sign-up to open one
- One-time price, no seats
- Source code transferred on delivery