About us

Built by people who've
lived inside engineering systems.

Most organisations can measure activity. Far fewer can diagnose whether their operating model is still serving the way software is actually being delivered.

Samix was built to close that gap.

Why we exist

If every team is busy, why isn't value moving?

We've both sat in rooms where every dashboard looked healthy — capacity utilised, tickets moving, sprints closing — and yet value still wasn't being delivered at the pace of all that activity.

The problem usually isn't effort. It's the system.

Teams optimise locally around their own goals, queues, workflows, and definitions of done. But very few organisations can see whether those optimisations are helping value flow across the broader engineering system. When every team is at capacity but delivery remains slow, the constraint is often structural.

That gap shows up in patterns every engineering leader recognises, but rarely has the data to properly diagnose.

"The native mobile team is holding everyone back" — but are they actually the bottleneck, or are they absorbing late-stage design changes that create expensive rework just before release?

"The developer team is blocked on design" — but is design really the issue, or are leadership decisions arriving too late in the cycle?

Anecdotal feedback points at teams. System data points at dynamics.

We see the same pattern emerging with AI adoption. Teams adopt the tools. Token spend increases. Individual output accelerates. But organisational value still doesn't move proportionally — because AI amplifies local productivity without necessarily changing the structural relationships between teams. If the review bottleneck already exists, AI simply helps organisations reach it faster.

Traditional engineering dashboards struggle to surface these dynamics because they're designed to measure teams and individuals in isolation, not the dependency relationships between them. A platform team at 100% utilisation can appear healthy on paper — it's only when they're the critical reviewer for eight other teams that the systemic constraint becomes visible.

As delivery evolves, leaders need visibility into how the entire system is moving — not just whether each individual part appears busy.

Our focus
Structural delivery bottlenecks

Identifying where the system, not the team, is the constraint.

Workflow friction

Understanding where work slows, stalls, or gets absorbed into the wrong coordination paths.

AI adoption outcomes

Helping teams adopt AI effectively and understand its operational impact.

Operational governance

Strengthening the systems that keep delivery aligned as organisations scale.

The team
MH

Mica Huynh

Co-founder

Mica has spent her career inside large-scale engineering organisations, leading operational systems that support engineering delivery at scale. At Block — across Cash App, Square, and Afterpay — she worked at the intersection of engineering operations, AI adoption, and operational governance. Her experience spans engineering effectiveness, customer-centric telemetry, operational visibility, resilience practices, and organisational systems design. She has seen firsthand what structural bottlenecks look like inside complex engineering environments — and what it costs when organisations cannot clearly see them.

Engineering operationsAI adoptionOperational governanceEx-Block
SK

Sam

Co-founder

Sam is an engineering, AI, and product executive with experience across technical strategy, product leadership, and applied AI systems. His background spans engineering leadership, machine learning, and product development — bringing both diagnostic rigour and practical execution thinking to Samix.

AI & machine learningEngineering leadershipProduct

See your system in two minutes.

Connect a repo, explore with demo data, or book time with us.