Skip to content

Work with me

From building a specific piece of software to becoming the person your company calls about technology, I help businesses solve real problems with software.

You do not need a defined project, a specification or a budget to get in touch. A problem is enough.

Currently available for new projects

Héctor Guedea
years building software
15+ years building software
projects delivered
35+ projects delivered
Computer Science
PhD Computer Science
countries worked with
3 countries worked with

Worked with

  • Sparq
  • Hotel Santa Fe
  • Akave
  • SEAD.ai
  • DeStor
  • Universidad de Colima
  • GRAYBOX
  • AdhocWorks
  • Secretaría de Cultura, Colima
  • Tropicana Community Services
  • mdBriefCase
  • BOGO FIT
  • Hacienda Cabo San Lucas
  • CMIC
  • Colegio Anáhuac Colima
  • Proyecto Arte 7
  • Instituto Tecomense
  • Cresenda
  • Skunk Socks
  • Casa Ofelia
  • Casona Roma
  • Grupo I / Grupo Tubac
  • Euromotors
  • Más Celular
  • Asesores Verdes
  • SOA
  • Taberna Atope
  • Casa Latón
  • Thunderobot
  • Cigis y Punto

Companies I have worked with directly, or whose platforms I built on while working for them.

Ways to work together

Three ways this usually works.

Most companies start with one of these and move between them over time. We work out which one fits in the first conversation.

Project-Based Development

A defined piece of work, scoped before it starts.

For companies that need a specific thing built: a platform, a system, a digitised process, an integration.

We agree the deliverables, the timeline and what "done" means before any code is written. You get weekly progress and something working to look at at each milestone, not a status report. At the end, the code, the infrastructure and the documentation are handed over and they are yours.

What it includes

  • Scoping and a written proposal before the work begins
  • Architecture and technical decisions documented
  • Weekly progress and a working version at each milestone
  • Deployment to production
  • Handover documentation and knowledge transfer

Right for you if

You know roughly what needs to exist, and you need it built properly and on a date.

Let's talk
Recurring

Ongoing Technology Partner

Technology capability every month, without hiring a team.

For companies that need technical work continuously — maintenance, improvements, integrations, automation — but not a full in-house development team.

A fixed monthly arrangement: your systems are maintained and monitored, and an agreed amount of development time goes to whatever matters most that month. Over time this becomes the most useful version of working together, because I know your systems well enough to be useful the same day you ask.

What it includes

  • Maintenance, updates and monitoring of your systems
  • An agreed amount of development time each month, spent as you choose
  • Integrations and automation as the need appears
  • Someone accountable when something stops working
  • A standing technical contact for your team

Right for you if

Technology is part of how you operate, the needs keep coming, and right now there is nobody to call.

Let's talk
Recurring

Fractional CTO

Technology leadership without a full-time hire.

For companies that need strategy, architecture and someone accountable for technology decisions, before a full-time CTO is justified.

I take on the technology direction on a defined commitment: the strategy, the architecture, the provider decisions and the hard calls. I am hands-on enough to still write code when that is the fastest way to settle something, and I am the person your team and your board can ask.

What it includes

  • Technology strategy tied to where the business is going
  • Architecture and the decisions that are expensive to reverse
  • Oversight of internal developers and external providers
  • Evaluation of proposals and quotes before you commit
  • Infrastructure, security and continuity planning
  • A defined number of days a month, agreed up front

Right for you if

Technology decisions are being made without anyone genuinely accountable for them.

Let's talk

How it works

From first message to working software.

Five steps, and the first two cost you nothing but a conversation.

  1. Initial conversation

    We talk about the company, what is not working and what you want to be different. You do not need a defined project, a specification or a budget for this.

  2. Discovery

    I look at the systems and processes involved and identify where the opportunity actually is. Sometimes it is not where it first appeared.

  3. Proposal

    Scope, the right working model, deliverables and timeline, in writing. If I am not the right person for it, this is where I say so.

  4. Execution

    I build and deploy it, with weekly progress and something working to look at rather than a status report.

  5. Ongoing support

    Where it makes sense, the relationship continues: maintenance, improvements and whatever comes next. Where it does not, you have everything you need to carry on without me.

What I do

The work itself.

All services

Proof

Work already in production.

View the full portfolio
In development
Client work Construction

TRAQ

Sparq

One place where a construction firm can see every project it has running.

A project management and tracking platform for Sparq, built around the way the firm actually works: architecture, preconstruction and construction, each with its own formats, and five roles that each see a different slice of the same portfolio. Planned against actual on schedule, on physical progress and on budget, with the deviation calculated rather than typed. Scope was signed before a line was written, and what is outside it is written down too.

Custom SoftwareEnterprise Systems
Client work Hospitality

Hotel Santa Fe

A bilingual hotel site built to take the booking, and to prove which campaign produced it.

The corporate site for a hotel in Puerto Escondido, Oaxaca: static, bilingual, and pointed at one outcome — a direct booking instead of one through an agency. Every call to action goes into the hotel’s own Zavia ERP engine, and the campaign that brought the visitor travels into the engine with them, so a reservation can be traced back to the ad, the post or the search that caused it.

Web DevelopmentIntegrations

What people say

From people I've built with.

Héctor consistently delivered well-architected solutions across multiple stacks. The kind of engineer you want when things need to actually ship.
Jennifer King DeStor DeStor — Platform development
Héctor built the systems that actually run the platform — real automation, not a prototype. He understood the business, not just the code.
Wayne Mask SEAD.ai SEAD.ai — Platform automation
Héctor built the core backend for DataDrop — uploads, payments, access control — production-ready from day one. He worked independently and just delivered.
Angelo Schalley Akave Akave — DataDrop

Before you write

The questions I usually get.

I do not have a defined project yet. Should I still write?

Yes — that is most of the conversations I have. A problem, a process that is costing too much, or a decision you are unsure about is enough to start from. Working out what should actually be built is part of the job, not a prerequisite for it.

How does a project get scoped?

We talk about the situation, I look at the systems and processes involved, and I turn that into a written proposal with deliverables, a timeline and what "done" means — before any code is written. If I think the right answer is to buy something rather than build it, I will say so there.

Do you work with non-technical companies?

That is most of my client work. I handle the technical decisions and explain the ones that affect your business in terms you can act on. You should never have to take a technical claim on faith.

Who actually does the work?

I do. There is no agency layer and no account manager. The person who scopes your project is the person who writes the code and the person who answers when something breaks.

Do you work remotely, and in which countries?

Remotely, from Mexico, with companies in Mexico, the United States and Canada. I work in Spanish and English. For local clients, meeting in person is not a problem.

Who owns the code?

You do, from day one — code, infrastructure and accounts, documented well enough that another developer could take it over. Nothing is locked to me.

Do you sign NDAs?

Yes, as a matter of course.

Get in touch

Tell me what's going on.

A few sentences about the situation is enough. I'll read it and tell you honestly whether I'm the right person for it.

I reply within 24 hours.

What is going on and what you would like to be different. You do not need a defined project or a specification — a few sentences is enough.

If you already know. If not, leave it — we work it out in the first conversation.

A range is enough, and it is fine to leave it blank. It only tells me what shape of project is realistic.

Prefer email? me@hectorguedea.com