People · two bases

Small team, full ownership of the work.

Alpgency is built by two founders who split time between Madrid and Zurich. We take fewer clients so the same people who scope a workflow are the ones who ship it and stay reachable after go-live.

Read how we commit on engagements See case studies

We started Alpgency after seeing too many AI projects die in slide decks. The pattern was always the same: big kickoff, vague roadmap, six months of meetings, nothing in production. We wanted the opposite: pick one painful process, automate it, measure hours reclaimed, charge only when the number is real.

About us

Business first. Not tech first.

We speak in hours saved and revenue unlocked, not in model names or framework wars. Small by design, so you work with the same people from first call to go-live.

We tell you upfront if we cannot help.: If your situation is not a fit, we will say so on the first call.
You own everything we build.: All code, automations, and systems are handed over to you.
We measure before we invoice.: Outcome fees are tied to real usage and validated saved hours.
Same team, start to finish.: The people in discovery are the same people who deliver.

Founders

Who you work with.

Delivery and architecture stay in-house from kickoff to the first month in production.

Zürich · CET

Co-founder · systems & architecture

Lucas Brunner

Owns technical scoping, integration design, and making sure what we ship survives contact with legacy tools.

Background in shipping production software for operations-heavy teams. Prefers boring, observable pipelines over demo-friendly prototypes. Spends most of the build phase in logs, not presentations.

Co-founder · delivery & client programs

Alejandro Pérez

Leads discovery workshops, writes the success metrics, and keeps projects inside a weekly rhythm instead of a quarterly fog.

Spent years translating between business owners and engineering teams. Cares most about the first thirty days after launch when habits either stick or snap back to manual work.

How we work together

Rules we do not outsource.

One thread from first call to handover: You do not get passed to a “delivery pod” you have never met. The founders stay on the account.
Measurement before the invoice: If we cannot show saved hours in a real month of use, we do not ask for outcome-based fees on that piece of work.
No parallel sales motion: We are not building a funnel of junior consultants. Capacity is limited on purpose.

Next step

Tell us which process costs the most hours.

We will reply with whether it is a fit, what we would measure, and what a first slice of work would look like.

Book a free consultation See the process