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

Reliable operational systems — scoped, documented, and built to survive handoff.

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

I replace recurring manual work, fragile data flows, and hard-to-own internal processes with reliable systems your team can run, inspect, and maintain.

Six focused services cover Python automation, recurring data collection, internal tools, financial controls, focused front ends, and web technical hygiene. Start with the closest operational problem.

International engagements are priced in USD. Chile and LATAM pricing is available in UF.View Chile / LATAM pricing

Compare services 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 →

3on PyPI

published packages with audit-grade logs

Check it yourself →

Measurable signals you can check before deciding whether the work fits.

Services

Six scoped services. One delivery standard.

Each service starts with a concrete operational problem, ends with something your team can run, and states what sits outside the engagement. Fixed scope, visible progress, and a documented handoff.

Python Automation & Data Pipelines

Turn recurring reports, ETL steps, and manual data delivery into scheduled, reproducible workflows.

Best when: Inputs, outputs, owner, cadence, and success criteria can be named.

Scope: One defined workflow or a coordinated multi-source system; excludes full data-platform programs and ML model development.

Deliverable: A tested pipeline with a schedule, logging, alerts, structured outputs, README, and runbook.

View service

Evidence:

Scope & evidence

Scope: One defined workflow or a coordinated multi-source system; excludes full data-platform programs and ML model development.

Evidence:

Recurring Data Collection

Collect public or authorized data repeatedly through resilient scraping and acquisition flows that fail loudly instead of drifting silently.

Best when: A recurring source feeds operations, analysis, or publishing.

Scope: Public or authorized sources with a repeatable collection need; excludes access-control bypasses and one-off lead harvesting.

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

View service

Evidence:

Scope & evidence

Scope: Public or authorized sources with a repeatable collection need; excludes access-control bypasses and one-off lead harvesting.

Evidence:

Internal Tools & APIs

Turn scripts and brittle operator steps into a CLI, internal API, or guided interface a team can use and hand off.

Best when: Several people touch the workflow, or the original author has become a bottleneck.

Scope: One known internal workflow; excludes full SaaS products, mobile apps, and open-ended staff augmentation.

Deliverable: A deployed CLI, API, or interface with validation, tests, operating docs, and handoff.

View service

Evidence:

Scope & evidence

Scope: One known internal workflow; excludes full SaaS products, mobile apps, and open-ended staff augmentation.

Evidence:

Financial & Audit Systems

Build reconciliation and control workflows that stop on mismatches, preserve audit trails, and make review easier.

Best when: A wrong answer costs more than a slower, explicit check.

Scope: One defined control flow or coordinated multi-source system; excludes certified audits, tax advice, and full ERP replacement.

Deliverable: A fail-closed control flow with deterministic outputs, validation rules, and audit-grade logs.

View service

Evidence:

Scope & evidence

Scope: One defined control flow or coordinated multi-source system; excludes certified audits, tax advice, and full ERP replacement.

Evidence:

Static Sites & Focused Front Ends

Build fast, maintainable public surfaces that explain the work clearly, convert the right lead, and survive handoff.

Best when: Clarity, performance, and maintainability matter more than decorative marketing.

Scope: Informational sites, landing pages, bilingual surfaces, and focused front ends; excludes complex SaaS and e-commerce backends.

Deliverable: A deployed, fast, indexable surface with forms, analytics, and maintenance documentation.

View service

Evidence:

Scope & evidence

Scope: Informational sites, landing pages, bilingual surfaces, and focused front ends; excludes complex SaaS and e-commerce backends.

Evidence:

Web Technical Hygiene

Review and improve security headers, HTTPS, DNS, forms, Search Console, and lightweight monitoring on an existing live site.

Best when: The site matters commercially, but nobody owns its technical basics.

Scope: Review, basic hardening, verified fixes, and light monitoring; excludes penetration tests and guarantees of total security.

Deliverable: A before/after report with verified fixes, clear priorities, and an optional monitoring plan.

View service

Evidence:

Scope & evidence

Scope: Review, basic hardening, verified fixes, and light monitoring; excludes penetration tests and guarantees of total security.

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.
Portfolio

Selected production work

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

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?

Six scoped services: Python automation and data pipelines, recurring data collection, internal tools and APIs, financial and audit systems, static sites and focused front ends, and web technical hygiene. Each one has a stated fit, boundary, deliverable, and documented handoff.

How much does it cost?

International automation builds start at $1,500, with paid scoping from $290 credited toward the build. An optional stabilization retainer starts at $290/mo. Web technical hygiene starts with a $69 diagnostic. Chile and LATAM pricing is available in UF on the Spanish version.

How does a project start?

With a free 15-minute diagnostic call to confirm fit. If there is a match, paid scoping locks the inputs, outputs, owner, failure modes, and success criteria in writing; that fee is credited toward the build.

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: a defined automation, data collection, internal tool, financial control, focused front end, or live-site hygiene problem 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 15-min diagnostic call · Paid scoping credited toward any build.