Houston, Texas
Back to profile
AI Work · Companion page

AI as a working layer, not a talking point.

My AI work sits between research, data, workflow design, and strategy. I use AI to gather signals, structure knowledge, build lightweight systems, and turn messy information into something a team can actually use.

Companion page

The main profile explains the arc of the work. This page extends it with AI-specific projects, the build stack, and visual wireframes. Back to profile →

01 / Build stack

My AI build stack.

Six layers, read from raw signal at the top to distribution at the bottom. The tools change. The shape of the stack does not.

A.Signal sources

Where the raw material comes from.

Alerts, feeds, and primary documents that surface what is actually happening across markets, policies, and partner ecosystems.

Sources
  • Google Alerts
  • Inoreader
  • RSS feeds
  • News sites
  • Company pages
  • Policy docs
  • Research reports
  • Event pages
B.Capture & storage

Where signals become records.

Structured tables and notes that let scattered information be queried, compared, and kept current over time.

Tools
  • Google Sheets
  • Airtable
  • Notion
  • Cloudflare
Shape
  • Structured tables
  • Linked records
C.Automation & workflow

The plumbing between layers.

Lightweight pipelines that move data, trigger reviews, and keep a human in the loop where it matters.

Tools
  • Make
  • Apps Script
  • Colab
  • APIs
Methods
  • Review loops
  • Enrichment scripts
  • Lightweight validation
  • Human-in-the-loop
D.Models & synthesis

Where AI does the heavy lifting.

Structured prompts and a few well-chosen models do most of the classification, summarisation, and entity work.

Models
  • ChatGPT
  • Claude
  • Gemini
  • OpenAI API
Methods
  • Structured prompts
  • Classification
  • Summarisation
  • Entity extraction
E.Interfaces & artifacts

What the team actually sees.

Pages, dashboards, and briefs that turn the underlying records into something useful in a meeting.

Tools
  • Softr
  • Looker Studio
  • Flourish
  • Figma
  • Claude Design
  • HTML / CSS
Outputs
  • Research pages
  • Dashboards
  • Executive briefs
  • Working notes
F.Distribution & feedback

Where the work meets readers.

The publications, products, and conversations that close the loop and shape what the next cycle looks like.

Channels
  • Website
  • Substack
  • LinkedIn
  • Newsletters
Loop
  • Client conversations
  • Reader replies
02 / How I use AI

Three working principles.

A short version of how I think about AI in practice. The same three lines show up across every project below.

i.

AI helps me move faster, not skip the thinking.

Models are useful for sourcing, drafting, and synthesis. The judgement still has to hold up in the room.

ii.

Structure matters more than prompts.

Most of the leverage is in the data model, the taxonomy, and the workflow. The prompt is the smallest part of the system.

iii.

The output has to survive a real decision.

A brief is only good if it can sit on a CEO or CRO's desk and shape the next move. That is the bar.

03 / Featured AI projects

Six projects, in detail.

Each has a short rubric and a stylised wireframe. The wireframes are editorial diagrams, not screenshots, and use synthetic placeholder content. More projects will land here as they are ready to show.

2026 Working system

Sovereign AI Vector visit

A knowledge product mapping how countries are approaching AI: national strategies, investments, infrastructure choices, institutions, policies, and convenings. Built so the picture is usable rather than just current.

Problem

Sovereign AI is being announced faster than it is being understood. Leaders need a map, not another news feed.

What I built

A structured intelligence system with country-level records, policy tracking, events, research, and signal feeds. 130+ programs across 50+ countries.

AI role

Classifying sources, summarising policy documents, extracting entities, identifying focus areas, enriching records, and turning raw signal into structured intelligence.

Current status

In active build. Live at sovereignaivector.com with continuous editorial and pipeline work.

In build Knowledge product Ontology Sovereign AI Decision intelligence
Wireframe · Country detail · synthetic data
National AI Posture / Country detail · synthetic data
Country placeholder
Region label
GDP
$XX,XXXB
Growth
X.X%
Population
XXXM
Focus areas
AI Infrastructure Cybersecurity Education & Workforce Diplomacy & Exports National Security Public Sector Regulation & Standards Research & Innovation
Policy summary

A short, structured description of the country's stated AI ambition, the institutions behind it, and what it implies for vendors and partners over the next 12 to 24 months.

2026 Working framework

Team LinkedIn presence assessment

A scored, ranked assessment of how a team shows up on LinkedIn, built from publicly available data using an orchestrated AI toolchain. Turns scattered signals into a single team scoreboard with one priority action per person.

Problem

Most team LinkedIn profiles quietly drift out of sync with the team's brand and the story the org is trying to tell. Inconsistent headlines, outdated employers, and the occasional departure signal — all visible to any buyer who looks before a meeting.

What I built

A four-tool workflow that turns a list of LinkedIn URLs into a ranked team scoreboard with individual assessment tabs. Five criteria, scored one to three, total out of fifteen, with status labels that point to a specific next move.

AI role

Enrichment via Clay. Structured staging in Sheets. Claude reads the structured record and the live profile, scores across all five criteria, and returns a JSON payload. Apps Script rolls each payload into a named tab and updates the team scoreboard.

