Records
Track what you actually deliver, not just what you sold
Define the kinds of thing your business handles for each customer — the details to capture, the paperwork each needs, and the rules it must satisfy — then see at a glance what's missing and what's about to run out.
What it solves
A CRM tells you a deal closed. It rarely tells you what you then owe the customer. Firms that deliver something ongoing — a licence, an approval, an audit, a renewal, a service contract — end up tracking the actual work in spreadsheets, because the CRM has no shape for it. So the sale is in one system, the obligation is in another, and the thing that lapses is the one nobody was looking at.
How we're different
Nothing is pre-loaded. There is no built-in catalogue of record types, because we don't know your business — you define the types, the fields, the paperwork each one needs and the rules it must satisfy, in your own words. Two different types can use the same field name without clashing. Rules can span fields ("if this is set, that becomes necessary") rather than just validating one at a time. And because a record hangs off the same client and account as the deal and the invoice, what you delivered and what you billed are the same record, not two systems to reconcile.
Inside Records
Record types you define
The paperwork each one needs
Rules that span fields
Records
Rules that span fields
Expiry in view before it bites
Records
Expiry in view before it bites
Attached to the customer, not beside them
Records
Attached to the customer, not beside them
Records
Rules that span fields
Records
Expiry in view before it bites
Records
Attached to the customer, not beside them
Works with the rest of Finocket
Part of CRM & pipeline. See how every module connects.
Questions
What kinds of thing can I track with this?
Whatever your business actually handles for a customer on an ongoing basis — a licence, an approval, a certification, a renewal, a service contract, a periodic audit. Finocket ships no examples on purpose: you name the types, so the words on screen are your team's own.
Is this a document management system?
No. It records which documents a type requires and whether each one is supplied, so nothing is missed. It is a checklist with rules attached, not a filing cabinet.
Can two record types use the same field name?
Yes. Fields are scoped to their record type, so two types can both have a "registration number" without one overwriting the other's meaning.
What happens if I set a rule up wrongly?
The record says so plainly. A rule that can't be read is reported as a fault rather than skipped — a record must never look complete because a broken rule was quietly ignored.
Learn how it works
Records — track anything you handle per customer
Set up the kinds of thing your business looks after for each customer — the details to capture, the paperwork each needs and the rules it has to satisfy — and every one you raise shows exactly what it still needs and what is about to run out.
Accounts — companies, not just contacts
Contacts and deals from the same company are grouped under one account automatically (from their business email domain), with a single view of that company's people, deals and history — and a roster that says who to reach for what.
Custom fields on your records
Add your own fields — 15 types across invoices, expenses, items, payments, clients and deals. Mark them required, validate with a pattern, and choose whether they show on the invoice PDF or the portal. They ride a stable api name into the report builder, the API and CSV exports.
Ready to ditch the spreadsheet?
Free for solo users. No credit card. Your books stay yours.