Skip to content

Services

Software for a problem you can name.

I work directly with the people who know the problem. That may lead to a public website, an application, an internal tool, or an integration that removes repeated work.

You communicate with the people building the solution. Jorge leads the technical work, with the option of additional experience from a small father-and-son development team when the project needs it.

Main services

Choose the type of work.

Services are temporarily unavailable while the content source reconnects.

How client work moves

A clear path from problem to release.

The client-facing process is the sequence of work you can see. The four-part philosophy below is how Jorge makes decisions inside that sequence.

Working philosophy

Decide what matters, decompose the hard part, ship something real, then compound what you learned into the next decision.

DecideDecomposeShipCompound
  1. 01

    Discovery

    Clarify the problem, people, constraints, and what a useful first release must prove.

  2. 02

    Planning

    Turn the brief into a small, ordered plan with decisions, risks, and a realistic definition of done.

  3. 03

    Development

    Build in visible increments so the important parts can be checked while they are still easy to change.

  4. 04

    Testing

    Test the real paths: mobile, keyboard, errors, empty states, integrations, and the hand-off to the next person.

  5. 05

    Launch

    Ship with the domain, deployment, metadata, analytics, and a short record of what changed.

  6. 06

    Support

    Leave the system understandable and make room for fixes, small improvements, or the next sensible step.

Have a real problem?

Bring the rough version. We can define the next step.

You do not need a finished specification. A useful first conversation is enough to decide whether there is a project here and what should happen first.

Start a project