Big Head Consulting
About

Twenty-five years inside
the operation, then the code.

Big Head Consulting is Robert Raymundo. The short version: a mortgage career that ran from originating loans to running operations, and then into building the systems those operations depend on — which is an unusual order to do it in, and the reason this firm exists.

The career, in order

Four jobs, and each one
explains the next.

  1. Loan officer

    Originating loans, which means sitting across from borrowers and being the person who has to explain a disclosure. Every design decision in a borrower journey traces back to having done this job — you cannot fake knowing where someone gives up.

  2. Sales leadership

    Running origination teams, carrying a number, and learning that a tool nobody adopts is indistinguishable from a tool that does not exist.

  3. Operations leadership

    Owning the machinery behind the loans: processing, underwriting handoffs, vendor orders, compliance timing, and the audit trail an examiner asks for. This is where you learn which shortcuts cost you a finding.

  4. Business intelligence and engineering

    Building the systems rather than requesting them — data models, integrations across the origination stack, and eventually a full origination platform. The rare part is not the engineering; it is the engineering done by someone who ran the operation it serves.

Licensed as a mortgage loan originator (NMLS) through June 2026; that registration went inactive on leaving salaried work to build Apsis Line full-time. Continuing education at MIT Sloan — AI: Implications for Business Strategy.

Why it matters to you

What that background
actually buys.

Compliance is not a phase

TRID, ECOA, HMDA, GLBA and BSA/AML are not requirements gathered from a document. They are constraints someone has been personally accountable for, which is why they show up in the architecture instead of in a checklist at the end.

No translation layer

You are not explaining your business to an engineer who will explain it to another engineer. The person writing the code has run the department that will use it.

Small on purpose, and honest about it

One person building carefully behind enforced checks, rather than a team whose coordination cost you would be paying for. The tradeoff is real, so the checks are published rather than described.

Where to go next

The claims, and the checks.

A career is a story, and a story is not evidence. The checks that constrain what this site is allowed to claim are the part you can actually inspect.