Skip to content

Your systems

What we build

NewMCP agents connected to your ERP and CRMMCP agents in your ERP and CRM

We put AI to work. And we build its workshop.

AI automation, web development, and mobile and desktop apps built with the latest technology. Designed and built by the same team, with the code and accounts in your company’s name.

The AI proposesA person confirmsYour systemsWhat we build
Each task leaves one of the company's systems, goes through the AI core and reaches one of the products we build. When needed, a person confirms before it goes on.

Live

The workshop, runningEach task leaves a system, goes through the AI and reaches a product.

0 tasks done0 confirmed by a person

What we do

Three crafts, one workshop.

We automate with AI, build software where the work happens and make it visible. All three with the same method: a real example, a written scope and a first release someone uses.

Fig. 02Agent relaysAGENT · MCPLooping

Automate

AI does the repetitive work. A person decides what matters.

Agents with permissions
They read emails, documents and tickets with minimal, revocable, logged access.
Human in the loop
If confidence falls short of the threshold, the case goes to review. Nothing expensive is published on its own.
Fig. 03Pneumatic tubeHTTP · 200Looping

Build

Web, mobile and desktop, each format where the work really happens.

Design and code, one team
Every screen is drawn knowing what data exists and which error has to be shown.
Current technology
Astro, Next.js, Expo, SwiftUI, Tauri and Rust, chosen for the problem, not for fashion.
Fig. 04Search radarSEO · GEOLooping

Make it seen

Brand, 3D and SEO so what we build gets found and remembered.

Experiences people remember
Creative development, real-time 3D and launch videos with the real product.
Visible on Google and in AI
Technical SEO and content that ChatGPT, Perplexity and Gemini can cite.

How we work

Four steps. None of them is an endless meeting.

  1. 01

    A real example

    An email, a report, a screen from last week. Without an example, the conversation stays in adjectives; with one, we can write down what's in.

  2. 02

    A written scope

    What gets built, what's out, which system isn't touched and which credential is used. Security and IT read it before anything is switched on.

  3. 03

    A usable first release

    The screen or workflow someone would miss tomorrow if it were gone. It’s shown early to the people who will use it, not on the last Friday.

  4. 04

    Operate and measure

    Errors, real use and cost are watched. If the team goes back to the old way, it shows. The code and accounts stay in your name.

Fig. 05Cam programmerPROCESS · 4One pin per step
Fig. 06Key cabinetLOCKEDno key, no accessCREDENTIALSOne key, one door

What we don't negotiate

The keys stay home.

  • The code is yours

    Repository, domain, cloud and app store accounts in the company’s name. No Veodar console that Monday depends on.

  • The credential doesn't live in the prompt

    Every workflow uses minimal, named, revocable and logged access. Security sees it on the same list as everything else.

  • Actually fast

    Core Web Vitals in the green, apps that open instantly and animations that don't drain the phone. We measure on real devices.

  • The model can be swapped

    Claude, GPT, Gemini or an open model: the task and the rules are yours. Changing provider doesn’t rebuild the business.

Questions

Frequently asked questions

Missing yours? Write it to info@veodar.com and we'll reply with a specific question, not a brochure.

What kind of AI automation do you build?

Specific tasks that already exist and repeat: sorting emails and tickets, extracting data from documents and invoices, drafting replies, reconciling orders or flagging when something doesn't add up. We use agents and workflows connected to your ERP, CRM or email, with a person or a rule that confirms before anything is published.

Which AI models do you work with?

Whichever solves the task best: Claude, GPT, Gemini or open models hosted by you. We connect tools with MCP and orchestrate with LangGraph, n8n or our own code. The task and the rules aren't tied to a provider.

Website, mobile app or desktop application?

The work decides. Web if there are accounts, permissions and data another system reads tomorrow; mobile if someone logs work standing up and without signal; desktop if the workstation depends on local files or devices. If none fits, we say so.

Who owns the code?

Your company. The repository, the domain, the cloud accounts and the app store accounts are created in your name. We hand over the deployment guide so another team can carry on without us.

How much does a project cost?

It depends on the scope: roles and permissions, integrations, offline work, app store publishing or how autonomous the AI is. We don't publish a rate card; in our first reply we tell you whether it fits and what would need narrowing to give a firm figure.

Do you work with companies outside Spain?

Yes, in English or Spanish, with teams in Spain, Latin America and the rest of Europe. Distance doesn't change the method: a real example, a written scope and a first release someone uses.

Do you also do design, 3D and SEO?

Yes. Our studio covers brand identity, web design, creative development, 3D websites, configurators, launch videos, redesigns that keep your rankings and SEO with visibility in AI search.

Get started

What is still done by hand at your company?

Send us this week's example: the email, the report or the spreadsheet. We'll tell you whether it's web, mobile, desktop or an AI automation, and if it fits.

Fig. 07Morse keyINFO@VEODARH · E · L · L · O