TWO SENIOR DEVELOPERS. UNFAIR AMOUNTS OF AI.

We vibe code
software
for a living._

Two senior developers. AI does most of the typing. We make sure the result actually works.

dudes / production
01const team = ["dude", "dude"];
02await build(idea, { ai: true });
03await humans.verify();
04ship("production");
ALL SYSTEMS HUMANmain*
HUMANAPPROVED100%
Less Jira. More shipped software.
IDEA → CODE → TESTS → PRODUCTIONSCROLL TO THE GOOD STUFF ↓

99% AI.
100% our responsibility.

The models write. We think, test, review and ship. Every line is our problem. So it doesn’t become yours.

01 / WHAT WE BUILD

An idea? A bottleneck? A gloriously weird problem?

If it can be expressed as software, we’ll probably build it.

Explore our services ↗
02 / THE METHOD

Fast doesn’t mean fingers crossed.

Small steps. Tight feedback loops. Actual engineering.

Inside our process ↗
01

Understand.

One problem. A clear outcome. We work out what matters and what can wait.

02

Build.

We break it down. The models get to work. You see real progress early.

03

Verify.

Tests, human review and real-world checks. Generated isn’t done. Verified is.

04

Ship.

Into production, with monitoring, documentation and a proper handover.

THE AI BUILD SPRINT

One week. One problem. Let’s ship it.

Let’s start simple: one week, two dudes and a sh*t load of tokens. We’ll show you what can be done in a week. Probably not the final product, but a really good MVP or prototype that you or we can keep building on.

5 000 €+ VAT · first week, fixed price
Challenge the dudesScope agreed together. No magic promises.
03 / THE HUMAN PART

AI makes mistakes. We built a process for that.

AI hallucinates. It writes bugs. So do humans. The job is catching those mistakes before your users do.

See what “done” means ↗
DEFINITION OF DONE
Automated tests & type checks01
Senior engineering review02
Security & data validation03
Real environment testing04
VERIFIED, NOT JUST GENERATED.
MODEL AGNOSTIC. OUTCOME OBSESSED.

The right model for the job. Not a lifelong commitment.

✳ Claude◉ OpenAI✧ Gemini
04 / FIELD NOTES

Less hype. More how.

All insights ↗

What is vibe coding, really?

A useful way to build faster. A terrible excuse to skip engineering.

Generated isn’t done. Verified is.

What we look for before AI-written code reaches production.

Your MVP needs a smaller scope.

The fastest route to a first release starts with what you leave out.

FAQ / NO BS

Fair questions.

Do you really use AI for almost everything?

Yes. From planning and coding to tests and debugging. That doesn’t mean every generated line gets into production. We stay responsible for the result.

Is AI-generated code safe?

Safety depends on the engineering process. We review authentication, permissions and data handling, test critical paths, and validate changes before release.

What if the AI gets it wrong?

It will. That’s why we verify against documentation, run the code and test the result. A confident answer isn’t evidence.

Can you work with our existing codebase?

Absolutely. We can investigate bugs, untangle legacy systems, add tests and modernize one part at a time.

Do you only build prototypes?

No. We build production software too. A prototype proves an idea; a production release also needs security, testing, monitoring and ownership.

LET’S MAKE IT REAL ↙

Got a “could you build…”?

That’s our favorite kind of conversation.

Tell us what to build