A system of record is the one place where a given fact, such as a customer, a loan file or an invoice, is officially true. Every other tool copies from it. A firm needs a dedicated one once that fact lives in three or more places and people reconcile them by hand. At our rates, custom builds start at $15,000.
What is a system of record, and when does a firm need one?
What a system of record actually is
A system of record is the authoritative source for one kind of data. If two tools disagree about a client’s billing address or a deal’s status, the system of record wins, and the other tool gets corrected. It is defined per entity, not per company. A firm can have HubSpot as the system of record for contacts and QuickBooks Online as the system of record for invoices at the same time.
| Entity | Typical system of record | Tools that usually hold copies |
|---|---|---|
| Contacts and companies | HubSpot or Salesforce | Email, Gmail, spreadsheets, billing |
| Invoices and payments | QuickBooks Online, Stripe | CRM deal records, finance spreadsheets |
| Case, loan or application files | Often nothing: a spreadsheet plus a shared drive | Inbox, CRM notes, team chat |
The third row is the one that causes trouble. Most firms have a clear system of record for contacts and money, and none for the thing they actually sell: the file, the case, the order, the engagement. That gap is where a dedicated system of record usually goes.
Signs your firm needs one
No single threshold applies. Two or more of these patterns usually means the reconciling already costs more than a build would.
- The same record is typed into three or more tools, and someone spends hours each week making them match.
- Nobody can answer "what is the status of this file" without asking a person.
- A spreadsheet has become the real database: tabs per month, color codes, one person who knows the formulas.
- You have to show later why a decision was made (an approval, a funding, a refund) and the evidence is spread across email.
- Reports to leadership are rebuilt by hand every month.
For scale, a team of five that each spend 3 hours a week reconciling is spending about 65 hours a month. At a loaded cost of $50 an hour, that is roughly $3,250 a month, or $39,000 a year, before counting the errors.
Your options, compared
A system of record does not have to be custom software. The cost figures for the custom row are ours; the others are general market ranges.
| Option | Upfront cost | Monthly cost | Who maintains it | What breaks first |
|---|---|---|---|---|
| Spreadsheet or Airtable as the record | Near zero | $0–$50 per user | Whoever built it | Concurrent edits, no audit trail, one person’s knowledge |
| Customised CRM (HubSpot, Salesforce) | $5,000–$30,000 in setup, market range | CRM seats, often the largest line | Admin or consultant | Custom objects that fight the CRM’s sales model |
| Vertical SaaS for your industry | Low to moderate | Per-seat subscription | The vendor | The 20% of your process it does not cover |
| Custom system of record (Smplfy) | From $15,000; integrations $1,500–$6,000 each | Hosting, plus engineering as needed at $85/hour | Your team or ours, with a runbook | Upstream field changes in connected tools, if not monitored |
If a vertical SaaS covers most of your process, buy it and integrate around the gaps. Build custom only when your workflow is what makes the firm different, or no product models it well.
How one works: a worked example
Take a services firm whose engagements start in HubSpot, get billed in QuickBooks Online and paid through Stripe. The engagement itself, with its documents, stages and owner, lives in a spreadsheet. A custom system of record makes the engagement the authoritative object and keeps the other tools in sync.
- A HubSpot deal moves to closed-won. A webhook creates an engagement record in the system of record, keyed on the HubSpot deal ID so a repeated webhook cannot create a duplicate.
- The system creates or matches a QuickBooks Online customer and a draft invoice, and stores both IDs on the engagement.
- When Stripe sends a
payment_intent.succeededevent, the system marks the invoice paid, updates the engagement stage and writes the status back to the HubSpot deal. - Every change is logged with who made it and which system it came from. Leadership reports read from this one database, not from three exports.
- Any call that fails goes to a retry queue. After the last retry it raises an alert with the record ID, so nothing fails silently.
In this design, HubSpot stays the system of record for contacts and QuickBooks for the ledger. The new system owns only the engagement and the links between them. Deciding who owns each field is most of the design work, and it happens before any code.
A build like this is the core pipeline, roles, the audit log and two or three integrations. At our rates it starts at $15,000, which is about 175 engineering hours. It rises with the number of integrations, the volume of documents and how much history has to be migrated. For Hoopes Vision, most of the work was moving years of spreadsheet data into one database.
Failure modes to plan for
- Two systems claiming the same field. If both HubSpot and the new system can edit a billing address, they will overwrite each other. Assign one owner per field.
- Duplicate records from retried webhooks or the same client entered twice. Match on external IDs and normalised email or tax ID, not names.
- Data arriving before its parent record, such as a Stripe payment for an invoice not yet synced. Queue it and retry instead of dropping it.
- Expired OAuth tokens and API rate limits on the connected tools, which cause partial syncs that look fine until month-end.
- Fields renamed or deleted upstream by a well-meaning admin. Monitor for schema changes and alert on them.
The decision rule
Do not build anything yet if fewer than five people touch the process, nothing about it is regulated or audited, and one spreadsheet still works. Tighten the spreadsheet and revisit in six months.
Use a no-code tool such as Zapier or Make if the only problem is copying records between two systems that already own their data cleanly. Customise your CRM or buy a vertical SaaS if your process is close to standard.
Build a custom system of record when the core object of your business has no real home, three or more systems have to agree about it, and you need an audit trail you can show a lender, auditor or client. Start with one workflow end to end, on a data model designed for the rest.
Frequently asked questions
What is the difference between a system of record and a source of truth?
They are often used interchangeably. Strictly, a system of record is the application that owns and stores a type of data, while a source of truth is the agreed authoritative value, which may be assembled from several systems of record. In practice, both mean the place you trust when tools disagree.
Can HubSpot or Salesforce be our system of record?
Yes, for contacts, companies and deals they usually already are. They work less well as the system of record for document-heavy, multi-step files such as applications or cases, where custom objects start fighting the CRM’s sales model. Many firms keep the CRM for relationships and add a separate system for the work itself.
How much does a custom system of record cost?
At Smplfy, custom systems of record start at $15,000, and each additional integration typically adds $1,500 to $6,000. The price rises with the number of connected systems, document volume, audit requirements and how much historical data must be migrated. Hourly work is billed at $85 an hour.
How long does it take to build a system of record?
A first release covering one workflow end to end with two or three integrations usually takes several weeks to a few months, depending mostly on integrations and data migration. Cleaning historical spreadsheet data is often the slowest part. We give a dated estimate in the written scope.
Is a spreadsheet ever a valid system of record?
Yes, for small teams with simple, unregulated processes and one person editing at a time. It stops working when several people edit at once, when you need a history of changes, or when the data has to stay in sync with other tools. At that point the hours spent reconciling usually exceed the cost of a proper database.
Related answers
Want to know whether you need a system of record?
Send us a short description and we’ll reply with a free written scope, or we can do a free 20-minute call. It helps to have ready which tools hold your data today, roughly how many records you manage, and which steps your team still does by hand. Start a conversation.