Traditional development
Meeting→Quote→Approval→Development→Waiting→First delivery→Review→Changes→Final delivery
betapAIr · live development with AI
Don’t commission the project.
Come build it.
Traditional development means explaining what you need, waiting for a quote, waiting for development and reviewing the result days or weeks later. With pAIr we do it together, live: decide what to do, decide how, and build it as we go with AI as the main tool. You pay for session time, not a project promise.
In person or online · one hour is one hour · start when it suits you.
2 people+ AI1 real project→ tangible result
SHOW COOKING → SHOW CODING
01 / THE CHANGE
From meetings to building live.
pAIr
Session→Decide + build + test→Result
If it needs more time: Session 1 → working product → Session 2 → finished product.
Start with what you need, not the technology
02 / WITH pAIr YOU CAN…
pAIr: a new way to develop projects in the spirit of show coding.
Live development. We make the magic by showing you the tricks: you are in the kitchen while we decide, build, test and correct with AI.
- 01Make an idea real
Turn it first into a prototype you can test and, if it works, into a finished product.
- 02Solve an immediate need
Answer a specific business question that cannot wait and needs solving now.
- 03Optimise the work
Automate and simplify management or production processes so work becomes easier, faster and more efficient.
One session, a visible result
03 / WHAT WE DO
You know the problem.
We know the solution.
You bring the context and the question; during the session we decide, write, design, test and correct together.
01I do not yet know what is possible
Discover opportunities
We look at your business, identify realistic uses for AI and prioritise one worth starting.
You leave withAn opportunity map, clear recommendation and manageable first step.
02I know what I need, but not how to make it
Shape and build
We define the solution, choose the tools and build a first version together around your real situation.
You leave withA prototype, automation, website, process or first working piece.
03I started, but got stuck
Unblock and continue
We review what you have, find the problem and move forward without wasting the work already done.
You leave withDecisions made, an unblocked project and an improved version.
04I do not know whether it is reliable
Review and safeguard
We check behaviour, data, permissions, dependencies and maintenance before customers use it.
You leave withA clear diagnosis and prioritised corrections.
No invisible development between sessions. If it is done, it is done. If it needs more time, book another session and continue exactly where you left off.
Pair programming, beyond code
04 / WHY pAIr
You are not the student
What is pair programming?
Where does it come from?
Pair programming is a way of developing in which two people work at the same time on the same project, sharing decisions and reviewing the result as they go.
It emerged from agile development and became established in the late 1990s through Extreme Programming. pAIr extends the idea: you bring business knowledge, I bring technology and facilitation, and AI accelerates, proposes and produces. We build the product together, live.
The practice · open
pAIr
It is a way of working. You can meet someone and practise pAIr freely: no permission, platform or contract with nualart.cat is required.
The service · paid
pAIr Sessions
Professional support from nualart.cat: facilitation, technical judgement and shared building around your challenge.
See how it worksBuilding means more than making it work
05 / TECHNICAL JUDGEMENT
What can fail when AI programs what nobody understands?
An app can work
and still be dangerous.
AI lets people build without knowing code, servers or databases. It can also leave invisible errors that only surface when real users, data or attackers arrive.
There is no rigorous figure for “all apps made by non-programmers”. The closest evidence is this: in a study of 200 real, deployed vibe-coded applications, 90% contained at least one vulnerability; over three quarters were high severity or critical.
Sources and scope
- Deng et al. (2026), Understanding the (In)Security of Vibe-Coded Applications: 200 deployed apps, 1,471 vulnerabilities, 90% with at least one.
- Veracode (2025), GenAI Code Security Report: over 100 models; 45% of samples failed security tests. This is not a percentage of complete apps.
- Perry et al. (2023), Do Users Write More Insecure Code with AI Assistants?: controlled study with 47 participants and five security tasks.
of 200 deployed vibe-coded apps contained at least one vulnerability.
of generated samples in a test of more than 100 models failed security tests.
tasks in a user study produced less secure solutions with an AI assistant.
Permissions that do not protect
A screen may look private while the server allows access to or changes in somebody else’s data.
Exposed secrets
API keys, passwords or personal data may end up in the browser, repository or public logs.
Inputs turned into attacks
Unvalidated forms can open the door to injection, cross-site scripting or malicious content.
Unsafe dependencies
AI may suggest packages that do not exist, are obsolete or vulnerable, turning installation into an entry point.
No plan for the day after
Without backups, logs, updates and rollback, a working demonstration is not yet a maintainable product.
The answer is not to stop building.
It is to combine AI’s power with technical judgement: understand the architecture, inspect the code, test the limits and take responsibility before publishing.
What can we bring to the table?
06 / CHALLENGES
An urgent project,
a postponed idea,
a problem that costs you every day,
an invention…
You do not need to arrive with a solution or know how to use AI. You need to explain what you want to change, what you already know and why it matters.
Build
A website, prototype, automation, visualisation or internal tool.
Solve
A slow process, repetitive task or problem that consumes time and money.
Think
A difficult decision, business idea or deep, challenging ideation session.
Review
A product, text, experience, strategy or campaign before publishing it.
Research
A complex topic, the available alternatives and the evidence that should guide a decision.
Learn by doing
A technology or method applied directly to your own project, not a generic exercise.
From challenge to result
07 / PROCESS
Meet.
Build.
Finish or continue.
One working session, in person or online. You see decisions, code, errors, tests and corrections as they happen.
- 01
Meet
Explain the problem, in person or online, and open the project in front of you.
- 02
Build
During the same session we define what to do, choose how and build it together with AI.
- 03
Test and correct
You see decisions, code, errors, tests and corrections on the fly.
- 04
Finish or continue
If it is solved, it is done. If it needs more work, book another session and resume exactly where you were.
pAIr Sessions · professional service
One hour is one hour.
Time is the product.
pAIr is billed by session time. No mandatory package, no traditional project quote and no waiting for delivery: you see exactly what you are paying for.
Tell us your challengeFocus Session
Clarify a problem, review a proposal, challenge a decision or unblock one specific point.
Possible resultA map, sound judgement, a decision or a first useful piece.Build Session
Work continuously and build a first version: a prototype, narrative, campaign, process or tool.
Possible resultA tangible result that can already be tested.pAIr Day
An intensive challenge that needs exploration, decisions, production and review in a single day.
Possible resultA solid version and clear next steps.pAIr Cycle
Two or more sessions separated by testing, feedback, reflection and further building.
Possible resultIterative development, not an improvised marathon.Share screen, context and decisions wherever it suits you.
What is produced during the session belongs to the client. No hidden work between meetings.
Start with one session and book another only when the result justifies it.
Where does it come from?
pAIr is an initiative by nualart.cat
A proposal to make the encounter between human knowledge, technical judgement and artificial intelligence useful.
nualart.cat initiates and coordinates pAIr, drawing on more than twenty years connecting data visualisation, interface design, research, code and digital projects. Every challenge requires different knowledge, so we study each case and propose the most suitable experts to prepare and guide the session, contribute sound judgement and help turn the need into a real result.
Frequently asked questions (FAQ)
Before doing pAIr
Can I do pAIr without hiring nualart.cat?+
Yes. pAIr is an open practice: meet another person, choose a real project and work with AI as your main tool. The paid service is professional support, not the right to practise pAIr.
What do I hire in a pAIr Session?+
Shared working time, facilitation and technical judgement. One hour is one hour: you see decisions and the result as it is built.
Is AI a tool or a third intelligence?+
Both: the main tool and a participating intelligence that can know more, reason, propose and produce. This does not remove human responsibility for goals, verification and consequences.
Is it only for programming?+
No. It originates in pair programming, but the practice can research, write, design, develop a campaign, review a product or transform a working process.
Do I need to know AI or programming?+
Not to begin: you need to know your context or have a real question. But if the result is software to be published, somebody must understand its architecture, code, servers and security.
What if we do not finish in one session?+
We close with what we have and, if it pays off, you book another session. The project continues exactly where we left off, with no invisible development in between.
pAIr Sessions · professional service
What do you want to build,
solve or rethink?
Tell me what you want to build, solve or rethink. We will start with a working session and make it visible from the first minute.