Edenio OS, the tool we use every day

An agency that sells management tools and tracks its own deals in a spreadsheet has a problem. So we started with ourselves.

Edenio OS is our internal operating system. It is live, we use it every day, and it is the only case study where we can show everything without asking anyone's permission.

1. Sales tracking#

The starting point: knowing where every deal stands without asking anyone.

The dashboard opens on what you need to know in the morning. Revenue, margin, pipeline, outstanding invoices. The summary depends on who is logged in: a salesperson doesn't need the same numbers as an executive, and a screen that shows everything to everyone stops getting looked at after two weeks.

What changed#

Before, the state of the pipeline was pieced together from memory in meetings. Now it is right, or it is wrong and that shows immediately, which comes to the same thing: someone fixes it.

2. Contacts and deals#

A contact, their conversations, deals, projects and reminders, on a single record.

• Timestamped history of every call, with the call summary
• Reminders attached to the person, not to a separate list
• Deleting shows a count of everything attached, so nothing gets lost by mistake
• Nothing is entered twice: a reminder created from a record stays attached to it

The detail that matters#

By default, reminders show for the whole team, not just for yourself. We made that change after a few weeks of use: filtering on "me" by default hid what everyone else had to do, and nobody noticed.

3. Quotes#

Quotes are generated from the tool, in a single template. A library of services, a calculated projected margin, the status of each quote, and the reason it was lost when it is turned down.

The actual conversion rate is read over a rolling twelve months. It is a number people think they know, and rarely do.

4. The partner portal#

Our referral partners submit a lead from a link, with no account to create, and track what they have brought in.

The portal never sees the database: it only receives what concerns it, and never a deal's internal notes. We apply the same rule for our clients, because a partner who isn't properly walled off is a leak you only notice after the fact.

5. The assistant#

A question asked in plain language, an answer with numbers, and actions carried out.

• Find an invoice from six months ago without digging through a table
• Summarize a call, create the contact and set the reminder in one go
• Read a screenshot pasted into the conversation
• Dictate instead of typing, with the transcript visible as you speak

What it taught us#

We built it on one AI provider, then the account was blocked overnight. We rebuilt that layer so it accepts five interchangeable providers.

It became a rule for us: no critical component depends on a single outside vendor. The same goes for your tools.

6. What we take away from it#

Building for yourself imposes a discipline a client project doesn't: we are the first to put up with a badly designed screen, and there is no one to tell that it's normal.

Every fix described here came from daily use, not from a design meeting. That is also how we work with our clients: first we look at how you really work, then we build.