01 · Access
What we need
- Peopleanswers in writing
- Examplesa week of real inputs
- Systemsread access, or a screen recording
For small teams · n8n · Postgres · DevOps
Automation and DevOps for small teams, built and then run: n8n workflows, AI steps a person approves, and the infrastructure under them, monitored after launch.
uros@foldnine.dev
The situation
A task that took one person an hour a day takes three people once the business doubles. Nobody decided that. It happened one hire at a time.
What costs the most is rarely visible: the order typed twice, the status copied from a carrier portal, the spreadsheet that has to agree with the ERP by Friday. None of it needs a new platform. It needs someone to look at the process on purpose, write down what each step costs, and automate the ones that are worth it.
Problems we remove
The common thread is repetition. When a person does the same steps every day, a system can usually do most of them — and the person approves the result instead of producing it.
How we work
01 · Start here · a few days
One repetitive process, as it actually runs rather than as it is described. It ends in a written report: every step, what it costs today, which are worth automating and in what order, and which should stay with people. Yours whether or not we build anything.
02 · Bounded · fixed scope, weeks
The system that does the work, in your environment, with a fixed scope and what will be measured agreed before it starts. It comes with documentation and a runbook, so it survives us not being in the room.
03 · Ongoing · monthly
Automation fails after the demo: an API changes, a retry sends a duplicate, a model returns something confident and wrong. Operating it means monitoring, fixes, keeping dependencies and models current, and a monthly report on what it did.
The process audit, in detail
The deliverable is a written report you can hand to someone who was not in the room — a partner, a board, the person who runs the process. That is the point of writing it down.
01 · Access
What we need
02 · What we look at
03 · What you get
The report
04 · After
No obligation
Sometimes the answer is a spreadsheet formula, a setting in a tool you already pay for, or "leave it with people". If that is the honest answer, it is the one in the document.
Capabilities
Find, research, qualify and prepare outreach to the right companies, with a person approving every message before it goes. We run this on ourselves: see below.
Remove repetitive back-office work: sync, notify, route, report, on a schedule or on an event. The process audit is where this starts.
Multi-step work where a model decides the next step, inside limits, with every action recorded. A model is used where a rule cannot do the job; everywhere else, code.
The screen people use to run, approve and inspect the work, so the system is something a team operates rather than something one person understands.
The APIs, integrations, data and infrastructure everything else depends on. This is where Foldnine started: infrastructure audits, DevOps sprints and fractional SRE.
Built so far
Foldnine finds its clients with a system we built: it discovers companies from public sources, researches each one, scores it, and drafts a first message. Nothing is sent until a person approves it.
Every fact in a draft carries the page it came from, so it can be checked in seconds. Every model call is recorded with its input and output. Rules that matter — who may never be contacted, what counts as evidence — are enforced by the database, not requested from a model. It is the same way we would build yours.
This is for you if
Probably not, if