Bring files together
You open similar spreadsheets and copy their rows by hand.
Combine them into one file using the columns and duplicate rules we agree.
SMALL TASK. BETTER WORKDAY.
01 / DELIVERABLES
You open similar spreadsheets and copy their rows by hand.
Combine them into one file using the columns and duplicate rules we agree.
You switch between two tables to find missing items or different amounts.
Match a shared key, such as an order ID, and flag the items to review.
You type the same totals into your weekly reporting template.
Fill your supplied template with the calculations and layout we agree.
Login, payments, multiple user roles, ERP integration and AI document recognition are scoped separately. A simple file task may need neither AI nor a server.
02 / FROM OUR WORK
Uploaded port-call reports and settlement statements are checked for time and amount differences, then written into the existing spreadsheet. Uncertain values are flagged for review, not guessed.
Read the implementation and validation recordThis is the relevant part of a larger settlement system. It does not set a price, timeline or performance promise for a smaller task. See the original case for its validation scope.
03 / YOUR TASK, YOUR TOOL
We narrow the task together. Before work starts, we agree the input, output, price, timing and acceptance criteria. You receive the code we create and instructions for running it.
Receive the files and code for the agreed environment, with setup and usage instructions. Third-party tool licences remain separate.
Check the tool against agreed samples and expected outputs. Exceptions, extra features and any operating costs are identified in the quote.
For now, describe the file type and current steps. There is no need to send source files or personal data in your first inquiry.
Share your email and current process. We’ll agree on a feasible scope, price and timeline after reviewing it.