Custom tools
Make recurring file work repeatable.
We turn a defined, repetitive task into a small tool with written rules and a predictable output. That might be preparing a supplier file, generating a feed or checking catalog data before import.
Included
One job, named up front
Generators
Descriptions, attributes, feeds, CSV for PrestaShop or WordPress. Rules written, not improvised each week.
Converters
A price file or a supplier sheet turned into the shape the shop expects. Bad rows listed, not guessed.
A helper for one admin task
A small utility or a one-off migration script. It does that task. It is not a product you will sell.
Notes for the next file
How to run it again when the supplier sends the next sheet. Not a tool only we can start.
Technical SEO
Titles, structure, and whether pages can be indexed. Not articles, not a content plan, not a ranking promise.
AI assist
We use a model only where it speeds up the same task. A person reviews each draft; this is not a standalone AI product or a customer-facing bot.
How we approach the work
From first review to handover
-
1
You send one real input
The file you actually get, and what the output must contain. A sample of ten rows is enough to start.
-
2
We write the rules and the rejects
We agree on the rules before building the tool. If a rule needs to change, we correct it before processing the catalog.
-
3
You get a run you can repeat
Clean file in, report of refused rows out.
-
4
Notes for the next sheet
If the output should land in the shop on a schedule, that next step is integrations or automation. We do not pretend this tool already does that.
Common situations
Issues that often share a cause
- Supplier names do not match the attributes in the shop.
- Required fields are empty on part of the file, and nobody notices until import.
- Each weekly run looks slightly different because the rules were never written.
- A feed has to be built from the catalog, and the export from the shop is the wrong shape.
- Titles and indexation are a mess, and the request is technical, not “write us 200 articles”.
Scope boundaries
When a custom tool is not the right fit
- A product you plan to sell to other shops.
- Content marketing, or an AI studio.
- A tool that pushes the catalog by itself. Preparing the file is this job. Loading it on a schedule is another.
- A platform that should survive every future change without a new rule.
If the file is the bottleneck
Send one real sheet and say what the shop needs from it. Ten rows are enough.
A practical question
“Will this be finished software?”
The tool is built for one defined workflow. If a supplier changes the file format, the mapping needs a review before the next run. A broader process can be scoped separately.
A useful first message
Start with a real example
What the file is, and what the shop must receive from it. Attach nothing secret if you would rather describe ten rows. We reply with what we need to see.