APFerrer
About APFerrer

I unpick the problem, order the solution and write the code that works.

Forward Deployed Engineer with 17 years of track record and 4.85/5 across 269 verified reviews. Software, architecture, automation, AI, data and product. Remote from Spain, for teams that need someone to step in, understand and deliver.

APFerrer workspace
About me

Forward Deployed Engineer.

For a long time I had no clear label for what I do.

I work directly with companies to unpick problems that often arrive badly defined, scattered across processes, documents, tools and people.

From there I design and build solutions that can actually be used day to day, not demos or prototypes that only work in ideal conditions.

My work sits at the intersection of software development, architecture, automation, artificial intelligence, data and product. I can join a project from the initial idea, understand how the company works, order the information, define the flows, connect the systems and build the full solution.

I do not start from a technology looking for a problem to solve. I start from the problem to find the technology.

I have worked on enterprise platforms, document management systems, data processing, task automation, integrations, SaaS products and AI-driven solutions. Often the challenge is not writing the code; it is turning an informally explained need into a coherent, maintainable and useful structure.

The way I work is direct: understand, order, build, test and correct against real use. No over-engineering, no filler AI, no complicating a system so it looks more advanced than it needs to be.

I help companies turn confusing or manual processes into products and tools that actually work.

Why work with me

One person accountable, from diagnosis to code in production.

I understand the problem, I design the flow, I write the code and I answer when something breaks. No subcontractors, no layers of translation.

Problem-first, not tech-first

I start from the problem to find the technology

I do not arrive with a preferred stack looking for a place to apply it. I listen, order and pick the piece that solves. Sometimes it is a spreadsheet with Apps Script. Sometimes it is Next.js with Postgres and an LLM. The decision comes from the problem, not from what is trending.

  • Diagnosis before writing any code
  • Fixed-scope quote per phase with closing criteria
  • Practical documentation at end of each phase
And someone who tells you no

I say NO when I should

If your problem solves with Google Sheets, then it is Sheets. If you need to build a product from scratch, we say so. If adding AI only complicates things, we do not. If I am not a fit for your case, I recommend who is.

  • First 30 minutes free, no strings attached
  • No unnecessary layers, no AI for hype
  • No mandatory retainers or long contracts
How I work

Five steps. No extra layers.

The method is direct. There is no decorative phase where I sell you the process. Each step moves the problem a little closer to being solved.

  1. 01

    Understand

    Free 30-minute initial session. I listen to the problem as it arrives: badly defined, scattered across processes, documents, tools and people. No templates, no checklist, just questions.

  2. 02

    Order

    I turn what you told me into a structure: flows, entities, dependencies, decisions. This is where the informal problem becomes an architecture you can build on.

  3. 03

    Build

    I write the code. Short sprints, tangible deliverables at the end of each one. No extra layers, no pieces added for show. If Google Sheets is enough it is Sheets. If Next.js with Postgres and an LLM is needed, that is what gets built.

  4. 04

    Test

    I test it, you test it, the team that will use it tests it. Against real data, real cases, in the real workflow. Not against a happy path the developer set up.

  5. 05

    Correct against real use

    Quick adjustments over what breaks in the wild. Handover to the team with practical documentation. Code and data always in your account. Post-launch support by the hour if you want it.

Areas and technologies

The stack I actually use, not the one that sounds good.

From code to orchestration, from data to product. Public list so you know where I fit and where I do not.

  • TypeScript / Node.js
  • Next.js 16 / React
  • Postgres / Supabase / Neon
  • Python (datos, LLMs, scripting)
  • n8n / Zapier / orquestación
  • APIs REST y integraciones
  • IA generativa (RAG, function calling)
  • OpenAI / Anthropic / Google GenAI
  • Google Sheets / Apps Script
  • Data Mesh / DAMA-DMBOK
  • BPMN / mapeo de procesos
  • AGILE / Scrum / OKRs
  • EU AI Act / cumplimiento
  • Looker Studio / dashboards
  • Formación online en vivo

4.85 / 5 across 269 verified reviews from students and clients.

The bar: what we build gets used tomorrow by your team, not shelved in six months.

Shall we talk for 30 minutes?

No commitment. If we are not a fit I will say so and recommend who is. If we are, you get a plan and quote tailored to your case.