USE CASE · CUSTOM CRM USERS
Builtfor your
CRM

Your team built your CRM. We built the AI that can read it without breaking it.

We've connected to homebrew PHP CRMs, Rails systems with 80+ tables, Django admin builds, .NET applications older than the people maintaining them, and no-code stacks held together by Apps Script. If your team built it, we can read it - without you teaching us your schema.

7+
Database systems supported
3 wks
Average time to live production
0
Schema changes required
9.2s
Average query response
kolossus · what we connect toALL READY
Detected · Your CRM stack
PostgreSQL, MySQL, MariaDBSQL
SQL Server, OracleSQL
MongoDB, SQLiteNOSQL
REST APIs (any auth)API
GraphQL APIsAPI
DB read + API writeHYBRID
6 / 6 paths supportedREADY · 9.2s avg
Why this page exists

Other AI platforms tell you to migrate to a supported CRM first. We don't.

Microsoft Copilot, Salesforce Einstein, Snowflake Cortex - all give you the same answer. "Yours isn't on our list. Migrate first." Your custom CRM works. Your team uses it daily. Your sales process runs on it. Throwing it away is not a serious suggestion.

OTHER AI PLATFORMS
What they ask of you
  • ✗"Migrate to a supported CRM first"
  • ✗Custom integration project quoted in months and crores
  • ✗Your team has to document everything for them
Outcome · status quo, slower
VS
KOLOSSUS
What we ask of you
  • ✓Connect to your CRM as-is, any database or API
  • ✓Schema discovered automatically, not documented manually
  • ✓3 weeks to live production
Outcome · live in 21 days
What you'll actually use

Three patterns that work across any custom CRM.
Whatever shape yours is.

The names below are illustrative. The patterns are real - they apply across any custom CRM, whether yours is built on PostgreSQL, MongoDB, MySQL, REST APIs, or something more exotic.

01 · COMPLEX QUERIES
Your sales lead needs specific records that match a complex condition - fast, without exporting to Excel.
7.8s
CRM · Stagnant manufacturing leads5 of 23 · ranked
23stagnant leads
LeadDeal valueNo contact
Lakshmi Industries₹85L98d
Premier Manufacturing₹62L76d
Ace Steel Works₹54L68d
Deccan Engineering₹47L61d
19 more leads₹5.94Cr
23leads
₹8.2Crat stake
7.8sto surface
What happens next
04 STEPS
  • 01Updates each lead's status to "Needs Follow-up" in your CRM
  • 02Tags by territory and rep for assignment
  • 03Drafts personalized outreach per lead
  • 04Logs query in your audit trail
2 hrs · CRM exports + Excel→7.8 SECONDS
02 · BULK UPDATES
A senior rep just left. You need to reassign their stagnant leads across your team - without spending a day in the CRM.
4.6s
CRM · Mehul's open leads · territory map142 reassigned · 6 reps
142leads reassigned
West India · Suresh
47
South India · Priya
38
North India · Rohit
29
East India · Anika
18
Unassigned (escalation)
10
4 territories · 6 reps · 1 escalation queueAUDIT-LOGGED
142reassigned
10escalations
4.6sto assign
What happens next
03 STEPS
  • 01Updates the owner field on every reassigned lead
  • 02Notifies receiving reps with handover context
  • 03Flags 10 unmapped leads for your review
Full day · manual CRM work→4.6s + 5 MIN
03 · CROSS-SYSTEM
Your CFO wants to know which customers are at churn risk - and that answer lives across your CRM, Tally, and support tickets.
11.4s
CRM × Tally × Support · joined8 accounts · ₹3.2Cr ARR
8high-risk accounts
CRMTALLYSUPPORT
Critical risk33 of 3 signals firing
High risk52 of 3 signals firing
Total ARR at risk₹3.2Cr
Avg days to renewal87 DAYS
3critical
5high risk
11.4sto join 3 systems
What happens next
03 STEPS
  • 01Creates save plays in your CRM for each at-risk account
  • 02Notifies account owners with full context on WhatsApp
  • 03Generates a weekly risk dashboard for your CFO
Cross-system analysis · not done→11.4s · AUTO MONDAYS
How we read your CRM

"But you've never seen our system." Here's how we connect anyway.

Three connection methods, picked based on what your CRM actually exposes. We don't need access to your application code, we don't need a developer on your team to teach us your schema, and we never copy your data anywhere.

PostgreSQLNATIVE
MySQL · MariaDBNATIVE
SQL Server · OracleNATIVE
MongoDB · SQLiteNATIVE
DATABASE ADAPTER
Direct DB connection
Direct connectionto your CRM's database. Schema is auto-discovered; no documentation required from your team.
RESTGraphQLOAuthAPI KeysJWTSessionCustom Hdrs
API ADAPTER
REST or GraphQL
Whatever your CRM exposes.Used when database direct-access isn't possible (security policy, hosted CRM, etc).
RReads · direct DBFAST
WWrites · via your APISAFE
HYBRID MODE
Read from DB, write through API
Reads are fast.Writes go through your CRM's API - preserving validations, triggers, audit logs, and business rules.
The custom CRM specifics