Current status

Working framework. Tested on a real team; the methodology applies to any LinkedIn assessment use case.

Working framework Multi-tool workflow Assessment design Public data only
Wireframe · Toolchain & team scoreboard · synthetic data
01 · Enrichment
Clay
LinkedIn URLs → structured fields
02 · Staging
Sheets
Single source of truth, consistent columns
03 · Assessment
Claude
Reads record + live profile · scores · JSON
04 · Automation
Apps Script
Paste & run · builds individual tabs
05 · Output
Scoreboard
Ranked team view · priority per person
# Person Segment Scores Total Status Priority action
01
Person 01
Senior · Practice A
14 / 15
Gold standard
Maintain cadence · post a case study
02
Person 02
Lead · Practice B
12 / 15
Good · gaps
Tighten headline to current role
03
Person 03
Senior · Practice A
10 / 15
Reach, no activity
Start a monthly post · keep it short
04
Person 04
Lead · Practice C
8 / 15
Headline drift
Rewrite headline · update employer
05
Person 05
Senior · Practice B
6 / 15
Possible departure
Manager conversation · check intent
Criteria · 1 → 3 low mid high
Bands 13–15 best in class 9–12 gaps remain 6–8 action needed
2026 Working prototype

VR walk-through of a modular data center

A browser-based, self-paced VR experience for explaining a modular data center to non-technical audiences. Designed for a microsite and an unattended kiosk.

Problem

Data center infrastructure is mostly invisible to the people deciding to invest in it. Modular builds in particular get described in stats — megawatts, PUE, deployment speed — without the texture of what is actually inside one.

What I built

An interactive VR walk-through that loads in any modern browser. A sequence of rooms, each with hotspots that open short, plain-English explanations. Self-paced for a microsite, and kiosk-friendly with an idle reset.

AI role

AI as co-builder. Drafting scene structures, scaffolding the 3D code, generating hotspot copy, and pressure-testing the sequence. The judgement about what to show, what to leave out, and how to name each room was the human work.

Current status

Working prototype. Runs on a laptop or a touchscreen kiosk.

Working prototype VR microsite Browser-based AI as co-builder Kiosk mode
Wireframe · Viewport · synthetic data
Exterior view · stylised placeholder
Immersive walk-through A sequence of rooms Stop 03
Stop · placeholder
Room title
A short, plain-English line that frames what this room is for.
Detail
Hotspot title

A short, plain-English explanation. Two or three sentences, no more.

Step through
1
2
3
4
↻ Start ← Prev
Next →
2026 Working prototype

AI-enriched M&A target screening

A confidential, single-page dashboard for screening M&A targets across a partner ecosystem. Turns a long list of candidates into a tiered shortlist with structured evidence and decision-ready recommendations.

Problem

M&A teams often start with a long list from a corporate-finance partner, then spend weeks turning that list into a shortlist they can actually act on. The work is structure, evidence, and consistent screening across every name.

What I built

A static, single-page dashboard with four tabs — Overview, Master List, Company Detail, Evidence & Audit — built around a two-stage screening method: structural priority first, then strategic recommendation. Self-contained, deployable behind access controls.

AI role

AI-enriched research per target: ownership verification, vendor partnerships, business description, ecosystem relevance, and diligence risk flags. The structured outputs feed every tab and every KPI.

Current status

Working prototype, used in a confidential engagement. Industry-agnostic; the screening framework is the reusable part.

Working prototype Confidential engagement AI-enriched research Decision dashboard Static deploy
Wireframe · Screening dashboard · synthetic data
Client name M&A Target Screening
Priority A & B target review
A confidential view across a partner-ecosystem long list, with AI-enriched research feeding each tier, risk flag, and recommendation.
Overview Master List 120 Company Detail Evidence & Audit
Reviewed
120
In universe
Priority A
14
Engage
Priority B
28
Qualify
Out of band
78
Excluded
Pipeline distribution · by priority tier
14
28
30
48
Priority A — Engage Priority B — Qualify Priority C — Watch Excluded
Master list · preview Filter · Priority Filter · Region Search
# Company Location Staff Priority Recommendation
01 Target 01 City · State 80–120 A · Engage Recommend · founder-owned · adjacent practice
02 Target 02 City · State 60–90 A · Engage Recommend · cybersecurity overlap
03 Target 03 City · State 40–60 B · Qualify Watch · multi-vendor · check ownership
04 Target 04 City · State 25–40 C · Watch Undersized for this band
2026 Working microsite

The Kellblog Companion

An unofficial, interactive companion to Dave Kellogg's writing on SaaS, marketing, and operating discipline. Built with explicit permission, the site turns selected Kellblog posts into chapters you can poke at, drag, and recompute.

Problem

A decade and a half of clear operating thinking sits as long-form posts. Operators rarely have time to read three thousand words to find the one decision lever they actually wanted.

What I built

A static microsite with two volumes and an appendix. Vol. 01 Marketing, Vol. 02 SaaS Metrics — Rule of 40, the Mendoza Line, the Magic Number, NRR, and the burn multiple, each as a calculator rather than a chart — plus a curated reading list. Every chapter cites the underlying post.

