Skip to content

Services

Different realities deserve different technological answers.

Once we understand how a business works, the answer can be software, a connection, an automation, useful information or a better customer experience. Sometimes it is nothing new.

Six situations

Each begins with something a business lives with, and ends with what can belong there.

  1. Stop 01 / 06−5 m

    What the business lives with

    A process the business cannot see.

    What it looks like

    Work lives on a whiteboard, in a chat and in someone’s memory. Nobody sees the whole until something is late.

    What can belong

    Make it visible.

    What you receive

    A board with every order, task or case and its status, so each person sees what is theirs.

    How we would approach it

    1. Give every unit of work a record and a state, in the states the team already uses, not a template’s.

    2. Show each role only what it acts on: packing an order and deciding about it need different views of the same record.

  2. Stop 02 / 06−8 m

    What the business lives with

    The same information, kept in several places.

    What it looks like

    A price or a stock count lives in three tools and agrees in none, so someone reconciles them by hand.

    What can belong

    Connect it.

    What you receive

    Integrations between what you already use (invoicing, point of sale, store, spreadsheets), so information is written once.

    How we would approach it

    1. Decide which system owns each piece of information before connecting anything. A connection without an owner copies the disagreement faster.

    2. Use each tool’s API where one exists and a scheduled sync where it does not. A person shouldn’t have to be the permanent connector between systems.

    Where we hold back

    Sometimes the fix is fewer places, not more connections: retiring a spreadsheet can do more than integrating it.

    In our work

    Hortiluma's till, electronic invoicing, orders and online store run on one system, Farol, in production. Hortiluma belongs to the same family behind Dimerso.

  3. Stop 03 / 06−11 m

    What the business lives with

    A handoff that consumes someone’s attention.

    What it looks like

    An order arrives in one place and someone types it again in another. The work is simple; the attention it takes is not.

    What can belong

    Automate what should be automatic.

    What you receive

    Automations and AI that do the repetitive handoffs (reading orders, producing documents, telling the right person) with a person confirming what matters.

    How we would approach it

    1. Separate the mechanical part of a handoff from the judgment in it. Automate the first; give the second a better view.

    2. Trigger from the event itself, an order placed or an invoice issued, not from someone noticing it.

    3. Where the input is loose language, such as an emailed order, a model can structure it, with a person confirming before anything is sent.

    In our work

    At Hortiluma, Farol reads its large customers' orders, whether they arrive as a sheet, PDF or photo, and builds one order per delivery day; a person checks what doesn't match. What took 6 to 10 hours every week now takes about 10 minutes a week. Hortiluma belongs to the same family behind Dimerso.

    Applied AI
  4. Stop 04 / 06−14 m

    What the business lives with

    An operation bent around generic software.

    What it looks like

    The team works around the tool: exports, side spreadsheets, steps done outside because the software has no place for them.

    What can belong

    Build what belongs.

    What you receive

    A system built to measure, or Farol if your operation turns on sales, invoicing and stock.

    Where we hold back

    If a standard product fits with sensible configuration, we recommend it. Custom software is a commitment, and it has to earn it.

    How we would approach it

    1. Model the data on the operation’s own vocabulary and on how the work actually moves.

    2. Build the smallest complete version that can run a real day, then extend it where the work shows it needs to go.

    In our work

    Farol began this way: a sale, an invoice, a stock count and a collection kept in step by hand, in business after business in Costa Rica, until the pattern became its own system.

    Farol
  5. Stop 05 / 06−17 m

    What the business lives with

    Decisions made without usable evidence.

    What it looks like

    The data exists, but a decision still waits for someone to build a spreadsheet, or is made by instinct.

    What can belong

    Make the information useful.

    What you receive

    Reports and alerts with the numbers you actually decide on, from the data you already have.

    How we would approach it

    1. Start from the decision, not the dashboard: which question, who asks it, how often, and what the answer would change.

    2. Fix where the numbers come from before charting them. A clean view of untrusted data only hides the problem.

    3. Use applied intelligence where a probable answer helps, such as anticipating demand, and plain queries where the answer must be exact.

    Where we hold back

    A decision made twice a year may need a well-kept report, not a live view or a model.

  6. Stop 06 / 06−20 m

    What the business lives with

    A customer experience disconnected from the business behind it.

    What it looks like

    The website promises one thing and the operation delivers another: a booking is received, and nothing behind the page knows it exists.

    What can belong

    Redesign both sides.

    What you receive

    A website, a booking flow or an assistant like Delfín AI, connected to how your business runs inside.

    How we would approach it

    1. Design the customer’s path and its operational counterpart together: every promise on screen needs a place in the operation that keeps it.

    2. Let the experience read the records the team works from, so availability, status and prices are true when a customer sees them.

    Where we hold back

    If the operation cannot keep a promise yet, it does not go on the page.

    In our work

    BeautyBox: a live public booking experience built around its services and locations.

    Cases

