Njin OS: how we build and run your sales system
Njin OS is the platform behind every Njin build. It is how we deliver, not software you buy. Here is what runs in your CRM, what you keep, how approvals work and how your data is handled.
What Njin OS is
Njin OS is the set of playbooks, agents, sequences, connectors and dashboards Njin uses to build and run an AI sales system inside a client’s CRM. The client’s CRM stays the system of record. Njin OS reads from it and writes to it through access the client approves. It runs the nurture and the agents and reports the results on a dashboard the client owns.
What runs where
Most of the system lives in your CRM. The agents run on Njin OS and write everything back.
| Part | Where it runs | What you see |
|---|---|---|
| Sales playbooks and scripts | Written as documents, then loaded as templates and rules in your CRM | The scripts your team uses and the rules the agents follow |
| Email and SMS nurture | Your CRM’s own sequences and workflows | Every send logged on the contact |
| AI SDR and sales chatbots | Njin OS agents, connected to your CRM and calendar | Each conversation saved to the contact, each booking in your calendar |
| Voice agents | Njin OS, calling from a number you own | Call summaries and outcomes on the contact |
| Lead scoring and routing | Rules in your CRM, written from your playbook | Owner, score and source on every lead |
| Dashboards and commission tracking | A dashboard that reads your CRM | Pipeline, conversion and commission, live |
| Connectors | HubSpot, GoHighLevel, Pipedrive or Salesforce APIs, with scopes you approve | An access list you can revoke at any time |
What you keep
Everything that matters stays yours.
- Your CRM and every record in it
- The playbooks and scripts, as documents you own
- The sequences, workflows and rules, because they live in your CRM
- The phone numbers, domains and ad accounts
- The dashboard and its history
If we part ways, the sequences and rules in your CRM keep running. The Njin OS agents stop, and we hand over what they were doing and how.
Human approvals
Nothing sensitive goes out on its own.
- New scripts and sequences are approved by you before they go live
- An agent hands over to a person when a lead asks for one, raises a complaint or goes outside the script
- Pricing and contract terms always come from your team. Proposals go out from templates you approved
- Changes to who the system contacts, and how often, are agreed in the monthly review
How your data is handled
Plain answers to the questions every client asks before we connect to their CRM.
Access through your CRM’s own permissions
Data stays in your CRM
Named Njin staff only
Your client list is not used to train anything
Australian privacy law applies
How a build runs
Four stages. You approve each one before the next starts.
-
Diagnose
The Revenue Leak Diagnostic or a 30-minute call. We map where enquiries are being lost and pick the first fix.
-
Design
The playbook and the scripts first. You approve every line before anything is built.
-
Build
Inside your CRM on Njin OS, tested with your team on real enquiries before it goes live.
-
Run
We run it with you. Every month we review the dashboard and change what is not working.
The platform in detail
AI and machine learning
Integrations and API
Analytics and reporting
Security and compliance
Njin OS questions, answered
Is Njin OS software I can buy?
Do we need to change CRM?
What happens if we stop working with Njin?
Who can see our data?
Can the AI send something without us seeing it?
See it running on your CRM
Know you need this? Book a call. Not sure yet? Find your revenue leaks first.