From bespoke automations to a platform: what changed and what didn't
BrewMy{Code} started by building custom automations for companies one workflow at a time. Here is why we turned that work into a product, and what our early customers taught us.
We started BrewMy{Code} doing something unglamorous: sitting with operations teams, mapping the manual chains that ate their week, and building automations to carry them. Invoice processing. Order handling. Monthly reporting. Ticket routing.
After enough of those projects, the same components appeared in every one.
The parts that were always the same
- A knowledge layer. Every automation needed to look things up — a policy, a supplier record, a previous ticket — and every company's knowledge lived in Drive, SharePoint, Notion, Slack and a handful of business systems. Connecting those, keeping them synced and respecting who was allowed to see what was a project in itself, every time.
- Tools with guardrails. Reading from a CRM is easy. Writing to an accounting system safely — with validation, approvals for unusual cases and a record of what changed — took most of the engineering effort.
- Traces. The first question after any automation runs is "what did it do and why?" We built logging and replay for every customer.
- Evaluation. Nobody switches an automation on without knowing how it performs on last quarter's cases.
So we built those four things once, properly, and made them the platform. The Knowledge Search Agent is the knowledge layer with a conversation on top. Enterprise Agents are the tools, guardrails, traces and evaluation, with configuration instead of custom code.
What didn't change
We still start every customer relationship the same way: a 30-minute call where we look at the actual workflows and say honestly whether an agent will pay for itself. Sometimes the answer is "not yet, fix the process first". We would rather say that than sell a pilot.
We are still a small team, and that is deliberate. The engineers who build the platform are the ones who sit with customers to get agents into production.
What the platform made possible
- Time to production dropped from months to weeks, because the connectors, permission model and approval flows already exist.
- Customers own their agents. Configuration is exportable and readable; there is no bespoke code base that only we understand.
- Improvements compound. A better re-ranker for Finnish documents helps every customer the day it ships.
If you have a manual chain that shouldn't need a person, we would like to look at it.