Where a small team should start with custom tools

9 October 2026. Crost.

The useful starting point is a job someone repeats, in a system the company already has. Crost maps that work first, then builds the tool or the automation around it. A model is chosen for that job. It is not the product.

What makes a good first job

• It repeats. Weekly or daily work gives a quick way to see whether the tool helped.
• The inputs are digital. Emails, spreadsheets, forms, and records in systems the business already uses.
• The rules are describable. If a person can explain how they decide, a tool can usually follow it, with a person approving the result.
• A mistake is cheap to catch. Drafts, summaries, and routing suit a first project better than anything that moves money on its own.

What to leave for later

Anything that spans several departments, depends on data nobody has cleaned up, or has no owner on your team. Those jobs are real, but they are second projects, after the first tool has shown how the team actually works with it.

What to bring to the first conversation

• The task, in the words of the person who does it.
• The systems it touches, and who has access to them.
• A recent example, including one that went wrong.
• What would count as better: hours back, fewer errors, faster answers.

What happens next

We scope that one job in writing, including data handling, the model, and where the tool runs, then build against the system you already have. The custom tools page describes the shape of the work and how we work covers the steps. A note through contact is enough to start. There is no public price.