We build systems your team actually runs
Most automation is built to win the demo, then quietly abandoned. The dashboard looks sharp in the pitch; a month later nobody opens it and the manual work is back.
We started Eclipse to work the other way around. Map the process your team already does, build the smallest system that removes the friction, and hand it over documented, so it keeps working long after we leave.
The first version was in front of my team in a week, and it actually matched how we work. I'd bought "automation" before that never got used. This did.
They handed us the docs and a walkthrough, and we've changed the workflow twice since without emailing them. That never happens.
No junior on a call reading a script. The person who built it explained it. Refreshing.
The story (so far)
Eclipse started with a spreadsheet nobody wanted to own.
A friend's ops team was re-keying the same orders into three systems every morning. Two hours a day, five people, every single day. The "automation platform" they'd bought a year earlier sat half-configured, because the demo never survived contact with their real data.
We rebuilt it in four days. One workflow, their actual fields, documented so their own coordinator could change it without calling us. The two hours went to zero.
That's the whole company. We're a small team of senior engineers who would rather ship one system that runs than five that demo well. We start from the work you already do, build the least software that removes the friction, and write it down so you own it.
The tools change every year. What we build for hasn't: fewer manual steps, less software to babysit, and a team that doesn't need us to keep it running.
— The Eclipse team