Product + Engineering · APIs, Integrations, Agentic AI

I build the connective tissue between software and AI.

I'm Steven Knight. Most people call me Chris. I work on APIs, integrations, and the agentic infrastructure that lets AI agents act on enterprise systems. The first version of that work solves it for one client. I build the version that solves it for the next dozen.

A production MCP server. A company's first client-facing developer API. Both shipped hands-on, in C#/.NET on AWS.

I work at the seam where systems meet.

For a decade I've moved, mapped, and reconciled data between platforms that were never built to talk to each other. Lease accounting, accounts payable and receivable, cash application, compliance screening, KYC. Different domains, same problem underneath - the data is in the wrong shape, in the wrong place, and somebody is doing it by hand.

The work I care about is the second half: taking the thing that worked once, for one client, and making it a product. An agent acting on an enterprise system needs the same things that work always needed - a clean contract, a real permission boundary, and a record of what it did.

APIs & Developer Platforms

API contracts, gateways, webhooks, partner self-service. Moving integrations out of ops and into the product.

Agentic Infrastructure

MCP servers in production, tool-calling surfaces over real enterprise data, agent-driven delivery.

Data Migration & Integration

ETL and mapping pipelines, schema reconciliation, migration tooling that replaces artisanal SQL.

Selected work.

Employers aren't named here. Details on request.

Transportation Compliance SaaS

A production MCP server, on top of the API I'd just launched.

The company had no public API. Integrations were built one at a time by ops, which meant every partner was a project. I launched the first client-facing developer API - contracts, a MuleSoft gateway, bidirectional webhooks - and moved integrations to partner and customer self-service. That unlocked connections into major HR and ERP platforms. Then I built a production MCP server on top of it, giving LLM and agentic workflows tool-calling access to compliance and screening data. I also led the company's first containerization effort on AWS and Kubernetes.

AR Automation Platform

Turned per-client migration code into a pipeline.

Every new client migration was hand-written SQL. I replaced it with a pipeline that ingests raw client flat files, runs statistical analysis on the fields to infer types and mapping candidates, auto-generates roughly 99% of the mapping, and flags the rest for a consultant.

~99% of mappings auto-generated

Lease Accounting SaaS

A rounding algorithm that saved a banking relationship.

Multi-year lease streams allocated across divisions left partial-penny remainders that wouldn't reconcile to the total. The proposed fixes were a third-party tool or a new backend service. I wrote the allocation algorithm in SQL instead - a function and a stored procedure - and it reconciled. The client stayed.

Retail Order Management

Fixed one customer's latency, then shipped the fix to about a dozen.

A client's order-allocation times had degraded badly against a growing on-prem database. I wrote an archive-and-purge package that identified archivable records while preserving auditable history. Then I generalized it into a configurable tool and deployed it across the install base.

~90s → sub-second · ~12 customers

How I work.

I stay close to the code. C#/.NET Core, SQL Server and PostgreSQL, AWS and Kubernetes, MuleSoft, REST and webhooks, MCP. I'm not a PM who used to be technical.
I lead through what I ship. I've aligned engineers, partners, and customers through influence rather than headcount, including an offshore team. I've never held a headcount title and I don't claim one.
I productize. The first version solves it for one client. The version that matters solves it for the next dozen.
I build with agents, in production. Claude Code-driven delivery, and a production MCP server as a real interface rather than a demo.

In the open.

Most of what I build belongs to an employer. What's public is the home-lab end of it - where I try a pattern on something low-stakes before trusting it at work.

WitcherScriptMerger ↗
A .NET modernization of a long-lived legacy WinForms tool: an in-process 3-way merge engine replacing an external binary, a shared core behind the projects that use it, a headless CLI, a cross-platform host, and an MCP server so an agent can drive merges directly. The domain is game mods. The exercise is retrofitting an agent interface onto software written years before the idea existed.
Orlog AI
A venture where I build in the open. The API and MCP-server work above was delivered in my product role, not at Orlog.

GitHub LinkedIn

Get in touch.

The fastest way to reach me is email. If you want the full record - roles, dates, references - ask and I'll send it.

stevenc.knight@gmail.com

Or find me on LinkedIn.