Sherppi
From zero to a live location-based travel product.
Sole technical lead across the React Native/Expo app, Python/Django backend, PostgreSQL, payments, geolocation and AI-assisted recommendations.
A mix of mobile, SaaS and zero-to-one work. Different contexts, same job: understand the system, make good technical decisions and get useful software into people’s hands.
From zero to a live location-based travel product.
Sole technical lead across the React Native/Expo app, Python/Django backend, PostgreSQL, payments, geolocation and AI-assisted recommendations.
Mobile product engineering inside a fast-moving product team.
Developed the Negotiator app beyond prototype stage and contributed to the renter platform, release processes and engineering practices.
Shipping inside an established production platform.
Worked alongside the CTO across frontend architecture, cloud infrastructure and product delivery for event and venue operations software.
A first concept turned into a working mobile product.
Built the mobile app and cloud backend for a motherhood-support product, while helping shape the product direction with the CEO.
Also: nine systems designed, built and in operation — three live products, a client platform in production, and the rest. See the systems ↗
Current engineering work across AI agent systems, integrations and publishing workflows. These projects are active and have not been publicly released yet.
Building agent systems and automations that connect information, tools and operational workflows.
Developing software for the work behind publishing: structured inputs, content flows and repeatable automation.
Ask about the work ↗My career started in backend-heavy C#/.NET systems and expanded into web, mobile, cloud architecture, product leadership and now AI-assisted product engineering.
I’m useful when a product is half idea, half system, and someone has to connect the dots. I can work at architecture level and still open the editor and ship the thing.
React Native, Expo, Flutter; app architecture, native integrations, shipping and release.
React, Next.js, TypeScript; interfaces that are fast, maintainable and connected to the real system underneath.
C#/.NET, Node.js, Python/Django, Postgres, Supabase, APIs, auth, payments, integrations and cloud infrastructure.
Agents, retrieval, knowledge systems and AI-assisted workflows used as part of a product—not pasted on top of one.
0→1 shaping, useful scope, trade-offs, technical direction, user feedback and deciding what not to build.
Don’t make the architecture impressive. Make the product inevitable.Start with the user problem. Choose the smallest useful version. Build the whole loop. Put it in front of people. Then earn the complexity.