Day job
Leading AI adoption at Lendi
Company-wide rollout. Strategy, tooling, training, KPIs. The unglamorous work of moving an org from 'we should do something with AI' to 'this is how we ship now'.
8.5 years at Lendi - frontend developer, then lead, then R&D, now AI Manager & Builder. My mandate: redefine the role of the engineer - from feature-shipper to product builder - and prove it ships. On the side I'm building jasne.ai.
Company-wide rollout. Strategy, tooling, training, KPIs. The unglamorous work of moving an org from 'we should do something with AI' to 'this is how we ship now'.
A vertical AI product. Solo, end-to-end. Vendor-agnostic stack. The proof that the model I sell at Lendi works in the wild.
Notes, essays, internal memos. What the engineering role becomes when AI is the default collaborator - and what hiring, performance, and team shape look like next.
Most "AI managers" arrive at AI from outside the company. I arrived from inside - eight and a half years of shipping the product, leading the team, and watching what actually breaks. That history is the leverage.
The part I'm especially proud of: helping scale Lendi from a startup into Poland's #1 broker and the fastest-growing broker in Europe.
Vue/Nuxt developer. Frontend on B2B and B2C surfaces.
Owned the front-end stack. Mentored juniors. Nuxt 2 -> 3 from alpha.
One year off the product, on the future. AI prototypes, internal tools, the company-wide case.
Lead AI adoption company-wide. Redefine the engineering function.
I roll AI into the seams of the company.
I move engineers from tickets to outcomes.
I find the 30% of work AI eats first - and don't pretend it's augmentation.
"If your AI strategy lives in one department, you're already behind. The work is to redefine the unit - not the tool."
A vertical AI product I'm building end-to-end - design, code, infra, distribution. The thesis I sell at Lendi, proven on my own time.
The model changes every quarter. The product surface - the workflow, the trust, the speed - is what compounds. I optimised for the parts that don't move.
Design, code, infra, distribution. Not because I had to - because the loop is the leverage. Anything I delegate slows the loop.
I sell 'engineers as product builders' to Lendi. jasne.ai is me being the product builder. If it didn't work, I'd know.
AI collapses the distance between idea and shipped feature. The job stops being 'write code' and becomes 'own outcomes'. That's my main KPI at Lendi.
Models, vector stores, infra - all swappable. Bet on interfaces, not providers. The wrapper is the product; the model is a commodity.
When AI eats 30% of a workflow, the move is to redesign the workflow - not wedge AI into the gaps. I redefine departments, not toolchains.
An adoption strategy that doesn't end in a deployed tool is a strategy that didn't happen. The deck is a side-effect, not the artefact.
Lead AI adoption company-wide. Redefine engineering function around the product-builder model. Ship internal tooling, agentic workflows, and the cultural shift that makes them stick.
Vertical AI product. Solo end-to-end: design, code, infra, distribution. Vendor-agnostic stack on Vercel AI SDK.
One year exploring AI as the next platform. Prototypes, internal tools, the case for company-wide adoption. The bridge between frontend lead and AI manager.
Seven years on Lendi's product. Started as Vue/Nuxt developer, grew into front-end lead. Shipped Nuxt 2/3 from alpha, mentored juniors, owned the front-end stack across B2B and B2C surfaces.
B2B financial calculators on Vue and Angular. Where I learned how much UI sits between a financial product and a customer.