AI role

AI as research and authoring partner. Reading and clustering posts, drafting chapter summaries, designing the interactive calculators, and writing micro-copy. The judgement about what to surface, how to frame it, and what to leave out was the human work — and the author's review.

Current status

Private staging build, prepared for the author's review prior to public launch.

In review Authored permission Interactive microsite AI as authoring partner
Wireframe · Companion home · synthetic preview
The Kellblog Companion
An unofficial, interactive companion to Kellblog — Dave Kellogg's writing on SaaS, marketing, and operating discipline, turned into things you can poke at.
Library · Interactive
A growing library of operating wisdom, made tinkerable.

A curated, interactive reading of Dave Kellogg's body of work, turned into chapters you can poke at, drag, and recompute.

§ The Library
Two volumes, both interactive.

Each volume is a sequence of chapters — sliders, drag-and-drop, scrubbable charts — not an essay.

I.Vol. 01 · Marketing
Make sales easier.

What marketing is for, how to staff it across the four pillars, when to say no, and how to keep your job long enough to do the work well.

Enter Vol. 01 →04 chapters
II.Vol. 02 · SaaS Metrics
The numbers tell the truth.

Five interactive readings — Rule of 40, Mendoza Line, Magic Number, NRR, and the burn multiple. Each one is a calculator, not a chart.

Enter Vol. 02 →05 chapters
§ Appendix
One reading list, for the curious.

The marketing canon, the strategy canon, and the “don't read that, read this” corrections.

§ Appendix · The Reading List16 books · 4 posts
What Dave's been telling you to read.

Sixteen books, four posts. Sorted, annotated, with the Kellblog post that put each one on the list — plus a few “read this instead” corrections.

Open the reading list →
A glimpse of the shelf
01PositioningAl Ries & Jack Trout1981
02Ogilvy on AdvertisingDavid Ogilvy1983
03Crossing the ChasmGeoffrey Moore1991
04Good Strategy, Bad StrategyRichard Rumelt2011
2024 Concept paper

PartnerGrok read

A concept paper for an AI copilot for B2B channel teams, built around the idea of Synthesis AI — turning the operational complexity of partner ecosystems into something a channel team can actually navigate.

Problem

Partner teams operate inside a tangle of vendors, partners, programs, customers, and internal roles. The traditional partner-management playbook scales linearly. The complexity scales exponentially.

What I designed

A conceptual data model and capability layer for a partner-ecosystem copilot. Five capabilities — personalised journeys, real-time guidance, predictive analytics, enhanced collaboration, and ontology-powered intelligence — sitting on a stack from infrastructure up to the partner-facing interface.

AI role

Two-sided. PartnerGrok is itself an AI proposal — the case for what an AI copilot in this domain should actually do. AI also helped sharpen the framing, the data model, and the language that channel chiefs would recognise as their own.

Current status

Published concept paper. Open to a build conversation with the right team.

Concept paper Authored Channel ecosystems AI in B2B Data model
Wireframe · Concept stack · from the published paper
PartnerGrok · concept stack
Synthesis AI for channel management
InteractionWhat partners and channel teams see
Partner portal Mobile app Dashboard Chatbots Embedded UI
Integration & APISystem-of-record connectors
PRM CRM ERP Marketing automation 3rd-party APIs
Core AIThe synthesis layer
Personalisation Proactive guidance Predictive analytics Recommendations Ontology Insight surfacing
DataWhere signals live
Ingestion Processing Storage Partner taxonomy Event log
Infra & trustFoundation
Cloud Identity Access control Compliance Encryption
What it aims to do
  • i. EngagementPersonalised journeys for each partner persona.
  • ii. VelocityReal-time assistance to accelerate sales cycles.
  • iii. PerformanceData-driven coaching across the partner base.
  • iv. EfficiencySelf-service and process automation.
  • v. DecisionsInsight surfacing for channel chiefs.
04 / Pattern

Research, workflow, data, and decision artifacts.

The six projects above are different shapes of the same idea: AI works best when it sits underneath a thoughtful research and workflow design, and the output is a thing a team can actually decide on or use.

i. Research

Start with a real question.

Sovereign AI Vector and PartnerGrok start from real, fast-moving questions about how countries are approaching AI and how partner ecosystems actually run. The tooling came second.

ii. Workflow

Build the smallest system that survives use.

The team LinkedIn assessment and the M&A screening dashboard are small pipelines first — clear inputs, a review step, a structured output. No platform around them yet.

iii. Decision artifact

End with something a team can act on.

The Kellblog Companion and the VR walk-through end as artefacts a reader can poke at or step into. The shape matters less than whether it shapes the next move.

05 / Contact

Get in touch.

A short note is more useful than a form. A paragraph about what you are working on, and what would be helpful, is usually enough to tell whether there is a real conversation here.

Open to most ways of working: advisory, fractional, or full-time. The format matters less than the work.
Email [email protected] Writing ontopraxis.ai Sovereign AI sovereignaivector.com Based Houston, Texas · U.S. work-authorized