Founder profile
Founder and CEO of Adamant Code · Custom software, AI and automation for businesses outgrowing their tools
Luka Abramović is the founder and CEO of Adamant Code, a software company based in Rijeka, Croatia that works with established businesses across the US, UK and EU. He leads the team that helps those businesses connect disconnected systems, remove recurring manual work, and build the custom software and AI their operations depend on.
How Luka leads the work
Adamant Code is deliberately small. Clients get product judgment and engineering from one accountable team, and the founder stays involved from the first scoping conversation through release.
Luka runs the first conversation on every engagement. Before anyone writes code, the work is to understand the current process, weigh integrating, replacing or building, and say so plainly when custom software is the wrong answer.
The person who scopes the work stays the person answerable for it. Luka leads a small core team, so scope changes, trade-offs and bad news reach the client from the founder rather than a handoff chain.
Results are reported with the qualifiers attached: what was measured, what was estimated and what was not tracked at all. Every number on this site carries the method behind it.
Background
Luka trained as a marine engineer, finishing his degree in Rijeka in 2017 before going to sea as an engineering cadet. He taught himself to program in the hours off watch, working from books, courses and videos downloaded on a ship with around 10 MB of internet a day.
After roughly two and a half years in the maritime industry he moved into professional software development, and founded Adamant Code in 2023. He has led the company's product direction, client relationships and delivery since.
The engineering habit carried over: understand the system you are operating in before you change it, and make sure the person responsible can verify the result.
Selected work
Enterprise document intelligence for bid packages that can reach 5,000–50,000 pages, answering with source citations, page references and highlighted paragraphs.
Estimated 83% document-search time reduction, based on engineer interviews and client estimates rather than usage-log measurement.
Leelou AI, built around TNM's coaching methodology: multilingual text and voice, memory, accountability, HR reporting and guardrails across around 18 months and two major versions.
A product designed to support coaches, not to replace them or provide medical or therapeutic care.
A non-technical founder arrived with rough wireframes. The finished marketplace has 50+ screens, 15+ core workflows and a six-step AI invention workflow.
These figures describe delivery scope, not revenue or adoption.
A successful first build turned into a multi-year internal operations partnership supporting 44 internal users, 400+ connected properties and around 220k rows per day.
Scale figures for an anonymised repeat client, not measured savings.
Podcast appearance
TNM Unplugged, hosted by TNM Coaching · January 2026
Luka joined TNM Coaching's podcast to talk through the decisions behind Leelou AI: how architecture, data structures and behaviour design were shaped to extend what coaches do rather than imitate them, and what repeated coach-led testing changed in the product.
Writing
How the agency started, what separates useful AI work from a demo, and how to decide whether a business should integrate, replace or build.
Founder story · Medium
In his own words: learning to code on a container ship with 10 MB of internet a day, finishing the marine engineering cadetship before switching careers, and the road from there to running an agency.
Guest byline · Fiverr Community · May 2026
Written for Fiverr's community blog: the edge in AI work comes from judgment, workflow design and honest client communication, not from access to better tools.
Article · Adamant Code · September 2026
A decision framework for businesses outgrowing their tools, with the cases where connecting existing systems beats building something new.
Elsewhere
Luka takes the first call on every engagement. Bring one manual process, disconnected workflow or piece of software that is holding operations back, and you will get a straight read on what is worth doing next.