Available for Q2 / Q3 2026 engagements

Hands-on CTO
& Systems Architect.

I turn messy operations into scalable revenue systems.

Scaled a transportation business from $500K to $3M+. Built real-time platforms serving 20M+ users a day. Shipped AI-driven optimization that lifted daily revenue 30% — with no added headcount.

View case study Let's talk
  • $500K → $3M+
    Annual revenue grown at D. Harris Tours
  • 2 → 14
    Buses in the fleet on the same operational backbone
  • +30%
    Daily revenue from AI trip & route optimization
  • 20M+
    Daily users on platforms I've architected at Conversant
01 What I do

Six things I get hired for.

The through-line is the same: find the operational bottleneck, design the system that removes it, ship it.

— 01

Operational systems design

End-to-end software for how the business actually runs: intake, scheduling, dispatch, billing, reporting. The plumbing that determines whether growth is painful or boring.

— 02

Workflow automation

Replace spreadsheets, group texts, and tribal knowledge with systems that don't forget, don't quit, and don't call in sick.

— 03

Dispatch, CRM & billing platforms

Custom-built where off-the-shelf doesn't fit, integrated where it does. Revenue-critical by design, not afterthought.

— 04

Real-time tracking & coordination

GPS, live status, automated notifications, customer portals. The nervous system of an operations company.

— 05

AI-assisted optimization

Applied where it moves a P&L line — routing, pricing, scheduling, forecasting — not where it looks good in a pitch deck.

— 06

Fractional CTO & architecture leadership

Strategic technical leadership for founders and teams that can't justify a full-time exec yet need senior judgment.

02 Featured case study

D. Harris Tours: from family operator to $3M+ regional carrier.

A family-run charter bus operator, stuck around $500K in revenue with two buses, running operations on phone calls, spreadsheets, and memory.

The problem
  • Dispatch lived in a group text.
  • Quotes took 24+ hours and often fell through.
  • Drivers lacked real-time trip info.
  • Billing and collections were manual, inconsistent, and leaking money.
  • Growth was capped by how many things one person could hold in their head.
The system
  • Unified TMS covering CRM, quoting, scheduling, dispatch, driver ops, GPS tracking, automated notifications, invoicing, payment collection, and a customer portal.
  • AI-assisted trip and route optimization layered over historical data.
  • Built to run the business — not to impress investors.
The results
Fleet
2 → 14 buses
Annual revenue
~$500K → $3M+
Daily revenue lift
+30% from optimization alone
Quote turnaround
Minutes, not days
Added headcount
Zero

The owner runs a bigger business with less chaos. That's the whole job.

03 How to work with me

Three ways to start.

Pick the shape that fits the problem. I'll tell you if it doesn't.

Engagement 01

Systems Audit

~2 weeks · fixed fee

One focused engagement. I map your current operational stack, interview your team, and deliver a candid written report: what's working, what's costing you money, and where the leverage actually is. Usually pays for itself before a single recommendation is implemented.

Start with an audit →
Engagement 02

Architecture Sprint

4–8 weeks · outcome-based

I design the system you actually need — data model, service boundaries, integrations, build-vs-buy calls, and a realistic implementation plan. You leave with something your team (or mine) can build against without guessing.

Scope a sprint →
Engagement 03

Fractional CTO

Ongoing · retainer

Senior technical leadership without the full-time hire. Roadmap, hiring, architecture calls, vendor decisions, and hands-on work when the problem warrants it. Best for founders scaling past the point where "just figure it out" stops working.

Discuss a retainer →
04 Selected builds

A short list. Each solved a specific problem.

These support the work — they aren't the work. The business results above are the point.

U2OS

Modular multi-tenant business operating system. The operational patterns that scaled D. Harris Tours, generalized into a platform other operations-heavy SMBs can deploy.

Multi-tenant SaaSOperationsPlatform
TextWeb

Messaging-first interface layer for business workflows. Moves intake, updates, and approvals to the channel customers and drivers actually read: text.

SMS infrastructureWorkflows
LARC

Agentic workflow framework for orchestrating long-running, multi-step business processes across humans, systems, and AI. Built to run to completion without a person holding the thread.

Agent orchestrationWorkflow engine
PanicBooking

Last-minute charter reservation system built for the "I need a bus in 90 minutes" end of the market. Inventory, pricing, and dispatch coordinated in a single flow.

BookingReal-timeTransportation
05 About

Engineering and operations, at the same time.

I've spent my career at two intersections: systems and operations, engineering and leadership.

At Conversant, I led rich-media and mobile systems serving 20 million users daily — REST APIs, mobile SDKs, metrics and reporting infrastructure. The unglamorous backbone of a platform at scale.

At D. Harris Tours, I wore both hats: architected and built the operational software, and helped run the business while the fleet grew 7× and revenue grew 6×. It's one thing to ship software that works. It's another to ship software that moves a P&L.

That dual perspective is the work now. I take on engagements where technical leadership and hands-on engineering both matter — where someone needs to understand the P&L and ship the code. I'm selective about full-time roles, intentionally broad on consulting, as long as the problem is real.

06 Contact

Let's talk.

I'm currently taking on a small number of consulting and fractional engagements, and I'll consider the right full-time role. The fastest way in is email — I read every message myself.

Email (preferred)
cdr@cdr2.com