The Qawqal Foundry

Superapp scope.
Three founders.

Superapps are normally built by hundreds of engineers and tens of millions of dollars. The Foundry is how Qawqal ships that scope without either.

Small coreFinite classesWritten termsPermanent recordRenewing pipeline
The operating thesis

Separate temporary capacity from permanent complexity.

Fast-growing software companies tend to solve every new product challenge by adding permanent headcount. That can work. It can also make the company slower, more expensive and harder to coordinate.

The Foundry asks a different question: which capabilities must live permanently inside the Core, and which can expand intensely around a single mission and then close?

The Foundry inverts it. The mission defines the seats, the seats are finite, and the compensation is ownership and permanent credit rather than payroll.

This only works because the tools changed. A senior engineer with current AI tooling covers ground that recently took a team, which is why companies now reach serious revenue at a fraction of the headcount it once required. The Foundry is a structure built for that shift rather than against it.

The usual answerHundreds of engineers
The usual timelineYears, and a balance sheet
The usual outcomeHeadcount that never shrinks
The FoundryA small core plus finite, credited classes
Classes are how ambition scales without headcount.
The engineering institution

Three layers. One unusually lean company.

01

The Core

A small permanent team with high responsibility, high context and high ownership. It stays lean for as long as that keeps Qawqal faster and more accountable.

02

Build Classes

Selective engineering groups assembled around a single product mission. Every class has a defined mission, seat count, duration and economic terms — set before it opens.

03

The Builder Network

People who have shipped Qawqal before. They return for future missions, nominate engineers they trust, mentor new classes and sometimes join the Core.

The cycle

Every class makes the next one cheaper to run.

01A hard missionWorth the attention of people who could work anywhere.
02A selective classProof before access. Finite seats, written terms.
03Consequential softwareNamed ownership of real systems, shipped to production.
04Permanent creditReputation compounds — for the builder and for Qawqal.
05A stronger next classBetter applicants, peer nominations, and the best converting to the Core.
What the Foundry is not

A new label is useless unless the structure is actually different.

Not outsourcingBuilders are selected around Qawqal's mission and product ownership, not handed anonymous task bundles.
Not open sourceProduction code stays private. Public proof comes through verified ownership, technical notes and Qawqal Hall.
Not an internship factorySeats are for people capable of owning consequential systems. The bar is proof, not junior status.
Not one compensation modelEvery class gets its own economics. Equity, salary, grants, bounties or hybrids can change with the mission and the company stage.
Not a hiring campaignA class opens when a mission exists, not when a quarter begins. There is no rolling pipeline and no perpetual vacancy.
Not a substitute for the CoreThe Core still owns architecture, standards and long-term accountability. Classes expand capacity, not responsibility.
Not volunteeringEvery seat carries a documented equity grant and a written bonus. This is early-stage compensation, not charity.
Not a guarantee of employmentCompleting a class earns equity, the bonus and a permanent record — not a salaried role. Conversion to the Core depends on need, funding and demonstrated ownership.

V2 is the first Foundry class — not the definition of the model.

Qawqal Hall

The record is the recruiting budget.

Qawqal does not pay market salaries for founding-stage engineering. It pays in ownership and in a permanent, verifiable record of what each builder owned and shipped — public, addressable, and durable even after the builder leaves.

See Qawqal Hall →
It renews.

Each major version opens a class. The pipeline refreshes on the product's schedule rather than a hiring calendar.

It compounds.

Every completed class raises the quality of the next applicant pool, and proven builders nominate peers.

It preserves optionality.

The company observes a builder for ninety days of real work before committing salary. Conversion is a decision made on evidence.

The obvious objection

Equity-only engineering is a legal question before it is a talent question.

It should be. An arrangement like this is only defensible if it is finite, documented and honest about what it is — so that is how it has been built.

01Written before codeConfidentiality, IP assignment and equity terms are executed before a builder receives production access.
02Finite by designEach class has a defined mission, seat count, duration and end date. Nothing open-ended.
03Documented grantsEquity is issued under formal grant documents with standard vesting and dilution — not a promise in a chat thread.
04A decision, alwaysEvery challenge closes with a written outcome inside two weeks. No indefinite unpaid evaluation.
05Stated plainly in publicThe terms, the bonus and the absence of a salary are published on the Build Qawqal page, not disclosed late in a private conversation.
What the model has produced

Ten miniapps. Eight months. Three founders.

Qawqal V1 reached Google Play before institutional capital — one Flutter codebase, ten miniapps, one shared values layer. The Foundry is how V2 gets built on the same principle: capacity that scales with the mission instead of with the payroll.

10miniapps shipped
8months to launch
3founders
9seats in V2
For investors and accelerators

The Foundry is the part that doesn't show up in a demo.

The product can be downloaded. The engineering model behind it is what determines whether the next ten miniapps cost what the first ten did. Traction, economics and the deck are shared privately.

Nine seats are open in the first Foundry class — Build Qawqal →

Request investor materials →
Talk to us