I’ve built two startups, delivered projects for clients, and set up AI systems that do real work every day. Here’s what I made, how I did it, and how I can help.

I'm one of those people who wakes up at 4:30 am to work out, and I've done it for 16+ years. I can't count how many of those mornings I thought about how easy it would be to keep my eyes closed and go back to sleep. Every time, I decide it's not who I want to be. I want to be someone who keeps trying to achieve their goals and puts in the work to get there.
It taught me grit. No matter how many mistakes I make or how many times I fail, I keep trying. I won't say that if you keep trying, you'll eventually succeed. I always have two options: keep trying, or don't.
If we keep trying, we may or may not succeed. But if we don't, we will never succeed.
Say your mom's birthday is coming up and she lives in another country. You can ship the gift yourself, but then you're paying for shipping and waiting on delivery and customs. Or you can try to find a shop there yourself, site by site, in a language you might not read, and hope the payment goes through. And I kept thinking, okay, the right shop is already in her country, so why does the gift have to travel at all? So we built Flomaru. You pick the country, you browse its local shops in your language, you pay in your currency, and the shop delivers it there.

My AI work was spread across notes, scheduled jobs and automations that never talked to each other. So I thought: what if I can visually see the exact step-by-step process of all the different things that the AI is doing? Not only that, what if I can, in real time, see exactly what it's doing, when it's doing it, and be able to just visually keep track? Maybe that is the way that we should be managing our AI work.
How Vizi works. The steps in order:
How Vizi works, drawn on a Vizi board. The agent proposes, a person approves.
A lot of our sellers on Flomaru make really good products, but the only pictures they have are the ones they took on their phone. So I thought, okay, what if they just send us that one picture, and we give them back everything else? The studio shot, the lifestyle shot, the one for a birthday. The only rule: it still has to be their actual product.

Maki: the seller's own phone photo, and the images made from it.
Every new AI chat shouldn't need a fresh explanation of my company, my projects and what it's allowed to do. And I was explaining it every single day. So the idea was simple: the files are the brain, and any AI is just a worker. A new chat reads the map of the work first, then gets on with the job.

A sentence can be translated correctly and still sound wrong for the person reading it. Native speakers kept telling me a correct word-for-word marketing line still read like a translation. So Loci captures what the sentence is supposed to say first, then writes it for that market, and a person approves the exact version.
A newer B2B company can have something useful and still struggle to reach the person who can move the conversation forward. Some startups have a product that's close to a guaranteed close and still spend most of their time cold calling. So Coni skips all that: one useful call with the right person, not a long list of attempts.
Skills, workflows and automations I built so AI does real work for me every day. Here are four of them, and the board I drew for each one.
An AI that builds something will often tell you it's done, and I kept seeing “done” mean “I changed something”, not “it works”. So I had a different AI review it, against checks written for that change, and if it fails it goes back to the builder. A person still signs off.
Two AIs, one checks the other. The steps in order:
A month of design work with AI kept failing in the same ways, and I was guessing at fixes, changing three things at once. Then I wrote one rule down: find the causes from evidence. The skill runs that rule the same way every time. I planted defects on purpose to test it, and a checker with no AI in it found 93% of them in 13 seconds, with no false alarms.
Testing a way of working. The steps in order:
Wiring a design to real data is scary, and not because of the look. It's losing the look while the data goes in, and calling stuff “done” when it isn't. The approved design comes in unchanged, one worker takes one item, and a blind auditor checks it, round after round. On Vizi that was 547 screens, and all 547 matched the board.
Building to match a design. The steps in order:
My dashboards disagreed with reality. Web analytics said zero purchase events, and the payment processor only sees payments that go through, so it misses cancellations and abandoned checkouts. The fix was a live copy of the production database, and that's now the source of truth for orders. It also showed me three traps, like revenue added across currencies as if it was all one.
One live copy of the data. The steps in order:
Every one has its own page: the problem I was fixing, how it works and what it costs to run.
Here's what I built for a client, what I did on contract, and the client and research projects.
Someone needed a team to build a marketplace. Nobody had asked me.
I built this for a client. Someone was looking for a team to build a marketplace, so I reached out and won them as a client, and they paid. I scoped it first so we both knew what was in and what was out. Then I put a team together, ran the build and delivered the whole thing.
Team project. I led it.
Rogers wanted to figure out what else they could do, outside of connectivity.
This was contract work. Rogers brought me in to figure out what else they could do outside of connectivity. I can't say what the problem was or what came out of it, because that's Rogers' to share. The work went the way most consulting does: research, then ideas, then proof, then a deck. I wrote the hypotheses, designed the interview guide and the survey, ran the interviews, and built the deck.
Innovation consultant
I was the person Canada Post talked to.
Canada Post was our client, and our team worked with them directly. We agreed the scope, did the research and handed over a report they could use. I was the client liaison and the interviewer, and I ran the sessions with them. I can't say what the project was about or what we found, because that's Canada Post's to tell.
Team project. I led the client sessions.
I map the work, separate what needs judgment from what can be repeated, then build the tools around it.
I get a usable version in front of people early, then turn the decisions into a prototype or a clear build handoff.
Sometimes the answer is a build and sometimes it isn't. I research the problem before I recommend the next step.
I work through how people find the offer, understand it and get started.
I show your team how I plan the work, hand it to AI and check the result, so they can run it themselves.
That's the rule I work by. When I finish a piece of work I break it into its smallest steps and experiment with automating them, one at a time.
A system that's brilliant once and wrong twice is worthless. So nothing I build gets trusted on day one.
My work is half directing AI and half doing the things AI can't. I break the work into pieces, file them where my agents pick them up, and by morning it's done and reported back.