Tooltician — Carlos Ortega Gonzalez Scoped engagements for ops-heavy teams · EN / ES

Python automation, internal tools, and web technical hygiene — built to survive handoff.

elrincondeebano.com live store · daily orders, 100+ SKUs, 0 outages in 14 months

I help operations-heavy teams replace spreadsheet glue, brittle reporting, and manual review loops with Python systems that are easier to run, inspect, and hand off.

Best fit: reporting pipelines, ETL cleanup, scraping, internal tools, and stabilization work where the workflow already matters. Start with proof, then open a short brief.

I also cover web technical hygiene for live sites: security headers, HTTPS, DNS, forms, and lightweight monitoring — no internal hire needed. View web technical hygiene

View work first →

What the work replaces

  • Replace recurring copy-paste and spreadsheet glue with repeatable runs.
  • Make ETL, scraping, and reporting failures easier to detect before they hurt operations.
  • Catch invisible technical issues in live sites — broken forms, misconfigured DNS, absent headers — before they quietly cost leads or trust.

Operating notes

Scope
Reporting automation, ETL reliability, scraping, internal data tools, and workflow stabilization.
Delivery
Scoped implementation, direct communication, explicit assumptions, and handoff-ready docs.
Availability
Open to new scoped engagements. Reply within 48 h with a direct fit or no. Free 15-min diagnostic call — you leave with clear scope direction, not a sales pitch.
Location
Santiago, working EN/ES across LATAM and U.S.-friendly hours.

Verifiable results

0outages

live store, 14 months in production

Check it yourself →

100+SKUs

daily orders handled without an internal team

A+headers

own site security grade, independently checkable

Check it yourself →

2on PyPI

published packages with audit-grade logs

Check it yourself →

Not testimonials yet — measurable facts you can check right now.

Portfolio

Selected production work

Live sites, published packages, and automation already running in production.

Filter
JavaScriptBrowser ExtensionPrivacy

Chrome Web Store + Firefox Add-ons · Local-only browser extension

LinkedIn Spam Blocker

Browser extension that hides LinkedIn engagement-bait spam locally, with no telemetry, remote blocklists, or network requests.

Why it mattered
LinkedIn engagement-bait posts crowd useful hiring, industry, and work updates, while platform reporting often leaves the pattern untouched.
Built
Built a Chrome and Firefox extension that scans supported LinkedIn pages locally, hides matching spam patterns, and gives users language toggles, custom phrases, whitelists, snooze, and false-positive recovery.
Verified result
Published in the Chrome Web Store and Firefox Add-ons with packaged releases, CI, a public privacy policy, and a zero-network design.
PythonCLIAudit

Published on PyPI · Fail-closed audit automation

Conciliador Bancario

Audit-grade reconciliation tool that stops on mismatches instead of masking them.

Why it mattered
Reconciliation tools often optimize for convenience even when the underlying data does not actually match.
Built
Built a Python tool that stops on mismatches, produces deterministic outputs, and keeps append-only audit logs rather than silently producing a wrong result.
Verified result
Published on PyPI with reproducible installation and a traceable record of every run.
PythonPyPICLI

12 stars · 3 forks · Published on PyPI

★ 12PyPICI ✓CodeQL ✓

Rutificador

Published Python package teams can drop into forms, ETL jobs, and batch workflows.

Why it mattered
Teams processing Chilean IDs need consistent validation and normalization instead of re-implementing edge cases.
Built
Published a Python library and CLI with clean install paths, CI, and CodeQL-backed maintenance.
Verified result
Installable on PyPI and usable inside scripted and pipeline-oriented workflows.
TypeScriptFastAPIReact

DNS benchmarking with statistical rigor

DNSpect

Percentile-based DNS benchmarking stack built for analysis, not demo-friendly averages.

Why it mattered
Resolver comparisons often rely on single averages that hide distribution and outlier behavior.
Built
Built a TypeScript CLI, FastAPI backend, and React dashboard around percentile-based benchmarking.
Verified result
Technical framing centers statistical rigor instead of demo-friendly averages.
PythonScrapingGoogle Sheets

5 stars · 1 fork · Recurring production pipeline

★ 5Production

Jackpot Data Pipeline

Recurring scrape-to-sheets pipeline that removes manual lottery result updates.

Why it mattered
Lottery result sources are volatile, making manual updates brittle and time-consuming.
Built
Automated scraping, normalization, and Google Sheets publishing on a recurring schedule.
Verified result
Production pipeline with GitHub visibility and outputs designed for repeat use.
AstroSEOAccessibility

Live at noticiencias.com · Spanish-language science media, 8 disciplines

Live8 categories

Noticiencias