Things that matter when your CRM was built by your team.

The realities of running an internal CRM at Indian mid-market scale. We've already met every one of them.

Schema auto-discovery
We map your tables, columns, relationships automatically by reading metadata. Your team doesn't write a documentation pack. Schema drift is re-discovered on a regular cadence - new columns appear, deleted columns disappear, renamed tables get re-mapped.
Tables ✓Columns ✓FK Relations ✓Indexes ✓Schema Drift ✓
No code changes
We don't touch your CRM application code. Zero modifications to the system your team built.
Read-replica friendly
Don't want us hitting your production DB? Connect us to a read-replica. We work fine with delayed-replication setups.
Field-level access
Hide sensitive fields (salary, PII, internal notes) from Kolossus entirely. Per-table, per-column, per-user.
Full audit trail
Every read query, every write operation logged with user, timestamp, and changes. Exportable to your security team.
On-prem Nano LLM
For regulated industries: deploy Kolossus on-premise via our Nano LLM. Data never leaves your environment.
Your first 21 days

Specific days. Specific outcomes. Not a generic "30 days to value" promise.

We've done this enough times to know exactly what week three looks like.

21days to live.

From first connection to your team running Kolossus on the CRM your team built. No generic milestones - every day below has happened with a real customer.

DAY 1
Connect
Kolossus connects to your CRM. Database connection or API setup, depending on what your system exposes. First test queries running within the same call.
DAY 3
First dashboard live
Whichever use case is most painful for your team. Your finance lead starts using it.
DAY 7
Write-back configured
Kolossus can mark invoices, schedule payments, update records - under your team’s permission tiers.
DAY 14
Team trained
Each person knows the queries relevant to their role. WhatsApp support channel established.
DAY 21
Production daily-use
Manual workflows for configured use cases stop. Your team works with Kolossus, not around it.
21-day production guarantee · Most teams hit it soonerLIVE BY DAY 21
Custom CRM FAQ

Questions custom CRM owners actually ask.

Yes.We don't care about your application code, the framework, or how old it is. What we connect to is your database (PostgreSQL, MySQL, etc) or your API layer (REST or GraphQL). Both are technology-agnostic.

If your CRM is built on Laravel, CodeIgniter, vanilla PHP, or anything else - none of that matters to us. We read the data, not the code.

Yes.No code changes. No schema migrations. No new fields or tables we'd require you to add. Your CRM stays exactly as your team built it.

We work around your existing structure, not the other way around. That's the whole point.

No. Kolossus re-discovers your schema on a regular cadence. New columns appear, deleted columns disappear, renamed tables get re-mapped.

For breaking changes (renaming a primary entity, restructuring a major table), we'll work with you on a 15-minute reconnect rather than a full reimplementation.

Three options work here:

One:Whitelist Kolossus's IP range to your CRM and treat us as another internal service.

Two: Connect through a VPN gateway you already have for remote-team access.

Three: Deploy Kolossus on-premise. Our Nano LLM runs inside your network, with no external traffic at all. Recommended for regulated industries.

Yes - at every level. Per-database, per-table, per-column, per-user.

Sensitive fields (salary, PII, internal notes, financial details) can be hidden from Kolossus entirely. We never see fields you mark as restricted.

For database connections, the cleanest approach is to give Kolossus a read-only role with explicit GRANTs only on the tables/columns you want analyzed.

Every query Kolossus runs is logged with full SQL/API call, user, timestamp, and result.

For write operations: we log the before-state, the after-state, and the user who approved the change. Exportable as CSV or directly queryable from your CRM database (we keep the audit log there).

That's expected with any system that's been in production for years.

During the first week of the POC, we typically surface data quality findingsyour team didn't know about - orphaned records, inconsistent formats, duplicate entries. You can decide whether to fix them in your CRM or have Kolossus normalize them on the fly.

Annual subscription model. Tier depends on number of users, query volume, and whether you need on-premise deployment.

Most standard mid-market customers fit our default tier.

POC is free for 14 days on your actual data - no credit card required.

NEXT STEP

Ready to see this on your CRM? Two paths from here.

RECOMMENDED
Start a conversation on WhatsApp
Message a co-founder directly. Tell us what your CRM is built on (database type, any APIs, deployment), the questions you'd want answered, and we'll tell you honestly whether a 14-day POC makes sense for your business.
Start WhatsApp conversation
Founder replies on WhatsApp · Usually within 5 minutes
EXPLORE FIRST
See how the full product works
Read about Kolossus more broadly - the full product overview, how it works across CRMs, Tally, and other systems, what our customers are doing with it.
Read the product overview

Frequently Asked Questions

How much does Kolossus cost?

Our Growth tier (which covers most of what a 150-500 person business needs) is ₹20,000–30,000/month. That’s ₹2.4–3.6L/year.

Is that expensive? Compared to what? If your finance team spends 8 hours a week on manual Tally reports, that’s ₹2L/year in analyst time alone. And that’s before counting the decisions made on stale data.

Have a question we didn’t answer? DM us on WhatsApp.
Ask on WhatsApp