Samuel Bearg
Platform & Cloud
Fifteen years leading infrastructure and platform strategy, and currently Head of IT at rHEALTH. Samuel keeps what we ship production-grade — secure, observable, and ready to scale before it has to be.
About
The engineer behind the work.
Alacrity is a small studio, not an agency floor. The person who scopes your workflow is the person who builds it — and who does this same work in production every day.
Founder
Leif Taylor.
Alacrity is founded and run by Leif Taylor, a principal engineer with a decade of production engineering and platform architecture — from shipping a 0→1 AI platform as a CTO to customer-embedded work with large enterprises. His days are still spent building software that carries real production load.
That is the vantage point Alacrity is built from. Most AI work fails not in the demo but in the six months after it — when the edge cases arrive, the data drifts, and the system meets people who did not build it. Someone who lives in production systems knows where those failures come from, and designs for them before they happen.
The team
A small bench, deep where it counts.
Alacrity stays intentionally small — senior people who ship, not a layer of account managers between you and the build. The people below are who you actually work with.
Laura Agudelo Osorio
Marketing & Business Development
Leads partnerships and growth — translating what enterprise teams actually need into AI work that earns its keep. Your first conversation with Alacrity often starts with Laura.
Kendall Anderson
Data Science & AI Alignment
Focuses on making models behave — evaluation, accuracy, and alignment — so the systems we put in front of your users stay trustworthy under real-world load.
Why this matters to you
What a principal engineer brings to AI work.
No handoffs to hide behind.
Strategy, product, architecture, and the code are the same person. Nothing gets lost in translation between a slide deck and the team that has to make it real.
Production is the default.
The instinct is not to reach the demo — it's to survive the shift after launch: measurement, failure modes, and human review designed in from the start, not bolted on later.
Honest about the fit.
Sometimes AI is the wrong tool, and you should hear that early. The value is in scoping the leverage point correctly, not in selling the largest possible build.
The studio
Small on purpose.
Staying small is a deliberate choice, not a stage to grow out of. It keeps senior attention on every engagement and keeps the work grounded in systems that actually ship — including a few Alacrity built and runs itself.
The clearest way to judge a studio is by what it has put into production. That's what the work page is for.
Start here
Tell us about the workflow.
A few sentences is enough. We'll reply within a business day with an honest read: whether AI creates leverage there, and what it would take to ship.
Replies come from [email protected]