About

The people who design it are the people who build it.

One team, two countries, and the same agenda from the first conversation to the last deployment.

8

platforms built by our own team

20+

specialists across architecture, engineering, data and cloud

4

ways in, one method behind all of them

2

countries, no handoff

From the founder

Why there is a team.

I spent twenty years inside large regulated organisations watching the same thing happen. A good strategy, a well-run pilot, then nothing — not because the technology failed, but because the way the work happened underneath it never changed.

As an adviser you can name that problem precisely. Naming it was never what I wanted to do. I wanted to be accountable for fixing it.

Twenty people and growing — architecture, engineering, data, cloud, clinical and domain specialists. None of it gets designed alone. The team is in the room for the design, not only the build.

— Bijal Sejpal · Founder & CEO

Formerly Chief Operating Officer, Technology, Bupa Asia-Pacific (2025–2026). Formerly Group Chief Operating Officer, Data, Analytics and AI, QBE (2019–2025). Earlier: NSW Department of Customer Service, the ABC, NSW Police. MBA (Executive), AGSM.

Bijal Sejpal, founder and chief executive of Omameh

The founding team

One delivery team, two companies.

Architecture in Sydney, engineering in Hyderabad, no handoff. Omameh holds a minority stake in Syntegreti, our engineering partner — so where someone’s company is not Omameh, their title says so.

Jay Jayakeerthy

Jay Jayakeerthy

Chief Technology Officer

Co-founder, Syntegreti

LinkedIn ↗
Manish Davda

Manish Davda

Chief Commercial Officer, Platforms

Co-founder, Syntegreti

LinkedIn ↗
Karthik Jayaraman

Karthik Jayaraman

AI & Technology Lead

Syntegreti

LinkedIn ↗

The team

Small on purpose. Not small in the room.

One team across Sydney and Hyderabad, led from Sydney. Advisory is founder-led; the engineering is Syntegreti, our engineering partner. The people who sit in your solution design are the people who build it — same meeting, same specification, no translation layer.

AI / ML engineers Full-stack developers Cloud architects Data scientists Clinical specialists Domain specialists DevOps

Build first, pitch second

We build a working proof and let the result decide.

Everyone ships

The person who talks to you on day one deploys it later.

Stay small, go deep

We would rather go further into fewer problems.

Own the outcome

Nothing is handed off.

And who we work with

Three directions, and we say which one applies.

We deliver for them

Platform vendors with customers in Asia-Pacific and no team here. We stand up the delivery and hold it with one engagement lead.

We carry each other's software

Their products into Asia-Pacific, ours into the US, UK and Europe. Where the software is not ours, we say whose it is.

We are someone else’s bench

For firms that own the client and have no engineering. You keep the client, the contract and the credit.

We do not take every partner. It has to sit inside one of the five pillars, be complementary rather than competing, and be a product we would put our own name next to. We have said no.

Where we play

Deep where it is regulated. Open where it is not.

Enterprise work concentrates in regulated, complex industries — that is where we started and where the lens is sharpest. Everything else, we take on any field.

Banking, financial services & insurance

APRA · ASIC · AFCA

Healthcare & clinical

TGA · ADHA · State health

Government & public sector

Commonwealth · State

Technology & operations

Sector-dependent

Everyone else · any field. Owner-led businesses, platform vendors and independent operators come to us from every industry there is. A roadmap that will not scale looks the same in construction as it does in law.

The work

We are the first case.

Everything on this site, we did to ourselves first — and in this order.

01 · Advisory

Positioned it

The practice, the brand, the legals, the architecture underneath. Before a single client, the thing itself had to be designed.

02 · The bench

Built the team

Engineering, deliberately — because advice you cannot deliver is only a recommendation.

03 · Fluency

Made it teachable

If it only works when we are holding it, it is not a method.

04 · Products

Built the products

Two in market, each its own company with its own customers — and we run the business on one of them.

What people ask us

The questions we actually get.

These are the awkward ones, so they are the ones on the page.

Enterprise

What happens when you leave?

Your team runs it. That is the whole design — we build with your people rather than around them, and the handover is a phase with a date on it, not a document at the end.

Owner-led business

We can’t afford a transformation.

You do not need one. We find the single thing that will return the most, fix that, and stop. You decide whether there is a second one.

Platforms

Why would we hand our customers to you?

You keep them. The relationship, the contract and the invoice stay yours — we are the delivery team behind you, and we appear only when you want us to.

An idea of your own

Who owns what we build?

You do. Written in before the first line of code, not negotiated at the end.

Everyone, quietly

How big are you?

One delivery team, two companies. Architecture in Sydney, engineering in Hyderabad, no handoff. You get the people who designed it, and a bench that does not have to be recruited first.

And the one nobody asks out loud — have you ever told a client to stop?

Yes, more than once. We would rather protect your budget than protect our next phase. It is the same reason our clients come back.