Contact

Tell me what's taking too long.

I reply within 24 hours on business days.

There are two ways in. One starts a project. The other costs you nothing.

Option 1: Book twenty minutes

Free. Twenty minutes. One question: is the paid diagnostic worth your money?

I'm not going to diagnose anything in twenty minutes. That's what the paid session is for. This call is to find out whether you have the kind of problem I work on, and to tell you if you don't.

If it's a fit, the next step is the diagnostic: USD 150, fixed, credited in full against the build. One working session of 60–90 minutes, then a written baseline and a fixed-price plan in your hands within five business days. You'd be buying a measurement, not a sales call: if it says automating this won't pay for itself, that's what the document will say, and you keep the number.

Book twenty minutes

Option 2: Just send a message

Not sure it's a fit? Describe what's taking too long and I'll tell you straight whether it's worth automating. No pitch, no follow-up sequence.

What helps in a first message

You don't need to write much. Three lines is plenty. The ones that get the most useful reply say:

What the task is. Quoting, booking, invoicing, a report, data being retyped somewhere
Roughly how often it happens. A few times a day, twice a week, every Monday
Who does it today. You, one person on your team, three people

If you don't know the second one, that's fine. Not knowing is the normal condition, and it's the first thing the diagnostic fixes.

Direct

Based in Medellín, Colombia. UTC−5. My working day overlaps almost entirely with North America. I work in English and Spanish.

Questions people actually ask

How much does a project cost?: The diagnostic is USD 150, fixed. Builds are quoted after it, at a fixed price agreed before any work starts. I don't publish build prices because the honest answer depends on what the diagnostic finds. The full reasoning is on the services page.
What exactly do I get for the USD 150?: A 60–90 minute working session where I watch the work actually being done, then two documents within five business days: a written baseline and a scoped, fixed-price plan. If you take the plan and build it yourself or with someone else, that's a valid outcome and you keep the measurement.
What if the diagnostic says I shouldn't automate it?: Then that's what it says, and I'll tell you before you spend anything more. Sometimes the answer is a shorter process rather than an automated one. Sometimes the prize is four hours a year and isn't worth six weeks of work. That conversation is uncomfortable for ten minutes and saves everyone six weeks.
How long does a build take?: Most take four to eight weeks. You'll see something working at the end of week 3. The week-by-week breakdown is on the process page, including what it costs you in time: under six hours across two months.
Do you work outside Colombia?: Yes. Most of my work is remote, across Latin America and North America, in English and Spanish. Being on UTC−5 means my working day and yours are the same working day.
Do I need you on a retainer afterwards?: No, and I don't offer one. I build systems and hand them over. If a system needs me permanently in order to keep running, it isn't finished. You get the accounts, the workflows, the documentation, the credentials and the off switch. If we stop working together, nothing shuts down.
Who owns what you build?: You do. All of it. Nothing is hosted on something only I can access.
What if it doesn't work?: Thirty days after launch I measure the same thing, the same way. If the number didn't move, you'll hear it from me first. Included in every build, never a separate line item.

Book twenty minutes.

Or send the message above. Either way you'll hear back within 24 hours on business days.

Book twenty minutes