Bring us the hard one.
We start two to four new partnerships a year. The rest of the year belongs to the partners who stayed. Tell us what the business needs to win and who owns it on your side. If it fits, a First Build starts within weeks, at a fixed price.

"I read every one of these myself. You will hear back within two working days, in writing, even when the answer is no. The first call is with me or our CTO."
Milos Zikic, Founder & CEO
Looking for a job? See open positions
What happens next
From one message to a working slice.
One conversation
What the business needs to win, who owns it on your side, what you have tried. A founder reads your message, and the first call is with a founder or our CTO.
A working slice
About a month on your real data or your real device, measured against criteria you sign off in week one. Not a deck. Not a prototype on sample data.
The plan and the price
The architecture, the evidence plan where a regulator is in the loop, and a fixed quote for what comes next.
Your decision
The slice, the architecture, and the plan are yours whether we continue or not. If you go on to the next stage, the First Build is credited against it. Every partnership that lasted began this way.
Before you write
What founders and executives ask us first.
What kind of companies do you partner with?
Companies with a real product and a real constraint: hardware, data, regulation. Device and medtech companies, IoT and access-control firms, operators and industrials turning hardware into platforms, and founders who have been burned before and know exactly what they do not want. Healthcare, mobility, IoT, and connected industry are where we have worked the longest.
What does working together look like?
We sit with the founders and executives, ask the hard questions before anyone writes code, own the result, set the direction together, and measure what the product does in the world. Product, design, engineering, and AI work on one roadmap, and every product we touch learns to monitor, predict, and decide.
Will you work with our in-house team?
Yes. Most of our partners have engineers of their own. We work beside the people who own the product on your side, on one roadmap. When your team is ready to take part of the work back, we hand it over cleanly. The IP is yours from day one.
Which AI models do you use?
Whichever the product and the regulator allow. We are not tied to one lab, so the choice follows your data, your costs, and where that data is allowed to live.
What does an engagement cost?
Every partnership begins with a First Build: about a month at a fixed price, ending in a working slice, the architecture, and a fixed quote for the next stage. First Builds start at $100K. Everything after is quoted from what the First Build shows.
Can you work under our quality system?
Yes. We work inside your quality system and follow your procedures, and every record lives where your Quality team can audit it: the repositories, the tickets, and every test run.
How fast can you start?
When a slot is open, a First Build starts within two to three weeks of the first call. When it is not, we tell you when the next one opens.
What if the fit is not right?
We will tell you, and we will tell you why. If a First Build does not show a path to a product worth owning, you keep the working slice, the architecture, and the evidence plan. Ongoing partnerships end on ninety days' notice, either way, and the IP is yours from day one.
What should I put in the message?
Three things. What the business needs to win, in a sentence. Who owns the product on your side. What you have tried before and what it cost. If a regulator or a device is in the loop, say which. Nothing confidential is needed for the first message; if you want an NDA before the detailed call, we sign yours. That is enough for us to answer within two working days.
A founder reads every message. Expect a written answer within two working days.

