In development
Fewer repeated steps
What you would get: a map of a repeated barcode, label, stock or order task, one working example, checks against known answers and instructions. If artificial intelligence is useful, the example would include a review step and show wrong or unanswered results.
By email: agree examples with private details removed, review the proposed steps, try a small build and send written feedback. Receive the files and check report.
Still needed: the barcode/label sample, the office help pack for AI-assisted tasks and a checked connection to a test system. No email or account action would be taken without an agreed scope.
In development
Custom software and internal tools
What you would get: a small application, source files, example data, checks and instructions for use and maintenance.
By email: agree the screens and examples, review a test build, send notes and receive a handover package.
Still needed: a complete spreadsheet-to-barcode labels and stock checker sample. Software with several users would need separate sign-in, permission and recovery checks.
In development
Data checks and reports
What you would get: repeatable file imports, visible error rows, checked totals, a report and instructions for refreshing it.
By email: agree a permitted sample and expected totals, review the mappings and report, then receive the code and example results.
Still needed: checked messy-file examples and a repeat run. Missing data would be reported, not filled in by guessing.
In development
Small studies and prototypes
What you would get: one bounded technical question, a small model or working example, its inputs, findings and a list of what to check next.
By email: agree the question and what counts as evidence, review tables or a test build, then receive runnable files and a written report.
Still needed: a checked reference example, starting with the planned energy model. A study may end with no clear answer; it cannot promise a discovery.
In development
Technical research reports
What you would get: a dated question, search terms, source links, a comparison table and unanswered questions. Later work may organize grant information or earlier published inventions.
By email: agree the question and permitted material, review a sample evidence table, then receive the annotated report and search notes.
Still needed: a report with checked citations; grant and patent searches need their own checked examples. This would not establish eligibility, patent rights or medical, legal or financial advice.
In development
Plans for updating systems
What you would get: a system list, a map of what depends on what, options, a staged change plan and steps for undoing changes.
By email: share permitted exports and written answers, review diagrams and assumptions, then receive a plan and a checklist for each step.
Still needed: a made-up company example with a tested small move and recovery. A plan alone does not show that a move will work.
In development
Ongoing workflow care
What you would get: a register of the workflows we maintain, an agreed email queue, scheduled checks, change notes and written progress reports.
By email: keep a thread for each issue, agree changes in writing and review a regular report. Receive the records and instructions at handover.
Still needed: a trial showing that scheduled work, missed-check alerts and restoring a backup all work. This would not include emergency attendance or continuous monitoring.
