Tecknow — Intelligent IT Service Delivery Platform

Enterprise IT service management has a reputation problem that's entirely earned. The dominant platforms — ServiceNow, Jira Service Management, Freshservice — are powerful in the sense that a freight train is powerful: they can carry enormous loads, but you need a team of specialists to drive one, and they're not turning corners quickly.

For a mid-market company with a competent IT team, the choice has historically been: buy an enterprise ITSM tool and spend months configuring it, or use a lightweight helpdesk that doesn't have the process structure IT actually needs. Neither option is right. The enterprise tools bring complexity that buries small teams. The lightweight tools don't model incidents, changes, and problems correctly — so IT teams end up building workarounds in Slack and spreadsheets.

The result is the same either way: tickets fall through gaps, resolution times are hard to measure, and employees — the people raising requests — have no visibility into what's happening with their issue. They submit a ticket and it disappears into a queue they can't see. They follow up by email. The IT team spends time chasing status rather than resolving problems.

The Tecknow team came to us wanting to build the middle path: a platform that has the structural rigour of an enterprise ITSM — proper incident classification, SLA tracking, escalation rules, change management — but is designed to be set up in days, not months, and used by IT teams without a dedicated platform administrator.

We designed the data model around ITIL process categories — incidents, service requests, problems, and changes — but kept the UI entirely free of ITIL jargon. The internal model is correct; the interface speaks in plain language. An employee raising a request doesn't need to know whether they're creating an incident or a service request. The classification happens automatically based on the category they select and rules configured by the IT team.

Ticket routing is driven by a rules engine: category, priority, affected asset, and requester attributes determine which team and which agent receives a ticket. Escalation triggers fire automatically when SLA thresholds are breached — the IT manager doesn't need to check a dashboard to know something is running late; the platform tells them.

The employee-facing portal was designed as a first-class product, not an afterthought. Employees can raise requests, check status, respond to agents, and close resolved tickets — all without needing to contact IT directly for updates. Status visibility is the single biggest driver of employee satisfaction with IT support, and it costs the IT team nothing if the platform surfaces it automatically.

The intelligent layer sits across two areas: suggested categorisation (the platform recommends an issue type and priority based on the description, reducing mis-categorisation) and resolution suggestions (when a ticket comes in that matches a previously resolved issue, the platform surfaces the resolution notes to the assigned agent before they start investigating).

The admin configuration surface was designed to be operated by an IT manager, not an implementation consultant. Routing rules, SLA policies, categories, and agent assignments are all managed through a structured UI — no scripting, no custom fields requiring developer access.

The backend is built on .NET Core with an Angular frontend, deployed on Azure with tenant-level isolation for multi-organisation support.

Tecknow is live and deployed as a commercial SaaS platform, available to IT teams looking to replace legacy helpdesk tools or graduate from informal ticket tracking.

The platform delivers on its core positioning: IT teams are operational within days of sign-up, not weeks of configuration. The employee portal removes the "ticket black hole" problem — requesters have real-time visibility without needing to contact IT for updates.

Resolution time visibility and SLA tracking give IT managers data they previously had to extract manually from helpdesk exports. Escalation automation means breached SLAs surface to management without anyone needing to notice them first.

For the client: Tecknow occupies a position in the market that the legacy vendors have left open — structured enough for IT teams that take process seriously, simple enough that they can actually run it themselves.

For us: Tecknow is the project we point to when someone in enterprise software asks whether we understand ITSM domain complexity. We do — and we know how to build platforms that handle that complexity without inflicting it on the user.