About
A studio that ships, run by someone who has to live with it
Apsan Works builds AI systems — agents, automations, and applications — for founders and operators who need software that works on the thousandth run, not just the demo.
The short version
Apsan Works is led by Chaim Apsan, based in Jerusalem and working with clients across Europe, North America and Israel.
The route here was not the usual one. It started on the growth side — SEO, content, paid acquisition, analytics — building and ranking sites for clients across a decade, and running products of our own. That work runs into the same wall repeatedly: the marketing is fine, and the bottleneck is a process nobody has built software for.
So we started building it. First internal tools, then complete products: a business-development platform for federal contractors, a geospatial monitoring service for planning applications, automated media pipelines, AI outreach systems. Real products with real users, billing, and the unglamorous operational work that comes with both.
That background shows up in how we scope. We tend to ask who is going to use this and how they will find it before asking what the architecture should be — which is an unusual order for an engineering studio, and it is the reason our builds tend to stay small.
Studio facts
- Based
- Jerusalem, Israel
- Working
- Remote, globally
- Languages
- English, Hebrew, Portuguese
- Engagements
- Fixed scope, fixed price
Background
- MSc International Management
Fundação Getúlio Vargas, Brazil - CEMS Double Degree
SSE Stockholm & HEC Paris - BSc Business Administration
Fundação Getúlio Vargas, Brazil
How engagements run
What working with us is like
Small by design
You talk to the person building the thing. There is no account layer, no handoff between the people who scoped it and the people who write it, and no incentive to staff a project bigger than it needs to be.
Fixed scope, fixed price
Discovery is a fixed-price piece of work that ends in an architecture and a real number. Builds run in phases with a price each, so there is a decision point at every boundary rather than an open meter.
Product-minded, not ticket-minded
We will push back on a requirement that will not survive contact with your users, and suggest the smaller thing that will. If you want a shop that builds exactly what the spec says, we are the wrong choice.
Handover as a deliverable
Your repository, your cloud accounts, your data, documented architecture and runbooks. Leaving should be easy. That is what makes staying a choice rather than a trap.
We are a good fit when
- You have a specific, painful problem rather than a general interest in AI
- You want the person who scoped it to be the person who builds it
- You would rather ship something narrow next month than something broad next year
- You want to own the result outright
We are not, when
- You need a large team scaled up quickly
- The requirement is a body to work through an existing backlog
- You want a fixed spec built exactly as written with no pushback
- The problem is genuinely solved by software you can buy today
Worth a conversation?
If the fit sounds right, describe the problem and we will tell you honestly whether we are the people to solve it.