Administration SaaS React is a JavaScript library for building user interfaces from reusable components, which keeps complex, interactive screens maintainable as an application grows. We build our frontends with it, almost always paired with TypeScript and often Next.js. You will find it across 3 client projects and 2 lab articles, with 1 specialist on our team.
Software Development Support
On-demand development expertise for any software project. From vibe-coded apps to enterprise integrations. We flexibly jump in as an extension of your team.
Vibe Coding Audit
Have your AI-generated code audited by senior developers. We'll tell you what holds up, what breaks under pressure, and what you can keep before you scale.
Vibe Coding Managed Development
Got a vibe coding project built with Lovable or Supabase and want it off your plate? We take it over: make it production-ready, host, maintain and keep developing it.
Other engagements where React expertise is central.
Real-world projects and research articles where we applied React.
Use Cases
Administration SaaS Tech Recruitment Agency How a recruitment agency used AI for CV screening without falling into the bias trap
Utilitarian When circularity meets agility
Lab Articles
010 Coding Collective Vibe coding works as long as you can see the result
unwrite.it An experiment against AI slop
1 specialist on our team specialises in this. Below you can see who they are, along with the other technologies they know.
-
Marcel Fleuren
-
Jur Ligteringen
-
Kevin Schenkers
-
Maikel Hofman
-
Jeroen Marchand
-
Kevin Land
-
Eward Bartlema
What does it cost to hire a React developer?
A freelance React developer in the Netherlands charges roughly 70 to 125 euro per hour excluding VAT, depending on seniority and how much responsibility comes with the work. Since AI arrived that number says a lot less than it used to. In nearly every project that reaches us, a large share of the code was written by a model, so the hours that go into typing have dropped sharply. What is left in those hours is reviewing, structuring and deciding. So compare what it costs to get a working feature safely into production, and how long you can keep maintaining it afterwards.
Why does an hourly rate say less than it used to?
An hourly rate used to be a reasonable yardstick because the spread in what an hour produced was bounded. An experienced developer wrote more and better code in that hour than a junior, and the gap fitted inside a factor of two or three. With AI in the mix that gap has widened enormously. Two people on the same rate can deliver a working, tested and understandable piece of software in the same hour, or a pile of plausible code that has to be thrown out three months later. The hour has stopped being a comparable unit. In practice, the question of what a developer costs has become the question of who reviews the generated code.
Has building with React become cheaper thanks to AI?
Partly. The building itself really is faster: a screen, a form or an integration stands in a fraction of the time it took four years ago. The work that does not scale along is review, architecture and cleaning up the choices a model made for you under time pressure. That part has become relatively more expensive, because more code passes by every week that someone has to understand. Projects that end up cheaper are the ones where that review work is properly organised. Where it is missing, the project looks cheap on paper and turns expensive in the second year.
So what are you paying for when part of the code is generated?
Judgment. Someone has to decide where the state of a screen lives, what renders on the server and what in the browser, and what happens on a slow or failed request. Someone has to read generated code and spot that a solution works in the demo and falls over at a hundred concurrent users. And someone has to hold on to the knowledge once the assignment ends, so the next change does not turn into archaeology. Those three things now set almost the entire price of a React project. The hours in which code gets typed have become the cheapest part of it.
Can you take over a React codebase that was built with AI?
Yes, and by now that is a sizeable part of our work. Such a codebase usually looks tidy and works at first glance, because a model writes readable code. The problems sit a layer deeper: the same logic in four places, state leaking across the whole screen, tests that only confirm what the code already does. We start with an audit that names what is there, what can go and what breaks first, and we build after that. You will also hear it from us when carrying on with what you already have is the sensible route.
How does 010 Coding Collective work with React?
React sits in almost every frontend we deliver, paired with TypeScript and often Next.js, and the work leaves the door as a whole: design, build, review and maintenance. Our process is built entirely around AI, with a human checking every line before it goes live. We push back when there is a better route, also when that route means less work for us. We are a senior studio at Hofplein in Rotterdam, so you can drop by and watch what is being built at the table.
From AI prototypes that need to be production-ready to strategic advice, code audits, or ongoing development support. We're happy to think along about the best approach, no strings attached.
free
Free Consultation
In 1.5 hours we discuss your project, challenges and goals. Honest advice from senior developers, no sales pitch.
1.5 hours with senior developer(s)
Analysis of your current situation
Written summary afterwards
Concrete next steps