Every enquiry gets an owner.Every lost deal carries a reason.
Run accounts, contacts, leads, activities and opportunities as one connected record, so anyone picking up a customer can see who matters and what has already happened.
The complete CRM core is in every package, with unlimited named users and contacts for one customer UEN. You step up a package because your business has more than one of something, not because KeelSG holds a feature back.
5 things, and what each one is for.
Accounts and contact relationships
Companies, people, contact points, custom attributes and relationship history stay linked, so one customer has one story rather than four half-versions of it.
Anyone picking up an account can see who matters and what has happened.
Accounts · contacts · relationship links · custom fields
Lead capture and assignment
Enquiries typed in from a phone call, imported from a spreadsheet of event names, or posted in by your website form all land in the same list, with the same required fields and a record of when and where they came from. You set the assignment rules. When a lead matches no rule it does not vanish, it goes to an unassigned queue a manager can see.
Nothing falls between two rules and disappears.
Manual · import · web form · owner · unassigned queue
Scoring and qualification
Lead scoring is a deterministic calculation from criteria you configure, not an opinion. The score recalculates when the data changes and you can open it and read the contribution of each individual factor.
A disputed score becomes a two minute conversation about a weighting, not an argument about trusting the software.
Configured criteria · factor breakdown · recalculation · audit trail
Configurable sales pipelines
Your stages, not a template's stages. A qualified lead converts into an opportunity carrying an owner, a stage, a value, a currency, a probability, an expected close date and its original source, without creating a second copy of the contact or the company.
You can see what is in play and roughly when it is expected to land.
Stages · opportunities · value · expected close · won/lost
Activities and next actions
Calls, meetings, notes and tasks record against the customer with due dates and an explicit owner for the follow-up, and closing a deal requires a close date and a reason from a list written in your language.
After one quarter, why deals die stops being one person's opinion and becomes a number with deals attached to it.
Calls · meetings · notes · tasks · due dates · won/loss reasons
Four steps, in this order, every time.
- 01
Capture
An enquiry lands with its source and creation date.
- 02
Own
A rule assigns it, or the unassigned queue holds it.
- 03
Progress
The opportunity moves through your configured stages.
- 04
Learn
The won or loss reason you chose feeds the reports.
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.