Live science publication with eight SEO-structured categories and readable editorial architecture.

Why it mattered
Science content sites often trade clarity for volume and lose structure as categories grow.
Built
Built an Astro editorial platform with category governance, source tracking, and methodology documentation.
Verified result
Live publication covering 8 disciplines with SEO-focused content architecture and RSS.
Services

Two service lines, seven delivery modes

Python automation for operations-heavy workflows — plus web technical hygiene for live sites that commercially matter but have no internal technical owner. Each service addresses a concrete problem with defined deliverables.

Reporting Automation

Replace recurring report assembly and back-office steps with scheduled or reproducible runs that emit the same answer every time.

Best when: Inputs, outputs, and workflow ownership are already known.

Deliverable: A scheduled job plus a runbook that reproduces the same report on demand.

View service

Evidence:

Web Technical Hygiene

Review security headers, HTTPS, DNS, forms, Search Console, and basic monitoring for live sites that have no internal technical owner.

Best when: The site is live, commercially matters, and nobody is reviewing the basics regularly.

Deliverable: A before/after report with verified fixes and clear priorities.

View service

Evidence:

Recurring Data Collection

Build scraping and acquisition flows that can be rerun safely, logged properly, and repaired without starting from zero.

Best when: The team needs dependable collection, not a one-off demo scrape.

Deliverable: A re-runnable collector with proper logs and repair notes.

View service

Evidence:

Operator-Ready Internal Tools

Package scripts behind internal APIs or guided interfaces so the workflow stays usable after the original builder steps away.

Best when: Several people touch the same workflow and handoff risk is real.

Deliverable: A documented internal API or interface the team can run without you.

View service

Evidence:

Public Technical Surfaces

Build lean Astro and web app surfaces that explain the system clearly, convert the right leads, and stay maintainable.

Best when: The site needs evidence and clarity more than decorative marketing.

Deliverable: A lean, maintainable Astro surface that loads fast and converts the right lead.

View service

Evidence:

Fail-Closed Financial Controls

Implement reconciliation and finance workflows that stop on mismatches, preserve audit traces, and make review easier.

Best when: A wrong answer is more expensive than a slower explicit check.

Deliverable: Reconciliation that halts on mismatch and preserves audit-grade logs.

View service

Evidence:

Structured Data Delivery

Produce outputs, dashboards, or publishing flows that remove manual copy-paste and make downstream use more predictable.

Best when: The pain sits in recurring delivery, not a single isolated analysis.

Deliverable: Structured outputs or dashboards with no manual copy-paste downstream.

View service

Evidence:

Not the right fit

  • Open-ended discovery with no concrete workflow already in use.
  • One-off analysis with no repeating delivery or operational need.
  • Engagements where the workflow owner has not been identified internally.
  • Cases where a full-time junior hire is a better economic fit than a scoped contractor.
Service with dedicated page

Is your site live but technically abandoned?

Web Technical Hygiene: review, basic hardening, and lightweight monitoring for live sites with no internal technical owner. Security headers, HTTPS, DNS, forms, Search Console, and small verifiable fixes — with a before/after report.

  • SMBs with a live site and no internal technical team.
  • Agencies needing external support for recurring low-margin maintenance.
  • Professionals and consultants where the site generates leads or reputation.

No alarmism. No promises of total security. Just clear technical review, verifiable fixes, and a before/after report.

Proof

Published, Live, and Tested

Packaging, quality systems, and communication style — all verifiable from public repositories and live deployments.

Packaging

Reusable libraries & CLIs

Projects like rutificador, bankrecon, and Monedario show the same packaging instinct across code and content: reliable structure, clear docs, and outputs people can actually use.

Quality

CI, scans & auditability

I bias toward test coverage, code scanning, deterministic outputs, and logs that make incidents easier to understand rather than harder to trace.

Communication

English-first, bilingual delivery

I write public project docs in a way that works for international readers while still supporting Spanish-speaking collaborators and clients.

Delivery

Lightweight systems that hold up

Automation that saves operator time, front ends that improve comprehension, and repositories that show how the work is maintained.

Portfolio Manager

Desktop-first Electron app with local-only persistence, session-secured Fastify backend, deterministic finance math, provider failover, and a deep automated test/quality stack.

LinkedIn Spam Blocker

Manifest V3 browser extension with zero-network privacy stance, multilingual spam heuristics, packaged releases, and live distribution in Chrome and Firefox stores.

Conciliador Bancario

Fail-closed behavior, append-only audit logs, architecture diagrams, and installable distribution.

Rutificador

Published package, CI workflows, CodeQL, and batch-friendly CLI documentation.

Monedario

Live site with finance calculators, editorial governance docs, and deterministic economic-data fallback.

About

