Four ways to start, one person who answers.
Kelynto has no sales team. Every message and every booking goes to the founder, Marc Estinville. Choose the path that matches where you are. Each one says what you can do today and what happens next.
The enterprise path.
Most teams move through these in order. None of them requires the one before it.
-
1. Exploreno conversation needed
See what it does before you talk to anyone
The product tour walks through nine real screens of the product on a synthetic retailer. How it works follows one week from the closed file to the published review, and the Answers page holds every verified answer the assistant on this site can give.
A one-click sample workspace is built. It is not open to visitors yet, because the product is not hosted yet.
The sample workspace is open: a private copy of a synthetic retailer that is deleted after 24 hours.
Start here Take the product tour
-
2. Evaluatewith your data
Run it on your own weeks
A pilot starts with a backtest: your past weeks are run and each draft is set beside the commentary your team actually wrote. Then about six live Monday reviews, measured on four numbers agreed before it starts. Two files are enough to begin, and both are weekly totals.
Pricing is not finalised. It will depend on deployment model, number of locations and pilot scope.
Start here See what a pilot involves
-
3. Deployin your environment
Have your architects and reviewers check it
Kelynto can run inside your own cloud account or as a managed service. The deployment page says what runs where and what crosses the boundary, and the Trust center labels every control with its real status. A written review pack is sent on request.
Neither model is running on live infrastructure yet. A first install is done alongside your IT team and treated as the validation run.
Start here Read the deployment notes
-
4. Talk to us20 minutes
A working conversation, not a pitch
How your Monday review gets written today, who writes it, what you plan in, and whether a pilot would answer a real question for you. If it is not a fit, we will say so in the conversation.
Start here Book a 20-minute conversation
What to put in a first message.
Four facts make the first reply useful instead of a round of questions.
- Your role, and who writes the weekly review today.
- Roughly how many locations you have.
- What your plan is built in: a planning suite, a warehouse or a spreadsheet, and whether it goes down to store and category.
- What prompted the question.
For a security or procurement review, say who the reviewer is and which deployment model you are considering, so the right documents are sent.
Please leave out
- Sales figures, plans or any other confidential data. A first conversation does not need them.
- Personal data about shoppers or employees. Kelynto does not use it at any stage.
What happens after you write.
No form, no sequence of automated emails, no hand-off between teams.
-
The founder replies himself
Your message is read and answered by Marc Estinville. There is no support desk and no response-time commitment to quote, because one person answers.
-
A 20-minute conversation
About your process and your questions. It helps to bring your number of stores, what your plan comes from, and whether you plan at store and category level.
-
A clear next step, or none
If it looks like a fit: a short pilot agreement, the data and identity checklist, and a backtest on your past weeks. If it does not, you will be told that plainly.
- Security and procurement. The review pack is sent on request, and your own questionnaire is answered in writing, with "not yet" where that is the answer.
- What we do with your email. We use it to reply and to continue the conversation with you. We do not sell it or pass it to anyone for marketing. The privacy notice has the detail.
- Booking. The booking link opens Calendly, a separate scheduling service with its own privacy notice.
- Vendor size. Kelynto is early and founder-led. If vendor size is a hard criterion in your procurement process, ask before you invest time in a review.
Direct lines.
Every address below reaches the founder.
- The product, a pilot or a deployment marc@kelynto.com
- A conversation Book 20 minutes
- A security report about this site or the product security@kelynto.com. The address is also published in security.txt.
- The security review pack, or a questionnaire marc@kelynto.com, with the subject "Security review pack"
- A privacy request marc@kelynto.com, with the subject "Privacy request"
Not available today: a phone line, live chat with a person, or a support desk. The question box on this site answers from verified, published answers and tells you when it has none.