Not a salesperson. Not just a coder. A builder who understands the business.

Scientists and problem solvers who experimentally validate apps that grow small businesses — applying math, algorithms, economics, psychology, social media, and AI, guided by a US team of entrepreneurs and senior developers.

Business Developer role information
ROLEBUSINESS DEVELOPER
SHEET01 · THE ROLE
WHAT THEY RUNREVENUE EXPERIMENTS, END TO END
GUIDED BYUS ENTREPRENEURS + SENIOR DEVS
WHAT SURVIVESAPPS THE MARKET VOTED FOR

The bridge between a real business problem and working software.

Technical enough to build it. Human enough to understand it. Three things define the role.

  1. POINT 01

    Scientist first

    They apply math, algorithms, economics, psychology, social media, AI — and their own innovative judgment — to a single question: does this measurably grow the business?

  2. POINT 02

    Grounded in the real business

    Ideation starts with ground truth. They sit inside a design-partner business — on-site, face to face — to find where it quietly loses time and money. That's data collection, not account management.

  3. POINT 03

    Guided by a US team

    Every experiment is mentored by US entrepreneurs (business & go-to-market) and senior developers (architecture & quality).

Willing to be wrong: Experimentation means unlearning, discarding, and giving dozens of ideas up to failure. Evidence advances an app; the lack of it kills it — and the lesson rolls into the next experiment.

Four phases. Every app earns the next one.

Every app is experimentally validated through ideation, development, market penetration, and scalability. The Business Developer runs the experiment at every phase.

  1. PHASE 01

    Ideation

    Form the hypothesis: a specific business's revenue leak or a specific consumer problem. Embedding with a design partner sharpens it before a line of code is written.

  2. PHASE 02

    Development

    Build working software fast and put it in front of real users early — so the market, not opinion, judges it. Guided by the US team at every step.

  3. PHASE 03

    Market penetration

    Channels, pricing, and messaging are all experiments. The app proves it can win real paying customers, or it teaches us why it can't.

  4. PHASE 04

    Scalability

    What survives validation gets hardened and scaled from one business to the whole vertical. What doesn't gets discarded.

One validated experiment. An app that survives all four phases is scaled from its first business to the whole vertical: evidence becomes recurring revenue at scale.

From day one to a validated product.

The everyday work of a Business Developer, hypothesis to scale.

The six phases of a Business Developer's work, in order.
NNPhaseWhat happens
01TrainGround in CS foundations, the lab's stack, and the experimental method for turning business problems into testable software.
02HypothesizeGo to the ground truth. Sit with a real business, map the workflow, and state the hypothesis: here is where revenue leaks, and here is the app that stops it.
03DesignTranslate the hypothesis into a system spec with a measurable success condition — reviewed by senior developers before a line is written.
04BuildShip working software with AI-assisted development, fast enough that the market can start judging it early.
05Test in marketRun the penetration experiments — channels, pricing, messaging — against real users and real revenue. Keep what the evidence supports; discard what it doesn't.
06ScaleGeneralize the validated build from one business to the whole vertical — your experiment becomes recurring revenue.

Backed by a US team of entrepreneurs and senior developers.

PILLAR 01Entrepreneurs
Business model, go-to-market, pricing, and vertical strategy — the economics half of the experiment.
PILLAR 02Senior developers
Architecture, code review, and quality — every spec and every build is guided and reviewed.
NOTE

The Business Developer brings the hypothesis and the ground truth; the US team brings the judgment that turns evidence into durable products.

Two ways in.

Whether you have the problem or you want to build the fix, it starts with the same conversation.

ROUTE A · FOR BUSINESSES

You run a business

Get software built around how your business actually works — validated against your revenue, not our opinion.

ROUTE B · FOR BUILDERS

You want to build

Become a Business Developer — a scientist who turns real business problems into apps the market votes for.