Engineering · Embedded finance
Consequential systems
Publicly documented principal engineering work and writing from the perspective of an original CorePro engineer at Helix by Q2.
Review the sourceTalks, advisory, and technical conversations
Start with the problem.
I enjoy giving practical 30-minute talks that help technical and leadership audiences understand what is changing and what to do next. I also welcome focused advisory work and serious conversations about complex engineering and applied AI problems.
Speaking
A useful 30-minute rundown.
The best talks give people a clear model of what is changing, working examples they can inspect, and a few decisions they can make next. I adapt the material to the audience instead of delivering a generic transformation pitch.
The exact topic can follow what is most useful to the room and what is changing now.
Useful formats
- A 30-minute company or leadership briefing, with optional Q&A.
- A conference or community talk grounded in working examples.
- An applied AI or agent-systems session for technical teams.
- A practical look at moving from experiment to reliable engineering practice.
A short note with the audience, timing, and question you want the room to understand is enough to begin.
Focused advisory
Help around a real decision.
I occasionally help leadership teams frame an applied AI decision, review the path from prototype to production, or build shared language around a technical shift.
The useful shape is narrow and concrete: a working session, an independent review, or a briefing built around a live technical choice.
Useful engagement shapes
- An executive or engineering leadership briefing.
- A focused working session around a live decision.
- An independent review of an AI initiative or operating approach.
- A prototype-to-production review grounded in the system at hand.
These conversations are scoped around a specific decision, audience, or session. I don’t sell a prepackaged transformation program.
Technical conversations
Serious problems are worth a conversation.
I’m always glad to hear from people working on complex engineering and applied AI problems. A short note about the problem, the people involved, and why it matters is enough.
The best conversations start with context rather than a polished pitch.
Public evidence
Start with work you can inspect.
The site is the supporting record: published technical judgment, public talks, community work, and systems built in the open.
Leadership · Public briefing
Emergencing Trends with AI
A DMACC leadership-session record focused on making emerging capability understandable and actionable.
View the talkCommunity · Build receipts
Into AI build sprints
Public challenges where builders shipped work, shared evidence, and learned in the open.
Explore Spring Into AIApplied AI · Working systems
Research and field work
Experiments, evaluations, agents, model training, and technical notes preserved with their context.
Explore selected workContact
Bring the problem, not a polished pitch.
A short note with the audience or problem, the people involved, and what a good outcome would change is enough to begin.