Skip to content
The team

Small by design, senior by default

Two practitioners covering the whole span of an engagement — the business analysis that works out what should be built, and the engineering that builds it. The people you meet on the first call are the people who do the work.

Role
CEO
Background
Banking
Discipline
BA & project management
Chief Executive Officer

Michael Manabat

Decades of business analysis and project management in banking — translating operations into systems that hold up under scrutiny.

Michael has spent decades as a business analyst and project manager in the banking industry — an environment where a vague requirement or a missed dependency is not a bug ticket but a regulatory problem. That work is fundamentally about listening to how a business actually runs, separating what people say they do from what they do, and turning it into something a delivery team can build against.

He leads 3rdLoop's discovery and consultancy work: mapping workflows, pinning down the one metric an engagement has to move, and writing the target-state architecture and roadmap clients take away at the end of week two. Banking taught him to be sceptical of scope that hasn't been interrogated, which is why our engagements start with a fixed-price discovery rather than a proposal.

It also means the commercial conversation stays honest. Michael is the one who will tell a client that a feature they've budgeted for won't pay off, or that the timeline they want isn't the timeline they'll get.

Owns

  • Client discovery and stakeholder interviews
  • Operating model and workflow design
  • Roadmaps, estimates and risk registers
  • Commercial scope and engagement structure

Expertise

  • Business analysis
  • Project management
  • Requirements engineering
  • Banking & financial services
  • Process mapping
  • Stakeholder management
Role
CTO
Engineering
15+ years
Applied AI
2+ years
Chief Technology Officer

Jehnsen Enrique

15+ years building software and API integrations, 2+ years in applied AI — the architecture and codebase behind every system we ship.

Jehnsen has been writing software professionally for over fifteen years, with a long specialism in API integration — the unglamorous work of making systems that were never designed to talk to each other exchange data reliably. That background shapes how 3rdLoop approaches automation: most of the value isn't in a new interface, it's in the plumbing underneath it that has to not fail at 2am.

For the past two years he has worked as an applied AI engineer, building retrieval-augmented assistants and document-processing pipelines. His position on AI is deliberately unfashionable: it belongs in a system only where it beats a deterministic alternative, and it needs an evaluation harness before it goes near a customer. Several of our engagements have ended with us recommending a plain pipeline instead of a model.

He owns the technical side end to end — architecture design, the codebase, code review, infrastructure and the engineering standards the team builds to. Every product in our catalogue runs on architecture he designed.

Owns

  • System architecture and technical design
  • Codebase ownership and code review
  • API integration and data pipelines
  • Applied AI: RAG, evaluation, guardrails
  • Infrastructure, CI/CD and deployment

Expertise

  • TypeScript
  • React & Next.js
  • Node.js
  • Python
  • API integration
  • System architecture
  • RAG & LLM applications
  • PostgreSQL
  • Cloud infrastructure

What working with a team this size actually means

01

Two people, no handoff gap

The person who runs discovery and the person who designs the architecture are in the same conversation from week one. Nothing gets lost being translated between an advisory firm and a delivery shop.

02

Senior people on the actual work

You are not pitched by principals and then handed to juniors. The people you meet are the people who do the work — that's the direct consequence of staying small.

03

Deliberately limited concurrency

We cap how many engagements run at once. It costs us revenue and it's the reason we can say what our timelines actually are instead of what you want to hear.

Talk to the people who'll do the work

The first call is a free 30-minute conversation with both of us — no account manager in between, no deck.