From Configurations to Rules: The End of the Settings Page

March 17, 2026 • 5 min read

You've just bought a shiny new CRM. It has a Lead Scoring feature. You open it, excited. Maybe this is finally the thing that brings some intelligence to your pipeline.

There's a form.

"Add [ ] points if deal value is greater than [$ ]."

"Add [ ] points if industry equals [ ▼]."

"Subtract [ ] points if lead source is [ ▼]."

You fill in some numbers. Close. Save. Done.

But then you remember your actual rule. The one you told your team last month on a Slack message: "If someone reaches out through a referral from an existing customer, treat them completely differently — warm introduction, skip the standard discovery, go straight to pricing."

You look at the form. There's no field for that.

There never will be.

You close the tab. You send another Slack message.

The Old World: Features, Then Configuration Options

Here's how every CRM — every serious one, the good ones too — was built.

A team of product managers and engineers would identify a sales problem. "Sales teams need to prioritize leads." They'd build a solution. Call it Lead Scoring. Then they'd expose configuration options for it.

Dropdowns. Sliders. Threshold fields. Number inputs.

The mental model was: we build the engine, you dial the settings.

And for a while, this felt like power. You weren't just using a generic tool — you were customizing it. Your CRM was tailored to your business.

Except it wasn't.

Because you could only customize the things the product team decided to expose. The parameters were their parameters. The categories in the dropdown were their categories. The logic was their logic — you were just picking the numbers.

The more sophisticated the vendor, the more settings they gave you. Some CRMs have literally hundreds of configuration screens. Settings for your settings. Tabs inside tabs. A support article for every field.

And yet, somehow, none of it quite matched how your business actually worked.

The Hidden Tax of the Settings Page

Here's what nobody says out loud: the settings page is a promise that was never really kept.

Your real sales rules are written in plain language. They live in your head, in your team Slack, in the onboarding doc that someone wrote two years ago and nobody has updated since:

• •"Be more aggressive with warm referrals — shorter cycles, skip the nurture sequence."
• •"If a lead mentions a competitor by name, escalate immediately. Don't wait for the weekly review."
• •"Wedding photographers are high-intent — same-day response, always."
• •"Never auto-dismiss a lead from a returning customer, no matter how cold it looks."

Not one of those fits in a dropdown.

So teams do what teams do: they work around it. The sales manager sends a weekly reminder. The VP writes a policy doc nobody reads. The most experienced rep just knows, and silently saves the deal every time.

The CRM? It's still scoring leads by industry and job title. Completely unaware.

The tragedy isn't that CRMs were poorly built. It's that the underlying model — build feature, expose configuration — hit a ceiling. You can only parameterize so much of human judgment before you run out of fields.

The Slokoto Way: Write the Rule. The AI Figures Out When.

In Slokoto, there's a Sales Rules tab.

You open it. There's a text field. You type.

That's it.

No dropdowns. No threshold sliders. No "select industry from list." Just a blank field and your actual words:

"After 10 follow-ups with no reply and at least 30 days elapsed, move the lead to Lost."

"Always prioritize leads with a deal value above $5,000."

"If a lead mentions 'wedding' or 'event', mark it as high-priority."

"Never auto-dismiss leads from returning customers, even if they've gone cold."

The AI reads these exactly as you'd read them — as instructions, as policy, as the kind of thing a good sales manager tells a new rep on their first week.

And then it applies them. Continuously. Across every lead, every email thread, every new conversation that comes in.

Not by matching keywords. By understanding context.

When a lead goes quiet for 32 days after 11 follow-ups, the AI doesn't need a config field. It knows. When a photographer emails in asking about rates for their venue, the AI doesn't need a dropdown for "industry = Events." It knows.

And when the rule doesn't apply — when the evidence isn't there — the AI doesn't force it. It won't invent facts to satisfy your policy. It applies rules only when the conversation actually supports it.

What This Shift Actually Means

This isn't a UX improvement. It's a completely different mental model.

With the old approach, you were a user of someone else's system. You worked within the bounds of what they decided to expose.

With Slokoto's Sales Rules, you're the author. You write your business logic in your own words, and the AI operationalizes it. You're not configuring a feature. You're setting policy.

No more:

• •❌ Hunting for the right dropdown to approximate what you actually mean
• •❌ Rules that only work for the 80% of cases the product team anticipated
• •❌ Slack messages as the de facto policy engine for your team
• •❌ CRMs that score leads without knowing what your business actually cares about

Instead:

• •✅ Any rule, in plain English, applied across your entire pipeline
• •✅ AI that reads context, not just fields
• •✅ Toggle rules on/off in seconds — no deployment, no IT ticket
• •✅ A system that finally knows what you think matters

Before vs. After

The Best Sales Rules Aren't Settings. They're Principles.

There's a reason great sales managers don't hand new reps a configuration guide. They tell them stories. They explain why. They say things like "when someone mentions a competitor, that's actually a great sign — here's how to handle it."

That's not a dropdown. That's a principle.

Slokoto lets you encode those principles directly. Not as parameters someone else designed, but as instructions you write in your own voice. The AI holds them, applies them, and uses judgment where judgment is needed.

The CRM finally speaks your language.

P.S. — If you've got a "Follow-up delay: 3 days" config sitting somewhere that hasn't been touched since 2023... we should talk. Your pipeline deserves better than a number someone picked at random.