Small tasks eat the whole year
Five minutes here, three there. It looks like nothing, but it repeats every week. This is the timesheet of one person in an ordinary office.
| Task | Per week | Minutes | Hours a year |
|---|---|---|---|
| Copying data from emails into Excel | 25 | 6 | 130 |
| Typing in PDF forms | 30 | 5 | 130 |
| Sending payment reminders | 40 | 3 | 104 |
| Putting together the weekly report | 1 | 180 | 156 |
| About 13 full work weeks | 520 | ||
Example figures. Hours a year = times per week × minutes × 52.
Run the numbers on one of your tasks
That is about 9 full work weeks, on a single task.
Real work
Systems I built that run every day. The crossed-out line is how it was done before.

Law firm
Legal Operations Hub
- Before
- Requests came in through Slack, Gmail and the client portal, and someone had to log and assign each one by hand.
- Now
- Every message turns into a ticket with an owner and a deadline on its own, and the team gets the alert in Slack.

Law firm
Contract Automation
- Before
- Every contract or claim was built by copying a Word template and changing names, amounts and dates by hand.
- Now
- Documents come out with the right data, linked to their case, and get signed online with an e-signature.

Law firms
Lawsuit Management
- Before
- Each lawsuit was scattered across folders, spreadsheets and shared inboxes.
- Now
- Every lawsuit in one place, with parties, deadlines, hearings, filings and spend per case.
I also build websites and applied AI

Pest control, US
The Pest Central
Lead-generation site: local SEO, forms that actually reach the right crew, fast on mobile.

Packaging
Plupack
Brand and product site built with a partner, with a component library and internal tooling.

Ranching, open source
Cattle Segmentation
Computer-vision model that segments and identifies cattle in aerial imagery.
How I work
We talk
You tell me how your team works today and what eats the most time.
I map the process
I chart every step and show you what can be automated and what you save.
I build it
I start with what has the most impact, in pieces you can test.
I keep it running
I adjust what is needed until your team uses it without thinking.

About me
I'm a software engineer with a specialization in artificial intelligence from Tec de Monterrey, based in Querétaro, Mexico.
By 22 I had architected commercial platforms now running in production, and I was certifying flight-critical software at GE Aerospace under DO-178C.
I own the whole thing, from understanding how you work to leaving the system running. If something breaks, I know where to look because I built it.
- Education
- BSc Software Engineering, AI track, Tec de Monterrey
- Experience
- Flight-critical software, GE Aerospace
- Based in
- Querétaro, Mexico