Skip to content

Full-stack developer · Argentina (UTC-3)

Reliable data collection and automation, built to keep running.

For teams that depend on web data and can't afford for it to break quietly. I build scrapers, data pipelines and the systems around them: queues, retries, recovery after failures and monitoring. I work async, with written updates.

nahuel@nahuelfb.com

Currently taking on new pilots. I reply within one business day.

what-i-build
collect
web sources · APIs · browser automation
queue
Redis job queues, split by type
recover
retries · resume after failure
watch
monitoring · alerts
ship
API + web app
stackTypeScript · Node.js · React · Next.js · PostgreSQL · Prisma · Python · FastAPI · Playwright · Redis

Case study · due-diligence platform

Data source modules
38
Automated tests
~1,700
Built solo
~3 months
Time per report
3–4 min

Measured on the first 20 reports.

01 / Case study

A due-diligence reporting platform, built solo

A web platform that produces due diligence reports on people and companies. It collects data from 38 source modules in parallel and assembles the results into one report. The client uses it internally, in production. I built the backend, the API and the web app on my own in about three months.

Simplified. Source names are left out for confidentiality.
Isolation

Redis queues are split by type of source, each with its own worker, so a heavy module doesn't hold up the light ones. A dispatcher shares capacity between accounts.

Testing

About 1,700 automated tests, and CI runs on every pull request.

role
Sole developer (backend, API, frontend)
sources
38 modules: 21 for people, 17 for companies
queues
Redis, separate queues and workers by type of source
scheduling
Global cap on concurrent reports, turns shared between accounts
backend
Python (RQ workers), FastAPI, Playwright, Redis
database
MySQL, private, not exposed to the internet
frontend
React, TypeScript
quality
~1,700 automated tests · CI on every pull request
sources used
Public and third-party web sources

Client and data sources anonymized.

Have a similar problem? Email me a short description.

Email me

02 / How I work

Start small, in writing

  1. 01

    You describe the problem by email.

    Tell me what data you need, where it comes from and how often.

  2. 02

    We agree on a small fixed-scope pilot.

    Scope, price and delivery date are agreed in writing up front. You get a working deliverable, then decide whether to continue.

  3. 03

    I work async and report every week, in writing.

    Each week you get a written update on what's done and we agree on what comes next. You can write to me in between if something looks off.

  4. 04

    Optionally, a monthly retainer.

    Sources change without warning. On a monthly retainer I monitor your collection, handle breakages quickly and send a written report each month on what ran, what failed and what I did.

03 / Personal projects

Three things I built for myself

Turnealo

A booking SaaS for businesses that run on appointments. Clients book themselves, each professional has their own schedule and services, and each business gets its own page.

  • Next.js
  • React
  • TypeScript
  • Prisma
  • Supabase
  • Zod
  • Web Push

04 / Contact

Have a data collection or automation problem?

Send me a short description and I'll reply within one business day with questions or a pilot proposal.