§ About · The case file · Established 2024

The story of how it started.

Three people, one shared frustration, six months of refusing to give up. Here's the case file — receipts, alibis, and all.

— § A SHORT MANIFESTO —
Most software is locked behind a wall of technical knowledge. We don't think it should be. We think anyone with an idea — and a sentence to describe it — deserves to build it.
— § 01 · Origin Story —

How AiGAP came to exist.

We've kept the receipts. Notes from notebooks, the actual founding emails, code from the first prototype. Make of it what you will.

March 2024 · Istanbul, Turkey

The frustration that started it all

Our founder spent six weeks trying to get a simple inventory app shipped for a friend's bakery. Three contractors. Two failed deployments. A no-code tool that broke the moment it was used.

Six weeks. For an inventory app. The bakery had been running on spreadsheets the entire time.

Voice note — found later
"There has to be a better way. The friend just wants to know how many croissants are left. Why is this impossible?"
April 2024 · Late one night

The email that changed direction

Three colleagues had been talking for months — separately — about the same gap in the market. One night, that conversation finally happened. The email below was the spark.

The reply came back within an hour: "I'm in."

July 2024 · The first prototype

Day fourteen · the breakthrough

Two weeks into the prototype, something worked. A user typed "give me a habit tracker with daily streaks" — and got a working habit tracker. Live, deployed, in 47 seconds.

It was ugly. It crashed on edge cases. It broke if you said anything off-script. But it worked.

Build log · 14 Jul 2024 · 03:42 GMT+3
01→ parsing intent: "habit tracker with streaks"
02→ generating ui: 7 components, 2 routes
03→ wiring data layer: postgres ✓
04→ deploying: live in 0.42s
05✓ build complete: 142KB · habit-tracker-v1
October 2024 · Beta launch

200 invitations. 2,400 waitlist signups.

We sent the beta to 200 people we trusted to break it — designers, founders, makers, a chef in Lyon, a notary in Berlin, a teacher in Cape Town. Within 72 hours, the waitlist had 2,400 names on it.

The chef in Lyon built her menu management system over a weekend. The notary automated his appointment scheduling. The teacher made a quiz tool for her students. None of them could write code.

Beta tester quote — anonymized
"I'm sixty-three. I've been a notary for thirty years. I just built a thing that will save me five hours a week. I am — to use the technical term — delighted."
February 2026 · Today

Where we are now

AiGAP has shipped tens of thousands of applications for people in 47 countries. Restaurant operators. Solo founders. Internal teams replacing $40k SaaS subscriptions. Notaries. A youth football coach.

We're a team of nine across three time zones. We're profitable. We've taken zero outside investment. We answer support emails personally. We intend to stay this way.

The case file remains open. The next entry is being written.

47
Countries shipped to
9
People on the team
$0
Outside investment
100%
Customer-funded
— § 02 · How we work —

Six principles we don't compromise on.

Every team has a wall of values. Most of them don't survive the first hard quarter. These have.

PRINCIPLE.01

Speed is a feature.

If a build takes more than a few seconds, we treat it as a bug. Not a nice-to-have, not a future optimization — a defect. Fast software respects the user.

We don't ship "we'll optimize later"
PRINCIPLE.02

Your data is your data.

Export anytime. Run on your hardware. Use your own AI model. We make money from subscriptions, not surveillance. Period.

We don't sell data, ever
PRINCIPLE.03

Plain language wins.

Our copy doesn't have weasel words. Our pricing isn't gamified. Our terms are written for humans. If we can't explain it to a friend, it's wrong.

We don't hide behind jargon
PRINCIPLE.04

Stay small.

Nine people today. We may grow — but slowly, and only when growth makes the product better, not when it makes a deck look better.

We don't hire to fundraise
PRINCIPLE.05

Take support personally.

The founders read every support ticket. We don't have an outsourced help desk. If something is broken, the person who broke it is going to fix it.

We don't use canned replies
PRINCIPLE.06

Refuse the easy compromise.

The dark pattern would convert better. The acquihire would pay better. The shortcut would ship faster. We say no, almost always. The long road is the right road.

We don't grow at any cost
— § 03 · The team —

The nine people who actually do this.

No "Chief Vibes Officer." No fractional anyone. Real names, real roles, real skin in the game.

E

Emrah B.

FOUNDER · CEO

Started the case file with the bakery story. Spends most of his time talking to customers and breaking things in production.

PREVIOUSLY · 5 years founding teams
D

Dmitri K.

CTO

Wrote the original parsing engine on a 14-hour flight. Lives by "if it can't be deployed in seconds, it can't be deployed."

PREVIOUSLY · infrastructure at scale
L

Lena O.

DESIGN

Made AiGAP look like AiGAP. Believes that good design is invisible until you go back to the alternative and feel the difference.

PREVIOUSLY · editorial design
A

Aisha R.

AI / RESEARCH

Owns the prompt routing layer. Reads three papers before breakfast. Has strong opinions on local vs cloud LLMs.

PREVIOUSLY · ML research
M

Marco T.

RUNTIME · PLATFORM

Owns the deploy pipeline. Has personally shipped your last build. Probably reading this from a terminal, not a browser.

PREVIOUSLY · edge infrastructure
S

Selin K.

PRODUCT

Translates "what users actually want" into "what we should build next." The most important and least visible job.

PREVIOUSLY · product at SaaS scale
N

Noah F.

CUSTOMER · FOUNDING

Answers your support emails. Probably the first AiGAP person you'll talk to. Has built more apps on AiGAP than most users.

PREVIOUSLY · community at startups
Y

Yui M.

SECURITY

Owns SOC2, GDPR, and the bug bounty program. Holds the keys you don't see. Sleeps with one eye on the dashboard.

PREVIOUSLY · security at scale
F

Finn O.

FINANCE · OPS

Keeps the lights on, the books closed, and the team paid on time. The person making sure the long road remains an option.

PREVIOUSLY · operations

The case file is open.
Add your story.

Build something. Ship it. Tell us what you made. We read every email.

Start Building Free→