Technical operator · practical AI systems

I build what I can explain.

I work where AI capability meets the way a business actually runs: find the friction, simplify the workflow, then build a useful system that stays under clear human control.

See the work Start a conversation

01 · Point of view

Name the real workflow first.

Most "AI transformation" skips the part that matters: the documents, the people, the review points, and the constraints that already exist. I start there, keep a human accountable at every decision, and leave you owning what gets built.

Understand

Map the workflow as it truly operates today and find the smallest useful place to change it.

Simplify

Remove steps and clarify handoffs before adding any tooling. A cleaner process beats a clever one.

Build with control

Install or build a capability you can inspect, review, and own — with the boundaries stated plainly.

02 · Owned proof

Things that already exist.

Not client outcomes — working artifacts and public code you can look at directly. Each is labeled for what it actually is.

Public GitHub profile

Public repository

Open code and project history under the handle rodaddy — the most direct evidence of how I actually build.

Source: github.com/rodaddyStatus: Public, verifiable

Open the profile ↗

Merged Fabric VertexAI contribution

Merged open source

A contribution adding VertexAI support to the Fabric project — a real, merged change to a tool other people use.

Type: Open-source contributionStatus: Public, verifiable

Verify merged Fabric PR #1908 ↗

Practical AI kits & proof-of-concepts

Working artifact

Concrete, adaptable capabilities I can demonstrate and shape to a specific workflow rather than describe in the abstract.

Type: Working artifactScope: Demonstrable

See how these work

Assessment & Concierge operating models

Operating system

Detailed frameworks for diagnosing a workflow and supporting recurring implementation. The commercial version of this runs through rTech.

Type: Operating systemDelivery: via rTech Consulting

Route to rTech ↗

Proof boundary. These are working artifacts, public code, and operating frameworks. They make no claim about client counts, conversion, retention, ROI, or time saved.

03 · The rTech relationship

Personal trust opens the door. rTech carries delivery.

This site is where you meet the person and see how I think. When there is real commercial work — an assessment, an ongoing AI Concierge relationship, or a scoped build — it runs through rTech Digital Consulting.

Understand

AI Assessment

A low-friction paid diagnostic: map the workflow, surface the friction, and name the smallest useful next move.

Work alongside

AI Concierge

A done-with-you monthly relationship for practical, recurring implementation — with capability transfer, not permanent dependency.

Build

Scoped implementation

Larger builds, kits, and client-owned systems delivered through rTech when the work calls for it.

Visit rTech Consulting ↗

Start with the workflow that keeps getting in the way.

Bring one real bottleneck. I read every message myself and reply as a person, not a booking bot.

Start a conversation