Own tooling, in daily use
An orchestration console for running AI work
The console I built and use to run and monitor AI agents and workflows across my own projects — sessions, tasks, and tool calls, all in one place. If your team is drowning in tickets, queues, or manual hand-offs, this is the same kind of system I'd build to run that instead.
Delivered, in use
An interactive tool, built for the browser
A browser-based interactive tool I built for a leadership-development practice — people work through it together in real time, no download or install. The same approach works for any process your team or your customers currently do by hand or on paper. I turn it into something people can actually use together, instantly.
Design & build
My own business site, front to back
Designed and built end to end for my own business — same craft I’d put into yours.
Real, ongoing
685 tools built. Still shipping.
685 custom scripts and tools I’ve built to run my own business and client work through AI, and 331 real commits on a paid client project alone — still receiving updates the day this was captured. Real, checkable numbers, not adjectives. This is the same muscle behind server management, integrations, and the specific, one-off problems most businesses just learn to live with because nobody offers to fix them.
Built together, ongoing
A landing page for an executive-coaching practice
Editorial marketing design I helped build for an executive-coaching practice I've worked alongside for years now, not a one-off job, polished enough to earn trust before anyone books a call. The same discipline goes into every site I design, whether it's the front door to an ongoing partnership like this one or your own business's first impression online.
Built together, ongoing
A landing page for a wellbeing platform
A calm, editorial landing page for a wellbeing and membership platform I've been building alongside its founder for months, not a one-off job, meant to make a first-time visitor feel invited in, not sold to. If your business's first impression online still reads like a sales page instead of an invitation, that is the tone I'd build for yours too.
Built together, ongoing
The architecture behind a working AI coach
A real AI implementation for an executive-coaching practice: one shared AI that a client can reach through text chat, a voice-and-video coaching session, or a guided assessment, all reading from and writing to the same living document so the coaching stays consistent no matter which channel someone is in. I designed this architecture and built the layer underneath it, working alongside the practice's own founder rather than delivering a spec and moving on, and I am still hardening it in production, the way real systems actually get built. This is what implementing AI into an existing business looks like: not a demo, a working system with real edge cases. If your business is past the demo stage but the AI still feels bolted on instead of built in, this is the kind of work that fixes it.
Built for a client, delivered
A client portal, built to replace a manual process
A construction company used to review every job by hand, back and forth over email, every time. I built them a portal that just handles it now, paid, live, and in daily use. No off-the-shelf product did this job, so I built the specific tool that did. Most real problems look exactly like this: not a market gap, just one process quietly costing your business time every day that nobody has built the fix for yet.
Built together, ongoing
A platform built together, not handed over
Some of the best work I do isn't handed to me as a finished brief. It's built alongside the person whose business it actually is, shaping what a real-time wellbeing and membership platform becomes together, over many months, not one project with a defined end. I'm not executing someone else's spec here, I'm a partner in what gets built and how. If what you actually want is someone who thinks with you and stays past the first delivery, not just someone who ships one thing and moves on, this is what that looks like.
Image coming soon
A real status panel from Ethan's own monitoring output
Own tooling, running unattended
A back office that runs itself
The systems that run my own invoicing, deployments, and monitoring do not wait for me to check on them. They report in on a schedule, catch their own failures, and fix or flag problems before I'd ever have to go looking. This is the same kind of unattended, self-checking backend I would build behind your business, so things keep running correctly on the days nobody's watching.
Own tooling, in daily use
An orchestration console for running AI work
The console I built and use to run and monitor AI agents and workflows across my own projects — sessions, tasks, and tool calls, all in one place. If your team is drowning in tickets, queues, or manual hand-offs, this is the same kind of system I'd build to run that instead.
Delivered, in use
An interactive tool, built for the browser
A browser-based interactive tool I built for a leadership-development practice — people work through it together in real time, no download or install. The same approach works for any process your team or your customers currently do by hand or on paper. I turn it into something people can actually use together, instantly.
Design & build
My own business site, front to back
Designed and built end to end for my own business — same craft I’d put into yours.
Real, ongoing
685 tools built. Still shipping.
685 custom scripts and tools I’ve built to run my own business and client work through AI, and 331 real commits on a paid client project alone — still receiving updates the day this was captured. Real, checkable numbers, not adjectives. This is the same muscle behind server management, integrations, and the specific, one-off problems most businesses just learn to live with because nobody offers to fix them.
Built together, ongoing
A landing page for an executive-coaching practice
Editorial marketing design I helped build for an executive-coaching practice I've worked alongside for years now, not a one-off job, polished enough to earn trust before anyone books a call. The same discipline goes into every site I design, whether it's the front door to an ongoing partnership like this one or your own business's first impression online.
Built together, ongoing
A landing page for a wellbeing platform
A calm, editorial landing page for a wellbeing and membership platform I've been building alongside its founder for months, not a one-off job, meant to make a first-time visitor feel invited in, not sold to. If your business's first impression online still reads like a sales page instead of an invitation, that is the tone I'd build for yours too.
Built together, ongoing
The architecture behind a working AI coach
A real AI implementation for an executive-coaching practice: one shared AI that a client can reach through text chat, a voice-and-video coaching session, or a guided assessment, all reading from and writing to the same living document so the coaching stays consistent no matter which channel someone is in. I designed this architecture and built the layer underneath it, working alongside the practice's own founder rather than delivering a spec and moving on, and I am still hardening it in production, the way real systems actually get built. This is what implementing AI into an existing business looks like: not a demo, a working system with real edge cases. If your business is past the demo stage but the AI still feels bolted on instead of built in, this is the kind of work that fixes it.
Built for a client, delivered
A client portal, built to replace a manual process
A construction company used to review every job by hand, back and forth over email, every time. I built them a portal that just handles it now, paid, live, and in daily use. No off-the-shelf product did this job, so I built the specific tool that did. Most real problems look exactly like this: not a market gap, just one process quietly costing your business time every day that nobody has built the fix for yet.
Built together, ongoing
A platform built together, not handed over
Some of the best work I do isn't handed to me as a finished brief. It's built alongside the person whose business it actually is, shaping what a real-time wellbeing and membership platform becomes together, over many months, not one project with a defined end. I'm not executing someone else's spec here, I'm a partner in what gets built and how. If what you actually want is someone who thinks with you and stays past the first delivery, not just someone who ships one thing and moves on, this is what that looks like.
Image coming soon
A real status panel from Ethan's own monitoring output
Own tooling, running unattended
A back office that runs itself
The systems that run my own invoicing, deployments, and monitoring do not wait for me to check on them. They report in on a schedule, catch their own failures, and fix or flag problems before I'd ever have to go looking. This is the same kind of unattended, self-checking backend I would build behind your business, so things keep running correctly on the days nobody's watching.