Skip to content
Datasmarts
Menu

AI assistants, automation and custom AI

I find where AI pays off in your business. Then I build it.

Assistants that answer your customers and automations that clear your team’s busywork, measured against what that work cost you before.

Jesús Martínez, founder.
You talk to the person who builds it.

Client story · Property rentals
<1 minfor a guest to get an answer, down from minutes
“With Jesús' help, we rebuilt our retrieval system from first principles, reworking an over-engineered behemoth into a lean, mean retrieval machine.”

Harry Dubke
CTO, Cortado, Inc.

Read the full story 

Two ways to work with me

Pick one or combine them.

Understand the problemBuild the system

How I work

One process, one number, one build.

  1. Understand the work

    We walk through one process: what runs by hand, how often, and what it costs you.

  2. Agree on the number

    We agree on what gets built and the number it has to move.

  3. Build, hand over, measure

    I build it in your accounts, hand it over documented, and we check the number together.

Jesús Martínez

Hi, I’m Jesús.

14 years in software, 10 of them shipping machine learning to production. Author of TensorFlow 2.0 Computer Vision Cookbook. When you hire Datasmarts, I’m the one building it.

More about me 

Common questions

Who actually does the work?

I do. Datasmarts is one person, Jesus Martinez, and the person you talk to on the first call is the person who writes the code. There is no account manager layer and no handoff to a delivery team you have not met. The trade-off is capacity: I take on a small number of engagements at a time, so timelines are real rather than optimistic.

How does an engagement start?

With a conversation about your processes, not a specification. We walk through what runs manually today, how often, and what it consumes, and that produces a ranked shortlist with a cost against each candidate. The build, if there is one, is quoted from that shortlist rather than from a wishlist.

What if the assessment says we should not build anything?

Then it says so, and you have still got the thing you paid for. Some processes run too rarely to justify the work, some are about to change and would be automated twice, and some are cheaper to fix by removing a step than by automating it. Knowing which of those you have is worth more than a build nobody uses.

Who owns what you build?

You do. The code, the workflows and the documentation are yours at handover, running in your accounts. Nothing is licensed back to you and nothing depends on a Datasmarts account continuing to exist.

All questions 

What would you take off your team’s plate?

Tell me which process eats the week. In fifteen minutes you’ll know whether AI would pay for itself there.