The Story Behind Failatech
Built on obsession.
Refined by discipline.
Failatech is a founder-led software studio. The passion for code was always there — pharmacy school was just the years it had to survive through. What came out the other side was a combination that's genuinely hard to find: technical depth, pharmaceutical precision, and an entrepreneurial instinct that makes it almost impossible not to get the job done right.
What Makes the Difference
Three things that are
rarely in the same room.
Pharmaceutical training instils a standard for accuracy that doesn't leave you. In clinical settings, a small error has real consequences — that awareness carries into every system we design, every data model we define, every edge case we anticipate before it becomes a problem.
This was never a career change or a late discovery. The interest in code and data systems has been constant — through years of demanding scientific training, through building late at night when the coursework was done. It is the original obsession, and the thing that drives the standard of work we hold ourselves to.
We don't think in tasks and deliverables. We think in problems, users, and outcomes. The drive to build things that compound — not just things that work — shapes how we approach every project. It's why we ask uncomfortable questions before we write a single line of code.
The Journey
Code. Science. Entrepreneurship.
In that order.
The Beginning
Code Was Always the Plan
The fascination with software started early — how systems are built, how logic becomes something a person can actually use, the quiet satisfaction of making something run. That curiosity became practice long before any university application was filled in. Writing code was never a career discovery. It was just what felt natural.
Pharmacy School
Five Years That Couldn't Change It
Pharmacy is demanding in a way that's hard to explain from the outside. The science load, the clinical placements, the non-negotiable accuracy required at every step. There were stretches where building software felt like something to get back to, not something to do right now. But the interest never left — it just waited. What pharmacy training added was unexpected: a standard for precision that transfers directly into engineering. In clinical settings, errors have consequences. That awareness never goes away.
First Products
Building Real Things
The first real products came alongside and after pharmacy training — hubby projects, internal tools, healthcare utilities, inventory systems. Each one closed the gap between textbook knowledge and the messiness of what users actually need. The healthcare background opened doors to problems that needed solving but had no one with both domain knowledge and technical ability to solve them.
2023 — Present
Founding Failatech
Failatech was founded not as a consultancy or an agency but as a studio — a place where software is built with ownership, not just execution. The goal was never to rent out hours. It was to build things that compound.
The Team
Small by design.
Deep where it counts.
We are a lean, focused studio — not a body shop. Every discipline is covered by people who specialise in it, working closely under a single standard of quality.
Founder & CEO
Pharmacist · Engineer · Builder
Founder's Note
I was writing code before I enrolled in pharmacy school, and I never stopped. The five-year programme was the hardest thing I've done — there were stretches where building software felt like a luxury I couldn't afford. But the interest never went away. I found time between pharmacology papers and clinical rotations to keep building, keep learning.
What I didn't expect was that pharmacy would make me a better engineer. The standard of accuracy required in clinical settings — the awareness of what a mistake actually costs, the discipline of checking and rechecking — that never left. It's in how I approach every data model, every system boundary, every edge case I anticipate before it becomes a problem.
"The discipline, the passion for data and programming, and an entrepreneurial drive that refuses to settle for good enough — those three things together make it almost impossible not to get the job done right."
Our Teams
Backend Team
APIs, databases, server architecture, and the infrastructure that keeps products running reliably — built to scale without drama.
Frontend Team
Interfaces that are fast, accessible, and feel right to use. Every component built with the end user in mind — not the design file.
Mobile Team
Cross-platform iOS and Android applications with native-quality performance, offline capability, and real-world connectivity in mind.
Data & Analytics Team
Scraping, cleaning, modelling, and structuring data — turning scattered information into something reliable, queryable, and ready to act on.
Automation Team
Mapping workflows, eliminating manual steps, and building AI-assisted pipelines that run without supervision and fail loudly when something needs attention.
Our Stack
We pick the right tool for the job
Ready to build something
that actually matters?
Every great product started as a conversation. Let's have ours.
Let's Build Something