The kit−24 m

Rarely one technology alone.

Most responses draw on more than one material. One draws on none.

  1. Purpose-built software

    1 of 6 stops

    Used at stops: 04

  2. Operational systems

    3 of 6 stops

    Used at stops: 010406

  3. Automation

    1 of 6 stops

    Used at stops: 03

  4. Integration

    4 of 6 stops

    Used at stops: 02030406

  5. Information & analytics

    3 of 6 stops

    Used at stops: 010205

  6. Applied intelligence

    2 of 6 stops

    Used at stops: 0305

  7. Digital experience

    1 of 6 stops

    Used at stops: 06

  8. Something that already works.

    0 of 6 stops

    Nothing new

Sometimes the right intervention is no new technology: a step that changes owner, a tool already paid for used properly, a report nobody reads that stops. When that is the answer, we say so.

After it exists

The work continues once the system runs.

  1. 01−12 m

    People are part of the system.

    Adoption is designed, not announced. The people who use a system shape it, and we prefer to try a first version against real work before it replaces anything.

  2. 02−9 m

    The business will keep changing.

    New services, a second location, another person taking orders. We build so the next change fits where the work moved, without rebuilding what works.

How we start

Four steps, and the first one is free.

  1. A free diagnostic.

    A 30 to 45 minute call to understand how you work today, and a written recommendation of what is worth doing, what is not needed, and where AI really helps.

  2. A proposal sized to your business.

    What to do first, in what order and what it costs, in writing. The first step is often small.

  3. We build it with your people.

    We put a first version to work on real work, and extend it with what we learn.

  4. We stay.

    The same people who built it look after it and adjust it as the business changes.

Let’s talk

Start with the business.

You don’t need a technical spec to talk to us. Tell us, in your own words, how the work runs today and where it gets stuck. Working out which technology belongs is our part.

Inside the Hortiluma store: blue crates in the foreground, tables of fruit and vegetables, two people arranging produce.
Hortiluma, the shop floorSan Antonio de Belén. It runs on Farol, and it belongs to the same family behind Dimerso.

What to bring

Just how your days really run. We’ll bring the rest.

Or write to ushola@dimerso.com

Debrief

What people usually ask us.

Out of the water, divers go over the dive. These are the questions we hear most before a first conversation.

What does Dimerso do?

We build the systems businesses run on: custom software, automation, integrations and applied AI, shaped around how your team works, so they actually use it. First we understand how the business runs, then we decide what technology belongs in it.

Do I need to know which technology I need?

No. You don’t need a technical specification to talk to us. Tell us in your own words how the work runs today and where it gets stuck. Deciding which technology fits is our part.

Do you always build new software?

No. The answer can be software, a connection between systems, an automation, useful information or a better experience for your customers. Sometimes it is nothing new: retiring a spreadsheet can do more than integrating it.

What happens once the system is running?

The work continues. We prefer to test a first version against real work before it replaces anything, and we build so the business’s next change fits where the work has moved, without rebuilding what works.

What are Farol and Booka?

They are Dimerso's own products. Farol is for selling, collecting and organising a business in Costa Rica: till, electronic invoicing, orders, stock, collections and banking, with Farol IA included. It is live at farol.cr. Booka, for online bookings, is in development.

Where are you?

In Santa Bárbara de Heredia, Costa Rica. Cases shows the work we have published, with each business and what was built for it.

How do we start?

With a free diagnostic. Message us on WhatsApp, write to hola@dimerso.com or use Contact, and tell us how your business runs today; we set up a 30 to 45 minute call and then send you a written recommendation.

Is my business too small for this?

Rarely. Many of the best changes are small: one automated handoff, or two systems that finally talk. If what you need is simple, we tell you, and if nothing needs building, we tell you that too.

I already have software. Do I have to replace it?

Not necessarily. Often we connect it to the rest or build around what already works. We only propose replacing something when it is really costing the business.

How long does it take?

It depends on the scope, and the proposal gives it to you in stages. We would rather put a first version to work on real work soon and extend it, than have you wait months for something complete.

How much does it cost?

It depends on what makes sense for your business, and sometimes what makes sense is small. The diagnostic is free, and the proposal tells you in writing what each stage costs before you decide.

Do you use artificial intelligence?

Where it really helps. At Hortiluma, Farol reads the orders that used to take 6 to 10 hours a week (now about 10 minutes; Hortiluma belongs to the same family behind Dimerso), and Delfín, our assistant, will serve customers on WhatsApp, Instagram and Facebook. Where it is not needed, we leave it out.