Consulting Practice
This practice focuses on making AI-assisted systems reliable enough to ship. The work is usually a mix of architecture review, control-plane design, agent workflow hardening, and implementation planning.
Engagements are through 17752709 Canada Inc. and are strongest when there is already a real workflow, product surface, or internal automation to inspect.
Typical Conditions
- Coding agents, workflow agents, retrieval, routing, or AI-assisted operations are already attached to a real team or product.
- Boundaries around approvals, permissions, audit trails, handoffs, rollback, or operator visibility need to become clearer.
- Existing system context is available to inspect: repositories, architecture notes, workflow traces, incidents, prompts, task queues, or deployment constraints.
- The useful output is a practical implementation sequence rather than a generic AI strategy deck.
Common Engagements
| Engagement | Best for | Typical shape |
|---|---|---|
| AI Agent Readiness Review | Teams about to rely on agents in engineering or operations | Written review, risk map, and prioritized next steps. |
| Control-Plane Audit | Teams with live automations, queues, routing, or review overhead | Architecture readout, failure-mode analysis, and implementation sequence. Scoped to the system. |
| Embedded Advisory | Founders or engineering leads making repeated AI architecture decisions | Recurring review, decision support, and implementation guidance while the system is moving. |
What Advisory Includes
- Review of the current system, repo structure, operational docs, and active workflows.
- Identification of brittle boundaries: permissions, tool access, review gates, stale knowledge, missing observability, and unclear ownership.
- A written implementation sequence with the smallest useful changes first.
- Optional build support after the architecture read, when the problem is scoped enough to execute cleanly.
Not A Fit
- Consumer app idea validation with no built surface yet.
- Generic prompt-pack or chatbot setup work.
- Unreviewed investment, tax, securities, or fundraising advice.
- Open-ended "make us use AI" requests without a concrete workflow or decision surface.
Working Boundaries
The work begins with a bounded system read rather than an open-ended sales call. A useful starting packet contains:
- The system or workflow under review.
- What is currently breaking, slowing down, or becoming risky.
- Links to any public docs, repo context, architecture notes, or product surfaces.
- The expected mode: review, build sprint, or ongoing advisory.
A short review usually comes before implementation work. That keeps the scope honest and produces a concrete basis for deciding whether further work makes sense.