Show HN: Worqlo – A Conversational Layer for Enterprise Workflows
by andrewdany | 2025-11-20 08:56:08+00:00
Most enterprise work isn’t slow because of bad data. It’s slow because the interface to that data is scattered.

A single question like “Which deals are stalled?” touches dashboards, spreadsheets, a CRM, BI tools, internal scripts, and a few Slack threads. Acting on the answer requires switching between systems again. The friction is in the middle.

Worqlo is an experiment in removing that friction by using conversation as the interface layer and deterministic workflows as the execution layer.

The idea is simple: natural language in → validated workflow out.

The LLM handles intent. A structured workflow engine handles execution: CRM queries, field updates, notifications, permissions, and audit logging. The model never executes actions directly.

Below is how it works.

Why Conversation?

People think in questions. Systems think in schemas. Dashboards sit between them.

Interfaces multiply because every system exposes its own UI. Engineers end up building internal tools, filters, queries, analytics pages, and one-off automations. That’s the UI tax.

Conversation removes the surface area. Workflows add safety and determinism.

Architecture (simplified) User → LLM (intent) → Router → Workflow Engine → Connectors → Systems

LLM

Extracts intent and parameters. No execution privileges.

Intent Router

Maps intent to a known workflow template.

Workflow Engine

Executes steps in order:

schema validation

permission checks

CRM queries

API updates

notifications

audit logs

Connectors

Strict adapters for CRMs, ERPs, internal APIs, and messaging systems.

The workflow engine will refuse to run if:

fields don’t exist

data types mismatch

permissions fail

workflow template doesn’t match user intent

This prevents the usual LLM failure cases: hallucinated fields, incorrect API calls, unsafe actions, etc.

Example Query

User:

"Show me this week's pipeline for DACH"

Internal flow:

intent = llm.parse("pipeline query") validate(intent) fetch(data) aggregate(stats) return(summary)

Follow-up:

"Reassign the Lufthansa deal to Julia and remind Alex to follow up"

Workflow:

find deal by name validate ownership change write CRM update send Slack notification write audit log

Everything runs through deterministic steps.

Why Start With Sales

Sales CRMs are structured and predictable. Workflows repeat (reassign, nudge, follow-up). Latency matters. Output is measurable. It makes the domain a good test environment for conversational workflows.

The long-term idea is not sales-specific. The same pattern applies to operations, finance, marketing, and HR.

Why Not Just Use “ChatGPT + API”?

Because that breaks fast.

LLMs are not reliable execution engines. They hallucinate field names, IDs, endpoints, and logic. Enterprise systems require safe, auditable actions.

Worqlo treats the LLM as a parser, not a worker.

Execution lives in a controlled environment with:

workflow templates

schema contracts

RBAC

logs

repeatable results

This keeps the convenience of natural language and the reliability of a classic automation engine.

What We’re Testing

We want to see whether:

conversation can replace UI for narrow, structured tasks

deterministic execution can coexist with natural language intent

multi-turn workflows can actually reduce operational load

a connector model can scale without creating another integration mess

engineers prefer exposing functionality through workflows instead of UI layers

It’s still early. But the model seems promising for high-volume, low-level operational work.