Private ordering was being coordinated informally.
A live storefront now handles 100+ SKUs and daily orders in production.
See the live business →If your operation still depends on copy-paste, fragile spreadsheets, or the one person who knows how it works, that is the problem I solve.
elrincondeebano.comreal business · daily orders · live productionI turn recurring manual workflows (reports, data collection, reconciliations, internal handoffs, and brittle scripts) into systems your team can run and trust.
You do not need a technical specification. Tell me what you do today, what breaks, or what keeps consuming time; I will tell you whether it is worth automating and what a sensible scope looks like.
International engagements are priced in USD. Chile and LATAM pricing is available in UF.View Chile / LATAM pricing
What the work replaces
- A recurring process still lives in copy-paste, spreadsheets, or manual handoffs.
- A report, collector, reconciliation, or script breaks often enough that people work around it.
- One person has become the operating manual because only they know the steps and failure modes.
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.
Visible proof
monedario.clpublic finance product · updated 2026, no ads, no paywallsbankrecon on PyPIfail-closed reconciliation · audit-grade logs
EN / ES handoffREADME + runbook, every engagement
What this looks like in practice
Chilean public data arrives fragmented and can change upstream without warning.
chile-hub turns it into reproducible, validated data builds with loud-failing checks.
Inspect the pipeline →A reconciliation should never look correct when the underlying data does not match.
bankrecon stops on mismatches and preserves a traceable record of every run.
Inspect the package →Proof should answer what changed for the operator, not only which stack was used.
Services
Start with the bottleneck, not the technology.
Tooltician is primarily for operations, finance, and small technical teams with recurring work that is manual, fragile, or owned by one person. The web services remain available, but they are secondary to that core.
Operational systems: primary focus
Automation, recurring data, internal tools, and financial controls for workflows already affecting day-to-day work.
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: Python Automation & Data PipelinesEvidence:
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: Recurring Data CollectionEvidence:
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: Internal Tools & APIsEvidence:
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: Financial & Audit SystemsEvidence:
Scope & evidence
Scope: One defined control flow or coordinated multi-source system; excludes certified audits, tax advice, and full ERP replacement.
Evidence:
Web surfaces: when the bottleneck is public-facing
Focused sites and technical hygiene when the business problem is clarity, reliability, or ownership of a live web surface.
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: Static Sites & Focused Front EndsEvidence:
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: Web Technical HygieneEvidence:
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.
Engagement shapes
Portfolio
Selected production work
Live sites, published packages, and automation already running in production.
Browse websites ↗Live at elrincondeebano.com · Private residential marketplace
El Rincón de Ébano
100+ SKU storefront handling daily orders for a live private-community business.
- Why it mattered
- Residents needed a private ordering flow that felt simpler than informal chat-based purchasing.
- Built
- Designed and run an Astro storefront with product filtering, bundle promotions, a real-time cart, and WhatsApp checkout.
- Verified result
- 100+ SKUs, daily transactions, and ongoing operator maintenance in production. This is not a demo.
Electron + React + Fastify + SQLite · Desktop-first portfolio tracker
Portfolio Manager
Desktop-first portfolio manager with local persistence, trust metadata, provider failover, and bilingual UI.
- Why it mattered
- Many portfolio tools push users into the cloud, hide pricing trust signals, or treat review workflows and financial math as afterthoughts.
- Built
- Built an Electron app with a Fastify API, SQLite storage, per-launch session auth, a decimal.js finance engine, provider fallback chains, and benchmark-aware review workflows.
- Verified result
- 1,470+ node:test assertions, 90+ Vitest tests, Playwright, mutation testing, and a 13-step CI pipeline covering lint, typecheck, quality, coverage, and audit gates.
★ 134 stars · 12 forks · Published data pipelines & CLI
chile-hub
A curated, reproducible data layer that normalizes and validates Chilean public datasets into single-line imports.
- Why it mattered
- Public datasets in Chile are fragmented, inconsistently formatted (e.g., variable-length CUT codes), and prone to silent upstream changes.
- Built
- Built an automated pipeline that extracts, sanitizes, and verifies geography, demography, and health data, exporting optimized Parquet, DuckDB, and JSON builds with loud-failing invariants.
- Verified result
- 134 GitHub stars, fully automated CI/CD pipeline, CLI/API package, and a public static dashboard with verified datasets.
Who you work with
You work directly with Carlos: the person who scopes, builds, and hands off the system.
Tooltician is not an agency front hiding an anonymous delivery team. I am Carlos Ortega: I read the first note, ask the uncomfortable scoping questions, write the code, review the failure modes, and hand the system over. That direct accountability is part of the product.
My goal is not to make you dependent on me. I prefer explicit tradeoffs, visible progress, and delivery notes that let the next person run, debug, and extend the system without needing the original author on a call.
Where I add the most value
- Recurring operational work already costs time, attention, or review risk.
- A script, spreadsheet, collector, reconciliation, or internal process has become fragile or person-dependent.
- You need a bounded system delivered by one accountable builder, not an open-ended product team.
What I personally own
- Scoping the workflow, constraints, failure modes, and success criteria before implementation.
- The build itself, including tests, observability, pragmatic tradeoffs, and the awkward edge cases.
- The handoff: README, operating notes, setup steps, and the failure points worth watching.
Why the handoff matters
- The system should still make sense when I am not in the room.
- Progress and assumptions stay inspectable instead of living in status calls or private memory.
- The default outcome is documented ownership by your team, not a permanent dependency on Tooltician.
Trajectory
- 2021–present · Independent software developer: Python/SQL automation, ETL, scraping, APIs, and internal tools for real operations, published under Tooltician.com.
- 2025–present · Founder & developer, Monedario.cl and Noticiencias.com: a personal-finance platform and an automated publishing pipeline with source verification.
- 2019–2021 · Atento Chile / Movistar: data analysis for churn and retention, and corporate-account reconciliation of balances, payments, and discrepancies.
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
- 01Send a brief or book a call
Describe the workflow, the bottleneck, and what working looks like. A short note is enough, no deck required.
- 02Fit 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.
- 03Scoped 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
carlos@tooltician.com
Address copied.
Need more detail before writing? Compare the fit, boundaries, deliverables, and evidence for allsix scoped services.