I'm a paragliding pilot.
Every time I want to fly somewhere new, I waste an hour piecing together info from 4 different sites.
So I'm building SLICK — every paragliding spot in the world, in one app.
Solo founder, building in public. Follow along.
Shipped this week:
— Several thousand spots in the db
— Geo-clustering on the map
— Filter by wind direction
— Distance-from-me sorting
~20 hrs of work. $0 spent.
Solo founder energy.
9 days of building SLICK in public.
What I've learned:
— Vulnerability outperforms polish
— Numbers earn trust faster than promises
— The pilots who reply become the first users
— Shipping daily beats shipping perfect
Onto the next 9.
For anyone following the SLICK journey — what would you want to see more of?
— Code/tech deep dives
— Design process
— Numbers + revenue
— Pilot-specific tips
— Failure stories
I'll lean into whatever resonates.
Build-in-public question:
Should I open the SLICK beta when I have:
A) 100 spots polished perfectly
B) several thousand, some still messy
C) the full database with disclaimers
Genuinely undecided. What would you want as a pilot?
If you fly paragliding and use an app for spot info, reply with which one.
Trying to map who's using what before I open SLICK to more users.
(Won't tag, won't compare, just curious about real usage.)
I vibe-code SLICK from home, sometimes from a hotel room when I travel.
No office. No coworkers. No standup.
Just me, a laptop, and a long todo list.
The setup matters less than the consistency.
Pilots — quick question.
When you're planning a flight, what's the ONE piece of data you wish was easier to find?
Building SLICK and want to make sure I prioritize the right thing.
A sustainable solo founder week:
Mornings: push-ups, ab wheel, then code
Two days at the gym
A long run on Thursdays
Family time in the evenings
SLICK in between
Burnout doesn't ship products. Compounding does.
I'm a paragliding pilot.
Every time I want to fly somewhere new, I waste an hour piecing together info from 4 different sites.
So I'm building SLICK — every paragliding spot in the world, in one app.
Solo founder, building in public. Follow along.
Hot take for paragliding pilots:
The data you need to plan a flight should fit on one phone screen.
If I have to scroll, the app failed.
Designing SLICK around this rule is harder than it sounds.
The boring stuff is shipped:
— Auth
— Database
— Spot detail pages
— Search
Now the fun starts: weather overlays, flight planning, and the feature I'm most excited about (saving for later).
Goal for SLICK by end of summer:
— 100+ active pilots
— Full database, fully cleaned
— First paying customer
Public goals. Public failures or wins. That's the deal with build-in-public.
SLICK update:
The map renders thousands of spots without lag.
Filters work in <100ms.
Coordinates are within 50m of accuracy after cross-referencing 2 sources.
This is what 1 week of vibe-coding gets you when you're solo and obsessed.
Cost stack for SLICK so far:
— Domain: $0 (haven't bought one yet)
— Hosting: $0 (free tiers)
— APIs: $0 (free tiers)
— Design: $0 (Stitch + Figma free)
— Total burn: $0/mo
You don't need VC to ship a product. You don't even need a credit card.
SLICK by the numbers, week 2:
— Spots in db: a few thousand
— Active beta testers: 2 (counting me)
— Revenue: $0
— Hours invested: ~20
— Spend: $0
— Coffees consumed: too many
Build-in-public means showing the small numbers too.
A weird truth about solo building:
Some of my best SLICK ideas come during the 30 seconds before takeoff.
That's when I'm most aware of what info I wish I had.
The product gets better every time I fly.
What "good" paragliding data actually means:
— Coordinates accurate to <50m
— Wind directions per spot, not per region
— Clear takeoff/landing distinction
— Last verified date
Most public databases get 1 of these right. The bar is low.