About
Founded in 2017. Still run by the person who started it.
I started Isenbrook after years on the buying side of software projects, watching capable teams ship the wrong thing. The fix I wanted was simple: talk to the engineers, write the decisions down, and see working software every week. That is the company.
What we believe
Four things we hold to.
Scope by what we leave out
A scope lists what the system will not do as clearly as what it will. Most arguments on a project trace back to something nobody wrote down.
Prove it with a number
An AI feature without a baseline and an evaluation is a guess. We do not call it working until it beats the number it was meant to beat.
Build what we would run
We operate the systems we ship, so we build them the way you build something you expect to be paged about.
Say the awkward thing early
If the right answer is to buy a product, build less or not build at all, you hear it on the first call. It costs us work sometimes and keeps clients for years.
The people
The people on the work.

Arslan Javed
Founder & Chief Executive Officer
Arslan founded Isenbrook to build the kind of software he wanted to buy and could not: systems designed around how a business actually runs, shipped by engineers you can talk to directly.
- Scoping and architecture
- Client relationships
- Engineering standards
Priya Natarajan
Head of AI Engineering
Priya leads the team that builds and evaluates every model we ship, and wrote the evaluation framework we use on all AI work.
- AI delivery
- Model evaluation
Tomasz Wróbel
Head of Platform
Tomasz owns infrastructure, pipelines and on-call, and has a strong opinion about every alert that pages a human.
- Infrastructure and pipelines
- On-call and reliability
How we work
How an engagement actually runs.
Five steps, with the person responsible named on each, because you are hiring people rather than a process diagram.
- 01
A scoping call, not a sales call
Arslan Javed · Chief Executive OfficerArslan takes the first call himself. You describe the problem; he asks about the process around it, who touches it, what breaks today and what a fix would be worth. If the honest answer is that you should buy something or build nothing, you hear it before any proposal.
A written scope you can take anywhere, before any price.
- 02
A direct line to the engineers
From the first week you share a channel with the people writing the code. Questions go to the person who knows the answer and come back the same day. Nobody sits between you and the work.
No account managers. The builders are your contacts.
- 03
Hard decisions first, in writing
Arslan Javed · Chief Executive OfficerStack, data model, integrations and the limits of any AI are settled before feature work starts. Each choice is recorded with the reasoning and the alternatives we rejected, so the next engineer, yours or ours, can see why it is the way it is.
An architecture record that belongs to you.
- 04
Working software every week
A short demo of running software, never slides, every week there is something to show. A wrong turn costs hours to fix in week two and weeks to fix in month three, so you see everything early.
You see the system as it is, not as it will be.
- 05
We stay after launch
Arslan Javed · Chief Executive OfficerMost systems get a second phase. We operate what we build, watch the monitoring and keep the same team on it, so the person who answers a question in year two is the one who wrote the code in year one.
Same engineers, for as long as you need them.
Not ready for a call? Astra will give you a first opinion on what to build, with no form to fill in first. Or write to hello@isenbrook.com.
Where we work
Six countries, 21 cities.
Each engagement is staffed to the client's working day, wherever that is.
Tell us what is slowing you down.
A short call is usually enough to say whether this is work we should do together. If it is not, we will tell you and suggest who else to talk to.
Or reach us directly: hello@isenbrook.com · +1 555 010 0199