Fit and Delivery

My approach starts with the workflow, not the code. Before implementation begins, every engagement goes through a scope pass — inputs, outputs, owner, failure modes, and handoff target. What gets built is a system the next person can run, diagnose, and improve without reverse-engineering it.

Explicit tradeoffs documented before decisions are made. Progress visible in GitHub commits, not status updates. Delivery notes written so the next person can run, debug, and extend the system without the original author on a call.

Best fit

  • Operations-heavy teams with a real reporting, ETL, scraping, or internal-tool bottleneck already affecting work.
  • Founders and managers who need a scoped build, not a permanent embedded product team.
  • Teams that value bilingual communication and a written handoff.
  • Not a fit: open-ended product teams, brand-only marketing sites, or undefined ownership.

What delivery includes

  • Short discovery to lock scope, constraints, and success criteria before implementation.
  • Visible progress, documented assumptions, and pragmatic tradeoffs instead of surprise scope creep.
  • Handoff materials: README, operating notes, setup steps, and the failure points worth watching.

Preferred stack and limits

  • Python, SQL, Bash, FastAPI, Selenium, BeautifulSoup, Pandas, Astro, and reliability-minded packaging.
  • GitHub Actions, CodeQL, package publishing, and repo structures built around tests and docs.
  • Not ideal for open-ended product strategy, full design-system programs, or staff augmentation with undefined ownership.
FAQ

Common questions before we start

What exactly do you do?

Two things: Python automation systems (ETL pipelines, scrapers, internal tools, and reporting workflows) and web technical hygiene for live sites (security headers, HTTPS, DNS, forms, Search Console, and lightweight monitoring). Both are scoped, documented, and built to keep running after handoff.

How much does it cost?

Scoped automation starts from 30 UF (~USD $1,200). An optional stabilization retainer is from 6 UF/month (~USD $240/mo). Web technical hygiene starts at a $69 diagnostic. Every engagement begins with a free 15-minute diagnostic call to confirm fit before any quote.

How does a project start?

With a free 15-minute call to confirm the problem is a fit. If it is, the next step is a short discovery to lock scope, inputs, outputs, owner, and success criteria — agreed in writing before implementation begins.

Do you work in English or Spanish?

Both. Delivery, documentation, and communication are bilingual. The Spanish-language services are calibrated for the Chilean and Latin American market; the English-language services are priced and delivered for US, UK, and European clients.

Where are you based, and do you work remotely?

I'm based in Santiago, Chile, and work remotely with clients worldwide. Engagements run async with visible progress in GitHub commits instead of status meetings.

What happens after the project is delivered?

You get handoff materials — README, operating notes, setup steps, and the failure points worth watching — so the next person can run, debug, and extend the system without me on a call. An optional retainer is available if you want ongoing stabilization.

Is this a one-off build or an ongoing service?

Either. Most work is a scoped, fixed-outcome build. If the system needs continued upkeep, a monthly stabilization retainer is available — but it is optional, not a lock-in.

Can I see real examples of your work?

Yes. Live systems include El Rincón de Ébano (e-commerce) and Monedario (personal finance for Chile), plus published PyPI packages (bankrecon, rutificador) and open-source tools on GitHub. The work section links each one.

Contact

Project Brief

Send the workflow, the bottleneck, the current owner, and the outcome you want.

How it works

  1. 01
    Send a brief or book a call

    Describe the workflow, the bottleneck, and what working looks like. A short note is enough — no deck required.

  2. 02
    Fit response within 48 h

    Direct yes or no on fit. If it is close, one clarifying question. No follow-up sequence if it is a no.

  3. 03
    Scoped proposal on a match

    Concrete deliverables, timeline, deposit terms, and handoff plan. No ambiguous retainers or open-ended commitments.

Use the form as the starting point. A short note is enough — cover the workflow, the bottleneck, and what a good result looks like.

Fit: scoped automation, ETL cleanup, scraping, internal tools, or web technical hygiene for a live site with a clear owner. Not fit: open-ended discovery without a concrete workflow or site.

Currently open for new scoped engagements.

Useful in the first note

  • Current workflow and tools involved.
  • Main bottleneck, failure, or review risk.
  • Desired output and who will operate it.
  • Deadline, cadence, or handoff constraint.

Primary contact

[email protected]

Address copied.

Project brief

A short, structured note is enough. The clearer the scope, the faster and more precise the reply — a direct yes/no on fit within two business days.

Prefer to talk first? Book a 15-min call →

Sent. I’ll reply by email within two business days.

Delivered via Formspree. See Privacy and Cookies.

Reply within 2 business days · Direct yes/no on fit · Free 30-min scoping call if it’s a fit · No sales sequence.