$15 Micro-Automation Sprint

Examples of tasks that may fit.

These are scope examples, not claims about prior client work. The actual task is reviewed before payment and must be small enough to define with a short acceptance checklist.

Good fixed-scope shapes

Data and file workflows

CSV cleanup utility

Input: a recurring CSV export with inconsistent columns or values.

Deliverable: a reusable script that normalizes the agreed fields and writes a clean CSV.

Acceptance check: the sample input produces the agreed output columns without manual editing.

JSON transformation

Input: JSON records in one known shape.

Deliverable: a small script that extracts, renames, filters, or restructures the agreed fields.

Acceptance check: a supplied sample converts deterministically into the target schema.

Folder/file organizer

Input: a folder whose filenames or extensions follow an identifiable pattern.

Deliverable: a script that renames, sorts, copies, or reports on those files under explicit rules.

Acceptance check: a test folder is transformed without touching files outside the agreed scope.

Public web and API workflows

Bounded public-data extraction

Input: a public webpage or small set of public pages with a stable structure.

Deliverable: a script that extracts the agreed public fields into CSV or JSON.

Acceptance check: the agreed pages produce the required fields, with missing values reported rather than invented.

Simple API glue

Input: a documented API endpoint and a bounded transformation or request sequence.

Deliverable: a script that reads the agreed input, calls the API, and writes the expected result.

Acceptance check: a test request completes and the output matches the agreed structure.

Repetitive browser-workflow helper

Input: a simple permitted browser workflow with a stable sequence.

Deliverable: a bounded automation or helper script for the agreed steps.

Acceptance check: the test workflow completes without bypassing authentication, access controls, or site rules.

Usually too large for $15

What needs a different scope

Full applications

Multi-screen products, authentication systems, databases, long-lived backend services, or substantial UI work are not one-sprint tasks.

Open-ended scraping or research

Large crawls, indefinite monitoring, or research whose output cannot be bounded in advance needs a different agreement.

Unsafe or deceptive automation

Credential bypass, malware, private-data harvesting, spam, deceptive behavior, or automation that violates access controls is outside the offer.

A good request is concrete.

The easiest requests to approve specify the input, desired output, one or two acceptance checks, and any important timing constraint.