I’m building Chrono because I want business software to help me understand the path, as well as the current position. I’ve spent 20 years working with CRMs. The records matter: contacts, companies, opportunities, campaigns and tasks. But I keep coming back to the connections between them. What changed? What did we understand at that moment? Why did a sensible decision lead to a different outcome than we expected?
The question behind the record
A current customer record can tell you where things stand. I also want to understand why. A moved date or a changed value is part of a larger story: a conversation, a new constraint, a decision, and the work someone agreed to do next. That context makes a record useful to the next person who opens it.
My experience with CRMs is the starting point for Chrono’s everyday workflow. The product needs to make it straightforward to look after customers, prepare campaigns and keep work moving. Temporal depth should help those jobs. It should be something a person can use during a normal working day, without becoming a separate research project.
An obsession with time and inflection points
I’m fascinated by inflection points: the moments when a relationship, campaign or business starts moving in a different direction. I want to understand the conditions around those moments. What led up to them? Which signals were available? What became clear only later? Those questions have shaped how I think about building Chrono.
There is a difference between seeing the result and understanding the sequence. A useful historical view should help us examine the information available at the time. It should also give us room to say that something remains uncertain. Mapping an interesting change is a starting point for investigation, rather than an automatic explanation of what caused it.
Bringing my AI experience into the workflow
My experience with AI brought another part of the idea together. I want to work with the business context through a conversation, ask better questions, and prepare practical next steps. The quality of that experience depends on the context underneath it: the sources, the history, and a clear distinction between a recorded fact and an interpretation.
That is why the Chrono Engine sits alongside the web workspace as an optional desktop companion. The direction is supported AI connections that help people work with the product, while keeping consequential steps understandable and reviewable. The interface should make the person more capable of deciding, with the relevant context close at hand.
One connected ecosystem, built in the open
Chrono brings CRM, marketing, sales, content, service and operations into a shared story. I want someone to follow a customer conversation into the campaign, opportunity or task it affects. I also want teams to choose the parts that fit their work. The free CRM foundation includes scenario planning; specialized packages are planned as optional additions.
The product is in private beta. The website shows actual product captures alongside conceptual artwork, and the State of the Build page describes what exists and what still needs work. I’m building the CRM I always wanted to use: grounded in daily business, curious about time, and able to put AI alongside human judgment. I’ll keep sharing the work as that idea becomes a more complete product.
