bring us one decision.
see it as a first model.
Name a decision your team makes every week. Pascal from kint replies with questions or a time for a call. In that call, kint's forward deployed engineers (FDEs), who build models directly with customers, show you the decision as a model planners can read.
- You bring
- one recurring decision
- You talk to
- Pascal, then kint's FDEs
- You see
- a first model planners can read
three steps to a first model.
You talk to kint's FDEs and founders. If kint is not the right tool for your decision, we say so.
- 01
we read and answer
You describe the decision. Pascal replies with questions or a time for a call.
- 02
a conversation
A call with your planners. We go through goal, rules and data, and show kint's decision agent writing the rules down.
- 03
a first model
On your data or on synthetic data shaped like it: a first model, a first plan, and a scope for a pilot if it fits.
you talk to Pascal.
Pascal is one of the founders and brings the FDEs who fit the decision into the call.
what helps us help you.
None of it is required. Each item brings the first model closer to how the operation really runs.
a planner
The person who makes the decision today. They know the rules nobody wrote down.
an export
A spreadsheet or system export of one planning period. If you cannot share data yet, a column list is enough: we generate synthetic data from it.
today's plan
How the last plan looked. It becomes the baseline kint is compared against.
what you will see.
The conversation starts from your decision. We show the parts below where they fit, plus the topics you ticked in the form.
- the agent flowA planner describes a rule. The agent writes it down as a rule card for review, builds the model and picks the solver. How it works
- a solved planWhitebox optimization on your kind of problem, with the binding limit, bound and gap. Whitebox
- a learned modelWhere no formula exists, kint learns the system from past data and optimizes against it. Blackbox
- scenariosWhat happens if demand rises or a machine fails, compared with today's plan. Simulation
- the recordData version, model version, release, and a re-check of the run against the record. Security
- oem integrationFor vendors: the same run as an API call inside your product, the response format and a white-label screen. OEM
not ready to name a decision yet?
See how kint works first, or write to us with any question.
- Write to us
- contact form
- hello@kint.pro