System initializing
About

Built in the field, not a boardroom.

CypherShip Labs didn't start with a pitch deck. It started with a laptop, a founder learning to build software from scratch, and a market he could walk into and talk to in person.

The Founder

David

Before SabaiPilot, David spent years in the French army, then moved through a few different careers without finding real fulfillment. Somewhere in there, he taught himself trading and crypto — a first real taste of the pull technology had on him — before eventually moving to Southeast Asia to build something of his own.

Before building it, David worked as a receptionist in Laos, managing reservations by hand across five different booking platforms — living the exact chaos SabaiPilot now solves, not just hearing about it secondhand. He's selling it the same grounded way: walking into hostels and guesthouses himself, and building a small network of referral partners who know the owners better than any ad campaign could.

He's not a career software engineer. He learned to build by building — working directly with Claude Code as a technical partner rather than treating AI as a shortcut around understanding the work. Every feature in SabaiPilot exists because a real conversation with a real hostel owner surfaced it first.

CypherShip Labs is the same instinct, scaled up: don't build a tool and go looking for a sector to sell it to — go stand in a sector, understand it properly, and build the tool it's actually missing. PetraPilot, still taking shape, is starting the same way — through a conversation with someone who's spent fifteen years running a construction business, not a market report.

This section is a first draft — it's your story, not mine to finalize. Correct anything that isn't right before this goes anywhere public.
Mission

Three things that don't change per sector.

01

Sector first, software second

No code gets written until the sector is genuinely understood — not researched, understood.

02

One stable team

The same crew, human and AI, carries context across every project — nothing starts over from zero.

03

Built to be used, not demoed

Every feature earns its place by solving something a real owner was actually stuck on.

Read the full manifesto →

Agentic Engineering

An automation trajectory, designed for your sector.

A first no-commitment conversation — together we identify the task most worth automating first.