guava
Book a call AI work, on paper before it starts.
Guava scopes, builds, and runs AI inside companies of ten to five hundred people. Every engagement begins as a written document: the workflow, the measure of success, the fixed fee, and the date it ends.
- Fee
- Fixed, and agreed in writing before work starts.
- Lead
- Romeo Diaz, principal, on every engagement through acceptance.
- Owner
- Your accounts, your code, your admin. Licences in your name.
- Start
- A twenty-five minute call about the bottleneck. No deck.
Three engagements, compared.
Pick by what you already know. If you cannot name the job yet, start with the audit; its fee is credited in full against an implementation that follows.
| 01 Two-week audit | 02 · most common Implementation | 03 Rollout & adoption | |
|---|---|---|---|
| For | You suspect AI could help but cannot name the job. | You know exactly what is broken and want it fixed. | You bought Claude seats and usage went flat. |
| Fee | $9k–14k | $30k–90k | $20k–45k |
| Duration | 2 weeks | 4–10 weeks | 3–6 weeks |
| You get | A workflow and data assessment, prioritised opportunities with costs, and feasibility criteria. Including a written case for not building. | A working integration inside your systems, tested against the criteria you helped write, with documentation and handover. | Role-specific workshops, reusable Skills built around your team’s work, and Elastic Cloud dashboards you own. |
| Discuss an audit → | Scope a build → | Plan a rollout → |
Ranges reflect scope, not seniority: the same two people work on every engagement. Claude and Elastic licences are billed to you directly and never marked up.
The engagement, clause by clause.
This is how every project runs, and the part of the relationship that is ours to guarantee rather than yours to hope for.
-
01
Scope
GuavaWritten before signature: the workflow, the measure of success, the fixed fee, and the date it ends. Three to five days, no charge.
-
02
Access
BothWe request the narrowest access that does the job, in writing, and log everything we touch. You grant it and you can revoke it.
-
03
Build
GuavaA senior engineer works inside your systems with weekly checkpoints against the agreed measure. You talk to whoever writes the code.
-
04
Acceptance
YouYou run the work on real tasks from your own queue and decide whether it meets the criteria. We do not declare it finished; you do.
-
05
Ownership
YouAccounts, code, Skills, and dashboards are yours at handover, with admin access and documentation. Licences stay in your name throughout.
-
06
Afterwards
OptionalMonthly care is available and optional, with thirty days’ notice to stop. It is never a condition of the build.
How you will know it worked.
The measure is agreed in writing before anything is built, then tested against real work rather than a rehearsed demonstration.
Real tasks
Representative work pulled from your live queue, not a curated sample set chosen to flatter the result.
Named limits
The cases the system should refuse, written down, with human review placed where the cost of being wrong is high.
Your dashboards
Business outcomes on Elastic Cloud instances in your account, so the reporting does not depend on us being in the room.
Launch is the beginning.
People change, workflows evolve, and a system nobody maintains quietly stops being used. Two monthly services exist for that, both optional.
- Adoption & Optimization
- Onboarding, Skills upkeep, usage reviews, and a focused improvement backlog.
- Workflow Operations
- Monitoring, troubleshooting, quality checks, and integration maintenance.
- Either service
- $4.5k+ / month
Thirty days’ notice to cancel. Defined coverage and improvement allowances. Claude and Elastic costs are billed to you separately.
Guava is new, and we would rather say so.
We launched in 2026 with no client logos to show you, and we are not going to borrow anyone else’s. So the engagement is built to make that irrelevant: an audit priced as a cheap test, a fee fixed before anyone starts, criteria you help write, and systems that remain yours whether or not you hire us again.
Fair questions.
You have no case studies. Why would I hire you?
Because the risk is bounded, not because we have asked you to trust us. The fee is fixed before work starts, the criteria are written with you, and you own the result. The two-week audit is the cheapest way to find out whether we are any good, and its fee comes off the build.
Why not just buy the team a chatbot?
Plenty of teams already have. Usage tends to flatten within a month, because a licence does not rebuild the workflow around the tool. That rebuild is the work, and we hand it back documented rather than keeping it as leverage.
Who actually does the work?
Romeo Diaz is the principal on every engagement, from scope through acceptance. A senior engineer builds alongside him and speaks to you directly. Small on purpose: there is no junior bench behind a project manager.
What happens to our data?
Work happens in your accounts and your cloud. We ask for the narrowest access that does the job, document what we touch, and return admin at handover. Your Claude and Elastic contracts stay in your name throughout.
What if it does not work?
We define success before building and test against it. If an audit concludes that AI is not the answer for a workflow, we write that down with the reasoning. You keep the assessment, and we have not sold you a build you did not need.
How soon can we start, and is monthly support compulsory?
An audit can usually begin within two weeks of signature, and implementations get a quoted start date alongside the fee. Monthly care is optional, priced separately, and cancellable with thirty days’ notice.
Bring your bottleneck.
Describe what is slowing the team down. We will tell you where to start, or that you do not need us yet.
Book a 25-minute call-
01
Twenty-five minutes on a call. No deck and no discovery workshop.
-
02
We ask about the data, the volume, and who does the work today.
-
03
You leave with a recommended engagement and a fee range, in writing.
- cal.com/romeodiaz/25min