The business behind every number.
A contract is not a PDF. It is terms, amendments, obligations, a revenue schedule, invoices, credits, posted revenue and the evidence for each, kept together as one object with a history. Records is where every figure in Sebastian ends up when you ask where it came from.
Acme Corp · Enterprise subscription
Data Engineer · Platform team
A position is still the same position after the person leaves.
An approved seat is filled, vacated, reopened and refilled, and finance needs to see all of it as one thing. Records keeps the budget, the employee assignment, the departure, the requisition and the expected start on one object, so a vacancy is never mistaken for a saving.
- Awaiting backfill, on hold and eliminated are explicit states
- Vacancy duration, annualised exit run rate and projected compensation per seat
- Recruiting pipeline stage from the ATS, beside the financial effect
Contracts, vendors, positions, transactions. Each with its relationships.
Records is not a document browser or a table viewer. It is the set of business objects that financial figures are made of, each showing what it is connected to: the operational facts, the financial consequences and the accounting that followed.
- Every object links to the figures it drives and the work that touched it
- Source and freshness on every field; stale or unmapped data is shown, not hidden
- Reached from a figure, from search, or from Ask Sebastian, without losing your place
Persistent objects, not documents
What stops happening
Hunting through the CRM, the ERP and a shared drive
One contract record holds the signed terms, the schedule, the invoices and the posted revenue, with the page each figure came from.
Losing the seat when the person leaves
The approved position keeps its identity and its history through filling, departure, backfill and refill.
Trusting a figure without its evidence
Every term is cited to a clause, every amount to a record, and every record says when it was last refreshed.
Business records, before and after Sebastian
| Aspect | Status quo | Sebastian |
|---|---|---|
| A contract | A PDF in DocuSign, an opportunity in the CRM, invoices in the ERP, a schedule in a spreadsheet. | One object: terms, amendments, obligations, schedule, billing, credits, recognition and evidence. |
| A position | A row in the hiring tracker that is deleted or renamed when someone leaves. | A persistent seat with its budget, assignment, departure, requisition and expected refill. |
| A vendor | Purchase orders in procurement, invoices in AP, the forecast in a model. | Commitments, receipts, invoices, incurred expense and posted actuals, reconciled on the vendor. |
| Getting there | Open another application and search again. | Click the figure. The record opens beside it, and back returns you to where you were. |