Axis
Four products around one axis, from the first sales contact to support.
Axis connects four products. LID is where a demand starts, on the commercial side. Serviços is where the technical team delivers it. Kyria is where the customer gets support. DocX holds the documentation. Each one passes what it learned to the next.
It belongs to Soeltech and a team builds it. I help lead that team, and I design and build parts of the products with them. Nothing on this page is something I made alone.
The premise is that tools for sales, support, documentation and projects work better when they share context. A customer shouldn't have to explain the same thing to sales, then to the people delivering the project, then to support. Each product hands the next one what it already knows.
The screens below are recreated from each product's interface. The companies and people in them are fictional.
LID
LID is the commercial side, where a demand starts. It's a CRM for teams that sell to other companies, at a desk and in the field.
A lead is someone still being qualified. When it's worth pursuing, it becomes an opportunity, once, and from then on the opportunity carries the negotiation. Opportunities move through stages on a kanban: qualification, proposal, negotiation, ready to close, and finally won, lost or cancelled.
Each opportunity keeps its whole history in one timeline: comments, stage changes, tasks, emails and calls. Two tools sit on top of it.
- Vox records calls and meetings, transcribes them by speaker, and attaches the recording to the opportunity.
- LID Intelligence reads that history and writes the summary: where the deal stands, what was done, what was promised, what to do next, and what's still missing.
Around the pipeline there are leads, contacts, organizations, tasks, a calendar and visits. For sales in the field, LID helps find companies on a map, plan commercial trips with their stops, and fill in a company's details from its website.
The interesting problem is modeling how complicated a real business is without forcing people into a rigid system.
Kyria
Kyria is where the customer gets support. The product's own line is that every request finds its way.
Requests arrive by email, WhatsApp, phone or chat, and each one lands in a team's triage. Someone accepts it, sets its status, and it leaves the queue. From there the ticket keeps the conversation with the customer and the activity side by side, with its properties, priority and the hours spent on it.
- Kyria Intelligence analyses a ticket. It suggests labels and fields, writes a summary, and shows the sources it used, including the team's pages in DocX.
- Dashboards show the operation as a whole: volume, response times and tickets by priority.
- Web and mobile share one design system, organized as atoms, molecules, organisms and templates. It's the approach I described in Atomic Design in React Native, at the size of a real product.
We've been exploring ways to make tickets, responsibilities, views, statuses and processes more intuitive and more flexible for the teams that live in them. A lot of what I think about quality, ownership and user experience has found a use here.
DocX
DocX holds the documentation. It's built on Docmost, an open-source wiki, and it's where the other three products meet.
Documents live in spaces, as a tree of pages. The tree can be grouped by page, by customer or by labels, without changing which page belongs under which. The editor is collaborative, with everyone's cursor on screen, and every page keeps its history: saved versions, published versions, and the changes between them highlighted.
- Signatures. A page can be verified and sent to be signed. The signer receives the exact version that was sent, and the result comes back as a signed PDF with a certificate and an audit trail.
- Maia, the AI chat, reads the documentation and answers with links to the pages it used.
- One page per customer. In Axis, the commercial summary comes from LID, the scope and deliveries from Serviços, and the support history from Kyria. Anyone who opens the customer's page sees the whole story.
What's mine and what isn't
My part is helping lead the work, shaping the products and building alongside the team. The products, their names and what they can do are at different stages of maturity, and some of what I describe here isn't released.