Morgan Labs is a one-person shop. I pick real problems, build focused software to solve them, and ship fast. No bloat, no committee, no roadmap theater.
Two focused tools, two completely different problems. That's the point.
Local service businesses lose jobs to missed follow-ups — not because they don't care, but because they're busy doing the actual work. LeadClaw is a lightweight CLI that shows you who to call today, drafts the follow-up text, and keeps your pipeline visible. No CRM subscription. No sales team required.
View on GitHub →Velocity-Based Training tells you how hard you're actually working — not by reps or weight on the bar, but by how fast it moves. The problem: the hardware that does this costs $2,000+. VeloBar does it with your phone camera. Point it at the bar, hit record. YOLOv8 tracks the bar path, segments every rep, and reports concentric velocity in real time. Built for home gym athletes who train seriously but don't have a sports science budget.
Follow the build →Something new is always on the bench. The rule: it has to solve a real problem I've personally run into, and I have to be able to ship a working version before the idea gets boring. Check back, or reach out if you have a problem worth solving.
Pitch me a problem →I'm Morgan. I build software because I keep running into problems that don't have good solutions — or have solutions that are way more expensive and complicated than they need to be.
The method is simple: find a problem I understand well enough to solve, build the smallest thing that actually fixes it, and put it in front of real users as fast as possible. No pivots, no feature sprawl. If it's useful, it grows. If it's not, I learn fast and move on.
Morgan Labs is the umbrella. The projects are the point.
The fastest way to know if something is worth building is to put it in front of a real person. A working v0 beats a perfect wireframe every time.
Feature bloat is how good tools become bad ones. Every decision starts with: does this make the core use case better, or is it just interesting?
Accountability is a feature. If I'm building something, I talk about it. The process is as useful to share as the product.
I write the code, make the decisions, and talk to the users. The overhead stays low because it has to — and because it should.