Data & cloud — quoted per engagement
Databricks, Snowflake, Oracle, OIC and the four big clouds. We deliver bounded engagements — a lakehouse foundation, a landing zone, a FinOps baseline — with written done-criteria and runbooks your team operates.
Hands-on implementation: pipelines, landing zones, catalogs, FinOps — never a license resale
Quoted per engagement, with written done-criteria before you commit
First governed datasets or a working landing zone in weeks, scoped in discovery
Architecture signed by an OCI Architect Professional; ~20 years of platform delivery behind it
Yerbabuena Digital delivers bounded data and cloud implementation engagements on Databricks, Snowflake, Oracle, OIC and the four big clouds: lakehouse foundations, pipelines, catalogs, landing zones, IaC and FinOps. Each engagement is quoted after discovery with written done-criteria and handed over with runbooks your team operates.
By Friday of week 1: the engagement boundary drawn on your estate, the first ingestion path mapped, and the done-criteria written for the first dataset or landing-zone engagement.
Your sources
Your platform — Databricks · Snowflake · Oracle
The ground it stands on
We inventory sources, platforms and the outcome you need.
Artifact: Engagement options in writing — not a framework deck.
Deliverables, calendar, done-criteria and one price for the chosen engagement.
Artifact: The quote your operators can hold us to.
Pipelines, zones, catalogs and docs in your tenant, reviewed with your platform team as we go.
Artifact: Working infrastructure, in git, in your accounts.
Runbooks, office hours, and follow-on engagements quoted separately only if you want them.
Artifact: A platform your team runs without us.
A mid-market team licenses Snowflake but every dashboard reads from ad-hoc tables nobody trusts. The engagement: medallion structure for two agreed domains, catalog entries with owners, lineage on the paths that feed the board pack, and a runbook. Done in weeks, not quarters, because the boundary was drawn before the work started. What we would not do in that engagement: migrate every legacy table, or evaluate access-control tooling — both are separate decisions, and writing them out of scope is what keeps the price honest.
If we part ways after week 1, you keep: the estate map, the engagement options in writing, and any IaC or pipeline scaffolding already in your tenant. You owe nothing further.
This is the motion our technical lead has spent the longest on: catalog and lineage work on Silicon Valley data platforms, principal-level cloud architecture across OCI, AWS, Azure and GCP, and enterprise implementation depth down to row- and column-level — two decades of it, verifiable from the certifications on About.
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.
| Discovery & estate mapping | Antonio de las Nieves Stoner (technical lead, OCI Architect Professional) |
|---|---|
| Architecture sign-off | Antonio — signs; your platform team challenges |
| Build reviews | Antonio with your platform engineers, in your tenant |
| Handoff & office hours | Antonio runs the runbook walk-through; Bárbara Trujillo owns the relationship |
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
To end an engagement: all infrastructure, IaC, pipelines and runbooks are in your tenant and your git. Office hours run to the agreed end date. A light retainer is optional and cancellable by email any month. We don't hold your data.
Databricks, Snowflake, Oracle (including ADW and OIC), open query engines and open table formats, and the four big clouds — OCI, AWS, Azure, GCP. Multicloud is normal; we document decisions instead of forcing a vendor story.
Quoted after discovery: deliverables, calendar, done-criteria, one number. Follow-on engagements are quoted separately, so you can stop after any one of them with everything working.
No. We implement on the platforms you license. Where retention or record-keeping hygiene matters for GDPR, it's built into the work — as engineering, not as a product pitch.
Yes — that's why this is one page. Foundations first where needed (landing zone, IaC), then the data engagements land on solid ground. One discovery, one program quote if you want both.
You do — that's the point of the runbooks and office hours. If you want ongoing help, we scope a light retainer; we don't sell a managed platform.
Antonio de las Nieves Stoner, our technical lead — OCI Architect Professional and Claude Certified Architect, both verifiable on About. He joins the technical calls on Zoom; Bárbara Trujillo leads the client relationship.
Mid-mess is the normal starting point. The first conversation maps what exists; the first engagement is chosen precisely because it doesn't require the mess to be solved first.
The first conversation maps your estate and names the smallest engagement that unblocks it — in writing, with done-criteria and a price.