About Dimerso
Why we go under.
We are Dimerso, from Santa Bárbara de Heredia, Costa Rica. Before we build anything, we go into your business to understand how it really works.
Olive ridley · they come back to the same beach, arribada after arribada. Further down, why it keeps us company.
In the founder’s words
I spent years at software companies, building for businesses we rarely set foot in. Dimerso started there, with a simple idea: go in first, understand how the work really happens, and only then build.
People are part of every system.
Before we build
Your business already runs before technology arrives.
People, customers, workarounds and habits hold it together. Technology does not arrive into an empty space, so first we look closely at:
Surface · the process on paper
- The work
How the work actually happens
Not the process on paper: the order as it really arrives, who touches it, and in what order.
- The information
Where information begins, and where it gets lost
The moment a number is first written down, and every place it is copied, changed or forgotten afterwards.
- The customer
What customers experience
The business from the other side of the counter, the form or the phone call.
- The hand work
What people compensate for by hand
The re-typing, the reminders and the checks that keep things working, and that nobody has written down.
- What stays
What already works
The whiteboard everyone trusts, the habit that catches mistakes. Things that should stay.
- The leverage
Where technology creates leverage
And where it would only add another layer to manage.
Inside the operation
With the business
We work with the people who run a business, not at a distance from them.
The people who do the work know things no document holds. They show us how it really runs, and the system is built with them, not handed to them.
What working together looks like
- We start where the work happens.
With the people who do it, in person or on a call, before there is any proposal.
- We say what we see.
Where it runs well, where it gets stuck. Even when the answer is to build nothing new.
- We build with your team.
They test what we make against their real day and tell us when something is wrong.
How we work
Six principles we hold ourselves to.
First we dive in. Then we build.
We understand first. A recommendation made before that is a guess.
Build what belongs.
Technology should feel native to the business that uses it, not like something the business has to adapt to.
People are part of the system.
Adoption and trust are design problems. A system people do not trust is not finished.
Clarity over accumulation.
More software is not automatically progress. Sometimes the clearest answer is to remove something, or to build nothing new.
Quality is functional.
Craft is not decoration. It decides whether a system is trusted, adopted, maintained and pleasant to use every day.
Continuous evolution.
The business will keep changing. The technology should be able to change with it.
We stay
Like the olive ridley, we keep coming back to the same place.
That place is your business. A first version is where the relationship starts: after launch we stay close to your team, adjust what the real day asks for, and the system changes with your business.
Olive ridleys come back to Ostional, in Guanacaste, arribada after arribada: thousands at a time, nesting together on the same beach. Between 2006 and 2010, a single arribada brought about 476,000 females ashore to lay their eggs.
Valverde et al., Chelonian Conservation and Biology (2012)Arribada at Ostional, Guanacaste. Photo: Laranapeleona, public domain
Where we are
Santa BárbaraHeredia · Costa Rica
- Local time in Costa Rica
- UTC−6
- Where we are
- 10°02′ N · 84°10′ W
We would rather be close to a business than impressive from outside it.
Coming back up
Tell us how your business really works.
The version nobody wrote down is the one we want to hear.
