Fixed-scope remote work
Practical help for founders, operators, and small teams that need a repo made safer for AI coding agents, a runnable script, a repaired test suite, or a narrow AI workflow prototype without a long agency process. Best first request: one sanitized sample, the desired output, and the command or workflow that currently fails.
CSV reconciliation
Self-serve download
A local Python kit for comparing two CSV exports and producing missing-row, duplicate-id, field-mismatch, and summary reports. Built for operators who can run a command and edit one rules file.
Done-with-you
A quick pass on one sanitized export pair. You receive a short findings report, mismatch examples, and the smallest next fix. Best when you want diagnosis before paying for cleanup.
$79 fixed diagnostic Start $79 auditDone-for-you
I adapt the workflow to one concrete file pair, run the reports, tune the matching rules, and return the script, output folder, README, and verification notes.
$199 fixed small scope Start $199 cleanupServices
Codex / repo workflow
A focused pass that makes an existing repo easier and safer to work on with Codex: command map, AGENTS.md guidance, test gates, PR checklist, and a short risk report.
Python / spreadsheets
Reconciliation scripts, cleanup tools, duplicate checks, report exports, API-to-spreadsheet helpers, and repeatable workflows from client-owned exports or documented APIs.
Repos / CI
Focused fixes for failing tests, broken builds, small React or Python bugs, GitHub Actions failures, stale PRs, and code paths that need a reproducible before/after result.
AI prototypes
A narrow prototype from provided docs, FAQ content, or internal notes. Built to validate the workflow before spending on a full production system.
Workflow
Read the CSV reconciliation checklist View a CSV reconciliation case study Read the Codex repo readiness checklist View a sample AI app rescue audit View a sample PR review View the proof index Copy a request brief
FAQ
Most fixed-scope jobs start after one sanitized sample, the expected output, and the failing command or current workflow are clear.
Yes, if access is authorized and the work can be verified without posting secrets or production customer data in public. Private repo or data access is handled only after fixed-scope agreement and payment, if needed.
Yes. A narrow audit can identify the next patch, missing tests, or automation plan before a larger implementation quote.
A fake-data sample, the expected output, a failing command, and a clear done condition usually make the first quote faster and safer.
A script, patch, review, or prototype with a short README, verification commands, and any known test or environment gaps.
Do not send passwords, API keys, payment details, customer records, production dumps, or files you are not allowed to share.
Payment and platform terms are handled outside the public brief. The public request should contain sanitized scope only; fixed-price work starts after scope agreement and payment.
Quote request
Open a GitHub issue with one sanitized input sample, the output you want, and any deadline or platform constraint. Do not post credentials, private customer data, payment details, production secrets, or files that you are not allowed to share.
Safety
No CAPTCHA bypass, account automation, spam, fake engagement, unauthorized scraping, credential handling, payment-platform bypass, or promises of accounting, tax, legal, financial, security, or business outcome correctness.