Independent at the core.Connected on your terms.
KeelSG keeps its own customer records and works with nothing else connected to it. That is deliberate. A CRM that only works when it is plugged into four other products is not independent, it is a hostage arrangement.
We do not publish a list of systems we connect to, and we do not show logos. Which systems, in which direction, carrying which fields, is scoped with you during implementation and built as part of your package. No connector is represented as live before it is proven end to end.
6 things, and what each one is for.
Take all of it out, any time
Filter a set of records on screen, choose CSV, XLSX, XML or TSV, and take it. All four contain the same permitted records and the same fields, each with a documented schema, so the file opens in whatever your accountant, your analyst or your next system expects.
Leaving is a menu option, not a negotiation.
CSV · XLSX · XML · TSV · documented schema
Every export leaves a record
Who asked for it, which filters were applied, which fields were included, how many rows, which format, a checksum, when it was created and when it expires. The audit record does not contain the personal data itself. Cell content beginning with an equals, plus, minus or at sign is neutralised so a spreadsheet does not execute it, while the value stays readable.
If somebody walks out with a customer list, that is a question with an answer.
Requester · filters · row count · checksum · expiry · formula neutralisation
Inbound capture contracts
A versioned REST API and signed webhooks accept validated lead and activity events, with schema validation and idempotency so a retried delivery does not create a second customer.
A new source can send data in without writing directly into CRM tables.
REST API · signed webhook · schema validation · idempotency
Outbound operating handoffs
Approved, scoped events queue for delivery to another system, with retries and receipts. Failed deliveries land in a ledger somebody can see and act on rather than disappearing silently.
A won deal can reach the next system without that system owning the CRM record.
Outbox · retries · receipts · failure ledger
Honest connector states
A connection is described by where it actually is: manifest only, contract verified, sandbox verified, or live. Nothing is called live before credentials, sandbox verification and an end to end receipt exist. That is a written product rule, which is why there is no logo wall on this page.
You are never told a connection is ready on the strength of somebody having drawn it on a diagram.
Manifest · contract verified · sandbox verified · live
Imports and data migration
Your existing data comes in. We validate and migrate the agreed sources during implementation, one, two or three of them depending on the package, so you begin with usable history instead of an empty system.
Data scattered across a spreadsheet and an old CRM is the work, not an obstacle.
1, 2 or 3 migration sources by package
Four steps, in this order, every time.
- 01
Contract
Name the system, the fields and the direction.
- 02
Validate
Check identity, schema and entitlement at the edge.
- 03
Operate
Queue the work with retries and visible receipts.
- 04
Prove
Nothing is called live without an end to end receipt.
The next three questions.
Thirty minutes, and you leave with three answers.
Which package fits, what we would migrate and how, and what the fixed fee would be. Written down, so you can put it in front of a partner or a board.