oc_
+++
OWEN COLWELL / OPERATOR & BUILDER

A little curiosity.
A lot of building_

I turn business problems into systems.
Currently leading AI Operations at Chargeflow ↗.

SCROLL TO EXPLORE ↓
+++
/ SELECTED WORK2023 — 2026
01 / NEXUSAI PLATFORM

Nexus lets teams create internal tools, automate work, and put AI to use—with governance built in.

AI AGENTSPLATFORM ENGINEERING
02 / ALEPHKNOWLEDGE SYSTEM

Aleph connects people and AI agents to permission-aware company knowledge. Every answer has a source.

RETRIEVALCOMPANY KNOWLEDGE
/ FROM THE BUILD
ARTICLE / NEXUS

Building Nexus.

Some thoughts and experiences building Nexus, the internal harness our team uses at Chargeflow.

READ ON X ↗
/ THE PERSON BEHIND THE SYSTEMS01 HUMAN

Business context.
Builder’s instincts.

I started in growth, close to customers and the everyday friction of running a business. Building better systems became the most useful way to solve it.

Today, I lead AI Operations at Chargeflow. I build AI platforms and the data systems behind them, while hiring, coaching, and helping others take ownership of their work.

Some days that means architecture and code. Others, a clearer brief, a design review, or getting the right people in a room. The through-line is understanding the problem and staying with it until the solution is useful.

SEATTLE → NEW YORK → TEL AVIV
  1. 2026 — PRESENT

    Head of AI Operations

    Chargeflow · Building AI platforms and data systems. Leading and coaching across AI operations and GTM engineering.

  2. 2023 — 2026

    Revenue Operations → GTM Engineering

    Chargeflow · Connecting the systems behind the business.

  3. 2021 — 2023

    Customer Relations → VP of Growth

    POSH · Helped grow revenue from ~$35k to $4m+ and the platform to over a million users.

  4. 2019 — 2020

    Learning the business

    Marketing, production, and finance internships in the Seattle area.

/ IDEAS I COME BACK TOOPEN A NOTE ↓

Field notes

(03)
001

Three ways AI changes a company

FRAMEWORK+

I think about AI implementation in three layers. They overlap, but each asks something different of the business.

01 / Make individuals more capable.

Put useful AI tools inside the workflows people already use: call preparation, research, summaries, and analysis.

02 / Let systems do the work.

Build agents and automations that carry a process from start to finish, with clear permissions and reliable handling of failures.

03 / Put AI in the product.

Turn those capabilities into something customers can use. The challenge expands from internal usefulness to product quality and trust.

Nexus and Aleph provide shared infrastructure for the first two layers: a place to create and run tools, and a source of grounded company knowledge.

002

Direct the agents. Own the outcome.

BUILDING+

AI coding agents give me more implementation capacity. I still need to decide what to build, understand the architecture, and verify the result.

My process pairs living architecture documents with automated checks, controlled deployments, and deliberate attempts to disprove an agent’s claim that the work is finished.

Sometimes that means setting completed work aside when a simpler approach holds up better. Generating code is only part of the job. Knowing what to keep matters just as much.

003

Start with the problem. Share the ownership.

LEADING+

A request often arrives with a solution already attached: a new field, another dashboard, an agent. I want to understand what’s actually getting in someone’s way before deciding what to build.

That same idea carries into leading a team. Write down the goal, agree on what done means, and give the person doing the work room to make decisions. Stay close enough to review and unblock.

A useful system should make people more capable. So should the way we build it.

Good things start with a conversation.

SAY HELLO ↗
BEYOND THE FOOTER / 000
SCROLL DOWN TO KEEP BUILDINGSCROLL UP TO RETURN ↑
/ PROJECT
OWEN.OS / CONSOLE
TRY “HELP” ↑ ↓ COMMAND HISTORY