Not software that only looks impressive in a demo. Software people can actually use.
To run a business. Teach a student. Manage a team. Serve a customer. Test an idea.
Or turn something that used to live in spreadsheets, WhatsApp messages and someone's head... into an actual system.
That's what we build.
We started by building things we needed. Software for our own ideas. Software for organisations we were part of. Software to solve problems that were annoying us.
And somewhere along the way, something became obvious:
We were getting pretty good at this.
We could take a messy idea, figure out what actually needed to exist, and turn it into software people could use. Not in six months. Not after a 97-page specification nobody wanted to read. Fast.
And with modern AI-assisted development, the gap between "I wish this existed" and "people are using it" became dramatically smaller.
So Ercomai became the place where we do that deliberately.
For a long time, turning an idea into custom software required a lot of time, a lot of money and a lot of people. That's changing.
AI has dramatically increased what a small, capable engineering team can build. We don't think the answer is to pretend that hasn't happened.
We partner with AI throughout our development process to move faster, explore faster and build faster. But faster doesn't remove responsibility.
The software still has to work. The decisions still have to make sense. The important things still have to be tested. And somebody still has to be responsible for what gets shipped.
We don't believe every software project needs a giant development team. Modern tools give small teams enormous leverage. So we keep Ercomai deliberately focused.
The people making decisions about your product aren't hidden behind six layers of account management. The people building understand what we're trying to accomplish. And the people thinking about the business understand what we're building.
Andrew leads the development side of Ercomai — architecture, development, technical decisions, integrations, testing. The parts nobody notices when they're working properly, and everybody notices when they're not. 😂
if it has an API, he's probably already looking at it.Lola works the other side of the equation: what should we actually build, who is it for, how should people experience it, and how do we get people to actually want and use it?
building the wrong thing beautifully is still building the wrong thing.Ercomai works with a broader team across the different parts of building and shipping software. Andrew and Lola are the two front-facing leads. They're not the entire company.
We assemble the right capability around what we're actually building.
We don't want you unable to leave because nobody else can access your product.
We don't want every tiny change to require a mysterious new invoice.
We don't want to disappear for months and emerge with something you've never seen.
We don't want to build 83 features because they sounded exciting in the first meeting.
And we don't want technology choices to become more important than the problem we're solving.
We want to build good software. Get it into people's hands. Learn what happens. And keep making sensible decisions from there.
We use modern development tools, AI and infrastructure to help us build effectively. The specific tools can change.
Hundreds of real users, real operations, one working platform.
View Project ↗From classroom signals to school-wide academic intelligence.
Case study coming soonA school portal staff picked up and started using immediately.
Case study coming soonMaybe it's still an idea. Maybe you've already started. Maybe people are already using it. Maybe something isn't working. Maybe something is working so well that it now needs to become something bigger.
Show us.
Start a Project →