BASOLS Observ
BASOLS Observ follows every record through your revenue operations flows (a form submission that should become a contact, then a deal, then get an owner) and tells you when a check does not happen within its deadline. It can also act on the failure: create a task for the owner, fix a property or send an email.
Failures in RevOps are silent: a form that does not load, a workflow someone turned off, a deal left without an owner. Nobody notices until a sales rep complains. Observ turns those silent failures into findings you can see, act on and measure.
How it works
- You connect your tools as integrations: today, HubSpot portals and the Observ Ingest API, which receives events over HTTP from Make, n8n, Zapier or your own backend.
- You describe a business process as a flow: what starts it (its triggers), what must happen next and by when (its checks and goal).
- Every time a trigger fires, Observ opens a run and checks each check against the result it should produce, not against the mechanism that produces it.
- When a check is missing after its deadline, Observ records it: the run fails (or carries a warning) and a finding opens for the affected record.
- Optional actions react to the finding: a HubSpot task, a property update or an email. When the record is fixed, Observ resolves the finding on its own.
Principles
- Metadata, not data. Observ keeps IDs, timestamps, counts and hashes, never the content of your records. Personal data that a flow needs (such as an email) is read again from HubSpot when a check needs it, or stored encrypted only while the runs that use it are open, 30 days at most. It is never shown in the panel nor written to logs.
- Measure the result, not the mechanism. Observ does not ask whether a workflow ran; it checks that the deal exists and has an owner.
- Failures are absences. A check fails when its deadline passes without the expected result.
- Few false positives. It is better to detect less and always be right.
- Everything in the EU.
Where to go next
- Getting started: from an empty workspace to your first flow.
- Using the panel: a tour of every screen.
- Flow elements: every trigger and check, with its options.
- API reference: send custom events from any tool.