Data is spent on repetition, large files and failed uploads. Preparation removes all three.
Do now: Complete one task with a fixed data budget and log what it actually cost.
Think fully offline, connect briefly, work offline again.Data costs money and connections fail. A workflow that only works on a good day is not a workflow. Designing for the constraint also produces better work, because it forces you to think before you generate.
Prepare offline, connect briefly
Write your full request before connecting — the context, the constraints, the format, and what you want returned. A well-prepared request answered once costs a fraction of six vague attempts, and the preparation improves the output regardless of connection.
Batch related questions into a single exchange. Five small questions asked across an afternoon cost far more than one message containing all five, because each round trip carries overhead and each partial answer invites another.
Ask for compact formats: a list rather than an essay, a table rather than prose, the specific section rather than the whole document. Ask for shorter responses explicitly; the default is verbose and you pay for every word of it.
One prepared request beats six improvised ones, on cost and on quality.
Manage files and failures
Compress images before uploading, crop to the part that matters, and send one file rather than five. A photograph straight from a modern camera is many times larger than anything a task requires.
Assume uploads will fail and design for it. Do the large upload once, on the best connection you have, and keep the result rather than re-uploading. Where a task can be done as text instead of an image, do it as text — it is a fraction of the size.
Save everything locally as you go. A long exchange lost to a dropped connection is not only frustrating, it is data spent twice. Copy useful outputs into a note as they arrive rather than trusting you can scroll back later.
Build the offline fallback
For anything you rely on, have a version that works without a connection: a saved prompt library, downloaded templates, a printed checklist, notes from the last session. The fallback is what makes the workflow dependable rather than merely possible.
Do the thinking offline. Deciding what you want, drafting the structure, and checking the result are all connection-free activities, and they are most of the work. The connected portion should be short and deliberate.
Track your actual cost for a week. Most people discover that a small number of habits — re-asking, uploading full-size images, long responses — account for the bulk of it, and each of those is straightforward to change once seen.
The fallback is what turns a workflow that can work into one you can depend on.