A software unit with an engineering parent — and a narrow offer.
Adqueo exists so operational software is specified with the same seriousness as the plant, the crew, and the audit it has to survive.
Mission
Specify and build the software operations actually run — custom systems, governed agents, and products that already encode that discipline.
Origin
Adqueo was formed inside Daezpro Corporativo — an engineering group whose plant, water, and utility clients kept asking for software that behaved like the systems around it: specified, auditable, safe to touch on a live shift. The unit was carved out so that discipline could sit under one roof with a software team that codes it, ships it, and stays with it.
Philosophy
Software is a specification of work. If the record cannot be walked from request to history, it is not ready. Intelligence is allowed where it can show its tools. Heritage from Daezpro Corporativo is a reason to be precise, not a reason to sell civil works from this site.
Daezpro Corporativo
The parent group offers a broader set of engineering services. Adqueo is the specialised unit for software, automation, and digital intelligence. Visitors looking for the full engineering catalogue should go to the group — not find it quietly bundled here.
Values
Specify the work
The loop is the spec. Screens come after.
Show the tools
Agents that cannot show a run log do not belong near a plant.
Stay a software unit
Heritage from the parent group. Not a second engineering brochure.
Methodology
- 01
Discover
Operations mapping, requirements, opportunities. Sample exceptions, not slogans.
- 02
Design
UX, architecture, prototype. Permissions as part of the workflow.
- 03
Engineer
Frontend, backend, mobile, AI — only where the spec earned it.
- 04
Integrate
ERP, IoT, APIs, identity. Event, payload, failure.
- 05
Launch
Deployment, migration, training. A cutover the operation can survive.
- 06
Evolve
Analytics, support, roadmap. The next loop.
Team
- FounderMariana Duarte-OcampoFounder & CEO
Eleven years specifying reliability and CMMS programs across mining and utilities operations before founding Adqueo inside Daezpro Corporativo. Trained as an industrial engineer, she still reviews every work-order schema personally before it ships — a habit from a plant manager who once made her re-walk a shutdown checklist twice. Off the clock she restores old field radios.
- Esteban Salgado ReyesHead of Engineering
Thirteen years in reliability engineering at a copper mine before joining. Still carries a torque wrench in his car trunk out of habit.
- Renata Ibarra CobosProduct Lead
Built CMMS and EAM software for a decade before Adqueo. Runs ultramarathons and treats specs the same way — pace, then endurance.
- Julián Restrepo NietoSolutions Architect
Spent nine years integrating SCADA and OT systems for a regional utility. Restores mechanical watches on weekends.
- Camila Otero VidalAI & Agents Lead
Shipped applied ML for industrial operations before agents were a product category. Keeps a shelf of failed models as a reminder.
- Tomás Bravo LinaresClient Delivery Lead
Ran field-service rollouts across four countries for a logistics operator. Learned to read a crew's mood before reading their tickets.
- Valentina Cruz MarínQA & Compliance Lead
Audited safety and quality systems for a food & bev plant before moving to software. Cannot walk past an unsigned checklist.
Composite team — illustrative. Names, roles, and portraits are representative, not a live roster.
Have an operation that generic software can't fit?
Bring the loop that is currently a spreadsheet. We will say whether this is custom software, a product, an agent — or not ours.