Custom software — quoted

Bounded systems for SMEs, built with an agent factory.

Quoted after a conversation. Internal tools, booking logic, operator inboxes, integrations — scoped in writing, owned by you. Not a lakehouse SKU, not an Operating Layer, not a US-vendor landing team.

What you get

Internal tools, customer portals and workflows — owned by you, documented

What it costs

Quoted after a 30-minute discovery — fixed scope, milestones, one number

How long it takes

First working build in weeks; you watch it grow every Friday

Who delivers

Senior engineers plus an agent factory; a named technical lead signs the architecture

Yerbabuena Digital builds custom software for Southern European SMEs: internal tools, booking logic, operator inboxes, quote workflows and integrations, sometimes with lightweight agents inside. An agent factory gives speed; senior engineers review what ships; your team approves anything that reaches a customer.

By Friday of week 1: a running skeleton on representative data, the architecture decisions logged in git, and a clickable preview of the one workflow you described in discovery.

Agents make it fast. People make it safe. At build time and at run time.

What we build

What we build

Pick one system or connect several. Always scoped in writing, always yours at handoff.

Tools your team lives in

Job queues, order boards, client portals and dashboards shaped around how you actually work — role-based access, audit logs, mobile-friendly.

  • Web interfaces your staff picks up in a day
  • Stripe, calendar and messaging wired in
  • Runbooks and handoff docs included

The end of copy-paste

We replace the glue work between tools you already pay for: inquiry triage, document routing, reminders, reconciliations — with a human approving every consequential step.

  • Inquiry classification with drafted replies
  • Document routing with readable logs
  • Scheduled jobs that tell you when they fail

Agents where they earn their keep

Lightweight agents that research, draft and classify inside your system — with approval gates, evaluation before launch, and traces you can read. Never customer-facing autopilot.

  • Approval queues on WhatsApp or email
  • An evaluation harness before anything goes live
  • Traces, logs and cost visibility

Everything talking to everything

CRM, spreadsheets, calendars, ERP exports, data platforms — connected with the fewest moving parts that will last. MCP and plain APIs where they help, not framework theater.

  • REST APIs and webhooks
  • MCP tool servers where they cut glue code
  • Accounting and ERP exports

We build and hand over systems you own. We don't resell chatbot subscriptions, and we don't sell packaged governance platforms.

In scope / Out of scope

In scopeInternal tools, customer portals, workflow automation, lightweight agents with approval gates, integrations, runbooks, training, handoff
Out of scopeChatbot subscriptions, packaged governance platforms, resold licenses, 24/7 managed operation, anything customer-facing without a human gate

The factory

You watch the build happen

AI where it saves weeks, seniors where it saves projects. Every Friday you see the branch running — not a status slide.

Week 0 — Discovery

A 30-minute call, then we map the job: tools, data, risk, the ritual your team repeats daily.

Artifact: Written scope, milestones, one fixed price.

Week 1 — Skeleton

The factory scaffolds the system on representative data. Seniors set the architecture and the security boundaries by hand.

Artifact: A running preview you can click.

Weeks 2–4 — Iterate

Agents write tests, drafts and refactors; every merge passes senior review. Friday demo, your feedback lands Monday.

Artifact: A changelog in plain language, weekly.

Handoff

Hardened build, credentials, runbooks and training. Care starts at go-live; after handoff, you can cancel and run it yourselves with the documentation.

Artifact: A system your team operates without us.

What a quote contains

  1. Goals and explicit out-of-scope — one page, no padding
  2. Milestones with dates and what you'll see at each
  3. One fixed price and the payment schedule
  4. Ownership and handoff terms — code, data, credentials: yours
  5. Risks we already see, written down before you sign

A worked example — hypothetical, so you can check our thinking

A repair shop runs jobs on paper and WhatsApp. The build: one queue with job status, parts notes, and drafted customer SMS a person approves. Where the value comes from: the owner stops re-typing the same three messages forty times a week, and no follow-up gets lost between two apps. Where it wouldn't pay: if the shop handles five jobs a week, a shared spreadsheet is the honest answer — and we'd say so in discovery.

Risks we name before you sign

  1. Agent steps drift without a weekly review — we run that review every Friday demo, you don't have to chase it.
  2. Integrations to a system you don't control (a third-party API, a legacy ERP) can slip on their calendar, not ours; we name that dependency in week 1.
  3. If your team can't review a branch a week, the cadence breaks — we surface that in discovery, not at the first missed demo.

What you keep if we stop after week 1

If we part ways after week 1, you keep: the skeleton repo, the architecture decisions log, and the written scope with milestones. You owe nothing further.

The factory isn't a metaphor — this site, its agents and its publishing pipeline are built and operated the same way, and the colophon shows the wiring.

Yerbabuena Digital grew out of Yerbabuena Software, a University of Málaga spin-off from 2005 — a separate company, same family, same town. Our technical lead, Antonio de las Nieves Stoner, has spent about twenty years running enterprise workshops, PoCs and first deployments — including Oracle Iberia, the first sales-engineering hire at Promethium, and buyer-facing architecture at Quantexa and Waterline Data, with around seven years operating in Silicon Valley. That is career history, not a Yerbabuena Digital client list — we keep those separate on purpose.

Who is in the room

DiscoveryBárbara Trujillo (client lead)
Architecture reviewAntonio de las Nieves Stoner (technical lead)
Friday demoAntonio de las Nieves Stoner (technical lead)
HandoffBárbara runs the handoff; Antonio walks runbooks if needed

How this page was made: drafted by an agent from the spec, reviewed by a senior engineer, copy-edited in English, Spanish and French, and shipped through the same approval queue we sell — a person pressed send. The full wiring is in our colophon

Exit / offboarding

To end the engagement: the handoff docs, repo, credentials and runbooks are yours at handoff. Care runs through go-live and handoff, then is cancellable by email any month. We don't hold your data or your domain.

First conversation — bring this

  • The one workflow your team repeats daily.
  • The tools it touches today (names, not categories).
  • The one step that must never run without a human approving.
  • Your real budget range — we'll tell you on the call if we can land inside it.

Common questions

How is the price set?

After discovery you receive scope, milestones and one fixed number in writing. Changes go through change control — agreed before they're built, never invoiced as a surprise.

Is this a chatbot subscription?

No — it's software you own, which sometimes has agent steps inside. When an agent is involved, it drafts and a person approves.

Do the agents run on autopilot?

Not toward your customers. Agents research, draft and classify; approval gates sit before anything customer-facing or contractual. Logs and traces are part of the build, not an add-on.

Who leads the delivery?

Bárbara Trujillo is the founder and your client lead. Antonio de las Nieves Stoner is the technical lead who signs the architecture — his credentials are on our About page, and he joins the technical calls on Zoom.

Can you integrate with our tools?

Yes — calendars, messaging, Stripe, spreadsheets, CRMs and data platforms when the scope calls for it. We prefer the fewest moving parts that will still be running in three years.

How small is too small?

If a spreadsheet or an off-the-shelf tool is the honest answer, we say so on the discovery call and point you to it — that call costs you thirty minutes, not a commitment.

Is this the same as your web packages?

No. Web & eCommerce has published prices and fixed scope. Custom software starts where the packages end — quoted, because no two systems are the same.

Tell us the job. We'll tell you the price.

A 30-minute discovery call, then a written scope with milestones and one fixed number. If we're not the right builders, we say so on the call.