From Creative Production to shipping AI: How I built Norte in 4 months as a Non-Technical Founder

Half a year ago, I couldn't write a function. Today, I have 80+ users using an AI platform I built solo that parses coverage documents and explains them in plain English.

I'm not sharing this as a "anyone can code" story. It's about what becomes possible when personal pain meets the right tools at the right moment.

The problem I couldn't ignore:

Living across 4 countries (Spain, USA, Finland, Netherlands) taught me that coverage confusion is universal. I'd panic-buy €500 travel insurance because I couldn't decode whether my Amex Platinum and Spanish health insurance would coordinate during a medical emergency.

The breaking point came when I saw a friend at rental counters buying insurance their credit cards already covered. I realized this wasn't just my problem. I learnt through my research it's systematic market failure affecting 213M consumers who don't understand their existing coverage.

But then, there is the reality check.

My background: creative, communications, growth. I'd always collaborated with developers, never been one. When I decided to build Norte, the obvious path was finding technical co-founders or outsourcing development.

But every conversation with developers did not help me move forward. So I decided to give it a try.

Three things made solo technical execution possible:

• Claude Code: Let me delegate actual coding tasks directly from terminal. Instead of learning syntax, I could describe what I wanted and iterate on working code.
• Lovable: Turned UI/UX ideas into functional interfaces. I could design flows while the system handled implementation details.
• Semantic AI APIs: Instead of building ML from scratch, I could train models on insurance documents using existing frameworks.

What I managed to build:

Norte parses credit card benefit guides, insurance policies, and employee benefits into a unified dashboard. The AI answers "Am I covered?" questions with confidence scoring to prevent costly mistakes.

Current functionality:

• 100+ credit cards parsed across US/EU markets
• Semantic search through complex policy documents
• Geographic coverage intelligence (crucial for expats)
• Receipt storage and claims preparation

Numbers are not impressive, but I can't complain:
80 users in one month, all organic so far.

Why I keep going:

• Personal pain: I experienced coverage confusion across multiple countries and regulatory systems. This isn't theoretical.
• Domain expertise: Years in marketing taught me how to position products and understand market dynamics.
• International perspective: Coverage rules vary dramatically by geography. Most fintech tools are US-centric.
• Timing: AI tools matured exactly when insurance transparency regulations started demanding consumer-friendly solutions.

My take to others building:

Norte exists because I understood coverage confusion from personal experience and could build a solution fast enough to matter. The technical skills were learnable; the market insight wasn't.

If you're a non-technical founder avoiding building because you "can't code," consider whether your domain expertise + current AI tools might be enough to ship something people actually want.

Questions for the community:

• Other non-technical founders making this transition?
• What tools are you using to bridge the technical gap?

Link to Norte: norteapp.io