Measure before building
Every engagement starts with an audit and a baseline. Without a number from before, "it's much faster now" is just a feeling — and we can't tell you whether the work paid for itself.
About
Engineers who happen to like operations
Most automation projects fail quietly — not because the model was wrong, but because nobody wired up the retries, or the person who understood the process left. We build the unglamorous parts properly.
Who we are
A small team, on purpose
Mindspace AI is a senior team of engineers, data folk and operators. We've built internal systems inside logistics firms, marketplaces and venture-backed SaaS — which is why we tend to ask about your invoicing process before we talk about models.
We take on a handful of clients at a time. Everyone who sells you the work also does the work, and you'll never be handed off to a junior team after the kickoff call. That limits how fast we can grow, which we have made peace with.
The work is usually less exciting than the brochure suggests. A good week might mean deleting a spreadsheet, replacing four manual handoffs with one, and writing the documentation that lets your team run it without us.
- Senior only. No layers between you and the person writing the code.
- You own everything. Your repos, your cloud accounts, your data. No lock-in.
- Honest about limits. If a spreadsheet solves it, we'll tell you to keep the spreadsheet.
2019Founded
11Team members
60+Clients served
4Continents covered
How we work
Four things we hold to
These are not values on a wall. They are the reasons we occasionally lose pitches.
Ship in small pieces
Something real goes live every fortnight. Long build phases hide problems until they are expensive, and a system nobody has used yet is a guess with a budget attached.
Build for the Tuesday after
Logging, retries, alerting and a runbook, on everything. It is the difference between an automation that lasts a year and one that quietly rots the first time an API changes.
Hand the keys over
Documentation and training are part of the build, not an upsell. If you need us to keep the lights on, we have failed at the part that matters most.
The team
The people who do the work
Eleven of us, across four continents. The person on your kickoff call is the person writing the code.
Straight answers
What we'll talk you out of
A chatbot on the website
Occasionally the right call, usually not. If the questions are answerable from documentation you haven't written yet, writing it is cheaper and helps every channel at once.
A forecast built on messy data
A model fed with stale, internally contradictory inputs will be confidently wrong, which is worse than no model. Fix the pipeline first — that is usually the whole project.
Replacing a system that works
Ageing software that quietly does its job is not a problem. We'd rather automate around it than spend your budget on a migration nobody asked for.
Automating something you're about to change
If a process is under review, automating it locks in a decision you have not made yet. We'll wait, and build it once.
Book a demo
Come and talk to the people who'd build it
Thirty minutes, no pitch deck, and a straight answer on whether we're a fit for what you need.